Essentials (Siebel 7.
7)
Module 35: Data Mapping
Module Objectives
After completing this module you will be able to:
Determine appropriate interface (EIM) tables and columns
to use to perform imports into and deletes from Siebel
base tables and columns
Document how external data maps to EIM tables and
base tables
Why you need to know:
Enables you to construct a strategy for successfully
importing and deleting from the Siebel database
Module 35: Data Mapping 2 of 19
Data Mapping
Data mapping determines:
Which Siebel base table columns will store external source data
Which interface (EIM) table columns will be used to import from
source to destination
Where data
ends up
Source Destination
(external) (base)
How to
get there
Interface
(EIM)
Module 35: Data Mapping 3 of 19
Source Data
Analyze external source data
Which attributes need to be stored?
Which entity does the collection of attributes represent?
What relationship(s) does this entity have to other entities?
M:M Sales
Entity Customer
Person
Attribute Name... M:M
Name...
Decision
Maker
Name...
Module 35: Data Mapping 4 of 19
Siebel Destination
Analyze Siebel destination tables and columns
Use the sample application to determine business components
(BCs), tables, and relationships
Use Siebel Tools to view tables and columns, business
components, and relationships
Use the data model reference to inspect tables and columns
Account Position
Contact
Module 35: Data Mapping 5 of 19
Map Source to Siebel Destination
Determine the source mapping to the Siebel destination
Which Siebel business component represents the external entity?
Which Siebel base tables and columns will store the source
attributes?
Account Position
Sales
Customer
Person
Name... Name...
Contact
Decision
Maker
Name...
Module 35: Data Mapping 6 of 19
Verify Mappings
Verify that the column mappings match the applet and business
component mappings
Make sure the control on the applet you intend to display maps to
the same column you are populating with EIM
Determine object name
Select field to Use Web Layout Editor
verify column to verify field
Module 35: Data Mapping 7 of 19
Document Mappings
Document mappings between source, EIM, and base so that
everyone has a common understanding
EIM and configuration tasks are often performed by different
people
Avoid re-doing tasks if team members leave the project
Source Source
EIM Table EIM Column Base Table Base Column
Entity Attribute
Customer Name S_ORG_EXT NAME
Customer Phone S_ORG_EXT MAIN_PH_NUM
Address S_ADDR_ORG ADDR
S_ADDR_ORG CITY
S_ADDR_ORG ZIPCODE
Module 35: Data Mapping 8 of 19
How to Get There
After verifying and documenting the source-to-base mappings,
determine EIM-to-base mappings using Siebel Tools
Source Source
EIM Table EIM Column Base Table Base Column
Entity Attribute
Customer Name S_ORG_EXT NAME
Customer Phone S_ORG_EXT MAIN_PH_NUM
Address S_ADDR_ORG ADDR
S_ADDR_ORG CITY
S_ADDR_ORG ZIPCODE
How to
get there?
Interface (EIM)
?
Module 35: Data Mapping 9 of 19
Table Relationships
An interface table may populate more than one base table
A base table may be populated by more than one interface table
EIM_ACCOUNT
S_ORG_EXT
EIM_ADDR_ORG
S_ADDR_ORG
Module 35: Data Mapping 10 of 19
Locate EIM Tables
Locate candidate EIM tables using Siebel Tools
Example: Locate EIM tables that populate S_ORG_EXT
Flat tab
Query
Result
EIM tables that
populate S_ORG_EXT
Note: Use EIM_ tables, not _IF tables
Module 35: Data Mapping 11 of 19
Select EIM Table
Select the EIM table that best maps to the target base tables
and columns
Example: EIM_ACCOUNT may be a better choice than
EIM_ADDR_ORG if you want to import into EIM_ACCNT_POSTN
in the same batch
Populates EIM table Populates
Base column EIM column
Main base
table
Module 35: Data Mapping 12 of 19
EIM to Base Mappings
Determine EIM columns that populate target base columns
Determine other EIM required columns to populate the target
base table
Other columns may be required based on required fields in the
base table
EIM Base
table table
EIM Base
column column
Module 35: Data Mapping 13 of 19
Determine EIM Columns
Determine which EIM column populates the target base column
in Siebel Tools
Example: MAIN_PH_NUM on EIM_ACCOUNT populates
MAIN_PH_NUM on S_ORG_EXT
Base EIM
column column
Module 35: Data Mapping 14 of 19
Determine EIM Columns Continued
Query Attribute Mappings in Siebel Tools to determine which
EIM column populates the base column
Example: MAIN_PH_NUM on EIM_ACCOUNT populates
MAIN_PH_NUM on S_ORG_EXT
Use Flat tab Base table
to query and column
Result
EIM table and column
Module 35: Data Mapping 15 of 19
Determine Base Required Columns
Determine required base table columns that do not have
defaults (EIM does not recognize non-system default values)
Query Column
Result = required
base columns
Default not
recognized by EIM
Module 35: Data Mapping 16 of 19
Mapping Considerations
Understand how to enter organization data
Fill in _BU column with name of the organization
Leave _BI column blank
Populated with foreign key during import processing
Understand additional columns that must be populated for party
business components
Examples:
PARTY_UID
PARTY_TYPE_CD
ROOT_PARTY_FLG
Module 35: Data Mapping 17 of 19
Summary
This module showed you how to:
Determine appropriate interface (EIM) tables and columns
to use to perform imports into and deletes from Siebel
base tables and columns
Document how external data maps to EIM tables and
base tables
Module 35: Data Mapping 18 of 19
Lab
In the lab you will:
Map external solutions data to EIM tables and base tables
Map external product data to EIM tables and base tables
Module 35: Data Mapping 19 of 19