EODS Master Customer Data Processing ETL Design Specification v1.1

EODS - Master Customer data processing AZAT561 Detail Design Document
AZAT561 DS EODS – Master Customer Data file

processing Detail Design Document
Project Name: Data Strategy _ Enterprise Operational Data Store

Batch – Master Customer Data Processing
Project Number: 018928
Prepared by: Raghavendra Bathula

Surya Swaroop Kumar P
Current Version: 1.0
Date: 08-July-10
Project Manager:
IT AS Manager:
EODS – Master Customer data processing Detail Design Page: 1 of 64

Allianz Proprietary and Confidential: Do not distribute
TABLE of CONTENTS
1 Overview........................................................................................................................................................... 3
2 Scope................................................................................................................................................................ 3
3 Solution Design................................................................................................................................................. 3
3.1 Process Flow Diagram............................................................................................................................ 3
3.2 Process Flow Description........................................................................................................................ 3
3.3 Traceability.............................................................................................................................................. 3
4 Design Considerations...................................................................................................................................... 3
4.1 Assumptions............................................................................................................................................ 3
4.2 Dependencies......................................................................................................................................... 3
4.3 Constraints.............................................................................................................................................. 3
4.4 Risks....................................................................................................................................................... 3
5 Data Mapping.................................................................................................................................................... 3
6 Data Sharing Agreements................................................................................................................................. 3
6.1 Input File Layouts.................................................................................................................................... 3
6.2 Output File Layouts................................................................................................................................. 3
6.3 Intra File Layouts..................................................................................................................................... 3
7 Logical View of the Design................................................................................................................................ 3
7.1 Design Components................................................................................................................................ 3
7.1.1 DataStage Sequences........................................................................................................................ 3
7.1.2 DataStage Jobs................................................................................................................................... 3
7.1.3 Shell Scripts........................................................................................................................................ 3
7.1.4 Metadata Objects................................................................................................................................ 3
7.1.5 Database Objects................................................................................................................................ 3
7.2 Error Handling Design Flow..................................................................................................................... 3
7.2.1 Exception Conditions.......................................................................................................................... 3
7.2.2 Error Codes and Messages................................................................................................................ 3
7.2.3 Restartability....................................................................................................................................... 3
8 Data and Information......................................................................................................................................... 3
8.1 Logical Data Model Reference................................................................................................................ 3
9 Environment Details.......................................................................................................................................... 3
9.1.1 File System......................................................................................................................................... 3
9.1.2 Enterprise Staging Area Files.............................................................................................................. 3
10 Logging/Auditing........................................................................................................................................... 3
11 Performance Considerations........................................................................................................................ 3
12 Reporting...................................................................................................................................................... 3
13 Security......................................................................................................................................................... 3
14 Deployment Details....................................................................................................................................... 3
14.1.1 Clear Case Reference......................................................................................................................... 3
14.1.2 Deployment Inventory......................................................................................................................... 3
14.1.3 Package List....................................................................................................................................... 3
14.1.4 Special Considerations....................................................................................................................... 3

15 Scheduling.................................................................................................................................................... 3
16 SLA............................................................................................................................................................... 3
17 Special Considerations................................................................................................................................. 3
18 Other Project Specific Requirements............................................................................................................ 3
19 Appendix....................................................................................................................................................... 3
19.1 Architectural Design Decisions Reference.............................................................................................. 3
19.2 Definitions, Acronyms, and Abbreviations................................................................................................ 3
19.3 References.............................................................................................................................................. 3
20 Approvals...................................................................................................................................................... 3
Document Revision History

Version No. Revision Date Change Description Author
1.0

1 Overview
EODS will acquire, update and store Personal Insurance Legal entity data for a policy data from PI Client. PI
Client would provide the data in a file.
This document describes the process to read files sent by PI Client, convert them to canonical format, store
in Enterprise Staging Area and finally load them to EODS database. This detail design is for loading Legal entity
information from PI Client Only. Payor Role data (Billing Account) will be filtered and would be written to a file
which will be used by Master Billing Account Setup Process.
The design demonstrated holds for the requirements attached in the appendix. Any change in the
requirements might lead to changes in this document.
2 Scope
The Scope of this document is to

 Read customer data file provided by PI Client application and load into Legal entity tables of EODS.
 MOT_LITE (“Master”) data and Billing Account Data are not in scope for this design.
3 Solution Design
The process flow diagram and a description for premium data processing are demonstrated in the subsections
below.
3.1 Process Flow Diagram

PI Scrubbed Data
Customer
Data
Canonical Data model Conversion
Apply transfromations to convert the

Move input customer data files to
input Customer data in work folder to
Archive and work folder
Canonical Data model format
Move all the files in CDM format to Enterprise Staging Area
EODS Master Legal Entity data Processing
Save the data in temporary

Read the CDM converted file LEBA _TYP = dataset which would be used
Yes
from ESA ‘PO’ for Master Billing account
data processing .
No
Join the data with the common

reference file generated while
Split the file into different files
Master Policy data processing
based on the transaction types .
which contains the database
internal ids
New or Renewal Business Endorsements processing

processing (Legal entity changes )
EODS
Database

3.2 Process Flow Description
1. Customer data files from PI Client will be available in source directory everyday by <TBD> Time. Master
Legal Entity Data Load process reads Customer data from Source directory copy them to work folder and
move to Archive folder.
2. Read the customer data files from Work folder and convert each one of them to Canonical format. Store
this file in Enterprise Staging Area.
3. Read CDM converted files from Enterprise Staging Area, and join the filtered records with the global
reference dataset generated during the Master policy data, to get the database ids generated during
creating policies in EODS
4. Check if the records whose LEBA_TYP = ‘PO’. If so save those records into a temporary file which would
be used for Master Billing account processing. Else, filter those records which would be processed in
further steps.
5. Join the filtered records with the global reference dataset generated during the Master policy data, to get
the database ids generated during creating policies in EODS.
6. Split the file into different streams based on the Transaction type. The different streams will be
New and renewal polices – Processed together
Endorsements – Legal entity changes
7. For New and Renewal Policies, legal entities would be added to the existing legal entities of EODS
database. Business action entry created during policy creation would be used here.
8. For all endorsements, update the EODS database with the changes. Add an entry to BUSINESS ACTION
table to track the endorsements applied on the EODS database. If we have multiple endorsements for a
same policy on a same date then use different BA_SEQ_NBR for each record.
3.3 Traceability
Traceability.xls
4 Design Considerations
4.1 Assumptions
# Assumption Comments
1 Policy information would be present in EODS We will be running Master Policy data processing
before this process starts. preceding Legal entity data processing.
2 PI Client will send all roles on a Policy without All Roles on a Policy would be sent to EODS for New
dropping any roles for New and Renewal and Renewal transactions.
Transactions.
3 EODS will NOT perform any data Validation. EODS will redirect any data issues if they are not
associated with transformations to the Billing and
Legacy systems to coordinate to fix.
4 EODS receive a file from PI Client everyday to EODS will check for the file at a specified time
load Customer data. <TBD>.

4.2 Dependencies
# Dependency Comments
1 Master Legal entity data inserts in the EODS Master policy data processing would insert data into
database would be performed after the policy tables for new policies which would be used in
corresponding Master Policy data is available this process.
in EODS.
4.3 Constraints
# Constraint or Issues Impact
N/A
4.4 Risks
# Risk Mitigation Strategy
1 Data discrepancies in PI Client will exist in All data in-consistencies should be fixed at PI Client
EODS. end.

5 Data Mapping
Mapping for converting data from source to Canonical format
EODS_Master_PI_PR
OCESSING_MAPPING_Src_to_MDR_V1.0.xls
Mapping for converting data from Canonical format to EODS database
EODS_Master_PROC
ESSING_MAPPING_MDR_to_EODS_V1.0.xls
6 Data Sharing Agreements
6.1 Input File Layouts
Input_file_format_PI
.xls
6.2 Output File Layouts

None
6.3 Intra File Layouts
Canonical data format for PI Customer data file
MDR_Fmt_PI.xls
7 Logical View of the Design

7.1 Design Components
7.1.1 DataStage Sequences
Sequence_LE.xls

7.1.2 DataStage Jobs
7.1.2.1 Audit Entry – Process Start
Job # 1 – Xfm_EODS_MASTER_ADT_LOG_00
Purpose:
This job is to log an audit message into EODS processing Audit table.
EODS process will insert an entry into the Audit_trail_log table for auditing and validation purpose.
This is a common job that is used to set the value of CRTE_TS, LAST_UPDT_TS and PROCESS_STATUS fields
in the table.
Job Parameters:
SNO Parameter Name Type Description Value

1 G_S_DBSchName String Database Name EODS
2 G_S_User String Database User Name Eodsusr
3 G_S_Password String Database Password **********
4 G_S_DBServerNam DEDS0D01
e String Database Server Name
The following steps describe the Process flow in the job:
Step Description
Insert a log record into Audit_trail_log table saying “EODS – MASTER file” processing has started.
Populate the Audit_trail_log:
 CRTE_TS as “Current System Timestamp”
 And I_rec_actv to ‘Y’
 SEQ_FLOW_NM to to ”Master_Legal_Entity_Data_Load”
 PROCESS_STATUS to ‘S’ (Started)
1  LAST_UPD_TS to “Current System Timestamp”
For more details about the job refer to the common flow section.
7.1.2.2 Creating CDM format
Job # 2 - Xfm_PI_MDR_Transform_00
Purpose:

This Job will transform the input PI customer data into Canonical data model format by applying the
transformation rules as said in the mapping document..
SN Type Value
O Parameter Name Description
1 G_S_Wrk_Dir Strin /Staging/eods/work/
g Work Directory
2 G_S_Cdm_Master_D /
ir Strin esa/eods/master/canonica
g Master Staging Area l
Step Description
1 Read the flat file received from PI client.
2 Implement transformations as mentioned in the data mapping sheet.

