Share

Siebel EIM – An Overview

Enterprise Integration Manager  Siebel Enterprise Integration Manager (EIM) is a server component that transfers data between the Siebel database and other corporate data sources. This data transfer is obtained through intermediary tables called EIM Tables. EIM tables act as a staging area between the Siebel application database and other data sources. EIM should be used to perform bulk imports, updates, merges, and deletes of data.

Below figure depicts how the data can be transferred from some other Database to Siebel Database using EIM  

EIM

 

The ETL in the above figure specifies: Extract, transform, Load. There are various tools available for ETL for eg.Datastage. The data exchanges between the Siebel database and external databases occur in two parts:

  1. Load data into EIM tables.
  2. Run Siebel EIM to import the data from the EIM tables into the Siebel base tables.

The step 1 involves only the use of EIM tables as to load the data into them while in step 2 the actual functionality of EIM comes into picture.  Process Flow for the load of data between Non Siebel/Siebel Database to Siebel Database.

 EIM PROCESS  

The above flow chart depicts the complete process flow of how EIM works when the data is required in Siebel database is lying in some other DB and needs to be transferred to the Siebel DB.  Major Functions of EIM

1. import

2. export

3. delete

4. merge

 

Import Function

1. While initially implementing a Siebel application, load the Siebel database tables with data which can be either legacy data or Siebel data which is required to be moved as a part of Data Migration during a Siebel Upgrade Process. For example Import of Contacts and related Account information from an existing DB to the Siebel database

2. Adding the attributes to the existing data available in Siebel. For example when a few new LOV’s have been created in the application and they are to be used/applied for certain existing Accounts or Contacts.

3. If maintaining a non-Siebel database, we can update it with information from the Siebel database. For example adding the new contacts from Siebel DB to an Accounting DB.

 Export Function Data contained within a Siebel application is available for transfer to non-Siebel/Siebel application (during upgrade process) by using EIM. When implementing a non-Siebel application, we can export data from the Siebel database tables for use by that application. For example, you can export employee information to a corporate sales commission application.

 Delete Function  For the purpose of maintaining the Siebel database, we can identify rows to be deleted from a table and its associated child and intersection tables. For example we might delete an obsolete product line and its associated products.

 Merge Function  In response to such external events as territory merger, account merge we can merge two or more database rows into a single row. For example you might merge the IFFCO. account information into the TOKIO. Account. A merge process deletes one or more existing rows from the base table and makes sure that intersecting table rows are adjusted to refer to the remaining rows. Data from the record we select as the surviving record is preserved. Data from the other records is lost. If there are other records associated with the records you merge, those records—with the exception of duplicates—are associated with the surviving record.  Duplicate child records of the deleted rows will have CONFLICT_ID updated during the merge process. For example, when merging two Accounts (parent), the user keys of the Contacts (child) will be compared, and if the same Contact belongs to both Accounts, the Contact of the deleted Account will have its CONFLICT_ID updated.

1 comment on “Siebel EIM – An Overview”

  1. Amit Reply

    Hi,
    I'm a regular visitor and reader of this site.
    1) Currently I'm working on public sector application and we have scanario where we have to delete orphan records from s_evt_ful_req i.e. correspondence records, these orphan corresponcence records are belongs to s_CASE. measn we do have data in CASE_ID column at s_evt_ful_req table but its related data is not related data is not available on S_CASE table.
    2) We also have to delete its chlid records however we dont want to delete any of the correspondence –> receipients records as they are the suspect(Contact records), we only have to nullify its related foregin key values.
    could you please help me on this issue and provide IFB file?
    Many Thanks
    Amit Joshi

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!