Siebel Database Upgrade Guide for DB2 UDB for z/OS > Postupgrade Tasks for a Siebel Development Environment >

Deleting Duplicate EIM Mappings

Upgrades: Release 6.2.1 only.

Environments: Development environment only.

Any custom Enterprise Integration Manager (EIM) mappings that were added to *_IF tables in previous versions of Siebel Business Applications are automatically migrated to *_IF tables during the upgrade to Siebel 8.0. However, those customizations are not migrated to the EIM tables that were introduced in Siebel 7.x to replace the *_IF tables. If you choose to use the new EIM tables rather than the *_IF tables, you must manually add any customizations to them.

If custom mappings in *_IF tables are duplicated by new mappings added as part of the current release of Siebel Business Applications, errors will result when you use EIM.

The Database Configuration Wizard that you ran to upgrade the physical schema (see Process of Upgrading a Siebel Development Environment) generated a file called mapclash.txt. This file lists any custom EIM mappings that conflict with Siebel-provided mappings. The file contains the columns illustrated and defined in Table 23.

Before proceeding with the upgrade, use Siebel Tools as described below to delete any custom mappings listed in this file.

To delete duplicate custom EIM mappings

1. Launch Siebel Tools and select Prior Customer Repository.
2. From the Object Explorer, choose EIM Interface Table > EIM Table Mapping.
3. From the EIM Table applet, select the interface table name (IT_Name), for example, S_ACCOUNT_IF, and query for the interface table.
4. From the EIM Table Mappings applet, choose the name assigned for the destination table (DT_Name); for example, S_ORG_EXT_X.
5. From the Object Explorer, choose EIM Table Mapping > Attribute Mapping.

   The fourth column in this applet is the DC_Name.

6. Delete the duplicate mappings.