Zims Master Data Management For Position Design Specification

MDM POSITION Extract v1.0 Version 1.
0
Design Specification
ZIMS
Master Data Management for
POSITION
Draft Version: 1.0
Date: 20- Jun-2010
Release: 1.0
06/20/2010 Page 1 of 29
MDM POSITION Extract v1.0 Version 1.0
Approvals
Approvers
Jim Liebenow <Date>
Consultant, Application
Services
USHH IS
As the Project manager and Architect for the MDM project, the approval above signifies
agreement that the contents herein identify a sound design for the data integration functions
for the MDM
Publication Record
Version Date Revised Primary Author Summary of Changes
1.0 20-Jun-2010 Ramesh Daddala Initial Draft
Document Attributes
Minimal Attribute Set
Document Descriptor Issue Date
MDM-POSITION Extract – Design 20-Jun-2010
Specification
Retention Date Record Status
N/A Final
Owner as Division Author as Person
U.S Human Health Ramesh Daddala
Retention Trigger Division Abbreviation
USHH
Retention Class
Administrative
SLC Repository
Document ID Business Version
T_D08 1.0
06/20/2010 Page 2 of 29
06/20/2010 Page 3 of 29
Table of Contents
1. Purpose:....................................................................................................................................5
2. Requirements:..........................................................................................................................5
3. Data Model Diagram/ER Diagram...........................................................................................6
4. Data Mapping - Source to Target.............................................................................................7
5. Pre-Processing Logic for POSITION tables...........................................................................13
6. Frequency……………………………………………………………………………… …..13
7. Low-Level Process:[Asgnmnt_type table]..............................................................................13
7.1 Technical Description...................................................................................................13
7.2 Design Elements...........................................................................................................13
7.3 Informatica Transformation Logic................................................................................14
7.4 Informatica High Level Design Overview....................................................................15
7.5 Configuration................................................................................................................15
7.6 Interfaces......................................................................................................................15
8. Low-Level Process:[Asgnmnt_type_ctgry table]...................................................................16
8.2 Design Elements...........................................................................................................16
8.5 Configuration................................................................................................................17
8.6 Interfaces......................................................................................................................17
9. Low-Level Process:[Job_type table]......................................................................................18
9.2 Design Elements...........................................................................................................18
9.5 Configuration................................................................................................................19
9.6 Interfaces......................................................................................................................19
10. Low-Level Process:[Pstn table]..............................................................................................20
10.1 Overview:.....................................................................................................................20
10.3 Design Elements...........................................................................................................20
10.6 Configuration................................................................................................................22
10.7 Interfaces......................................................................................................................22
11 Low-Level Process:[Pstn asgnmnt table]................................................................................23

11.1 Overview:.....................................................................................................................23
11.3 Design Elements...........................................................................................................24
11.6 Configuration................................................................................................................25
11.7 Interfaces......................................................................................................................25
06/20/2010 Page 4 of 29
12 Low-Level Process:[Sales team pstn table]............................................................................26

12.1 Overview:.....................................................................................................................26
12.3 Design Elements...........................................................................................................27
12.6 Configuration................................................................................................................28
12.7 Interfaces......................................................................................................................28
06/20/2010 Page 5 of 29
1 Purpose:
This document provides details of the load process, ETL design methodology, design
considerations and architectural overview for the position. It describes in detail the various
ETL activities and methodology employed.
2 Requirements:
BUSINESS REQUIREMENTS:
Sales force resources as effectively as possible to meet corporate, division and product
revenue goals, the use of alignment data is critical in the overall analysis and understanding
of how customers in each geographic territory respond to the sales representative's
promotion of respective products. Effective deployment of field sales force resources.
 Geography, including territories and their respective regions, zip codes, etc.
 Periodic analysis of field sales force effectiveness.
 Customer targeting including prescribers, outlets and institutions.
 Market penetration for new product offerings (Product Launch).
 Sales Promotion activities.
06/20/2010 Page 6 of 29
3 Data Model Diagram/ER Diagram

