Siebel Enterprise Integration Manager Administration Guide > Merging Data >

Preparing the EIM Tables for Merge Processing


This section provides assistance in loading the EIM tables with data used to control the process of merging rows in Siebel applications base tables. Your database administrator can use the loading tool provided by your database.

You must make sure that each EIM table row to be processed contains the appropriate values in the following columns. Table 16 shows a merge example for special columns.

Table 16. EIM Merge Example for Special Columns
IF_ROW_BATCH_NUM
NAME
ROW_ID
IF_ROW_MERGE_ID

1

IBM

100

NULL

1

IBM Japan

101

100

1

IBM Europe

102

100

IF_ROW_BATCH_NUM. Set this to an identifying number for all EIM table rows to be processed as a batch.

ROW_ID. This value in combination with the nonempty contents of if_row_batch_num must yield a unique value.

IF_ROW_MERGE_ID. Set this value to one of two values. For an EIM table row whose row_id and if_row_batch_num columns identify the surviving or merged-into row, set this value to null. For EIM table rows whose row_id and if_row_batch_num columns identify a row to be merged (and subsequently deleted), set this value to the row_id where this row will be merged. Upon completion of the merge process, the first row survives and the remaining rows are deleted. All child and intersection table rows that previously pointed to row_ids 101 and 102 now point to 100.

IF_ROW_STAT. In each row to be merged, set this column to FOR_MERGE to indicate that the row has not been merged. After processing, if certain rows were not merged due to a data error, you should change:

  • IF_ROW_BATCH_NUM value for the rows that require remerging.
  • BATCH NUMBER line in the configuration file.

NOTE:  In addition to populating these columns, user key information for each row to be merged must be loaded into the EIM table.

If you do not correctly populate all the user key columns, the merge process will fail and the IF_ROW_STAT column in the EIM table will be set to the value NO_SUCH_RECORD. This indicates that EIM cannot find the appropriate rows to merge using the specified user keys.

For more information on special columns, see EIM Table Columns. For general information on EIM tables, see Siebel EIM Tables.

Siebel Enterprise Integration Manager Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.