Siebel Enterprise Integration Manager Administration Guide > Siebel EIM Tables > EIM Table and Column Mappings >

EIM Table Mappings Provided as Common Parents to Nontarget EIM Table Mappings

Some EIM table mappings (usually to the target base table) are provided only as a common parent to nontarget EIM table mappings. An example of this type of EIM table mapping is mapping from the EIM_OPTY_DTL interface table to the S_OPTY base table. These EIM table mappings have a comment in the Siebel repository, indicating that they do not support inserting or updating data.

In such EIM table mappings, only the user key columns are mapped. Except for updating the primary foreign key columns, EIM does not support inserting and updating rows using these EIM table mappings.

Parameters to Set

For stability of EIM when using these EIM tables, follow the template in the default.ifb file by including the following parameters for the relevant section in the EIM configuration file:

CAUTION:  If you do not include these parameters, the EIM process may fail or some exceptions may occur.

Exception to Recommended Parameter Settings

One exception to the recommendation provided above is when you want to update the primary foreign key columns in the parent table, in which case you do not want to include the following parameter in the EIM configuration file:

UPDATE ROWS = parent_table, FALSE

For example, EIM_ACCOUNT1 maps to the user key columns of S_ORG_EXT only. You can use EIM_ACCOUNT1 to update the primary foreign keys in S_ORG_EXT if the explicit primary mappings exist, such as S_ORG_EXT.PR_INDUST_ID, the explicit primary mapping contained in the table mapping of S_ORG_INDUST. For more information, see About Explicit Primary Mappings.

In this case, you should use the default setting, UPDATE ROWS = S_ORG_EXT, TRUE in the EIM configuration file. If you do not need to update primary foreign keys in S_ORG_EXT, then you should set UPDATE ROWS = S_ORG_EXT, FALSE in the EIM configuration file.

 Siebel Enterprise Integration Manager Administration Guide 
 Published: 05 January 2004