_PRE_REVISION_003
PARTY JOB_TYPE
PARTY_ID: NUMBER(9) NOT NULL
ASGNMNT_TYPE_CTGRY ORG_UNIT
ORG_UNIT_ID: NUMBER(9) NOT NULL
RLTN_TYPE PSTN
RLTN_TYPE_CD: VARCHAR2(10) NOT NULL ORG_UNIT_ID: NUMBER(9) NOT NULL (FK)
PRMRY_CODE_NM: VARCHAR2(64) NULL JOB_TYPE_CD: VARCHAR2(10) NOT NULL (FK)
PSTN_SEQ_NO: NUMBER(9) NOT NULL
EFFCTV_DT: DATE NULL
EXPRTN_DT: DATE NULL
ASGNMNT_TYPE CRTN_ID: VARCHAR2(8) NULL
CRTN_DT_TM: DATE NULL
ASGNMNT_TYPE_CD: VARCHAR2(10) NOT NULL
LAST_UPDT_ID: VARCHAR2(8) NULL
ASGNMNT_TYPE_CTGRY_CD: VARCHAR2(10) NULL (FK)
LAST_UPDT_DT_TM: DATE NULL
LAST_RPLCTN_DT_TM: DATE NULL
SALES_TEAM_PSTN
SALES_TEAM_ORG_UNIT_ID: NUMBER(9) NOT NULL (FK)
ORG_UNIT_ID: NUMBER(9) NOT NULL (FK)
JOB_TYPE_CD: VARCHAR2(10) NOT NULL (FK)
PSTN_SEQ_NO: NUMBER(9) NOT NULL (FK)
EFFCTV_DT: DATE NOT NULL
EXPRTN_DT: DATE NULL
CRTN_ID: VARCHAR2(8) NULL
PSTN_RLTN CRTN_DT_TM: DATE NULL
PRMRY_ORG_UNIT_ID: NUMBER(9) NOT NULL (FK) LAST_UPDT_DT_TM: DATE NULL
PRMRY_JOB_TYPE_CD: VARCHAR2(10) NOT NULL (FK) LAST_RPLCTN_DT_TM: DATE NULL
PRMRY_PSTN_SEQ_NO: NUMBER(9) NOT NULL (FK)
RLTD_ORG_UNIT_ID: NUMBER(9) NOT NULL (FK)
RLTD_JOB_TYPE_CD: VARCHAR2(10) NOT NULL (FK)
PSTN_ASGNMNT
RLTD_PSTN_SEQ_NO: NUMBER(9) NOT NULL (FK)
ORG_UNIT_ID: NUMBER(9) NOT NULL (FK) RLTN_TYPE_CD: VARCHAR2(10) NOT NULL (FK)
JOB_TYPE_CD: VARCHAR2(10) NOT NULL (FK) EFFCTV_DT: DATE NOT NULL
PSTN_SEQ_NO: NUMBER(9) NOT NULL (FK) EXPRTN_DT: DATE NULL
EFFCTV_DT: DATE NOT NULL CRTN_ID: VARCHAR2(8) NULL
PARTY_ID: NUMBER(9) NOT NULL (FK) CRTN_DT_TM: DATE NULL
PSTN_ASGNMNT_SEQ_NO: NUMBER(9) NOT NULL LAST_UPDT_ID: VARCHAR2(8) NULL
ASGNMNT_TYPE_CD: VARCHAR2(10) NULL (FK) LAST_UPDT_DT_TM: DATE NULL
EXPRTN_DT: DATE NULL LAST_RPLCTN_DT_TM: DATE NULL
CRTN_ID: VARCHAR2(8) NULL
CRTN_DT_TM: DATE NULL
LAST_UPDT_DT_TM: DATE NULL
LAST_RPLCTN_DT_TM: DATE NULL
06/20/2010 Page 7 of 29
4 Data Mapping - Source to Target

Data types for Source and Target Tables: ASGNMNT_TYPE
Source Table: SIMON. ASGNMNT_TYPE

Target Table: ZIFSX_ASGNMNT_TYPE
SOURCE (RDBMS) DATA TYPE TARGET(RDBMS) DATA TYPE

SIMON. ASGNMNT_TYPE ZIFSX_ASGNMNT_TYPE
ASGNMNT_TYPE_CD ASGNMNT_TYPE_CD
VARCHAR2(10) NOT NULL
VARCHAR2(10)
ASGNMNT_TYPE_CTGRY_CD ASGNMNT_TYPE_CTGRY_CD
VARCHAR2(10) VARCHAR2(10)
CODE_NM VARCHAR2(64) CODE_NM VARCHAR2(64)
CODE_DESC VARCHAR2(512) CODE_DESC VARCHAR2(512)
EFFCTV_DT DATE EFFCTV_DT DATE
EXPRTN_DT DATE EXPRTN_DT DATE
SORT_ORDER_NMBR NUMBER(5) SORT_ORDER_NMBR NUMBER(5)
CRTN_ID VARCHAR2(8)
CRTN_DT_TM DATE
LAST_UPDT_ID VARCHAR2(8)
LAST_UPDT_DT_TM DATE
LAST_RPLCTN_DT_TM DATE
06/20/2010 Page 8 of 29
Data types for Source and Target Tables: ASGNMNT_TYPE_CTGRY
Source Table: SIMON. ASGNMNT_TYPE_CTGRY

Target Table: ZIFSX_ASGNMNT_TYPE_CTGRY

SIMON. ZIFSX_ASGNMNT_TYPE_
ASGNMNT_TYPE_CTGRY CTGRY
ASGNMNT_TYPE_CTGRY_CD VARCHAR2(10) ASGNMNT_TYPE_CTGRY_CD NOT NULL

