Siebel Enterprise Integration Manager Administration Guide > Deleting Data >

Preparing the EIM Tables for Delete Processing

This section provides assistance in loading the EIM tables with data used to control deletion of rows from Siebel base tables.

You must make sure that each EIM table row to be processed contains both data that correctly identifies the exact base table rows to delete and the appropriate values in the following columns.

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

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

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

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

It is not possible to delete rows that have the same primary user key and different conflict IDs using EIM, because EIM relies on user keys to identify rows in base tables. If there are two rows in the base table that have the same user key but different conflict IDs, EIM cannot distinguish these rows. In such case, the IF_ROW_STAT field of the row in the EIM table will be marked as AMBIGUOUS.

NOTE:  When you are deleting records based on user keys, specify the parameter DELETE EXACT in the .IFB file.

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.