Upgrade Guide for UNIX > Postupgrade Tasks > Postupgrade Tasks for All Environments >

Resolving Duplicate EIM Mappings

CAUTION:  Skip this procedure if you are upgrading a production environment or if you are upgrading from Release 7.x to Release 7.5. Proceed to Producing a New Custom Configuration File.

Any custom Enterprise Integration Manager (EIM) mappings that were added to previous versions of Siebel eBusiness Applications are automatically migrated to the new custom repository. If custom mappings are duplicated by new mappings added as part of Siebel version 7.x, errors occur when you use EIM.

NOTE:  Custom EIM mappings are only added to old _IF tables, not to new EIM tables. If you need to use the new EIM tables, you must manually add the customization to them.

The Siebel Software Configuration Utility that you ran in Upgrading the Siebel Database Schema generated a file called mapclash.txt. This file lists any custom EIM mappings that conflict with Siebel Systems-provided mappings. The file contains the columns illustrated and defined in Table 23.

Table 23.  Mapclash.txt File Column Names and Definitions
Column Name
Definition
IT_Name
Interface table name (example: S_ACCOUNT_IF)
DT_Name
Destination table (base table) name
DC_Name
Destination column (base table column) name

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 New 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.

 Upgrade Guide for UNIX
 Published: 20 October 2003