|Bookshelf Home | Contents | Index | PDF|
Figure 81 illustrates the objects and relationships that EIM uses.
An EIM interface table is an object type that provides an alternative representation of the table object type. It includes some of the same properties as the table object type plus other properties that are specific to an interface table.
An EIM interface table column is an object type that provides an alternative representation of the column object type. It contains all the properties of the column object type in addition to some properties that are specific to EIM.
Figure 82 illustrates how the child columns of a given interface table are the same as the child columns of a table. The EIM_PRI_LST price list interface table is an example.
Figure 83 illustrates how the Destination Table property of each EIM table mapping object identifies the name of the data table to update.
An interface table user key usage is an object type that provides support for alternative user keys for base tables. It defines the use of a nontraditional user key for a given base table in a specific interface table.
An attribute mapping is an object type 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:
Figure 84 illustrates an example of how an EIM table mapping references a data table.
A foreign key mapping is an object type 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 illustrates an example of how a foreign key map references a data table. To access the desired row, Siebel CRM uses a combination of attribute columns in the destination table of the foreign key. EIM obtains 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. Because the numeric foreign key does not exist in the interface table, you cannot map it.
A user key is an object type that provides a set of attribute columns and related information that specifies how EIM can access the table rows for a specific EIM usage. For more information, see How a User Key Creates a Unique Set of Values.
A user key column is an object type 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.
A user key attribute is an object type 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.
A user key attribute join is an object type 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.
EIM must use a join to obtain 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.
|Configuring Siebel Business Applications||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|