Beruflich Dokumente
Kultur Dokumente
1 of 3
http://siebelnotes.blogspot.in/2008/01/siebel-data-migration-and-eim-tabl...
18/11/2015 2:10 AM
2 of 3
http://siebelnotes.blogspot.in/2008/01/siebel-data-migration-and-eim-tabl...
IF_ROW_STAT
EIM updates this column after processing the row to indicate the status of the record. The IF_ROW_STAT column is
not used by EIM when determining which rows to process. When populating the EIM tables, you can set this column
to any value except NULL. You can initially set this value to FOR_IMPORT to indicate that the row has not been
imported.
2. User Key Columns
These are the columns which are mapped with the user key column into the base tables.
3. Default Value Columns
These columns are the ones which are required for the visibility on UI. These columns are assigned with some hard
coded values as identified by the EIM person required for further processing. The values are generally like Y, N,
Siebel Administrator, Default Organization etc
4. Data Columns
These are the columns which hold the data coming from the source systems.
5. Extended Columns
EIM tables can be extended for your specific need. If there is a need to store some source data which do not have
any place holder, the EIM table can be extended with new columns and those columns are known as extended
columns.
Lookup on Siebel Base Tables
As mentioned earlier, Siebel doesnt recommend accessing the base tables directly. So if there is a need of doing a
lookup against any base table, what to be done? To resolve this issue, data can be retrieved in to the XML format.
Siebel gives the facility to export data into the XML format. ETL tool can read these XML files and create the
required lookup files. These look up files can be used for the lookup purpose.
EIM Process
This is the second part of the data migration. After data is loaded into the EIM table using ETL tools, EIM process is
used to load the data into base tables. These processes read the data from the EIM tables and load it in to the
appropriate base tables. Generally not much transformation is done into EIM process. EIM process can be run
either navigating through Administration - Server Management > Jobs in the GUI or from the command line
interface. EIM Configuration file (.IFB) is used to define the EIM process.
Data Load Strategy in EIM Tables
As mentioned earlier EIM tables are like the staging tables. Generally the data load strategy used for the staging
area is truncate and load. A similar approach with a little different strategy is taken for EIM tables.
Data is always inserted into the EIM tables. To avoid the unique key constraint with the existing (previous load) data
the existing IF_ROW_BATCH_NUM is updated with the SYSDATE+IF_ROW_BATCH_NUM (concatenation). This
way the previous data is retained and new data is also inserted. This approach is taken to enable the possibility of
any finding/debugging on the previous data. This data can be retained for few days.
Posted 13th January 2008 by J N
Labels: Siebel Data Migration and EIM Tables
1
View comments
18/11/2015 2:10 AM
3 of 3
http://siebelnotes.blogspot.in/2008/01/siebel-data-migration-and-eim-tabl...
Our address:
2002 Timberloch Place, Suite 200
The Woodlands, TX 77380
281-364-1799
prologic-corp
Reply
Comment as:
Publish
18/11/2015 2:10 AM