You can load data from a corporate source into a Siebel EIM table, and then invoke an EIM task that merges the data in the Siebel base tables. When you load data of rows marked for the merged operation, you must link the IF_ROW_MERGE_ID port in the source to the IF_ROW_MERGE_ID port of the Siebel EIM Load transformation. You must configure the IFB file for the merge operation and use this file to invoke the EIM task. The merge operation merges data from the Siebel EIM table into existing rows in a Siebel base table. The merged data from the Siebel EIM table replaces existing values in the Siebel base table.

For example, you create a mapping that extracts company data from an Account database, loads the company data into a Siebel EIM table, and then merges the company data into a Siebel base table.

The following table describes the parameters required to configure the IFB file for the EIM task:

You configure the EIM task to merge rows in batch 300.

The following table displays the source information:

You run the session.

The following table contains the EIM table information after the PowerCenter Integration Service loads the source data into the EIM table:

Next the PowerCenter Integration Service invokes the EIM task. Siebel EIM runs the EIM task based on the IFB file configuration and merges the rows into the Siebel base table. Siebel EIM merges the data of row 1002 into row 1001 and deletes row 1002 from the base table. It does not merge date of row 1003 into row 1001 because the batch number of row 1003 does not match the batch number configured in the IFB file.

The following table shows how Siebel EIM updates the status for these rows in the EIM table:

The status for row 1003 does not change because Siebel EIM does not merge date of row 1003 into row 1001.