Impement mapping between (LEAD_TYP, SUB-CLT-REL-TYPE) and (BA_ENTRY_SYS_CD,
3 SUB-ORIGINATING-SYST) as mentioned in the data mapping sheet.
4 Derive LEAR_TYP and LEBA_TYP. Refer Mapping sheet for the transformation.
Store the transformed data into a temporary dataset “DS_PI_MDR.ds” and a temporary CSV file
5 “Seq_PI_MDR.csv” for further processing.
7.1.2.3 Merging Policy data with Customer data
Job # 3 - Xfm_MDR_Merge_00
Purpose:
This Job will merge the Legal entity canonical data model format with the dataset from Master policy data
processing, which contains the database sequences like POL_SYS_ID, BA_ID, AGMT_SYS_ID
Job parameters:

1 G_S_Wrk_Dir String Work Directory /Staging/eods/work/
Step Description
1 Read all the records from the DS_PI_MDR.ds.
Join the records in step 1 and the records in the dataset “DS_AgreementGlobalRef.ds”,
2 generated during “Master policy Data processing” using the POL_ID

Filter all those records which have LEBA_TYP as ‘PO’, save these records in a temporary
dataset (DS_MasterBillingAccountRec.ds) which would be used for processing in Master Billing
Account data processing. For all those records which do not have LEBA_TYP use them in next
3 step. Create a Temp data for all records having LEAR_TYP roles.
 Save all the records which are matching and has the UBA_TYP as ‘ISS’ and
UBA_RSN_CD = ‘NEW’ or “RENEWAL’ into DS_CutomerNew.ds
 Save all the records which are matching and has the UBA_TYP as ‘END’ and
4 UBA_RSN_CD = ‘CHGNM’, ‘CHGAD’, ‘CHGBN’ into DS_CustomerEndorsement.ds
7.1.2.4 Loading PI Client New business data
Job #4 – Xfm_PI_EODS_RA_Transform_00 (RA-Risk Address)

Purpose:
The purpose of this job is to save the Risk address details from the transformed CDM data into temporary
datasets which would be used to load ADDRESS and PHYSICAL_LOCATION_SAR_ASSN tables in the
subsequent jobs.
Job Parameters:

1 G_S_Wrk_DataSet_D /Staging/eods/dst/
ir String Work Directory
Step Description
1 Read the records in the dataset DS_CustomerNew.ds.
Filter all the records which have LEAD_TYP as ‘PRIR’ (LEAD_TYP derived in CDM Conversion
2 process.)
 For all the filtered records from step 2, we need to create an entry in ADDRESS table. Create
system generated sequence number and assign it to ADDRESS_SYS_ID.
 Write all the contents into a temporary dataset “DS_PI_InsertAddress” with data from
previous step according to the data mapping document. This dataset would be used to insert
into ADDRESS table.
 To Populate CANP_CD perform the following transformation.
3 If CTRY_CD=”CAN” then Populate ST_CD else NULL
 For all the filtered records from step 2, we need to create an entry in
PHYSICAL_LOCATION_SAR_ASSN table. Create system generated sequence number and
assign it to PLOC_SYS_ID.
 Use the ADDR_SYS_ID from step 3 and lookup the input data with data from step 4 using
SAR_TYP as lookup key and get the SAR_SYS_ID and save all the contents into a
temporary dataset “DS_PI_InsertPLOC” according to the data mapping document. This
4 dataset would be used for inserting data into PHYSICAL_LOCATION_SAR_ASSN table.

Job #5 – Put_ADDRESS_EODS_LOAD_RA_00
Purpose:
The purpose of this job is to read the dataset “DS_PI_InsertAddress” and populate the ADDRESS table. Bulk
Load will be used to load the data into the database.
Job Parameters:

4 G_S_DBServerName String Database Server Name DEDS0D01
Step Description
1 Use dataset stage to read the DS_PI_InsertAddress file.
2 Use DB2 stage and load all the contents from step 1 into ADDRESS table.
Job #6 – Put_SUBJ_AT_RSK_EODS_LOAD_RA_00 (Deleted)

Purpose:
The purpose of this job is to read the dataset “DS_PI_InsertSAR” and populate the SUBJECT_AT_RISK table.
Bulk Load will be used to load the data into the database.
Job Parameters:

5 G_S_Wrk_Dir String Work Directory /Staging/eods/dst/
Step Description
1 Use dataset stage to read the DS_PI_InsertSAR file.

2 Use DB2 stage and load all the contents from step 1 into SUBJECT_AT_RISK table.
Job #7 – Put_PHY_LOC_SAR_ASSN_EODS_LOAD_RA_00
Purpose:
The purpose of this job is to read the dataset “DS_PI_InsertPLOC” and populate the
PHYSICAL_LOCATION_SAR_ASSN table. Bulk Load will be used to load the data into the database.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_PI_InsertPLOC file.
2 Use DB2 stage and load all the contents from step 1 into PHYSICAL_LOCATION_SAR_ASSN table.
New Job - Xfm_EODS_Legal_Entities_PI_AR_01

Note: The target dataset of the job Xfm_EODS_Legal_Entities_PI_AR_01 being used in the below job
Xfm_EODS_Legal_Entities_PI_AR_02, so we created the new job
Purpose:
The purpose of this job is to retrieve data related to columns LGLE_ID, LGLE_SYS_ID and LGLE_EFF_DT from
LEGAL_ENTITY table.
Job Parameters:


Step Description
Execute the following query in DB2
SELECT LGLE_SYS_ID,
LGLE_ID,
LGLE_EFF_DT
FROM LEGAL_ENTITY
1 WHERE LGLE_EXP_DT >= #Current_Processing_Date#
2 Use Dataset stage and load all the contents from step 1 into dataset DS_LGLEDB.ds
Job #8 – Xfm_EODS_Legal_Entities_PI_AR_02 (AR- Agreement Role)
Purpose:
The purpose of this job is to create a new system generated sequence number in EODS for the LGLE_ID from the
input dataset if that LGLE_ID is not present in EODS but if the LGLE_ID is present in EODS then get the
LGLE_SYS_ID from the dataset. Additionally this job would also create a temporary dataset containing the legal
entities which are not present in EODS. This dataset would be used to insert into LEGAL_ENTITY table.
Job Parameters:

Step Description
1 Read all the records in the dataset DS_CustomerNew.ds.
Filter all the records which have the LEAR_TYP in (NIN , MT, SMT , LEN, OPER,CI ) AND
2 LEAD_TYP <>"PRIR"
Join the records from step 2 and dataset DS_LGLEDB.ds (target dataset of job
Xfm_EODS_Legal_Entities_PI_AR_01) using LGLE_ID as joining key. Data will be partitioned and
3 sorted on LGLE_ID in DataStage environment.
All the non matching records should be inserted into LEGAL_ENTITY table. Create a system
generated sequence number and assign it to LGLE_SYS_ID and save the data into a temp dataset
4 “DS_InsertLGLE.ds”
5 For all the matching records, get the LGLE_SYS_ID from the step 3.
Merge these details into a temporary dataset “DS_PI_Customer_LGLE.ds”. This dataset will be used
6 as a reference to get LGLE_SYS_ID.
Job #9 – Xfm_EODS_LE_SA_PI_AR_Transform_00

Purpose:
This job would be used to transform the input PI data and create temporary datasets which would be used to
load the EODS
Job Parameters:

Step Description
1 Read all the records from the dataset “DS_PI_Customer_LGLE.ds”.
 For all the records from step 1, we should create an entry in LEGAL_ENTITY_ROLE table.
Create system generated sequence number and assign to LERL_SYS_ID and write the input
data into a temporary dataset “DS_LGRLInsert.ds” according to the data mapping document.
 If LGLE_TYP is ‘BS’ create an entry in BUSINESS_ENTITY table. Create a system

generated sequence number and assign to BEN_SYS_ID and write the input data into a
temporary dataset “DS_BENInsert.ds” according to the data mapping document.
 If LGLE_TYP is ‘IN’ create an entry in INDIVIDUAL_PERSON_NAME table. Create a system

generated sequence number and assign it to IPN_SYS_ID and write the input data into a
temporary dataset “DS_IPNInsert.ds” according to the data mapping document.
 If input LEAR_TYP = (‘NIN’ OR ‘MT’ OR ‘SMT’ OR ‘TMT’ OR ‘OPER’ OR ‘LEN’ OR ‘CI’), we

should insert data into LEGAL_ENTITY_AGREEMENT_ROLE table. Create a system
generated sequence number and assign it to LEAR_SYS_ID and write the input data into a
temporary dataset “DS_LEARInsert.ds” according to the data mapping document.
 If input LEAR_TYP in (‘MT’, ‘SMT’,’TMT’) And LOAN_ID Exists then create entry in
CLIENT_BANK_ASSN table. Create a system generated sequence number and assign it to
CB_SYS_ID and write the input data into a temporary dataset “DS_CBInsert.ds” according to
the data mapping document.
 If input LEAD_TYP = ‘INHA’ or ‘BSM’, then create an entry in ADDRESS table. Create a
system generated sequence number and assign it to ADDR_SYS_ID and write the input data
into a temporary dataset “DS_PI_AddrInsert.ds” according to the data mapping document.
 For all the records inserted into ADDRESS table, an entry should be made in
LEGAL_ENTTY_ADDRESS_ASSN table. Create a system generated sequence number and
assign it to LEAD_SYS_ID and write the input data into a temporary dataset
2 “DS_LEADInsert.ds” according to the data mapping document.