VARCHAR2(10)
SORT_ORDER_NMBR NUMBER(5) SORT_ORDER_NMBR NUMBER(5)
CRTN_ID VARCHAR2(8)
CRTN_DT_TM DATE
06/20/2010 Page 9 of 29
Data types for Source and Target Tables: JOB_TYPE
Source Table: SIMON. ROLE_TYPE

Target Table: ZIFSX_JOB_TYPE

SIMON. ROLE_TYPE ZIFSX_JOB_TYPE
ROLE_TYPE_CD VARCHAR2(10) JOB_TYPE_CD NOT NULL

VARCHAR2(10)
SORT_ORDER_NMBR VARCHAR2(8) SORT_ORDER_NMBR VARCHAR2(8)
CRTN_ID DATE
CRTN_DT_TM VARCHAR2(8)
LAST_UPDT_ID DATE
DATE
LAST_UPDT_DT_TM
06/20/2010 Page 10 of 29
Data types for Source and Target Tables: PSTN
Source Table: SIMON.ORG_UNIT_ROLE_HIST

Target Table: ZIFSX_PSTN

ORG_UNIT_ROLE_HIST ZIFSX_PSTN
ORG_UNIT_ID NUMBER(9) ORG_UNIT_ID NOT NULL

NUMBER(9)
JOB_TYPE_CD NOT NULL

ROLE_TYPE_CD VARCHAR2(10) VARCHAR2(10)
ORG_UNIT_ROLE_SEQ_NO NUMBER(9) PSTN_SEQ_NO NOT NULL

NUMBER(9)
CRTN_ID VARCHAR2(8)
CRTN_DT_TM DATE
LAST_RPLCTN_DT_T DATE
M
06/20/2010 Page 11 of 29
Data types for Source and Target Tables: PSTN_ASGNMNT
Source Table: SIMON.ORG_UNIT_ROLE_ASGNMNT

Target Table: ZIFSX_PSTN_ASGNMNT
SOURCE (RDBMS) DATA TYPE TARGET (RDBMS) DATA TYPE

ORG_UNIT_ROLE_ASGNM ZIFSX_PSTN_ASGN
NT MNT
ORG_UNIT_ID NUMBER(9) ORG_UNIT_ID NOT NULL

NUMBER(9)
ROLE_TYPE_CD VARCHAR2(10) JOB_TYPE_CD NOT NULL

VARCHAR2(10)
ORG_UNIT_ROLE_SEQ_N NUMBER(9) PSTN_SEQ_NO NOT NULL

O NUMBER(9)
EFFCTV_DT DATE EFFCTV_DT NOT NULL

DATE
NOT NULL
PARTY_ID NUMBER(9) PARTY_ID NUMBER(9)
ORG_UNIT_ROLE_ASGNM NUMBER(9) PSTN_ASGNMNT_SEQ_ NOT NULL

NT_SEQ_NO NO NUMBER(9)
ASGNMNT_TYPE_CD VARCHAR2(10) ASGNMNT_TYPE_CD VARCHAR2(10)
CRTN_ID VARCHAR2(8)
CRTN_DT_TM DATE
06/20/2010 Page 12 of 29
Data types for Source and Target Tables:
Source Table: SIMON.ORG_UNIT_ROLE_SALES_TEAM

Target Table: ZIFSX_SALES_TEAM_PSTN

SIMON.ORG_UNIT_ROLE_SALES
_TEAM ZIFSX_SALES_TEAM_
PSTN
SALES_TEAM_ID NUMBER(9) SALES_TEAM_ORG_UNIT_I NOT NULL

D NUMBER(9)
ORG_UNIT_ID NOT NULL

VARCHAR2(10) ORG_UNIT_ID NUMBER(9)
NOT NULL
ROLE_TYPE_CD NUMBER(9) JOB_TYPE_CD VARCHAR2(10)
ORG_UNIT_ROLE_SEQ_NO DATE PSTN_SEQ_NO NOT NULL

NUMBER(9)
EFFCTV_DT DATE EFFCTV_DT NOT NULL

DATE
CRTN_ID VARCHAR2(8)
CRTN_DT_TM DATE
VARCHAR2(8)
LAST_UPDT_ID
LAST_RPLCTN_DT_TM NULL
06/20/2010 Page 13 of 29
5 Pre-Processing Logic for POSITION tables

6 Using the command CRONTAB, script fsmsx_position.sh will be run daily at the UNIX
prompt: \fsms\data001\fsmsx\Scripts.
1. Frequency – daily
7 Low-Level Process:
Load ZIFSX_ASGNMNT_TYPE Table
7.1 Technical Description

Environment: Development, RDBMS
 Source Database: D_SIMON_MDM
 Source Schema: SIMON
 Source Table: ASGNMNT_TYPE

 Target Database: D_ZIFSX
 Target Schema: FSMSX
 Target Table: ZIFSX_ASGNMNT_TYPE
