Professional Documents
Culture Documents
Each objective and “why you need to know” should be stated aloud.
Module Objectives
After completing this module you should be able to:
} Determine correct interface (EIM) tables and columns to use to
import data into and delete data from Siebel base tables and
columns
} Document data mappings between EIM tables and Siebel base
tables
Source Destination
(external) (base table)
2. Determine
how to get
there Interface
(EIM) table
This is not specific to a Siebel implementation. Any time you are looking
Source Data to move or migrate data, you must analyze what the data represents.
Entity and attribute are common terms used along with entity
n Analyze external source data relationship diagrams (ERDs).
} Decide which attributes to store
} Determine which entity the collection of attributes represents
} Analyze relationships between entities
M:M Sales
Entity Customer
Person
Attribute Name... M:M
Name...
Decision
Maker
Name...
Students have practiced techniques for exploring the Siebel Data Model
Siebel Destination earlier in the course. Since the goal is to move data into the Siebel
database, one must understand what the Siebel database has to offer. The
n Analyze Siebel destination tables and columns engineering teams at Siebel Systems have put significant effort into
} Start with applets and fields used, and work down to business designing the database and most of the data mapping needs should be
layer
addressed. Notice that the base table for each of the three depicted
} Use Siebel Tools to view tables and columns, business components is S_PARTY, which was defined in previous modules.
components (BCs), and relationships
Table
BC
Account Position
Contact
2. Identify BC Fields
Applet name
Desired
destination
applet
BC Name
Control to map
2. Identify BC Fields
n Use Siebel Tools to map the applet control to the BC field
BC field
being
mapped
Table and
column
Once you understand both sides, external and internal, in the Siebel
Map Source to Siebel Destination database, then you must bring the data together. Which external piece
ends up where in the Siebel database?
n Specify the source mapping to the Siebel destination
} Identify business component mapped to external entity
} Determine Siebel base tables and columns that will store source
attributes
BC Table
External
entity
Account Position
Sales
Customer
Person
Name... Name...
Attribute
Contact
Decision
Maker
Name...
Copyright © 2007, Oracle. All rights reserved.
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
This is the focus of the module. Once you know where the data should
How to Get There: Determine Interface Tables reside in the Siebel base tables, then you need to identify the EIM tables
that would expedite the process.
n After verifying and documenting the source-to-base mappings,
determine and document EIM-to-base mappings Notice that the spreadsheet lists the EIM column on the left and the base
column on the right. This is reversed when looking at the EIM Interface
Source Source
EIM Table EIM Column Base Table Base Column
Tables report within Siebel Tools. Ensure that students do not get
Entity Attribute confused.
Customer Name S_ORG_EXT NAME
Customer Phone S_ORG_EXT MAIN_PH_NUM
Make sure students understand what a base table is and how it will be
Address S_ADDR_ORG ADDR
used in the EIM process. Refer to the student note for a base table
S_ADDR_ORG CITY definition.
S_ADDR_ORG ZIPCODE
ü
How to
ü
Source Destination
get there?
Interface (EIM) ?
Copyright © 2007, Oracle. All rights reserved.
The point of this slide is that depending on the target base table, there
Table Relationships may be several EIM tables to choose from.
n An interface table may populate more than one base table
n A base table may be populated by more than one interface table
EIM_ACCOUNT
S_ORG_EXT
EIM_ADDR_ORG
S_ADDR_ORG
This slide shows a technique for finding the candidate or potential EIM
Locate EIM Tables tables that would populate a given base table. Stress to students that
EIM_ tables must be used. The graphic adds EIM_ as additional query
n Locate candidate EIM tables using Siebel Tools
criteria.
} Example: Locate EIM tables that populate S_ORG_EXT
Flat tab
Query
Result
The best EIM table will be the one that allows you to populate the most
Interface Table Documentation Continued data. You can use options to limit the target tables during the run.
Therefore, having more targets or destinations than you need is an
n The EIM Interface Table report shows mapping from a single
advantage. The graphic shows a modified screen capture of the EIM
EIM table to one or more Siebel base tables
Interface Tables report generated in Siebel Tools and annotates how to
} EIM column (source) to base table column (destination) mapping read it.
} Column attributes (user keys, foreign key tables, required fields)
Note: The graphic was modified in order to fit it on the slide.
EIM table
name
Base column EIM column
Base table
Base table
Destination
column attributes
Copyright © 2007, Oracle. All rights reserved.
S_ACCNT_POSTN
columns mapped by
EIM_ACCOUNT
EIM Base
table table
EIM Base
column column
Notice that the column name on EIM tables is often the same as the
Determine EIM Columns column name on the base table, but not always.
n 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
Column Names Column names are often the same, but not always.
You can also determine mappings using Siebel Tools. It may be quicker
Determine EIM Columns Continued to search if you are not sure where to look in the documentation.
n Alternate method is to 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
Query
Result
EIM table and column
Result = required
base columns
Defaults not
recognized by EIM