7.1.2.5 Load jobs: Legal entity New business
The following jobs would be used for loading all the Legal entity tables for all the agreement role data.
Job #10 – Put_ LEGAL_ENTITY_LOAD_AR_10

Purpose:
The purpose of this job is to read the dataset “DS_PI_Customer_LGLE.ds” and populate the LEGAL_ENTITY
table. Bulk Load will be used to load the data into the database.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_PI_Customer_LGLE.ds file.
2 Use DB2 stage and load all the contents from step 1 into LEGAL_ENTITY table.
Job #11 – Put_ LEGAL_ENTITY_ROLE_LOAD_AR_11

Purpose:
The purpose of this job is to read the dataset “DS_LGRLInsert.ds” and populate the LEGAL_ENTITY_ROLE
Job Parameters:


Step Description
1 Use dataset stage to read the DS_LGRLInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into LEGAL_ENTITY_ROLE table.
Job #12 – Put_BUSINESS_ENTITY_LOAD_AR_12

Purpose:
The purpose of this job is to read the dataset “DS_BENInsert.ds” and populate the BUSINESS_ENTITY table.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_BENInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into BUSINESS_ENTITY table.
Job #13 – Put_INDIVIDUAL_PERSON_NAME_LOAD_AR_13

Purpose:
The purpose of this job is to read the dataset “DS_IPNInsert.ds” and populate the INDIVIDUAL_PERSON_NAME
Job Parameters:


Step Description
1 Use dataset stage to read the DS_IPNInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into INDIVIDUAL_PERSON_NAME table.
Job #14 – Put_ LEGAL_ENTITY_AGREEMENT_ROLE_LOAD_AR_14

Purpose:
The purpose of this job is to read the dataset “DS_LEARInsert.ds” and populate the
LEGAL_ENTITY_AGREEMENT_ROLE table. Bulk Load will be used to load the data into the database.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_LEARInsert.dsfile.
Use DB2 stage and load all the contents from step 1 into LEGAL_ENTITY_AGREEMENT_ROLE
2 table.
Job #15 – Put_CLIENT_BANK_ASSN_LOAD_AR_15

Purpose:
The purpose of this job is to read the dataset “DS_CBInsert.ds” and populate the CLIENT_BANK_ASSN table.
Job Parameters:


Step Description
1 Use dataset stage to read the DS_CBInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into CLIENT_BANK_ASSN table.
Job #16 – Put_ADDRESS_LOAD_AR_16

Purpose:
The purpose of this job is to read the dataset “DS_PI_AddrInsert.ds” and populate the ADDRESS table. Bulk Load
will be used to load the data into the database.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_PI_AddrInsert.ds file.
Job #17 – Put_LEGAL_ENTTY_ADDRESS_ASSN_LOAD_AR_17

Purpose:
The purpose of this job is to read the dataset “DS_LEADInsert.ds” and populate the
LEGAL_ENTTY_ADDRESS_ASSN table. Bulk Load will be used to load the data into the database.
Job Parameters:



Step Description
1 Use dataset stage to read the DS_LEADInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into LEGAL_ENTTY_ADDRESS_ASSN table.
7.1.2.6 Endorsements – Risk address changes
Job #18 – Xfm_EODS_PI_END_RA_Transform (RA-Risk Address)

Note: The Xfm_EODS_PI_END_RA_Transform is split into two jobs
1) Xfm_EODS_PI_END_RA_Transform_00 and
2) Xfm_EODS_PI_END_RA_Transform_01
Here Xfm_EODS_PI_END_RA_Transform_00 output dataset DS_CutomerEndorsement_NewBa.ds, These
dataset is input to the following job Xfm_EODS_PI_END_RA_Transform_01
Purpose:
This job would transform the input data and save the data into temporary datasets which would be used for
loading the tables.

5 G_s_Work_DataSet_D /Staging/eods/dst/
The following would give the description of the job.

Note 1: Here step 2 is deleted because instead of table we can use the common dataset
DS_BusinessAction_Agg.ds
Note 2: Here Subject_At_Risk Operation is not required
Ste
p Description

Read the input dataset “DS_CutomerEndorsement.ds” and filter all the records which have UBA_TYP =
1 END and UBA_RSN_CD = CHGADDR, DELGARG, CHGGARG, ADDGARG and LEAD_TYP as ‘PRIR’
Execute the following query in database
SELECT BA_ID,
MAX(BA_SEQ_NBR),
BA_EFF_DT
FROM BUSINESS_ACTION
2 GROUP BY BA_ID, BA_EFF_DT
Lookup all the records from step1 in the data in dataset DS_BusinessAction_Agg.ds using BA_ID,
3 BA_EFF_DT as join key and get the BA_SEQ_NBR.
 For all the records from step 3, we should insert data into BUSINESS_ACTION table. So insert
into the table by incrementing the BA_SEQ_NBR. Please refer the data mapping sheet for a
detailed mapping. Save all the contents in a temporary dataset “DS_RA_BAInsert.ds”
 For all the records from step 3, we should insert data into ADDRESS table. Create a system
generated number and assign the value to ADDR_SYS_ID. Save the contents from the input file
to a temporary dataset “DS_RA_ADDRInsert.ds” according to the data mapping document. Use
BA_ID, BA_EFF_DT and BA_SEQ_NBR from previous sub step.
 For all the records from step 3, for each unique occurrence of SAR_TYP, we have to insert into
SUBJECT_AT_RISK table. Create a system generated sequence number and assign it to
SAR_SYS_ID. Save the contents from the input file to a temporary dataset
“DS_RA_SARInsert.ds” according to the data mapping document. Use BA_ID, BA_EFF_DT and
BA_SEQ_NBR from previous sub step.
 For all the records from step 3, we should insert data into PRIMARY_SAR_LOCATION_ASSN
table. Create a system generated number and assign the value to PLOC_SYS_ID. Save the
contents from the input file to a temporary dataset “DS_RA_PLOSInsert.ds” according to the
data mapping document. Use Business action information and subject at risk information from
4 previous sub steps.
Job #20 – Put_EODS_PI_END_RA_BA_Insert

Purpose:
This job would insert data into BUSINESS_ACTION table from the dataset
“DS_CutomerEndorsement_NewBa.ds”.

Ste
p Description

1 Read the input dataset “ DS_CutomerEndorsement_NewBa.ds.

2 For all the records, insert into BUSINESS_ACTION table.
Job #19 – Put_EODS_PI_END_RA_update (RA-Risk Address) This is for Physical Location Sar Association
Update.
Put_EODS_PI_END_RA_update_01(New Job) This is for Address Update
Purpose:
This job would expire the old records in tables PRIMARY_SAR_LOCATION_ASSN and ADDRESS for all the
records which have changes in risk address.

Ste
p Description
Read the input dataset “DS_CutomerEndorsement_NewBa.ds” and filter all the records which have
UBA_TYP = END and UBA_RSN_CD = CHGADDR, DELGARG, CHGGARG, ADDGARG and
1 LEAD_TYP as ‘PRIR’
2 For all the filtered records,
 Update PRIMARY_SAR_LOCATION_ASSN table using AGMT_SYS_ID and AGMT_EFF_DT
from the input dataset.
Following columns would be updated:
PLOC_EXP_DT
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
Please refer the data mapping sheet for detailed mapping.
 Update ADDRESS table using AGMT_SYS_ID and AGMT_EFF_DT from the
PHYSICAL_LOCATION_SAR_ASSN Table
ADDR_EXP_DT
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS

REC_STUS_CD
Job #21 – Put_EODS_PI_END_RA_ADDR_Insert

Purpose:
This job would insert data into ADDRESS table from the dataset “DS_RA_ADDRInsert.ds”.

Ste
p Description
1 Read the input dataset “ DS_RA_ADDRInsert.ds .
2 For all the records, insert into ADDRESS table.
Job #22 – Put_EODS_PI_END_RA_SAR_Insert (Deleted this job)

Purpose:
This job would insert data into SUBJECT_AT_RISK table from the dataset “DS_RA_SARInsert.ds”.

Ste
p Description
1 Read the input dataset “DS_RA_SARInsert.ds” .
2 For all the records, insert into SUBJECT_AT_RISK table.

Job #23 – Put_EODS_PI_END_RA_PLOC_Insert

Purpose:
This job would insert data into PHYSICAL_LOCATION_SAR_ASSN table from the dataset
“DS_RA_PLOSInsert.ds”.

Ste
p Description
1 Read the input dataset “DS_RA_PLOSInsert.ds .
2 For all the records, insert into PHYSICAL_LOCATION_SAR_ASSN table.
7.1.2.7 Endorsements – Legal entity ADD
Job #24 – Xfm_PI_EODS_END_Transform_24 (END - Endorsements)