Environment: Development, UNIX

 Server: uctsd500
 Path: \fsms\data001\fsmsx\Scripts
 Shell Script File: fsmsx_position.sh
 Usage: To start workflow using ‘pmcmd’ command and send a notification email
Environment: Development, INFORMATICA

 Server:- UCTSD500
 User: dagar
 Folder:- FSMS_dagar
CONNECT STRING IN INFORMATICA

 RDBMS environment : D_SIMON_MDM pointing to D2_SIMON-SIMON
 RDBMS environment : D_FSMSX pointing to D_FSMS - FSMSX
7.2 Design Elements
 Informatica workflow: w_d_i_fsmsx_position

 This workflow calls the mappings : m_fsmsx_asgnmnt_type
 Mapping loads the data as per the logic mentioned below
06/20/2010 Page 14 of 29
7.3 Informatica Transformation Logic
Processing 1.EXPRESSION TRANSFORMATION:

Expression Name: exp_ ASGNMNT_TYPE
Just assign hard coded values
Values:
O_CRTN_ID =’FSMSETL’
O_CRTN_DT_TM= SESSSTARTTIME
O_LAST_UPDT_ID=’FSMSETL’
O_LAST_UPDT_DT_TM= SESSSTARTTIME
O_LAST_RPLCTN_DT_TM=NULL
Outputs Target Name Target Layout

Field Comments
ZIFSX_ASGNMNT_TY SIMON. ASGNMNT_TYPE.
PE (ORACLE) ASGNMNT_TYPE_CD ASGNMNT_TYPE_CD
ASGNMNT_TYPE_CTGRY_ SIMON. ASGNMNT_TYPE.

CD ASGNMNT_TYPE_CTGRY_CD
CODE_NM SIMON.
ASGNMNT_TYPE.CODE_NM
CODE_DESC SIMON.
ASGNMNT_TYPE.CODE_DESC
EFFCTV_DT SIMON. ASGNMNT_TYPE.

EFFCTV_DT
EXPRTN_DT SIMON. ASGNMNT_TYPE.

EXPRTN_DT
SIMON. ASGNMNT_TYPE.
SORT_ORDER_NMBR SORT_ORDER_NMBR
CRTN_ID ‘FSMSETL’
CRTN_DT_TM SESSSTARTTIME
LAST_UPDT_ID ‘FSMSETL’
LAST_UPDT_DT_TM SESSSTARTTIME
06/20/2010 Page 15 of 29
7.4 Informatica High Level Design Overview

ASGNMNT_TYPE Mapping
EXPRESSION
SOURCE TARGET
SIMON.ASGNMNT_TYPE FSMSX.ASGNMNT_TYPE
ASSIGN HARD CODED
(ORACLE) (ORACLE)
VALUES
7.5 Configuration
 Informatica 7.1 Client, UNIX, ORACLE9i, TOAD.
7.6 Interfaces
 None
06/20/2010 Page 16 of 29
Load ZIFSX_ASGNMNT_TYPE_CTGRY Table

 Source Table: ASGNMNT_TYPE_CTGRY

 Target Database: D_FSMSX
 Target Table: ZIFSX_ASGNMNT_TYPE_CTGRY


 User: dagar

8.2 Design Elements
 This shell script executes the Informatica workflow: w_d_i_fsmsx_position

 This workflow calls the mappings : m_fsmsx_asgnmnt_type_ctgry
Processing 1. EXPRESSION TRANSFORMATION:

Expression Name: exp_ ASGNMNT_TYPE_CTGRY
Values:
06/20/2010 Page 17 of 29

Field Comments
ZIFSX_ASGNMNT_TY SIMON. ASGNMNT_TYPE_CTGRY.
PE_CTGRY ASGNMNT_TYPE_CTGRY ASGNMNT_TYPE_CTGRY_CD
(ORACLE) _CD
SIMON. ASGNMNT_TYPE_CTGRY.
CODE_NM CODE_NM
CODE_DESC SIMON.
ASGNMNT_TYPE_CTGRY.CODE_DESC
EFFCTV_DT SIMON.
ASGNMNT_TYPE_CTGRY.EFFCTV_DT
EXPRTN_DT SIMON.
ASGNMNT_TYPE_CTGRY.EXPRTN_DT
SORT_ORDER_NMBR SIMON. ASGNMNT_TYPE_CTGRY.

SORT_ORDER_NMBR

ASGNMNT_TYPE_CTGRY Mapping
EXPRESSION
SOURCE TARGET
SIMON.ASGNMNT_TYPE_CTGRY FSMSX.ASGNMNT_TYPE_CTGRY
ASSIGN HARD CODED
(ORACLE) (ORACLE)
VALUES
8.5 Configuration
8.6 Interfaces
 None
