Siebel EIM

What is the recommended number of rows that can be loaded in a single batch?

For an initial load, you can use 30,000 rows for a large batch. For ongoing loads, you can use 20,000 rows for a large batch. You should not exceed 100,000 rows in a large batch.
Furthermore, you should limit the number of records in the interface tables to those that are being processed. For example, if you have determined that the optimal batch size for your system is 19,000 rows per patch and you are going to be running

How can I tune my EIM batches to improve performance?

You should try the following options to improve EIM performance:

Verify that all indices exist for the tables involved.

Limit tables and columns to be processed using ONLY BASE TABLES/COLUMNS configuration parameters to minimize EIM processing.

Consider switching off transaction logging during the EIM run. This will definitely improve performance. However, it must be balanced with the need for mobile users to reextract afterward.

How do I use the DELETE EXACT parameter to delete data from base tables other than the target base table?

To use the DELETE EXACT parameter to delete data from base tables other than the target base table, specify the user key columns only for a single base table for each row in the interface table. When specifying rows for exact deletion, make sure any columns not necessary to specify the row to be deleted are NULL to avoid problems with deleting from the wrong base table. EIM tries to enforce this behavior by requiring other user key columns to be NULL.

Real time Siebel EIM (Enterprise Integration Manager) Interview Questions – Part 1

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 do I populate the PR_PROD_LN_ID column in the S_PROD_INT base table

Complete the following procedure:

 To populate the PR_PROD_LN_ID column in the S_PROD_INT base table

Populate the S_PROD_INT base table using the EIM_PROD_INT interface table.

Populate the S_PROD_LN base table using the EIM_PROD_LN interface table, and the S_PROD_LN_PROD base table using the EIM_PROD_INT1. You need to populate the S_PROD_INT base table before the S_PROD_LN and S_PROD_LN_PROD base tables so that the PROD_ID key is resolved appropriately.

We successfully imported most of our interface table rows and want to delete them. However, we want to leave rows that were not fully imported so that we can examine and correct them. How can we do this?

Each interface table imports data into one or more target base tables.

For example, EIM_ACCOUNT imports into S_ORG_EXT, S_ACCNT_POSTN, S_ADDR_ORG, S_ORG_INDUST, S_ORG_PROD, S_ORG_REL, S_ORG_SYN, S_ORG_TYPE, S_TERR, and S_TERR_ITEM.

Each interface table includes a separate temporary column that contains a status code for each base table into which it has imported data. The names of these columns are contractions of the target base table name.