Purpose:
The purpose of this job is to filter the input records into three separate datasets which should be used in adding,
update or expiring legal entity datasets in EODS.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_CutomerEndorsement.ds dataset.
2  If the UBA_TYP=’END’ and UBA_RSN_CD IN (‘ADDLEN’, ‘ADDMTGI’, ‘ADDOPR’ is ADD,
then the legal entity should be added, write this data into a temp dataset
DS_Cust_End_ADD_LE.ds
 If the UBA_TYP = ‘END’ and UBA_RSN_CD is CHGNM, CHGAD, CHGBA then there is a
change on the legal entity, write this data into a temp dataset DS_Cust_End_Chng_LE.ds

 If the UBA_TYP=’END’ and UBA_RSN_CD IN ( DELLEN, DELMTGI) then the legal entity
should be expired in EODS, write this data into a temp dataset DS_Cust_End_Del_LE.ds
Job #25 – Get_BA_EODS_END_READ_25

Purpose:
The purpose of this job is to get the contents of the BUSINESS_ACTION table which would be used in the
succeeding jobs.
Job Parameters:

Step Description
Use the following query to get the BUSINESS_ACTION table
SELECT
BA_ID,
BA_EFF_DT,
BA_SEQ_NBR
1 WHERE BA_EXP_DT > Scheduled job run date
Use the aggregator stage and get the maximum BA_SEQ_NBR grouped by BA_ID, BA_EFF_DT
Group by
BA_ID, BA_EFF_DT
Aggregate function
2 MAX(BA_SEQ_NBR)
3 Save the above data in a dataset “DS_BusinessAction_Agg.ds”
Job # – Get_EODS_LE_End_Read_26_02 (NEW JOB)

Purpose:
The purpose of this job is to get the contents of the LEGAL_ENTITY table which would be used in the succeeding
jobs.
Job Parameters:


Step Description
Use the following query to get the LEGAL_ENTITY table
SELECT
LGLE_ID,
LGLE_EFF_DT,
LGLE_SYS_ID
FROM LEGAL_ENTITY
1
2 Save the above data in a dataset “ DS_LegalEntity.ds”
Job #26 – Xfm_EODS_LE_END_Transform_00

Note : This job is split into two jobs
Xfm_EODS_LE_END_Transform_26_00
Xfm_EODS_LE_END_Transform_26_01
The output of Xfm_EODS_LE_END_Transform_26_00 is DS_Cust_End_ADD_LE_With_Ba.ds .
This Dataset is input to the Xfm_EODS_LE_END_Transform_26_01
Purpose:
The purpose of this job is to transform the input dataset containing the legal entities that are to be added and save
the data into temporary datasets which would be further used for loading into tables.
Job Parameters:

Step Description

1 Read all the contents of the DS_Cust_End_ADD_LE.ds

2  For all the records in step 1, we need to insert records into BUSINESS_ACTION table. For
the columns BA_ID, BA_EFF_DT from the input and lookup in the dataset
“DS_BusinessAction_Agg.ds” and get the BA_SEQ_NBR. Increment this number and save
the details in a temporary dataset “DS_Cust_BAInsert.ds”. Detailed mapping is present in the
data mapping sheet.
 For all the records in step1, check if Legal Entity already exists in LEGAL_ENTITY Table. If it
exists get LGLE_SYS_ID else we need to insert records into LEGAL_ENTITY table. Create a
system generated sequence number and assign it to LGLE_SYS_ID. Save all the contents
that are to be saved in LEGAL_ENTITY table, according to the data mapping document, in a
temporary dataset “DS_Cust_LGLEInsert.ds”. Use the BUSINESS_ACTION details to be
added from the previous sub-step.
 For all the records in step 1, we need to insert records into LEGAL_ENTITY_ROLE table.
Create a system generated sequence number and assign it to LERL_SYS_ID. Save all the
contents that are to be saved in LEGAL_ENTITY_ROLE table, according to the data
mapping document, in a temporary dataset “DS_Cust_LERLInsert.ds”. Use the
BUSINESS_ACTION details and LEGAL_ENTITY details to be added from the previous sub-
steps.
 If LGLE_TYP is ‘BS’, then we should insert records into BUSINESS_ENTITY table. Create a
system generated sequence number and assign it to BEN_SYS_ID. Save all the contents
that are to be saved in BUSINESS_ENTITY table, according to the data mapping document,
in a temporary dataset “DS_Cust_BENInsert.ds”. Use the BUSINESS_ACTION details,
LEGAL_ENTITY details and LEGAL_ENTITY_ROLE details from the previous sub steps.
 If LGLE_TYP is ‘IN’, then we should insert records into INDIVIDUAL_PERSON_NAME table.
Create a system generated sequence number and assign it IPN_SYS_ID. Save all the
contents that are to be saved in INDIVIDUAL_PERSON_NAME table, according to the data
mapping document, in a temporary dataset “DS_Cust_IPNInsert.ds”. Use the
BUSINESS_ACTION details, LEGAL_ENTITY details and LEGAL_ENTITY_ROLE details
from the previous sub steps.
 For every record from step 1, where LEAR_TYP is present, we have to make an entry in
LEGAL_ENTITY_AGREEMENT_ROLE table. Create a system generated sequence number
and assign it to LEAR_SYS_ID. Save all the contents that are to be saved in
LEGAL_ENTITY_AGREEMENT_ROLE table, according to the data mapping document, in a
temporary dataset “DS_Cust_LEARInsert.ds”. Use the BUSINESS_ACTION details,
 For all the records from step 1, if LEAR_TYP is ‘MT’ or ‘SMT’ or ‘TMT’ and if there is value in
LOAN_NBR, then we need to create an entry in CLIENT_BANK_ASSN table. Create a
system generated sequence number and assign it to CB_SYS_ID. Save all the contents that
are to be saved in CLIENT_BANK_ASSN table, according o the data mapping document, in
a temporary dataset “DS_CustCBInsert.ds”. Use the BUSINESS_ACTION details,
 For all the records where the LEAD_TYP = ‘INHA’ or ‘BSM’ then we need to create an entry
in ADDRESS table. Create a system generated sequence number and assign that value to
ADDR_SYS_ID. Save all the contents that are to be saved in ADDRESS table, according to
the mapping document, in a temporary dataset “DS_CustADDRInsert.ds”. Use the
 For all the records where the LEAD_TYP = ‘INHA’ or ‘BSM’ then we need to create an entry
in LEGAL_ENTITY_ADDRESS_ASSN table. Create a system generated sequence number
and assign that value to LEAD_SYS_ID. Save all the contents that are to be saved in
LEGAL_ENTITY_ADDRESS_ASSN table, according to the mapping document, in a
temporary dataset “DS_CustLEADInsert.ds”. Use the ADDRESS details,

Job #27 – Put_ BUSINESS_ACTION_LOAD_LE_END_27

Purpose:
The purpose of this job is to read the dataset “DS_Cust_BAInsert.ds” and populate the BUSINESS_ACTION
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_BAInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into BUSINESS_ACTION table.
Job #28 – Put_ LEGAL_ENTITY_LOAD_ LE_END _28

Purpose:
The purpose of this job is to read the dataset “DS_Cust_LGLEInsert.ds” and populate the LEGAL_ENTITY table.
Job Parameters:


Step Description
1 Use dataset stage to read the DS_Cust_LGLEInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into LEGAL_ENTITY table.
Job #29 – Put_LEGAL_ENTITY_ROLE_LOAD_LE_END_29

Purpose:
The purpose of this job is to read the dataset “DS_Cust_LERLInsert.ds” and populate the LEGAL_ENTITY_ROLE
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_LERLInsert.ds file.
Job #32 – Put_ LEGAL_ENTITY_AGREEMENT_ROLE_LOAD_LE_END_32

Purpose:
The purpose of this job is to read the dataset “DS_Cust_LEARInsert.ds” and populate the
LEGAL_ENTITY_AGREEMENT_ROLE table. Bulk Load will be used to load the data into the database.
Job Parameters:


Step Description
1 Use dataset stage to read the DS_Cust_LEARInsert.ds file.
Join this data with Billing Account data (LEBA_TYP=’PO’) on LGLE_ID and if we find a match then
2 set LEAR_PAYOR_IND=’Y’ Else ‘N’
3 table.
Job #31 – Put_INDIVIDUAL_PERSON_NAME_LOAD_LE_END_31

Purpose:
The purpose of this job is to read the dataset “DS_Cust_IPNInsert.ds” and populate the
INDIVIDUAL_PERSON_NAME table. Bulk Load will be used to load the data into the database.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_IPNInsert.ds file.
Job #30 – Put_ BUSINESS_ENTITY_LOAD_LE_END_30

Purpose:
The purpose of this job is to read the dataset “DS_Cust_BENInsert.ds” and populate the BUSINESS_ENTITY
Job Parameters:


Step Description
1 Use dataset stage to read the DS_Cust_BENInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into BUSINESS_ENTITY table.
Job #33 – Put_ LEGAL_ CLIENT_BANK_ASSN_LOAD_LE_END_33
Purpose:
The purpose of this job is to read the dataset “DS_CustCBInsert.ds” and populate the CLIENT_BANK_ASSN
Job Parameters:

Step Description
1 Use dataset stage to read the DS_CustCBInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into CLIENT_BANK_ASSN table.
Job #34 – Put_ LEGAL_ADDRESS_LOAD_LE_END_34

Purpose:
The purpose of this job is to read the dataset “DS_CustADDRInsert.ds” and populate the ADDRESS table. Bulk
Load will be used to load the data into the database.
Job Parameters:



Step Description
1 Use dataset stage to read the DS_CustADDRInsert.ds file.
Derive the CANP_CD column as:
2 If CTRY_CD=’CAN’ then ST_CD else nothing
Derivation for LEAD_CAREOF_NM is as follows:

Split the records into three streams
(i) LEAR_TYP=NIN
(ii) LEAR_TYP=CI
(iii) Others (Except NIN all others which include LEAR_TYP=’CI”)
For Stream ‘Others’ (include LEAR_TYP=CI) LEAD_CAREOF_NM will be ‘NULL’ .
For LEAR_TYP= NIN Join the data with LEAR_TYP=CI data on LGLE_ID and if we found a match
3 (NIN – LEGLE_ID = CI – LGLE_ID) then BEN_NAME from CI record (stream LEAR_TYP=CI)
Job #35 – Put_LEGAL_ENTITY_ADDRESS_ASSN_LOAD_LE_END_35

Purpose:
The purpose of this job is to read the dataset “DS_CustLEADInsert.ds” and populate the
LEGAL_ENTITY_ADDRESS_ASSN table. Bulk Load will be used to load the data into the database.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_CustLEADInsert.ds file.
2 Use DB2 stage and load all the contents from step 1 into LEGAL_ENTITY_ADDRESS_ASSN table.

Job #27 – Xfm_EODS_Cust_END_LE_ADD_BA_Merge_27_01(New Job)

Purpose:
The purpose of this job is to Merge the Business Action details for dataset “DS_Cust_BAInsert.ds” and
DS_BusinessAction_Agg.ds populate the data into Dataset DS_Cust_End_ADD_LE_With_Ba_Data.ds . Because
these Dataset is used in the succeeding jobs in a Legal Entity Delete.
Job Parameters:

Step Description
1 Use dataset stage to read the data from DS_Cust_BAInsert.ds , DS_BusinessAction_Agg.ds files
2 Save the step 1 data into Dataset DS_Cust_End_ADD_LE_With_Ba_Data.ds.
7.1.2.8 Endorsements – Legal entity DELETE
Job #36 – Xfm_EODS_CUST_LE_Del_36_01 (New Job)

Purpose:
The purpose of this job is to read the data from dataset DS_Cust_End_Del_LE.ds is join with
DS_Cust_End_ADD_LE_With_Ba_Data.ds It will get the BUSINESS_ACTION Load Data.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_End_Del_LE.ds file.
Join this data with Legal Entity Add data on BA_ID and if we find a New records loaded into a
2 temporary datasets
3 Save the Step 2 data Into a DS_Cust_End_Del_BAInst.ds, DS_Cust_End_Del_LE_with_BA.ds
Job #36 – Put_EODS_CUST_LE_Del_BA_Load_36_02

Purpose:
The purpose of this job is to load BUSINESS_ACTION table for all the legal entities which have been deleted.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_End_Del_BAInst.ds
Note : Deleted the below description …………step 1,2,&3
Step Description
1 Read the data from the dataset DS_Cust_End_Del_BAInst.ds

SELECT BA_ID,
BA_EFF_DT
MAX(BA_SEQ_NBR)
GROUP BY BA_ID,
BA_EFF_DT
2 WHERE BA_EXP_DT > #Scheduled run date#
For all the records from step 1 lookup the data in the data from the step 2 using BA_ID, BA_EFF_DT
increment the BA_SEQ_NBR by one and insert the same in BUSINESS_ACTION table. Detailed
mapping is present in the data mapping sheet.
Also save the new BA_SEQ_NBR along with the columns from step1 in
3 DS_Cust_End_Del_LE_with_BA.ds
Job #37 – Get_EODS_LEAR_Read_37

Purpose:
The purpose of this job is to get all active records from LEGAL_ENTITY_AGREEMENT_ROLE table to find the
Legal Entity Roles and legal entity IDs for an agreement.

Job Parameters:

Step Description
SELECT
AGMT_SYS_ID,
AGMT_EFF_DT.
LERL_SYS_ID,
LERL_EFF_DT,
LGLE_SYS_ID,
LGLE_EFF_DT,
LGLE_ID
FROM LEGAL_ENTITY_AGREEMENT_ROLE
1 WHERE LEAR_EXP_DT > #Scheduled run date#
2 Get the data from step1 and write into a temp Dataset DS_CustLEARReference.ds
Job #38 – Xfm_EODS_LE_SA_LE_Del_Update_38_01
Purpose:
The purpose of this job is to update LEGAL_ENTITY tables for all the legal entities which have been deleted.
Records would be updated in the following tables LEGAL_ENTITY_AGREEMENT_ROLE,
LEGAL_ENTITY_ROLE, LEGAL_ENTITY_ADDRESS_ASSN
Job Parameters:

5 G_s_Work_DataSet_D String Work Directory /Staging/eods/dst/

ir

NOTE : In this Job Step 5 is deleted
Step Description
1 Read the data from the dataset DS_Cust_End_Del_LE_with_BA.ds
Join the data from step 1 with data from dataset DS_CustLEARReference.ds on AGMT_SYS_ID,
2 AGMT_EFF_DT
Use BUSINESS_ACTION table keys inserted in Put_EODS_CUST_LE_Del_BA_Load_36_02 Job
3 for all the tables below.
For the records in step2
Update (expire) LEGAL_ENTITY_AGREEMENT_ROLE table. Following columns would be updated:
LEAR_EXP_DT
BA_ID
BA_EFF_DT
BA_SEQ_NBR
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
And these data should be loaded into a temporary dataset DS_LEAR_Upd.ds
3 Detailed mapping is found in the mapping document
Update (expire) LEGAL_ENTITY_ROLE table. Following columns would be updated:
LERL_EXP_DT
BA_ID
BA_EFF_DT
BA_SEQ_NBR
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
And these data should be loaded into a temporary dataset DS_LERL_Upd.ds
5 Update (expire) ADDRESS table. Following columns would be updated:
ADDR_EXP_DT
BA_ID
BA_EFF_DT
BA_SEQ_NBR
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD

Detailed mapping is found in the mapping document

Update (expire) LEGAL_ENTITY_ADDRESS_ASSN table. Following columns would be updated:
LEAD_EXP_DT
BA_ID
BA_EFF_DT
BA_SEQ_NBR
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
And these data should be loaded into a temporary dataset DS_LEAD_Upd.ds
Update (expire) INDIVIDUAL_PERSON_NAME table. Use LERL_SYS_ID and LERL_EFF_DT from
step2 for the update.
BEN_EXP_DT
BA_ID
BA_EFF_DT
BA_SEQ_NBR
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
And these data should be loaded into a temporary dataset DS_IPN_Upd.ds
Update (expire) BUSINESS_ENTITY_NAME table. Use LERL_SYS_ID and LERL_EFF_DT from
step2 for the update.
IPN_EXP_DT
BA_ID
BA_EFF_DT
BA_SEQ_NBR
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
And these data should be loaded into a temporary dataset DS_BE_Upd.ds
Job # – Put_EODS_CUST_LE_Del_LEAR_Update_38_02(New Job)

Purpose :
Records would be updated in the following tables LEGAL_ENTITY_AGREEMENT_ROLE.

Job Parameters:

Step Description
1 Use dataset stage to read the data from DS_LEAR_Upd.ds
2 table.
Job # – Put_EODS_CUST_LE_Del_LERL_Update_38_03 (New Job)
Purpose :
Records would be updated in the following tables LEGAL_ENTITY_ROLE.
Job Parameters:

Step Description
1 Use dataset stage to read the data from DS_LERL_Upd.ds
Job # – Put_EODS_CUST_LE_Del_LEAD_Update_38_04 (New Job)

Purpose :
Records would be updated in the following tables LEGAL_ENTITY_ADDRESS_ASSN.
Job Parameters:


Step Description
1 Use dataset stage to read the data from DS_LEAD_Upd.ds
Job # – Put_EODS_LE_IPN_Del_Update_38_05 (New Job)
Purpose :
Records would be updated in the following tables INDIVIDUAL_PERSON_NAME
Job Parameters:

Step Description
1 Use dataset stage to read the data from DS_IPN_Upd.ds
Job # – Put_EODS_CUST_LE_Del_BEN_Update_38_06 (New Job)

Purpose :
Records would be updated in the following tables BUSINESS_ENTITY_NAME
Job Parameters:


Step Description
1 Use dataset stage to read the data from DS_BE_Upd.ds
2 Use DB2 stage and load all the contents from step 1 into BUSINESS_ENTITY_NAME table.
Job # – Put_EODS_CUST_LE_ADDR_Del_Update_38_07 (New Job)
Purpose :
Records would be updated in the following table ADDRESS
Job Parameters:

Step Description
1 Use DB2 stage to read the data from LEGAL_ENTITY_ADDRESS_ASSN
Job #27 – Xfm_EODS_Cust_END_LE_DEL_BA_Merge_36_03 (New Job)

Purpose:
The purpose of this job is to Merge the Business Action details for dataset “DS_Cust_End_Del_BAInst.ds” and
DS_Cust_End_ADD_LE_With_Ba_Data.ds populate the data into Dataset DS_Cust_End_Del_LE_With_Ba_data.ds.
Because these Dataset is used in the succeeding jobs in a Legal Entity Change.
Job Parameters:


Step Description
Use dataset stage to read the data from DS_Cust_End_Del_BAInst.ds,
1 DS_Cust_End_ADD_LE_With_Ba_Data.ds files
2 Save the step 1 data into Dataset DS_Cust_End_Del_LE_With_Ba_data.ds
7.1.2.9 Endorsements – Legal entity Changes
Job #39 – Xfm_EODS_Cust_END_LE_CHG_39 (New Job)

Purpose:
The Purpose of this job is to filtered the Legal entity Change records based on the UBA_RSN_CD is
CHGAD,CHGNM and CHGBA and these are loaded into a temporary datasets.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_End_Chng_LE.ds file.
Join this data with DS_CustLEARReference.ds on AGMT_SYS_ID,AGMT_EFF_DT and if we find a
2 New records and filter the records into a temporary datasets
Save the Step 2 data Into a DS_Cust_End_Chng_LE_Addr_Chng.ds,

3 DS_Cust_End_Chng_LE_Nm_Chng.ds, DS_Cust_End_Chng_LE_CB_Chng.ds
Job # – Xfm_EODS_Cust_END_LE_Addr_Chg_40_00(New Job)

Purpose:
This is to read the Change Name Endorsement data and Performs the Business action transformation by joining
the Change Name Endorsement to Business action DataSet. And the DataSet
DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds would be populated with the new Ba_SEQ_NBR and
BA_EFF_DT.
Job Parameters:


Step Description
1 Use dataset stage to read the DS_Cust_End_Chng_LE_Addr_Chng.ds file.
Join this data with DS_Cust_End_Del_LE_With_Ba_data on BA_ID and if we find a New records
2 and loaded into a temporary datasets
Save the Step 2 data Into a, DS_Cust_End_Chng_LE_Addr_Chng_Ba_Inst.ds,

3 DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds
Job # – Put_EODS_Cust_LE_Addr_Chng_BA_Load_40_01 (New Job)

The purpose of this job is to load BUSINESS_ACTION Details for all the legal entities which have been changed.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_End_Chng_LE_Addr_Chng_Ba_Inst.ds
Note : Here Step 1,2 & 3 is Deleted.
Step Description
1 Read all the records from the dataset DS_Cust_End_Del_LE_With_Ba_data.ds

SELECT BA_ID,
BA_EFF_DT
MAX(BA_SEQ_NBR)
GROUP BY BA_ID,
BA_EFF_DT
2 WHERE BA_EXP_DT > #Scheduled run date#
3 For all the records from step 1 lookup the data in the data from the step 2 using BA_ID, BA_EFF_DT
increment the BA_SEQ_NBR by one and insert the same in BUSINESS_ACTION table. Detailed
mapping is present in the data mapping sheet.
Also save the new BA_SEQ_NBR along with the columns from step1 in

DS_Cust_End_Chg_LE_with_BA.ds
Job # – Put_EODS_Cust_LE_Addr_Chng_LEAD_Update_40_02 (New Job)

Purpose:
The purpose of this job is to update LEGAL_ENTITY_ADDRESS_ASSN table to expire the address association
for all the legal entities which have been changed.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds
Job # Put_EODS_Cust_LE_Addr_Chng_ADDR_Update_40_03 (New Job)

Purpose :
This job would expire the old records in ADDRESS for all the records which have changes in address.
Job Parameters:

Step Description
Use dataset stage to read the DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds and join with updated
1 LEGAL_ENTITY_ADDRESS_ASSN table

Job # – Xfm_EODS_Cust_END_LE_Addr_Chg_40_04 (New Job)

Purpose:
The purpose of this job is to read the data from DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds dataset and
generate the sequence for the following tables ADDRESS and LEGAL_ENTITY_ADDRESS_ASSN and loaded the
data into temporary datasets.
Job Parameters:

Step Description
1 Read all the record fomr the dataset DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds
we have to insert data into DS_Cust_End_Chng_LE_Addr_Chng_LeadInst.ds dataset. Create a

system generated sequence number and assign it to LEAD_SYS_ID column. Insert into
2 LEGAL_ENTITY_ADDRESS_ASSN table according to the data mapping document.
we have to insert data into DS_Cust_End_Chng_LE_Addr_Chng_AddrInst.ds dataset. Create a
system generated sequence number and assign it to ADDR_SYS_ID column. Insert into ADDRESS
3 table according to the data mapping document.
Job #40 – Put_EODS_LE_CHG_Update_00 (Deleted This Job)
Purpose:
The purpose of this job is to load BUSINESS_ACTION table for all the legal entities which have been changed.
Job Parameters:


Step Description
1 Read all the record from the dataset DS_Cust_End_Chg_LE_with_BA.ds
Join the data from step 1 with the data with the data from dataset DS_LGLESysIds.ds on
2 AGMT_SYS_ID, AGMT_EFF_DT
 If the UBA_RSN_CD = ‘CHGAD’ then use ADDR_SYS_ID, ADDR_EFF_DT and update the
ADDRESS table (expire the old records). Following columns would be updated
ADDR_EXP_DT
BA_ID
BA_EFF_DT
BA_SEQ_NBR
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
 If the UBA_RSN_CD = ‘CHGAD’ then use LEAD_SYS_ID, LEAD_EFF_DT and update the
LEGAL_ENTITY_ADDRESS_ASSN table (expire the old records). Following columns would
be updated
LEAD_EXP_DT
BA_ID
BA_EFF_DT
BA_SEQ_NBR
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
3 Detailed mapping is present in the data mapping document.
4  If the UBA_RSB_CD = ‘CHGNM’ and LGLE_TYP = ‘BS’ then join the input dataset with the
dataset DS_LGLEBenSysIDs.ds on AGMT_SYS_ID, AGMT_EFF_DT and update the
BUSINESS_ENTITY_NAME table (expire the old records). Following columns would be
updated.
BEN_EXP_DT
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
 If the UBA_RSB_CD = ‘CHGNM’ and LGLE_TYP = ‘IN’ then join the input dataset with the
dataset DS_LGLEIPNSysIDs.ds on AGMT_SYS_ID, AGMT_EFF_DT and update the
INDIVIDUAL_PERSON_NAME table (expire the old records). Following columns would be
updated.
IPN_EXP_DT
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS

REC_STUS_CD
Detailed mapping is present in the data mapping document.
If the UBA_RSB_CD = ‘CHGBA’ then join the input dataset with the dataset DS_LGLESysIds.ds
on AGMT_SYS_ID, AGMT_EFF_DT and update the CLIENT_BANK_ACCOUNT_ASSN table
(expire the old records), Following columns would be updated.
CB_EXP_DT
CB_LOAN_ID
UPDATED_DT
UPDATED_BY
ACT_INSUPD_TS
REC_STUS_CD
5 Detailed mapping is present in the data mapping document.
Job # – Put_EODS_LE_CHG_ADDR_Load_40_05
Purpose:
The purpose of this job is to load ADDRESS table for all the legal entities which have a address change.
Job Parameters:

Step Description
1 Read all the record fomr the dataset DS_Cust_End_Chng_LE_Addr_Chng_AddrInst.ds
Note : Deleted the following Step 1, 2 & 3.
Step Description
1 Read all the record fomr the dataset DS_Cust_End_Chg_LE_with_BA.ds
Join the data from step 1 with the data with the data from dataset DS_LGLESysIds.ds on
2 AGMT_SYS_ID, AGMT_EFF_DT
3 If the UBA_RSN_CD = ‘CHGAD’ then we have to insert into ADDRESS table. Create a system
generated sequence number and assign it to ADDR_SYS_ID column. Insert into ADDRESS table

according to the data mapping document.
Job # – Put_EODS_LE_CHG_ADDR_ASSN_Load_40_06
Purpose:
The purpose of this job is to load LEGAL_ENTITY_ADDRESS_ASSN table for all the legal entities which have a
address change.
Job Parameters:

Step Description
1 Read all the record fomr the dataset DS_Cust_End_Chng_LE_Addr_Chng_LeadInst.ds
Job # – Xfm_EODS_Cust_END_LE_Addr_Chg_BA_Merge_40_07
Purpose:
The purpose of this job is to Merge the Business Action details for dataset
“DS_Cust_End_Del_LE_With_Ba_data.ds” and DS_Cust_End_Chng_LE_Addr_Chng_Ba_Inst.ds populate the data
into Dataset DS_Cust_End_Chng_LE_Addr_Chng_Ba_Data.ds. Because these Dataset is used in the succeeding
jobs in a Legal Entity Change.
Job Parameters:

Step Description
Use dataset stage to read the data from DS_Cust_End_Del_LE_With_Ba_data.ds,
1 DS_Cust_End_Chng_LE_Addr_Chng_Ba_Inst.ds files

2 Save the step 1 data into Dataset DS_Cust_End_Chng_LE_Addr_Chng_Ba_Data.ds
Job # – Xfm_EODS_Cust_END_LE_Name_Chng_NewBA_41_00(New Job)

Purpose :
This is to read the Change Name Endorsement data and Performs the Business action transformation by joining
the Change Name Endorsement to Business action DataSet. And the DataSet
DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds would be populated with the new Ba_SEQ_NBR and
BA_EFF_DT.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_End_Chng_LE_Nm_Chng.ds file.
Join this data with DS_Cust_End_Chng_LE_Addr_Chng_Ba_Data.ds on BA_ID and if we find a New
2 records and loaded into a temporary datasets
Save the Step 2 data Into a DS_Cust_End_Chng_LE_Name_Chng_Ba_Inst.ds,

3 DS_Cust_End_Chng_LE_Nm_Chng_NewBa.ds
Job # PUT_EODS_Cust_END_LE_Name_Chg_Ba_LOAD_41_01 (New Job)

Purpose:
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_End_Chng_LE_Name_Chng_Ba_Inst.ds
Job # – Xfm_EODS_Cust_END_LE_Name_Chng_Ins_41_02(New Job)

Purpose:
The purpose of this job is to read the data from DS_Cust_End_Chng_LE_Nm_Chng_NewBa.ds dataset. Filter
LGLE_TYP is BS or IN and generate the sequence for the following tables INDIVIDUAL_PERSON_NAME and
BUSINESS_ENTITY_NAME and loaded the data into temporary datasets.
Job Parameters:

Step Description
1 Read all the record form the dataset DS_Cust_End_Chng_LE_Nm_Chng_NewBa.ds
we have to insert data into DS_CUST_CHNG_BENInsert.ds dataset. Create a system generated

sequence number and assign it to BEN_SYS_ID column. Insert into BUSINESS_ENTITY_NAME
we have to insert data into DS_CUST_CHNG_IPNInsert.ds dataset. Create a system generated
sequence number and assign it to IPN_SYS_ID column. Insert into INDIVIDUAL_PERSON_NAME
Job # – Xfm_EODS_Cust_END_LE_Name_Chng_Updt_41_03(New Job)

Purpose:
The Purpose of the job is update the Legal Entity Change Name based on AGMT_SYS_ID, AGMT_EFF_DT for
the following tables INDIVIDUAL_PERSON_NAME and BUSINEE_ENTITY_NAME (expire the old records)
Job Parameters:

Step Description
1 Read all the record form the dataset DS_Cust_End_Chng_LE_Nm_Chng_NewBa.ds
From step 1 filter the LGLE_TYP is IN then update the INDIVIDUAL_PERSON_NAME table and data
2 is loaded into the dataset DS_CUST_CHNG_IPNUpdt.ds.
From step 1 filter the LGLE_TYP is BS then update the BUSINESS_ENTITY_NAME table and data
3 is loaded into the dataset DS_CUST_CHNG_BENUpdt.ds

Job # – Put_EODS_LE_CHG_BEN_Update_41_04(New Job)

Purpose:
The purpose of this job is to update the BUSINESS_ENTITY_NAME table for all the legal entities which have a
name change.
Job Parameters:

Step Description
1 Use dataset stage to read the data from DS_CUST_CHNG_BENUpdt.ds
2 Use DB2 stage and update all the contents from step 1 into BUSINESS_ENTITY_NAME table.
Job # – Put_EODS_LE_CHG_IPN_Update_41_05 (New Job)

Purpose:
The purpose of this job is to update the INDIVIDUAL_PERSON_NAME table for all the legal entities which have a
name change.
Job Parameters:

Step Description
1 Use dataset stage to read the data from DS_CUST_CHNG_IPNUpdt.ds

Job # – Put_EODS_LE_CHG_BEN_Load_41_06(New Job)

Purpose:
The purpose of this job is to load the BUSINESS_ENTITY_NAME table for all the legal entities which have a
name change.
Job Parameters:

Step Description
1 Use dataset stage to read the data from DS_CUST_CHNG_BENInsert.ds
2 Use DB2 stage and update all the contents from step 1 into BUSINESS_ENTITY_NAME table.
Job # – Put_EODS_LE_CHG_IPN_Load_41_07 (New Job)

Purpose:
The purpose of this job is to load the INDIVIDUAL_PERSON_NAME table for all the legal entities which have a
name change.
Job Parameters:

Step Description
1 Use dataset stage to read the data from DS_CUST_CHNG_IPNInsert.ds

Job # – Xfm_EODS_Cust_END_LE_Name_Chg_BA_Merge_41_08 (New Job)

Purpose:
The purpose of this job is to Merge the Business Action details for dataset
“DS_Cust_End_Chng_LE_Addr_Chng_Ba_Data.ds” and DS_Cust_End_Chng_LE_Nm_Chng_Ba_Inst.ds populate
the data into DS_Cust_End_Chng_LE_Nm_Chng_Ba_Data.ds Dataset. Because these Dataset is used in the
succeeding jobs in a Legal Entity Change.
Job Parameters:

Step Description
Use dataset stage to read the data from DS_Cust_End_Chng_LE_Nm_Chng_Ba_Inst.ds,
1 DS_Cust_End_Chng_LE_Addr_Chng_Ba_Data.ds files
2 Save the step 1 data into Dataset DS_Cust_End_Chng_LE_Nm_Chng_Ba_Data.ds
Job # – Xfm_EODS_Cust_END_LE_CB_Chng_NewBa_42_00 (New Job)

Purpose :
This is to read the Change Name Endorsement data DS_Cust_End_Chng_LE_CB_Chng.ds and Performs the
Business action transformation by joining the Change Name Endorsement to Business action
DS_Cust_End_Chng_LE_Nm_Chng_Ba_Data.ds Dataset. And the Dataset
DS_Cust_End_Chng_LE_CB_Chng_NewBa.ds would be populated with the new Ba_SEQ_NBR and
BA_EFF_DT.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_End_Chng_LE_CB_Chng.ds file.
Join this data with DS_Cust_End_Chng_LE_Nm_Chng_Ba_Data.ds on BA_ID and if we find a
2 New records and loaded into a temporary datasets
Save the Step 2 data Into a DS_Cust_End_Chng_LE_CB_Chng_Ba_Inst.ds,

3 DS_Cust_End_Chng_LE_CB_Chng_NewBa.ds

Job # – Xfm_EODS_Cust_END_LE_CB_Chg_42_01 (New Job)

Purpose:
The purpose of this job is to load CLIENT_BANK_ACCOUNT_ASSN table for all the legal entities which have a
bank account change.
Job Parameters:

Step Description
1 Read all the record from the dataset DS_Cust_End_Chng_LE_CB_Chng_NewBa.ds
From step 1 we have to insert into CLIENT_BANK_ACCOUNT_ASSN table. Create system

generated sequence number and assign it to CB_SYS_ID. Insert into DS_CLIENT_BANK_Insert.ds
2 dataset
3 From step 1 we have to update the CLIENT_BANK_ACCOUNT_ASSN table as for the mapping
document and data should be loaded into a dataset DS_Cb_Updt.ds
Job # – Xfm_EODS_Cust_END_LE_CB_Chg_BAIns_42_02 (New Job)

Purpose:
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cust_End_Chng_LE_CB_Chng_Ba_Inst.ds

Job # – Put_EODS_LE_CHG_CB_Update_42_03
Purpose:
The purpose of this job is to Update the CLIENT_BANK_ACCOUNT_ASSN table (expire the old records) for all
the legal entities which have been changed.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_Cb_Updt.ds
2 Use DB2 stage and load all the contents from step 1 into CLIENT_BANK_ACCOUNT_ASSN table.
Job # – Put_EODS_LE_CHG_CB_Load_42_04(New Job)

Purpose:
The purpose of this job is to load the CLIENT_BANK_ACCOUNT_ASSN table (expire the old records) for all the
legal entities which have been changed.
Job Parameters:

Step Description
1 Use dataset stage to read the DS_CLIENT_BANK_Insert.ds
2 Use DB2 stage and load all the contents from step 1 into CLIENT_BANK_ACCOUNT_ASSN table.

Note: Deleted below jobs Job #42 and Job #43

Job #42 – Put_EODS_LE_CHG_BEN_IPN_Load_00
Purpose:
The purpose of this job is to load BUSINESS_ENTITY_NAME or INDIVIDUAL_PERSON_NAME table for all the
legal entities which have a name change.
Job Parameters:

Step Description
If the UBA_RSN_CD = ‘CHGNM’

 If the LGLE_TYP is ‘BS’ then we have to insert into BUSINESS_ENTITY_NAME table.
Create a system generated sequence number and assign it to BEN_SYS_ID column. Insert
into BUSINESS_ENTITY_NAME table according to the data mapping document.
 If the LGLE_TYP is ‘IN’ then we have to insert into INDIVIDUAL_PERSON_NAME table.
Create a system generated sequence number and assign it to IPN_SYS_ID column. Insert
2 into INDIVIDUAL_PERSON_NAME table according to the data mapping document.
Job #43 – Put_EODS_LE_CHG_CB_Load_00
Purpose:
The purpose of this job is to load CLIENT_BANK_ACCOUNT_ASSN table for all the legal entities which have a
bank account change.
Job Parameters:



Step Description
If the UBA_RSN_CD = ‘CHGBA’, then we have to insert into CLIENT_BANK_ACCOUNT_ASSN

table. Create system generated sequence number and assign it to CB_SYS_ID. Insert into
2 CLIENT_BANK_ACCOUNT_ASSN with the data as said in the data mapping document.

7.1.2.10 Audit Entry – Process End
Job # 44 - Xfm_EODS_MASTER_ADT_LOG_00
Purpose:
This job is to log an audit message into EODS processing Audit table.
EODS process will insert an entry into the Audit_trail_log table for auditing and validation purpose.
This is a common job that is used to set the value of CRTE_TS, LAST_UPDT_TS and PROCESS_STATUS fields
in the table.
Job Parameters:

Step Description
Insert a log record into Audit_trail_log table saying “EODS – MASTER file” processing has started.
Populate the Audit_trail_log:
 CRTE_TS as “Current System Timestamp”
 And I_rec_actv to ‘Y’
 SEQ_FLOW_NM to to ”Master_Legal_Entity_Data_Load”
 PROCESS_STATUS to ‘E (Finished)
1  LAST_UPD_TS to “Current System Timestamp”
For more details about the job refer to the common flow section.
7.1.3 Shell Scripts
7.1.3.1 Script #1: FnMove_Master_File.ksh
Description:
1. Copy <Src_Loc>\<FILE_NM> to <Wrk_folder_Loc>\<FILE_NM>;
2. Move <Src_Loc>\<FILE_NM> <Archv_folder_Loc>\<FILE_NM>;
3. Remove <Src_Loc>\<FILE_NM;

7.1.3.2 Script #2: Call_Master_LE_data_processing.ksh
Description:
1. For all the files in the work folder order by the created date
2. Call the DataStage sequence which would process the Master Customer data.
3. If any error occurs during this process, send mail to application support team mentioning the reason
for job abort.
7.1.4 Metadata Objects

NA
7.1.5 Database Objects
Object #1: EODS_BATCH_AUDIT

Type: EODS staging audit Table
Purpose:
This table holds information about when the Master Policy data files (MOT_LITE Files from Legacy Policy
Admin systems) processing statistics which includes Start time, End time and Processing status etc. Please refer
to the reference section mentioned IBM_EODS_COMMON_FLOW.doc for more information about the table.
S.No Name Definition Data Type Is Is

. PK FK
SYS_ID This is a DB generated unique ID. Serves as the Integer Yes No
1 primary key.
SEQ_FLOW_NM This is the Job Sequence/Flow name for which an Varchar (255) No No
2 entry is made in the audit table.
CRTE_TS The system timestamp when the record was Timestamp No No
3 inserted
LAST_UPD_TS The system date time when the record was last Timestamp No No
4 updated
PROCESS_STATUS This is a Boolean identifier that indicates if ETL Varchar(50) No No
Processing is "Complete" or "Not Complete”.
Possible domain Values are “PRCS_STARTED”
5 “PRCS_CMPLTED”
I_REC_ACTV Record active indicator CHAR(1) No No
6
K_REC Number of records Integer No No
7.2 Error Handling Design Flow
7.2.1 Exception Conditions

Design Component handling

S.No Error Condition Post Condition the Error Condition
No master data Master data process will abort and send mail to the
available for the application support team that the job has been Call_Master_LE_data_processi
1 day aborted since no file has been received for the day. ng.ksh
Master files will be accumulated in the mainframe
systems for SFTP. EODS will process all
backlogged files in the next scheduled or manual
EODS is run in chronological order of the file received in Call_Master_LE_data_processi
2 unavailable EODS. ng.ksh
If master processing fails in between for any reason,
then mail would be sent to application support team
stating the reason and a manual restart would be
performed which would exclude all the jobs which
Master has executed in previous run successfully and start
3 processing fails from the job which had aborted. Manual
7.2.2 Error Codes and Messages

Please refer Common flow detail design.
7.2.3 Restartability
Master Customer processing will not support automated restartability. But the checkpoints would be
implemented at every job so, if any job fails due to any reason, manual intervention is needed to sort out the issue
and restart the sequence which then would skip all the jobs which have been executed successfully in the
previous run and start from the job which has aborted. But if the job has failed due to data problem, then the
corrected files should be loaded into the source directory and the whole sequence should be reset so that the new
data would be processed from the beginning.
8 Data and Information

8.1 Logical Data Model Reference
EODS PDM version

3.0 July 01 2010.pdf
<Link will be provided after update in the delivery Hub>
9 Environment Details
Please refer “EODS Batch Common Framework Tasks – Section – Environment Topology” detail design
document.
9.1.1 File System

Please refer “EODS Batch Common Framework Detail Design Specifications – Section – File System
Structure” detail design document for a complete View of EODS File System Structure.
Files system structures used by Master customer Data processing

Folder Description Files Format

../eods/scripts Unix Shell Script Files *.ksh, *.sh
Source master customer
../eods/source/MasterCustomer Files <will be revisited>
../eods/archive/MasterCustomer Archive master customer files <source file name<Sched_Run_Dt>.dat
../eods/reports Report files NA

../eods/logs Log files *.log
../eods/rejects Reject Files *.rej
../eods/work/MasterCustomer Intermediate work files for
master customer Processing <will be revisited>
9.1.2 Enterprise Staging Area Files
Folder Description Files and Format Details
../esa/eods/MasterCustomer/cannonic Master files in c_<source file name><Sched_Run_Dt>.txt

al canonical form
10 Logging/Auditing
EODS logs a complete trace of the master file legal entity process execution in audit tables.
All input, output and master files are archived for a period of 45 days as per the NFR requirements for audit
reasons.
11 Performance Considerations
The projected volume of customer data is less than 20000 records a day.
The volumes being small, Master Customer jobs for EODS will follow the default configurations.

12 Reporting
N/A
13 Security
File Transfer
Master customer data files are transferred from the PI Client to the DataStage AIX servers using the SFTP
Process.
The SFTP typically relies upon SSH, a protocol that provides secure communications using a key_based
encryption scheme. SSH is a proven secure method to transmit files. It fully encrypts the file transfer process,
from start to finish with limited threat exposure for the user. Due to the use of keys, it is easy to setup a scripted
SFTP session that transmits files as part of an automated process.
14 Deployment Details
14.1.1 Clear Case Reference
Please refer “EODS Batch Common Framework Tasks – Section - Version Control” detail design document.
14.1.2 Deployment Inventory
Worksheet in EODS
Master Customer Data Processing ETL Design Specification v1.1.xls
14.1.3 Package List
# Package Name in Order for Deployment

1 EODS_MASTER_Legal_Entity_DS
2 EODS_MASTER_Legal_Entity_SCR
14.1.4 Special Considerations

NA
15 Scheduling
ESPX scheduling tool would be used for scheduling Datastage Jobs, Sequences and UNIX scripts so as to
control and monitor the execution of the flow, ESPX is a mainframe based scheduling tool.
For more details please refer “EODS Batch Job Scheduling R1A”.

16 SLA
For details please refer “EODS Batch Job Scheduling R1A”.
17 Special Considerations
N/A
18 Other Project Specific Requirements

N/a
19 Appendix
19.1 Architectural Design Decisions Reference
Item Document Section
19.2 Definitions, Acronyms, and Abbreviations
Acronym/Abbreviation Description
POLICY ADMIN Legacy (HOACT,AUTOACT,FLASH..) and EPAS applications that handle
SYSTEMS Policy transactions in FFIC
HOACT Home Owners Automated Computer Transactions
AUTOACT Automobile Automated Computer Transactions
PVR Premium Verification and Recording System
FLASH Dwelling Fire System
EPAS Enterprise Policy Admin System
BCWS Billing and Collections Workstation / System. The current functional billing
system for Direct Billing
SAP - FSCD SAP for Insurance Collections/Disbursements (FS-CD) has the task of
Collecting Premiums for running policies, and of disbursing benefits.
Currently used for Billing operations in FFIC
NWPA Nationwide Premium Accounting. Currently used for Agency Billing.
LEID Legal Entity ID

19.3 References
S.No. Document Description Reference Location

1. DataStage Standards for EODS_V2.doc Link
Last Updated : 2/24/2010
2 AZAT568 EODS Non Functional Requirements
v1.0.doc
Last updated: 6/11/2010 Link
3 EODS Billing Batch Requirements vs 1.9.doc
Last Updated: Link
4 3.8 – Update Tables – Mapping v1.0
Last Updated: 06/21/2010 Link
5 3.8 – Update Tables v.10
Last Updated: 06/25/2010 Link
20 Approvals
End of document– AZAT560 Conceptual Design Document

Document Control Page
AZAT561 Detail Design Document

This document is to be located in the AZOA Process Asset Library (PAL)
Document Version: 1.020
Document Status: Current
Owning Process: TS
Document Filename: 59794699.doc
Revision History:
Version Revision Change Description Changed Approved PI Request
Number Date Name Name #
1.00 03/28/08 Initial Version Process Team Bobbi Stark None
1.01 12/31/08 Remove logo. Remove version number. Dan Ellis Bryan Gilbert 80151,
80153
1.02 9/30/09 Added reference to FFIT888 WMB Template Doreen Nigri Lan Elsner 90062


EODS Master Customer Data Processing ETL Design Specification v1.1

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

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

EODS Master Customer Data Processing ETL Design Specification v1.1

Hochgeladen von

Copyright:

Verfügbare Formate

EODS - Master Customer data processing AZAT561 Detail Design Document

AZAT561 DS EODS – Master Customer Data file

Project Name: Data Strategy _ Enterprise Operational Data Store

Project Number: 018928

Prepared by: Raghavendra Bathula

EODS – Master Customer data processing Detail Design Page: 1 of 64

EODS – Master Customer data processing Detail Design Page: 2 of 64

Document Revision History

EODS – Master Customer data processing Detail Design Page: 3 of 64

The Scope of this document is to

3.1 Process Flow Diagram

EODS – Master Customer data processing Detail Design Page: 4 of 64

Canonical Data model Conversion

Apply transfromations to convert the

Move all the files in CDM format to Enterprise Staging Area

EODS Master Legal Entity data Processing

Save the data in temporary

Join the data with the common

New or Renewal Business Endorsements processing

EODS – Master Customer data processing Detail Design Page: 5 of 64

3.2 Process Flow Description

EODS – Master Customer data processing Detail Design Page: 6 of 64

EODS – Master Customer data processing Detail Design Page: 7 of 64

Mapping for converting data from source to Canonical format

Mapping for converting data from Canonical format to EODS database

6 Data Sharing Agreements

6.1 Input File Layouts

6.2 Output File Layouts

Canonical data format for PI Customer data file

7 Logical View of the Design

7.1.1 DataStage Sequences

EODS – Master Customer data processing Detail Design Page: 8 of 64

7.1.2 DataStage Jobs

7.1.2.1 Audit Entry – Process Start

SNO Parameter Name Type Description Value

The following steps describe the Process flow in the job:

7.1.2.2 Creating CDM format

EODS – Master Customer data processing Detail Design Page: 9 of 64

The following steps describe the Process flow in the job:

2 Implement transformations as mentioned in the data mapping sheet.

7.1.2.3 Merging Policy data with Customer data

SNO Parameter Name Type Description Value

The following steps describe the Process flow in the job:

EODS – Master Customer data processing Detail Design Page: 10 of 64

7.1.2.4 Loading PI Client New business data

Job #4 – Xfm_PI_EODS_RA_Transform_00 (RA-Risk Address)

SNO Parameter Name Type Description Value

The following steps describe the Process flow in the job:

EODS – Master Customer data processing Detail Design Page: 11 of 64

SNO Parameter Name Type Description Value

The following steps describe the Process flow in the job:

Job #6 – Put_SUBJ_AT_RSK_EODS_LOAD_RA_00 (Deleted)

SNO Parameter Name Type Description Value

The following steps describe the Process flow in the job:

EODS – Master Customer data processing Detail Design Page: 12 of 64

SNO Parameter Name Type Description Value

The following steps describe the Process flow in the job:

New Job - Xfm_EODS_Legal_Entities_PI_AR_01

SNO Parameter Name Type Description Value

EODS – Master Customer data processing Detail Design Page: 13 of 64

The following steps describe the Process flow in the job:

Job #8 – Xfm_EODS_Legal_Entities_PI_AR_02 (AR- Agreement Role)

SNO Parameter Name Type Description Value