06/20/2010 Page 18 of 29
Load ZIFSX_JOB_TYPE Table

 Source Table: ROLE_TYPE

 Target Table:ZIFSX_JOB_TYPE


 User: dagar

9.2 Design Elements
 Informatica workflow: w_d_i_fsmsx_position

 This workflow calls the mappings : m_fsmsx_job_type

Expression Name: exp_JOB_TYPE
Values:
06/20/2010 Page 19 of 29

Field Comments
ZIFSX_JOB_TYPE( SIMON.ROLE_TYPE.ROLE_TYPE_C
ORACLE) JOB_TYPE_CD D
CODE_NM SIMON.ROLE_TYPE.CODE_NM
CODE_DESC SIMON.ROLE_TYPE.CODE_DESC
EFFCTV_DT SIMON.ROLE_TYPE.EFFCTV_DT
EXPRTN_DT SIMON.ROLE_TYPE.EXPRTN_DT
SORT_ORDER_NMBR SIMON.ROLE_TYPE.SORT_ORDER_
NMBR

JOB_TYPE Mapping
EXPRESSION
SOURCE TARGET
SIMON.ROLE_TYPE FSMSX.JOB_TYPE
ASSIGN HARD CODED
(ORACLE) (ORACLE)
VALUES
9.5 Configuration
9.6 Interfaces
 None
06/20/2010 Page 20 of 29
Load ZIFSX_PSTN Table
10.1 Overview:
 The source SIMON.ORG_UNIT_ROLE_HIST would be read and ORG_UNIT_ID will be looked
up in the ZIFSX_ORG_UNIT_ALTRNT_ID based upon the ALTRNT_ID_TYPE_CD being
“ORGUNTID” load into the ZIFSX_PSTN.
 ORG_UNIT_ID row is populated to the target from source and the header
information as mapped in the STTM will be populated to the ZIFSX_PSTN table.
 In case the informatica mapping failure an Email will be sent out with the relevant
details for action.

 Source Table: ORG_UNIT_ROLE_HIST

 Target Table: ZIFSX_PSTN


 User: dagar

10.3 Design Elements

 This workflow calls the mappings : m_fsmsx_pstn
06/20/2010 Page 21 of 29

Expression Name: exp_CONVERSION
This will be used to convert ORG_UNIT_ID decimal value into string values
and Assign hard coded value as I mentioned below
Values:
O_ORG_UNIT_ID=TO_CHAR(ORG_UNIT_ID)
O_ALTRNT_ID_TYPE_CD=hard coded ”ORGUNTID”
2. LOOKUP TRANSFORMATION:
Lookup name:lkp_ORG_UNIT_ALTRNT_ID
Create a lookup transformation (lkp_ORG_UNIT_ALTRNT_ID) that will do
lookup on table ZIFSX_ORG_UNIT_ALTRNT_ID on column
ALTRNT_ID_TYPE_CD, ALTRNT_ID to get ORG_UNIT_ID.This value will go in
PSTN
Lookup conditions:
o_ALTRNT_ID_TYPE_CD=ALTRNT_ID_TYPE_CD
ALTRNT_ID=i_ORG_UNIT_ID
3. EXPRESSION TRANSFORMATION:
Expression Name: exp_PSTN
Create an expression transformation (exp_PSTN) this will used to assign hard
coded values.
Values:

Field Comments
ZIFSX_PSTN(ORA FSMSX. ORG_UNIT_ALTRNT_ID.
CLE) ORG_UNIT_ID ORG_UNIT_ID
SIMON. ORG_UNIT_ROLE_HIST.
JOB_TYPE_CD ROLE_TYPE_CD
PSTN_SEQ_NO ORG_UNIT_ROLE_SEQ_NO
EFFCTV_DT EFFCTV_DT
EXPRTN_DT EXPRTN_DT
06/20/2010 Page 22 of 29

PSTN Mapping
EXPRESSION LOOKUP
SOURCE O_ORG_UNIT_ID=TO_CHAR(ORG_ o_ALTRNT_ID_TYPE_CD=ALTR
UNIT_ID)
SIMON. ORG_UNIT_ROLE_HIST O_ALTRNT_ID_TYPE_CD=hard
NT_ID_TYPE_CD
coded ”ORGUNTID” ALTRNT_ID=i_ORG_UNIT_ID
EXPRESSION
ASSIGN HARD CODED VALUES
TARGET
FSMSX.PSTN
10.6 Configuration
10.7 Interfaces
 None
06/20/2010 Page 23 of 29
10.7.1 Low-Level Process:

Load ZIFSX_PSTN_ASGNMNT Table
10.8Overview:
 The source SIMON.ORG_UNIT_ROLE_ASGNMNT would be read and ORG_UNIT_ID will be
looked up in the FSMSX.ORG_UNIT_ALTRNT_ID based upon the ALTRNT_ID_TYPE_CD being
“ORGUNTID” load into the ZIFSX_PSTN_ASGNMNT
 PARTY_ID will be looked up in the FSMSX.PARTY_ALTRNT_ID based upon the

