Siebel Tutorials : EIM Data Mapping

Siebel Tutorials on Data Mapping.

Which base tables will store external data and which interface tables will be used to get the data there.

• Key inputs:

Which Attributes (i.e. fields) need to be stored?

What Entities do the collection of these attributes represent?

What is the relationship between these entities?

Which Siebel BC represents entity?
# I.e. Dept of Ed Borrower = Contact, Student Loan = Asset

Analyze Siebel destination tables + columns using:
# Siebel Tools for available tables + columns + BCs + relationships

• Using Source-to-Base table mappings:

Determine EIM-to-base mappings with Bookshelf and/or tools
# I.e. for S_ORG_EXT, locate IF tables that support S_ORG_EXT, like EIM_ACCOUNT, etc
# Best of those tables is the one that allows you to import the most data
# Determine required columns

• Required if there is a mapping from it to one of the required, non-system default columns on the base table
• Could include “defaults” from tools

# Verify column mappings match applet and BC mappings

• Use Data Map for cross-team communication

Interface tables may populate more than one base table.

Base table can be populated by more than one interface table.

Additional Party considerations
# BU column holds name of organization, BI column is populated automatically

# PARTY_UID, PARTY_TYPE_CD, ROOT_PARTY_FLG required