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 relevant account in S_ORG_EXT.PR_POSTN_ID.
In a typical data migration application using EIM, the IFB file contains a large number of sub-processes, which are called from the main process (SHELL). Often while running the EIM process, there are situations, when we would like to run only a sub set of these processes. Such situations normally arise in testing environments, when we prefer running only those processes for which testing needs to be performed.
The settings for the TRACE FLAGS, SQL TRACE FLAGS and ERROR FLAGS can be specified either from the GUI or from the Command Prompt when starting an EIM task.
If the EIM process is being run from the GUI, then the flags can be set in the COMPONENT REQUEST PARAMETERS list in the COMPONENT REQUESTS View of the Enterprise Operations Screen.
When migrating data using the EIM, the process can fail due to several reasons. In certain cases, it is found that the EIM process was successful for migration into some of the Base tables, but failed for some other base tables. In other cases, records get imported into the base tables, but some of the columns fail migration. This section discusses the various causes of EIM failure, how they can be tracked and finally resolved.
The unique identifier associated with every record in Siebel Enterprise databases is known as a Row ID. The column in which this value is found is ROW_ID and it is present on every table. The ROW_ID is unique for an entity. For example, the ROW_IDs for the same person in S_PARTY, S_CONTACT, and S_CONTACT_X are the same because they each refer to the same person.
It is mandatory to load the required columns of the base tables. If one or more required fields are missed, then the EIM process will fail to load the base table and generate the REQUIRED_COLS error status. To identify which are the required columns for a base table, the following query can be used:
Using EIM task user cannot normally update User key attributes of the base table. However, there are some special interface tables EIM_ORG_EXT_UK and EIM_PROD_INT_UK that can be used to update user key columns for some key tables S_ORG_EXT and S_PROD_INT.
Updating user key columns using EIM task with these special tables will not update denormalized columns. For example, updating S_ORG_EXT.LOC will not update S_ACCNT_POSTN.ACCT_LOC AND S_ORG_BU.ORG_LOC.
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.
When migrating data to or from Siebel Base tables, one of the main tasks is to identify the Interface table that would be used in the EIM process. There are cases in which a base table can be loaded from more than one EIM Interface tables. In such cases, the choice of interface table could optimize the EIM performance significantly. ROW_ID and IF_ROW_BATCH_NUM are mandatory columns for EIM processing.
The order in which legacy data is imported is critical to make sure that relationships between dependent data elements are established correctly. Siebel interface tables do not map one-to-one with Siebel target database tables. To make sure that the necessary data is present to establish relationships between data entities, import data in the following recommended order: