Siebel Enterprise Integration Manager Administration Guide > EIM Performance Tuning > EIM Usage Planning >

Mapping Data into Siebel Applications

EIM uses EIM table mappings to map columns from EIM tables to Siebel base tables. Siebel predefined EIM mappings are fixed and cannot be remapped.

NOTE:  EIM uses only EIM table mappings to determine table relationships. EIM does not use configuration logic in the Siebel repository to determine table relationships.

Using Siebel Tools, you can view:

Some base tables may not be mapped to a corresponding EIM table. In such cases, use Siebel Visual Basic (VB) to load data into these base tables and inform Siebel Technical Services regarding the missing mapping. For information on using Siebel VB, see Siebel Tools Online Help.

If you have licensed database extensibility and created extensions, you can use the Column Mapping screen to specify mappings to the new fields. Database extensibility and EIM support mappings between columns in extension tables and EIM tables only if these columns share the same base table. To map EIM table extensions to base table extensions, you must specify which column the extended field will point to in the base table. For more information on database extensibility, see Siebel Tools Reference.

To map data into a Siebel application

  1. Determine which Siebel base table columns need to be populated for the Siebel implementation, along with the external data that will be loaded into these base tables.
  2. Determine which EIM table and columns will be used to import from the source to the destination.
  3. Analyze this external data to determine which attributes need to be stored and the relationship this data has to other entities.

    To facilitate this, you can request an EIM Data Mapping and Design review from Siebel Expert Services. This review can be used to make sure that the EIM mappings are correct and will accomplish intended goals.


 Siebel Enterprise Integration Manager Administration Guide 
 Published: 05 January 2004