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.
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.
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.
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 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.
Integration Manager (EIM) reports the following low-severity error when the foreign key value in the base table does not match with value in the interface table (Note: The following example is based on Siebel version 7.0.4 data model):
The S_PARTY table is the parent of many Person or Organization related objects in Siebel. For example, S_CONTACT, S_ORG_EXT, S_POSTN, S_EMP_PER are all child objects of S_PARTY.
Yes, EIM supports various case values defined for base table columns in Siebel Tools. EIM will adjust the case value of an interface table column according to the Force Case property of the corresponding base table column.
Enterprise Integration Manager (EIM) interacts with data objects (tables and columns) via SQL statements. How those queries are executed by the database in use is directly related to the EIM performance.
In Siebel application, follow the steps below to generate an Enterprise Integration Manager (EIM) detailed log file:1. From User Interface, navigate to View > Site Map > Server Administration > Components
1. Before using the utility, the user needs to create the view S_EIM_MAP_V in the database. The database platform independent script for creating the view is create_EIM_MAP_V.sql and can be found in <dbsrvr>\common directory.
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).