Configuring Siebel Business Applications > Transferring Data Between Databases > Overview of Transferring Data Between Databases >

Object Types That Enterprise Integration Manager Uses

Figure 81 describes the objects and relationships that EIM uses.

Figure 81. Objects and Relationships That EIM Uses

EIM Interface Table Object Type

An EIM interface table is an object that provides an alternative representation of a table. It includes some of the same properties as a table plus other properties of an interface table.

EIM Interface Table Column Object Type

An EIM interface table column is an object that provides an alternative representation of a column. It contains all the properties of a column in addition to some properties that are specific to EIM.

Figure 82 describes how the child columns of an interface table are the same as the child columns of a table. The EIM_PRI_LST price list interface table is an example.

Figure 82. child Columns of an Interface Table Are the Same as Child Columns of a Table

EIM Table Mapping Object Type

An EIM table mapping is an object that references a data table that the parent EIM interface table object definition updates. One EIM interface table can update one or more data tables.

Figure 83 describes how the Destination Table property of each EIM table mapping object identifies the name of the data table to update.

Figure 83. Example of How an EIM Interface Table References a Data Table

Interface Table User Key Usage Object Type

An interface table user key usage is an object that provides support for alternative user keys for base tables. It defines the use of a nontraditional user key for a base table that are specific to an interface table.

CAUTION:  Do not modify the object definition of an interface table user key usage. Any modification can adversely affect performance and operation.

Attribute Mapping Object Type

An attribute mapping is an object that identifies a column in a data table that EIM updates. This column resides in the destination table that is defined in the parent EIM table mapping. An attribute mapping includes the following properties:

• Interface Table Data Column. Identifies the column in the interface table that supplies the data.
• Base Table Attribute Column. Identifies the column in the destination table that receives the data.

If you add an extension column to a table, and if an interface table must provide data to the extension table, then you must add a corresponding attribute mapping.

Figure 84 includes an example of how an EIM table mapping references a data table.

Figure 84. Example of How an EIM Table Mapping References a Data Table

Foreign Key Mapping Object Type

A foreign key mapping is an object that identifies a foreign key column in the destination table. EIM pulls data from an interface table and enters it into this foreign key column. EIM stores a foreign key as a numeric row ID value in a data table. To use data from an interface table in a foreign key, you must map the interface column to a combination of user key columns in the destination table rather than directly to the foreign key column.

Figure 85 includes an example of how a foreign key map references a data table. To access the row, Siebel CRM uses a combination of attribute columns in the destination table of the foreign key. EIM gets the foreign key value from that row. A foreign key mapping is not a one-to-one column mapping from an interface table to a destination table. The numeric foreign key does not exist in the interface table, so you cannot map it.

Figure 85. Example of How a Foreign Key Map References a Data Table

Foreign Key Mapping Column Object Type

A foreign key mapping column is an object that does the following:

• To locate rows in the table that the foreign key references, identifies one of the attribute columns EIM uses. EIM combines values from the user key columns to form a key that uniquely identifies rows in that table.
• Identifies the user key columns so EIM can get foreign key values during an import or export.

User Key Object Type

A user key is an object that provides a set of attribute columns and related information that specifies how EIM can access the table rows. For more information, see How a User Key Creates a Unique Set of Values.

User Key Column Object Type

A user key column is an object can be an attribute or a foreign key. In most situations user key columns constitute the columns in the user key index with the exception of the CONFLICT_ID column. A user key index typically includes a _U1 suffix.

User Key Attribute Object Type

A user key attribute is an object that the parent user key specifies in the set of attribute columns that collectively identifies rows in the grandparent table. The column name is defined in the Name property of the user key attribute.

User Key Attribute Join Object Type

A user key attribute join is an object that specifies a join operation that EIM can use to convert a user key attribute that is a foreign key to another table into attribute column values in that table.

For example, the S_PROD_INT products table includes the S_PROD_INT_U1 user key. This user key references the following columns:

• PROD_NAME
• PROD_VENDOR
• PROD_VEN_LOC

EIM gets the PROD_NAME column from the S_PROD_INT table. No join is required.

EIM must use a join to get the PROD_VENDOR and PROD_VEN_LOC columns from the S_ORG_EXT accounts table. EIM uses a join on VENDR_OU_ID, which is a foreign key from the S_PROD_INT table to the S_ORG_EXT table.