Scribd
Upload
91 views

Module 50 Data Maps

This document discusses data mapping for importing external data into Siebel base tables using EIM (Enterprise Integration Manager). It covers: - Mapping source data to Siebel business components, tables, and columns - Identifying required interface (EIM) tables and columns to transfer data from source to destination - Documenting all mappings between source, interface tables, and Siebel base tables The goal is to specify how external data will be imported and stored in Siebel's database structure.

Uploaded by

RealVasyaPupkin
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
91 views

Module 50 Data Maps

This document discusses data mapping for importing external data into Siebel base tables using EIM (Enterprise Integration Manager). It covers: - Mapping source data to Siebel business components, tables, and columns - Identifying required interface (EIM) tables and columns to transfer data from source to destination - Documenting all mappings between source, interface tables, and Siebel base tables The goal is to specify how external data will be imported and stored in Siebel's database structure.

Uploaded by

RealVasyaPupkin
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 22

Siebel 8.

0 Essentials

Data Maps

1 of 22

Module 48: Data Maps

Module Objectives
To construct a strategy to import,export,update,delete and merge

data to/from siebel base tables

Data Maps

3 of 22

Data Mapping
Is the first step in using EIM to import external data Determines:

1. Which Siebel base table columns will store external source data 2. Which interface (EIM) table columns will be used to import from source to destination
Map the source data with base table columns

External Source Data Base Table

Interface Table

Data Maps

4 of 22

Source Data

External source data should be analyzed


Decide which attributes to store Determine which entity the collection of attributes represents Analyze relationships between entities

Data Maps

5 of 22

Siebel Destination
Analyze Siebel destination tables and columns

Start with UI layer and work down to business layer Use Siebel Tools to view tables and columns, business components (BCs), and relationships
Steps to identify and test destination tables and columns

1. Determine Destination Applet 2. Identify BC Fields 3. Map BC Field to Database Column

Data Maps

6 of 22

1. Determine Destination Applet


Use the Siebel client to identify applets and controls where external data

is to be displayed Determine applet and business component names


Example: Verify mapping for Site field of an account Data to appear in SIS Account List Applet
Applet Name BC Name

Destination Applet

Data Maps

7 of 22

2. Identify BC Fields
List column properties should be examined to know the business

component field that is mapped to it

Data Maps

8 of 22

3. Map BC Field to Database Column


Business Component should be examined to know the table and

column properties of the field


A base table is the destination table in the Siebel database for your data import
Business component

BC field that is being mapped to

Table and column properties of the field to which it is mapped to

Data Maps

9 of 22

Map Source to Siebel Destination


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

Data Maps

10 of 22

Document Mappings
Mappings between source attributes and base columns and tables is

documented for a common understanding by everybody


EIM and configuration tasks are often performed by different people Can reduce need to re-do tasks if team members leave the project

Source Entity Customer Customer

Source Attribute Name Phone Address Site

EIM Table

EIM Column

Base Table S_ORG_EXT S_ORG_EXT S_ORG_EXT S_ORG_EXT

Base Column NAME MAIN_PH_NUM ADDR LOC

Data Maps

11 of 22

Determine Interface Tables


Determine and document EIM-to-base table mappings once source-

to-base mappings are confirmed


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

Data Maps

12 of 22

Locate EIM Tables


Locate candidate EIM tables using Siebel Tools Example: Locate EIM tables that populate S_ORG_EXT Determine and document EIM-to-base table mappings once source-to-base

mappings are confirmed


An interface table may populate more than one base table A base table may be populated by more than one interface table Query for finding EIM tables to populate S_ORG_EXT

Result showing EIM tables that populate the S_ORG_EXT Destination table

Data Maps

13 of 22

Interface Table Documentation


Mappings from interface tables to base tables are documented by:

EIM Interface Table report available in Siebel Tools EIM Table Mapping objects Less convenient than using report

Data Maps

14 of 22

Interface Table Documentation


Determine and document EIM-to-base table mappings once source-

to-base mappings are confirmed


An interface table may populate more than one base table A base table may be populated by more than one interface table

Data Maps

15 of 22

Select EIM Table


Select the EIM table that best maps to the target base tables and

columns
Pick the EIM table that maps the most columns that you need to migrate
Example: EIM_ACCOUNT can be used to map Account-related

Position data because it maps to the intersection table S_ACCNT_POSTN

S_ACCNT_POSTN columns mapped by EIM_ACCOUNT

Data Maps

16 of 22

Determine EIM Columns


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
Base Column EIM Column

Alternative Way to determine the EIM columns

Data Maps

17 of 22

Determine Base Required Columns


Determine required base table columns that do not have defaults

(EIM does not recognize non-system default values)

Data Maps

18 of 22

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
Use EIM Interface Table report to identify these Examples:
PARTY_UID
Gets populated with the value specified in the EIM table for this column May have a calculated value with logic PARTY_TYPE_CD Indicates the type of party data that is being imported Can have values Person, Organization, Position, UserList or AccessGroup, Household ROOT_PARTY_FLG Supports performance for Oracle Set to 'Y' for top-level Positions, Organizations and Access Groups Set to 'N for other party subtypes

Data Maps

19 of 22

Mapping Considerations
Be aware of access control and data visibility issues Set access control by:

Importing ownership information, or Using assignment manager If ownership is not set or is set incorrectly, data visibility will be incorrect
Example: Import product information to Siebel database

Product visibility is determined by organization Map product and ownership information to EIM_PROD_INT (Product interface table) Be sure to map from EIM_PROD_INT to both S_PROD_INT (Internal product base table) and S_PROD_INT_BU (Product/BU intersection table)

Data Maps

20 of 22

Module Highlights
Data mapping specifies:

Which base tables and columns will hold external data Which interface tables and columns will be used by EIM during data movement
Steps to create data mappings for EIM:

Map external entities to Siebel business-layer objects Use the Siebel Web Client to identify and verify mapping of external attributes to BC fields Select the interface table used by the mapping Use Siebel Tools EIM Interface Table report to perform column-to column mappings between interface tables and base tables Map all external attributes of interest plus required non-system columns
Data mappings should be clearly documented

Data Maps

21 of 22

Lab
In this lab you will:

Create datamaps to import Products into Siebel database

Data Maps

22 of 22

You might also like