ALTRNT_ID_TYPE_CD being “WINNO” load into the ZIFSX_PSTN_ASGNMNT
 ORG_UNIT_ID and PARTY_ID would be populated to the target from source and
the header information as mapped in the STTM will be populated to the
ZIFSX_PSTN_ASGNMNT table.
details for action.

 Source Database: T_SIMON
 Source Table: ORG_UNIT_ROLE_ASGNMNT

 Target Table: ZIFSX_PSTN_ASGNMNT


 User: dagar

 RDBMS environment : T_SIMON pointing to T_SIMON-SIMON
06/20/2010 Page 24 of 29

 This workflow calls the mappings : m_fsmsx_pstn_asgnmnt

Processing 1 EXPRESSION TRANSFORMATION:
Expression Name: exp_PSTN_ASGNMNT
This will be used to convert SALES_TEAM_ID, ORG_UNIT_ID decimal
values into string values and Assign hard coded values as I mentioned
below
Values:
O_ORG_UNIT_ID=TO_CHAR(ORG_UNIT_ID)
O_ALTRNT_ID_TYPE_CD=”ORGUNTID”
O_PARTY_ID=TO_CHAR(PARTY_ID)
O_ALTRNT_ID_TYPE_CD1=”WINNO”
CRTN_ID =’FSMSETL’
CRTN_DT_TM= SESSSTARTTIME
LAST_UPDT_ID=’FSMSETL’
LAST_UPDT_DT_TM= SESSSTARTTIME
LAST_RPLCTN_DT_TM=NULL
2. LOOKUP TRANSFORMATION
Lookup name: lkp_ORG_UNIT_ID
Create a lookup transformation (lkp_ORG_UNIT_ID) that will do lookup on
table FSMSX. ORG_UNIT_ALTRNT_ID on column ALTRNT_ID_TYPE_CD,
ALTRNT_ID to get ORG_UNIT_ID.This value will go in PSTN_ASGNMNT
Lookup condition:
O_ORG_UNIT_ID= ALTRTN_ID
O_ALTRNT_ID_TYPE_CD=ALTRNT_ID_TYPE_CD
3. LOOKUP TRANSFORMATION
Lookup name:lkp_PARTY_ID
Create a lookup transformation (lkp_PARTY_ID) that will do lookup on
ALTRNT_ID to get ORG_UNIT_ID.This value will go in PSTN_ASGNMNT.
Lookup condition:
O_PARTY_ID=TO_CHAR(PARTY_ID)
O_ALTRNT_ID_TYPE_CD1=ALTRNT_ID_TYPE_CD

Field Comments
ZIFSX_PSTN_ASG FSMSX. ORG_UNIT_ALTRNT_ID.
NMNT(ORACLE) ORG_UNIT_ID ORG_UNIT_ID
SIMON.
JOB_TYPE_CD ORG_UNIT_ROLE_ASGNMNT.
ROLE_TYPE_CD
SIMON.
PSTN_SEQ_NO ORG_UNIT_ROLE_ASGNMNT.
ORG_UNIT_ROLE_SEQ_NO
SIMON.
EFFCTV_DT ORG_UNIT_ROLE_ASGNMNT.
EFFCTV_DT
FSMSX.PARTY_ALTRNT_ID.
PARTY_ID PARTY_ID
SIMON.
06/20/2010 Page 25 of 29
PSTN_ASGNMNT_SEQ_ ORG_UNIT_ROLE_ASGNMNT.
NO ORG_UNIT_ROLE_ASGNMNT_SEQ
_NO
SIMON.
ASGNMNT_TYPE_CD ORG_UNIT_ROLE_ASGNMNT.
ASGNMNT_TYPE_CD
SIMON.
EXPRTN_DT ORG_UNIT_ROLE_ASGNMNT.
EXPRTN_DT

PSTN_ASGNMNT Mapping
LOOKUP
o_ALTRNT_ID_TYPE_CD=ALTRN
T_ID_TYPE_CD
ALTRNT_ID=i_ORG_UNIT_ID
SOURCE
EXPRESSION
O_ORG_UNIT_ID=TO_CHAR(ORG_UNIT_ID) TARGET
SIMON.ORG_UNIT_ROLE_ASGNMNT
O_ALTRNT_ID_TYPE_CD=”ORGUNTID” PSTN_ASGNMNT
O_PARTY_ID=TO_CHAR(PARTY_ID) (ORACLE)
(ORACLE)
O_ALTRTNT_ID_TYPE_CD1=”WINNO”
LOOKUP
o_ALTRNT_ID_TYPE_CD=ALTRN
T_ID_TYPE_CD
ALTRNT_ID=O_PAARTY_ID
10.13 Configuration
10.14 Interfaces
 None
