Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Tools Reference > Adding Custom Extensions to the Data Model >
EIM Table Mapping Wizard
The EIM Table Mapping Wizard is accessed by right-clicking on a table entry in the Table list applet. The EIM menu item is only enabled with the non-standalone customer table. You can select an interface table and specify a prefix for the interface table columns that are generated by the wizard and that create a complete hierarchy of EIM Table Mapping objects needed to import and export data to and from the selected table. See Figure 74.
The EIM Table Mapping Wizard does not map foreign key columns if they point to a parent table column that does not have user key attributes. Because you cannot add user key attributes, this means that the EIM Table Mapping Wizard does not work with either standalone tables or foreign keys to custom tables.
In order to invoke the EIM Table Mapping Wizard for those Siebel base tables that do not have the foreign key as part of the user key, you need to create a temporary column with the following properties:
By creating this temporary column, when you launch the EIM Mapping Wizard, it will list standard EIM interface tables that are already mapped to this table as the target or destination tables. The wizard will also list EIM tables that are mapped to tables to which this table has a foreign key. However, the foreign key must be part of the "Traditional U1 Index" user key of this table. After the EIM Mapping Wizard finishes, you should delete this temporary column.
NOTE: The EIM Table Mapping Wizard is only available to tables of type Data (Public). Data (Intersection), Data (Extension), and Data (Extension-Siebel).
The EIM Table Mapping Wizard is only available to tables of type Data (Public), Data (Intersection), Data (Extension), Data (Extension-Siebel).
To map a new table to an EIM interface table using the EIM Table Mapping Wizard
- Lock the project.
- Select Table object type in the Object Explorer.
- Select an entry in the Object List Editor.
Choose from the list a base table that will be mapped to an EIM Table. It will be the primary table into which data from the existing Interface table will be imported.
- Right-click and select EIM Mapping Table from the menu.
The Interface Mapping dialog box is displayed with the Base Table name field populated with the selection you made in the Object List Editor.
- In the Edit the Column name prefix field, enter a distinguishing prefix.
If a prefix does not already exist for the selected EIM table, the new prefix will be added to specified EIM Interface Table Columns related to the target table. If a prefix already exists, the existing prefix will be used.
- In the Select an interface table field, select from the picklist.
The picklist for selecting the EIM Interface Table is constrained to show interface tables that are mapped to tables to which your new custom table has a foreign key relationship.
The list of candidate interface tables is sorted by EIM table name. Interface tables with EXIST=Y means that these EIM tables already have the base table mapped. If you extend existing Siebel tables, consider these tables the ideal candidates for EIM mapping.
- Click Next on the Interface Table Mapping dialog box.
The Summary dialog box appears with a summary of the choices you have made.
- Click Finish on the Summary dialog box to accept the choices you made and generate the EIM Interface Table object.
Based on this information, the wizard creates new EIM table mapping objects and adds several child objects to an existing EIM interface table object:
EIM Object Specifications
The specifications for EIM objects are as follows:
- EIM Interface Table (Table 14)
- EIM Interface Table Columns (Table 15)
- Generic EIM Interface Table Columns for EIM processing
For each EIM Table Interface the following three columns are created to facilitate processing. Customers cannot change their values, which are shown in Table 16.
- EIM Interface Table Columns for processing a mapping to a particular table
There are four of these columns for each EIM Table Mapping object, with the following properties (Table 17):
For example, if the target table selected by the user is CX_SEC_LEV, an EIM Table Mapping object is created. The following four column objects are generated, with the corresponding default properties (Table 18):
- EIM Interface Table Columns for foreign key processing
A column is created for each foreign key on the relevant EIM Table Mapping object (that is, the target table). These columns have the following properties (Table 19):
For example, if CX_SEC_LEV contains foreign key columns called OPTY_ID and ACCNT_ID to the S_OPTY and S_ORG_EXT tables, respectively, the following EIM Table Columns are generated (Table 20):
- EIM Interface Table Columns for foreign keys
A separate foreign key column will be created for each U1 user key column on the foreign key tables. The columns have the following properties (Table 21):
Continuing with the CX_SEC_LEV example (Table 22):
NOTE: Depending on the base column type, corresponding EIM columns are generated accordingly.
- EIM Interface Table Column for each attribute on the target table
Attribute columns on the target table are those of type Data (Public) that have a null Foreign Key Table property. These EIM interface table columns will have the following properties (Table 23):
For example, if you enter a prefix of SECL and have the following attribute columns in CX_SEC_LEV: NAME (Varchar 100), DESC_TEXT (Varchar 250), and AUTO_UPDATE (Char 1), the following EIM interface table columns are generated (Table 24):
- EIM Table Mapping objects based on the target table
The name and destination columns will be set to the name of the target table. The processing column properties will correspond to those that have been automatically generated. For example (Table 25):
- Attribute Mapping objects for each EIM interface column generated
These should have the following property values (Table 26):
Table 26. Attribute Mapping Objects for Each EIM Interface Column Name of corresponding EIM interface table column generated (Table 24)- Foreign Key Mapping for each foreign key column on the Target Table
A separate Foreign Key Mapping object is created for each foreign key mapping column on the target table. The following properties are set for each (Table 27):
Continuing with the CX_SEC_LEV example (Table 28):
- Foreign Key Mapping Columns for each Foreign Key Mapping object
A separate Foreign Key Mapping Column object is created for each user key column in the user key specified for the parent Foreign Key Mapping object (Table 27). The following properties are set for each foreign key mapping column (Table 29):
Table 29. Foreign Key Mapping Columns for Each Foreign Key Mapping Object This EIM interface table column is generated according to the specifications in Table 21. This EIM interface table column is generated according to the specifications in Table 21. Name of the corresponding user key column that belongs to the user key specified in Table 27.Continuing with the CX_SEC_LEV example (Table 30):
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Tools Reference Published: 20 October 2003 |