Through EIM process we load bulk amount of data from an external system to Siebel base tables. The performance of these EIM jobs has to be maintained at optimum levels in order to reduce the load on the Siebel application and database servers.
Some base tables like Note tables do not have user keys. Since user keys play a vital role in migration of data using EIM, the EIM behavior is significantly different in case of Base Tables without user keys.
Prior to running EIM it is important to clean up fragmented objects, especially those that will be used during the EIM processing. The following SQL statement can be used to identify objects with greater than 10 extents:
The account data need to be imported into S_PARTY, S_ORG_EXT, S_ACCNT_POSTN, and S_ORG_BU among other relevant tables. S_ORG_BU is a new table in Siebel 7 and must be populated for visibility in the "All Accounts" view.
Normally, User key updationare not possible through EIM except for few entities, of which Product is one. Here is a useful information to update one of the user key columns for Product (Product NAME for instance) through EIM.