We have collected the Siebel real time interview questions related to EIM ( enterprise integration manager) , these are asked in real interviews in most of the companies. All the best for your job interview! 1. After successfully importing quote information, my users are unable to edit their quotes. Why? Ans: You probably initialized the APPROVED_FLG field to Y for each quote. A Y makes the quote read-only and not editable by the user. Instead, set this field to N or leave it blank. 2. How can we import contacts so that they are visible in the Contact list? Ans: You need to import contacts using the EIM_CONTACT2 interface table, since it maps to the S_POSTN_CON intersection table. Populate the EIM_CONTACT2 interface table with the user key values for each contact and the S_POSTN_CON intersection table. When specifying values for EIM_CONTACT2.RESP_POSTN_DEPT and EIM_CONTACT2.RESP.POSTN_NAME columns, make sure that the divisions and positions are valid, and that there is at least one employee associated with each position. 3.How can data be imported into List of Values (LOV) tables? Ans: When importing data from interface tables, you may encounter the following error message in your trace file: [ERR00] Interface table: [ERR00] S_XXXX_XMIF (Interface for XXXX Built-In M:1 Extension Table) [ERR00] -------------- [ERR00] [ERR00] Base table: [ERR00] S_XXXX_XM (Account M:1 Extension) [ERR00] ------------ [ERR00] TYPE (Type) [ERR00] This column contains a bounded picklist value and the value given does not [ERR00] correspond to a value in the list-of-values table for the given picklist type. This error message indicates that either a picklist has not been created for this column (TYPE) or the value in your interface table for this column (TYPE) does not correspond to one of the values in the picklist for this column. To resolve this issue, you need to make sure that: ■ A picklist already exists for this column ■ The value you are importing for this column corresponds to one of the values in the picklist The following procedure explains how to import data into a LOV table using the S_ORG_EXT_XM table as an example. To import data into a LOV table 1 Using Siebel Tools, find the LOV type for the S_ORG_EXT_XM table. a. In Siebel Tools, select Types. b. Click Table. c. Select S_ORG_EXT_XM. d. With the S_ORG_EXT_XM table highlighted, expand Column tree control, and find the Type column. e. With the Type column highlighted, find the following two attributes in the Properties window: ❏ Lov Bounded: TRUE ❏ Lov Type: ORG_EXT_XM_TYPE The TYPE column should contain the value as the VAL column in the S_LST_OF_VAL table. NOTE: Although the TYPE column in the S_LST_OF_VAL and S_ORG_EXT_XM tables have the same name, they are not the same column and do not need to be populated with the same values. 2 Using the Siebel client, find S_ORG_EXT_XM_TYPE. a. Navigate to the List of Values screen. b. Query the Display Value column for ORG_EXT_XM_TYPE to make sure that the picklist already exists. 3. Using the Siebel client or EIM, add values for this bounded picklist. NOTE: If you are using the Siebel client to import data, the Siebel client will check the PickList property for each field in a certain business component. If you are using EIM to import data into base columns, EIM will check the LOV Type property defined for each column in a base table. It is possible that you could insert data into a particular column using the Siebel client, but not using EIM, since they are looking at different properties. If you are using the Siebel client: a. In the List of Values view, create a new record. b. In the Type column, type ORG_EXT_XM_TYPE. c. In the Display value column, insert any value you want to use for this type. d. Repeat Step c until you have created records for all values you want to have in this picklist. If you are using EIM: e. Populate the EIM_LST_OF_VAL table, set the TYPE column to ORG_EXT_XM_TYPE, and set the VAL column to any value you want to use for this type. Make sure to populate all the required fields in the EIM_LST_OF_VAL table. f. Repeat Step e until you have inserted all records into the IF table for all values you want to have in this picklist. g. Import data from EIM_LST_OF_VAL to S_LST_OF_VAL using EIM. For information on importing data, see Chapter 4, “Importing Data.” The VAL column in the S_LST_OF_VAL table should contain the same value as the TYPE column in the S_ORG_EXT_XM table. NOTE: Although the TYPE column in the S_LST_OF_VAL and S_ORG_EXT_XM tables have the same name, they are not the same column and do not need to be populated with the same values. 4. When importing many accounts and positions using EIM, how do I make sure that the correct position is selected as the primary position for each account? Ans: To make sure that accounts imported using EIM are associated with the correct primary position, import each account with its primary position first as a separate batch. ■ In the first batch, import the account using EIM_ACCOUNT and populate ACCNT_TEAM_POSTN (position) and ACCNT_TEAM_DEPT (division) in addition to ACCNT_NAME and ACCNT_LOC. This batch will make sure that a position has been inserted as the primary position for that account (S_ORG_EXT.PR_POSTN_ID is populated correctly). ■ In the second batch, import the rest of the positions to be associated with the account to make up the sales team. This batch will insert additional rows in S_ACCNT_POSTN but will not update the primary position column S_ORG_EXT.PR_POSTN_ID. For the position in the first batch to be inserted as the primary position, there should not be any positions associated with the account. EIM will not update PR.POSTN_ID once the row has been populated with a ROW_ID. NOTE: You can use this method to set the primary position for other entities. 6. How can I import multiline fields such as addresses? Ans: When importing multiline fields such as addresses, you should use CHR(13) and CHR(10) for the field to be displayed as a multiline field. Otherwise, the following warning may be displayed in the GUI: You have tried to modify a group of fields that may have more than one value. To edit or add field values in this group, please open the first field in the group by clicking on the multivalue field control. 7.How do I import exported rows into target and secondary tables? Ans: If user keys from the secondary tables are made up of foreign keys referencing the target table and additional user keys of nonrequired columns, note that: ■ If you export rows from both target and secondary base tables, one interface table row will be created for every target table row, and a separate interface table row will be created for every related secondary table row. ■ If you reimport the exported batch rows into both the target and secondary base tables, the exported target table rows will be imported into the secondary table as well, since the exported target table rows have NULL values in the secondary table interface columns, and the secondary table's additional user keys allow NULL values to be imported. Additional rows will thus be mistakenly imported into the secondary base table. To avoid this problem, after exporting the target and secondary base tables rows, you should split the secondary table rows out from the exported batch into another batch, and then import the target and secondary table rows separately.