Siebel Enterprise Integration Manager Administration Guide > EIM: Examples of Common Usage > Other Examples >

Foreign Key Column Values: NO MATCH ROW ID versus NULL versus a Valid ROW_ID


There are three possible values that EIM can define for primary columns (foreign key columns) when it processes a batch:

  • NO MATCH ROW ID
  • NULL
  • A valid ROW_ID

NO MATCH ROW ID. EIM sets the foreign key columns to NO MATCH ROW ID if the primary value cannot be found when EIM processes Step 10. EIM does this because the primary key is missing in the linked table.

NOTE:  The following are special considerations regarding NO MATCH ROW ID:

S_CONTACT. The export function will update the BU_ID on the S_CONTACT table to NO MATCH ROW ID when there is no record existing in the S_CONTACT_BU table for a given contact. To avoid this, every contact should have a corresponding record in the S_CONTACT_BU table.

S_PRI_LST_BU. The S_PRI_LST_BU table must be loaded to avoid having the UI set S_PRI_LST.BU_ID to NO MATCH ROW ID.

NULL. If the foreign key columns allow a NULL value in the parent table, EIM carries the NULL value.

A valid ROW_ID. If a valid ROW_ID is not defined, EIM uses the value in the primary column to determine the ROW_ID.

Siebel Enterprise Integration Manager Administration Guide