Siebel Enterprise Integration Manager Administration Guide > Importing Data > Preparing the EIM Tables for Import Processing >

Required Initial Values for Special Columns

Each row to be imported must contain the data you want to import 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 value to an identifying number for all rows to be processed as a batch.

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

Change the IF_ROW_BATCH_NUM value in the EIM Interface Table for those rows on which the EIM task (import, update, delete) needs to be executed. This value must correspond to the BATCH value or values provided in the IFB-File.

To identify rows that are not imported, use the following SQL statement:

SELECT * from <EIM Interface Table>

where IF_ROW_BATCH_NUM = <BATCH NUMBER USED IN PRECEDING EIM TASK> AND IF_ROW_STAT <> 'IMPORTED'

NOTE:  If a row in the EIM table is successfully imported into the base table, the row's IF_ROW_STAT will be set to 'IMPORTED'. By using " <> 'IMPORTED', you are only selecting rows that failed the import)

Once you determine which rows have failed, change the batch number for those rows in the EIM table to another batch. For example, if the first run uses batch number 100, and 10 rows failed, run a SQL to update the 10 failed rows to a new batch number, such as, Batch 101. After the batch number is changed for the failed 10 rows, run EIM the Import operation again, set BATCH = 101 in the ifb file. When you rerun the EIM Import, the operation will pick up the 10 rows under batch 101.

For more information on the BATCH IFB Parameter see Table 6 Process Section Parameters Generic to All EIM Processes.

For more information on special columns, see EIM Table Columns.