Siebel Enterprise Integration Manager Administration Guide > Importing Data > Special Considerations for Imports >

Importing Exported Rows Into Target and Secondary Tables

If user keys from the secondary tables are made up of foreign keys referencing the target table and additional user keys of nonrequired columns, note that:

• If you export rows from both target and secondary base tables, one EIM table row will be created for every target table row, and a separate EIM table row will be created for every related secondary table row.
• If you reimport the exported batch rows into both the target and secondary base tables, the exported target table rows will be imported into the secondary table as well. This is because the exported target table rows have NULL values in the secondary table interface columns, and the secondary table's additional user keys allow NULL values to be imported. Additional rows will thus be mistakenly imported into the secondary base table.

To avoid this problem, after exporting the target and secondary base tables rows, you should split the secondary table rows out from the exported batch into another batch, and then import the target and secondary table rows separately.