Siebel EIM

This happens when the Enterprise Integration Manager (EIM) component's Component Event Configuration - SQL Tracing Event Type log level value is not set to 4.

In standard Siebel applications, ‘CREATED’ and ‘CREATED_BY’ are system columns that will be automatically populated when importing data via EIM.

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.

You should try the following options to improve EIM performance:

Verify that all indices exist for the tables involved.

PARTY_TYPE_CD, PARTY_UID, ROOT_PARTY_FLG are the required columns in S_PARTY table which have to populated while doing an import of party records(like contact, position, etc.) using Enterprise Integration Manager (EIM).

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.

Primary associations can be set using the Primary Flag; for example, in EIM_ACCOUNT there is an ACC_PR_POSTN column that is defaulted to “N”, but when set to “Y”, EIM will attempt to update the Primary Position in the relev

S_REVN table was introduced in Siebel version 7.0 which is used to store Revenue data. For example Revenue by an employee on an Opportunity, an Agreement, a Service Request, etc.

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.

EIM will not interfere with Siebel VB code because Siebel VB works at the business component and business object level, and EIM works at the table level.


Subscribe to Siebel EIM