06/20/2010 Page 26 of 29
Load ZIFSX_SALES_TEAM_PSTN Table
11.1 Overview:
 The source SIMON.ORG_UNIT_ROLE_SALES_TEAM would be read and SALES_TEAM_ID will
be looked up in the FSMSX.ORG_UNIT_ALTRNT_ID based upon the ALTRNT_ID_TYPE_CD
being set to “SLSTEAMID” load into the ZIFSX_SALES_TEAM_PSTN.
 The source SIMON.ORG_UNIT_ROLE_SALES_TEAM would be read and ORG_UNIT_ID will be

looked up in the FSMSX.ORG_UNIT_ALTRNT_ID based upon the ALTRNT_ID_TYPE_CD being
set to “ORGUNTID” load into the ZIFSX_SALES_TEAM_PSTN.
 ORG_UNIT_ID and SALES_TEAM_ID are populated from source and the remaining
header information as mapped in the STTM will be populated to the FSMSX.PSTN
table.
details for action.

 Source Database: T_SIMON
 Source Table: ORG_UNIT_ROLE_SALES_TEAM

 Target Table: ZIFSX_SALES_TEAM_PSTN


 User: dagar

 RDBMS environment : T_SIMON pointing to T_SIMON-SIMON
06/20/2010 Page 27 of 29

 This workflow calls the mappings : m_fsmsx_sales_team_pstn

Expression Name: exp_SLSTEAM_ORGUNT_ID
This will be used to convert SALES_TEAM_ID, ORG_UNIT_ID decimal
values into string values. Assign hard coded values as I mentioned below.
Values:
o_SALES_TEAM_ID=TO_CHAR(SALES_TEAM_ID)
o_ALTRNT_ID_TYPE_CD=hard coded ”SLSTEAMID”
o_ORG_UNIT_ID= TO_CHAR(ORG_UNIT_ID)
o_ALTRNT_ID_TYPE_CD1= hard coded ”ORGUNTID”
o_CRTN_ID =’FSMSETL’
o_CRTN_DT_TM= SESSSTARTTIME
o_LAST_UPDT_ID=’FSMSETL’
o_LAST_UPDT_DT_TM= SESSSTARTTIME
o_LAST_RPLCTN_DT_TM=NULL
Lookup name:lkp_SALES_TEAM_ID
Create a lookup transformation (lkp_SALES_TEAM_ID) that will do lookup
on table FSMSX. ORG_UNIT_ALTRNT_ID on column ALTRNT_ID_TYPE_CD,
ALTRNT_ID to get ORG_UNIT_ID.This value will go in SALES_TEAM_PSTN
Lookup conditions:
o_ALTRNT_ID_TYPE_CD=ALTRNT_ID_TYPE_CD
ALTRNT_ID=o_SALES_TEAM_ID
Lookup name:lkp_ORG_UNIT_ID
Create a lookup transformation (lkp_ORG_UNIT_ID) that will do lookup on
ALTRNT_ID to get ORG_UNIT_ID.This value will go in SALES_TEAM_PSTN
Lookup conditions:
o_ALTRNT_ID_TYPE_CD1=ALTRNT_ID_TYPE_CD
ALTRNT_ID= o_ORG_UNIT_ID

Field Comments
SALES_TEAM_PST
N(ORACLE) SALES_TEAM_ORG_UN FSMSX. ORG_UNIT_ALTRNT_ID.
IT_ID ORG_UNIT_ID
FSMSX. ORG_UNIT_ALTRNT_ID.
ORG_UNIT_ID ORG_UNIT_ID
SIMON.ORG_UNIT_ROLE_SALES_TEAM.JOB
JOB_TYPE_CD _TYPE_CD
SIMON.ORG_UNIT_ROLE_SALES_TEAM.EFF
PSTN_SEQ_NO CTV_DT
SIMON.ORG_UNIT_ROLE_SALES_TEAM.
EFFCTV_DT EFFCTV_DT
06/20/2010 Page 28 of 29
SIMON.ORG_UNIT_ROLE_SALES_TEAM.EXP
EXPRTN_DT RTN_DT

SALES_TEAM_PSTN Mapping
LOOKUP
o_ALTRNT_ID_TYPE_CD=ALT
RNT_ID_TYPE_CD
ALTRNT_ID=o_SALES_TEAM_
ID
TARGET
SOURCE EXPRESSION
SIMON.ORG_UNIT_ROLE_S
FSMSX.SALES_TEAM_PS
ALE_TEAM ASSIGN HARD CODED
TN
(ORACLE) VALUES
(ORACLE)
LOOKUP
o_ALTRNT_ID_TYPE_CD1=AL
TRNT_ID_TYPE_CD
ALTRNT_ID=
o_ORG_UNIT_ID
11.6 Configuration
11.7 Interfaces
 None
06/20/2010 Page 29 of 29

