Configuring Siebel Business Applications > Transferring Data Between Databases >

Mapping a Custom Table to an Interface Table

This topic describes how to map a custom table to an interface table. It includes the following topics:

• Guidelines for Using the EIM Table Mapping Wizard
• Starting the EIM Table Mapping Wizard for a Table That Does Not Use the Foreign Key
• Deactivating Instead of Deleting an EIM Attribute Mapping
• Modifying Data from NULL to No Match Row Id

To map custom columns and tables to a predefined EIM interface table, you use the EIM Table Mapping Wizard.

To map a custom table to an interface table

1. Make sure the table you must map is the appropriate type, includes a user key attribute, and that Siebel CRM supports the mapping.

   For more information, see Guidelines for Using the EIM Table Mapping Wizard.

2. In Siebel Tools, display all child object types of the EIM Interface Table object type.

   For more information, see Displaying Object Types You Use to Configure Siebel CRM.

3. in the Object Explorer, click Table.
4. In the Tables list, locate the table that must reference an EIM table.

   This table is the primary table where EIM imports data from the predefined interface table.

5. Right-click the record, and then click EIM Table Mapping.

   Siebel Tools displays the Interface Table Mapping dialog box. It enters data into the Base Table name window of this dialog box. It gets this data from the table you located in Step 4.

6. In the Enter Column Name Prefix window, enter a prefix.

   Siebel Tools does the following:

   • If a prefix does not already exist for the EIM table, then Siebel Tools adds the new prefix that you enter for the EIM interface table columns that reference the table.
   • If a prefix already exists for the EIM table, then Siebel Tools uses the existing prefix.

     If you specify a prefix, then the EIM Table Mapping Wizard adds this prefix to the new columns and makes the column properties uneditable.

7. In the Select the Interface Table window, choose a value from the list, and then click Next.

   Siebel Tools constrains the list you use to choose the EIM interface table. It displays only the interface tables that include a foreign key relationship with your new custom. Siebel Tools sorts this list by EIM table name. If the Exist field of the interface table is Y, then the EIM table is already mapped to the base table. If you extend a predefined Siebel table, then a table with a Y in the Exist field is an ideal candidate for EIM mapping.

8. Click Finish to accept the configuration and create the EIM Interface Table object.

   Siebel Tools begins the mapping, which might take several minutes. For more information, see Relations That the EIM Table Mapping Wizard Creates.

9. To verify the mappings, do the following:
   1. In the Object Explorer, click EIM Interface Table.
   2. In the EIM Tables list, run a query for all modified records.

      When you run the query, make sure the Changed property contains a check mark. Leave all other properties empty.

   3. To verify the mapping, examine child objects.
   4. Identify any new mappings that are not necessary.
10. If any new mappings are not necessary, then do the following:
    1. Deactivate the unnecessary mappings.
    2. Rename or delete the ORACLE_HOME\bin\diccache.dat file on the Siebel Server.
    3. Run the following query to review any more columns that Siebel Tools created:

    T_*

Relations That the EIM Table Mapping Wizard Creates

Figure 86 describes the relations that exist between objects that the EIM Table Mapping Wizard creates. The wizard maps objects and adds child objects to the predefined EIM interface table object. For more information about EIM objects that the wizard creates, see Objects You Use with Enterprise Integration Manager.

Figure 86. Relations That the EIM Table Mapping Wizard Creates