Why is the Primary ID not populated during an EIM task even though the corresponding EIM mapping columns are appropriately populated in the Interface table

When encountering  the Primary ID not populated during an EIM task even though the corresponding EIM mapping columns are appropriately populated in the Interface table issue modify the IFB file to include the PRIMARY KEYS ONLY = TRUE parameter. This will force EIM to update only the primary key values like PR_POSTN_ID, PR_EMP_ID etc.

What values must be populated for PARTY_TYPE_CD, PARTY_UID and ROOT_PARTY_FLG columns in S_PARTY table using EIM

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). The following are the description of these columns and the possible values it can hold:

 

PARTY_TYPE_CD:

PARTY_TYPE_CD is used to indicate what type of party data is being imported. It can have the following values:

How are CREATED and CREATED_BY columns populated using EIM?

In standard Siebel applications, ‘CREATED’ and ‘CREATED_BY’ are system columns that will be automatically populated when importing data via EIM. The starting time of the EIM server task and login information of the employee starting the EIM server task populates these columns. There is no EIM mapping from the Siebel Interface tables to the CREATED and CREATED_BY columns in any of the base tables.

How can users determine if there is an interface mapping to a particular table or column and which interface tables or columns can be used for importing to this base table or base column?

This information pertains to Siebel version 3.x, 4.x, 5.x, 6.x and 7.x.

In order to find this information, please follow the steps outlined below:

1. Launch the Siebel client with /h option and navigate to the view in the Graphical User Interface (GUI) that has the field.

2. Choose Help > About View

3. Note which applet the field belongs to

4. Launch the Siebel Tools client

5. Navigate to the Applet Object in the Object Explorer

Can the PRIV_FLG column of S_CONTACT base table be updated using EIM? (Private_Flag is used to enforce Personal Contacts)

No. The S_CONTACT.PRIV_FLG is not part of the user key to the S_CONTACT table. However, it is included in the criteria used by Enterprise Integration Manager (EIM) to locate an existing row in the S_CONTACT table (It is a required column, but not a part of user key). Currently it is not possible to update the S_CONTACT.PRIV_FLG using EIM. For contacts loaded using EIM, the only supported value for the PRIV_FLG is "N".

How can I tune my EIM batches to improve performance?

Here are some options that can be tried to improve Enterprise Integration Manager (EIM) performance:

Check to make sure all the standard indices are in existence for the tables involved.

Limit tables and columns to be processed using ONLY BASE TABLES/COLUMNS configuration parameters to minimize the work that EIM has to perform.

Recent content