Zims Master Data Management For Position Design Specification

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Zims Master Data Management For Position Design Specification

Hochgeladen von

Copyright:

Verfügbare Formate

MDM POSITION Extract v1.0 Version 1.

11 Low-Level Process:[Pstn asgnmnt table]................................................................................23

12 Low-Level Process:[Sales team pstn table]............................................................................26

3 Data Model Diagram/ER Diagram

4 Data Mapping - Source to Target

Source Table: SIMON. ASGNMNT_TYPE

SOURCE (RDBMS) DATA TYPE TARGET(RDBMS) DATA TYPE

CODE_NM VARCHAR2(64) CODE_NM VARCHAR2(64)

CODE_DESC VARCHAR2(512) CODE_DESC VARCHAR2(512)

EFFCTV_DT DATE EFFCTV_DT DATE

EXPRTN_DT DATE EXPRTN_DT DATE

SORT_ORDER_NMBR NUMBER(5) SORT_ORDER_NMBR NUMBER(5)

Data types for Source and Target Tables: ASGNMNT_TYPE_CTGRY

Source Table: SIMON. ASGNMNT_TYPE_CTGRY

SOURCE (RDBMS) DATA TYPE TARGET(RDBMS) DATA TYPE

ASGNMNT_TYPE_CTGRY_CD VARCHAR2(10) ASGNMNT_TYPE_CTGRY_CD NOT NULL

CODE_NM VARCHAR2(64) CODE_NM VARCHAR2(64)

CODE_DESC VARCHAR2(512) CODE_DESC VARCHAR2(512)

EFFCTV_DT DATE EFFCTV_DT DATE

EXPRTN_DT DATE EXPRTN_DT DATE

SORT_ORDER_NMBR NUMBER(5) SORT_ORDER_NMBR NUMBER(5)

Data types for Source and Target Tables: JOB_TYPE

Source Table: SIMON. ROLE_TYPE

SOURCE (RDBMS) DATA TYPE TARGET(RDBMS) DATA TYPE

ROLE_TYPE_CD VARCHAR2(10) JOB_TYPE_CD NOT NULL

CODE_NM VARCHAR2(64) CODE_NM VARCHAR2(64)

CODE_DESC VARCHAR2(512) CODE_DESC VARCHAR2(512)

EFFCTV_DT DATE EFFCTV_DT DATE

EXPRTN_DT DATE EXPRTN_DT DATE

SORT_ORDER_NMBR VARCHAR2(8) SORT_ORDER_NMBR VARCHAR2(8)

Data types for Source and Target Tables: PSTN

Source Table: SIMON.ORG_UNIT_ROLE_HIST

SOURCE (RDBMS) DATA TYPE TARGET(RDBMS) DATA TYPE

ORG_UNIT_ID NUMBER(9) ORG_UNIT_ID NOT NULL

JOB_TYPE_CD NOT NULL

ORG_UNIT_ROLE_SEQ_NO NUMBER(9) PSTN_SEQ_NO NOT NULL

EFFCTV_DT DATE EFFCTV_DT DATE

EXPRTN_DT DATE EXPRTN_DT DATE

Data types for Source and Target Tables: PSTN_ASGNMNT

Source Table: SIMON.ORG_UNIT_ROLE_ASGNMNT

SOURCE (RDBMS) DATA TYPE TARGET (RDBMS) DATA TYPE

ORG_UNIT_ID NUMBER(9) ORG_UNIT_ID NOT NULL

ROLE_TYPE_CD VARCHAR2(10) JOB_TYPE_CD NOT NULL

ORG_UNIT_ROLE_SEQ_N NUMBER(9) PSTN_SEQ_NO NOT NULL

EFFCTV_DT DATE EFFCTV_DT NOT NULL

ORG_UNIT_ROLE_ASGNM NUMBER(9) PSTN_ASGNMNT_SEQ_ NOT NULL

ASGNMNT_TYPE_CD VARCHAR2(10) ASGNMNT_TYPE_CD VARCHAR2(10)

EXPRTN_DT DATE EXPRTN_DT DATE

Data types for Source and Target Tables:

Source Table: SIMON.ORG_UNIT_ROLE_SALES_TEAM

SOURCE (RDBMS) DATA TYPE TARGET(RDBMS) DATA TYPE

SALES_TEAM_ID NUMBER(9) SALES_TEAM_ORG_UNIT_I NOT NULL

ORG_UNIT_ID NOT NULL

ORG_UNIT_ROLE_SEQ_NO DATE PSTN_SEQ_NO NOT NULL

EFFCTV_DT DATE EFFCTV_DT NOT NULL

EXPRTN_DT DATE EXPRTN_DT DATE

5 Pre-Processing Logic for POSITION tables

7.1 Technical Description

Environment: Development, RDBMS

Environment: Development, UNIX

Environment: Development, INFORMATICA

CONNECT STRING IN INFORMATICA