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.
TYPE: This parameter specifies the type of process being defined (IMPORT, EXPORT, DELETE, MERGE, or SHELL). A shell process uses the INCLUDE statement to invoke a sequence of processes in a single run.
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.
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:
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.
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):
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.