EODS Master Customer Data Processing ETL Design Specification v1.1

8/6/2019 EODS Master Customer Data Processing ETL Design Specification v1.1

1/63

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 BathulaSurya Swaroop Kumar P

Current Version: 1.0Date: 08-July-10

Project Manager:IT AS Manager:

EODS Master Customer data processing Detail Design Page: 1 of 63

Allianz Proprietary and Confidential: Do not distribute


2/63


TABLE of CONTENTS

1 Overview ................................................................................................................................................................4

2 Scope .............................................................................................................................................................. ......4

3 Solution Design ......................................................................................................................................................43.1 Process Flow Diagram ....................................................................................................................................4

3.2 Process Flow Description ................................................................................................................................6

3.3 Traceability ......................................................................................................................................................6

4 Design Considerations ...........................................................................................................................................6

4.1 Assumptions ....................................................................................................................................................6

4.2 Dependencies .................................................................................................................................................7

4.3 Constraints .....................................................................................................................................................7

4.4 Risks ............................................................................................................................................................ ...7

5 Data Mapping ................................................................................................................................................ ........8

6 Data Sharing Agreements ............................................................................................................................... ......8

6.1 Input File Layouts ............................................................................................................................................8

6.2 Output File Layouts .........................................................................................................................................8

6.3 Intra File Layouts .............................................................................................................................................8

7 Logical View of the Design ............................................................................................................................ ........8

7.1 Design Components ........................................................................................................................................8

7.1.1 DataStage Sequences ..............................................................................................................................8

7.1.2 DataStage Jobs ........................................................................................................................................9

7.1.3 Shell Scripts ............................................................................................................................................56

7.1.4 Metadata Objects ....................................................................................................................... ............57

7.1.5 Database Objects ...................................................................................................................................57

7.2 Error Handling Design Flow ..........................................................................................................................587.2.1 Exception Conditions ..............................................................................................................................58

7.2.2 Error Codes and Messages ....................................................................................................................58

7.2.3 Restartability ...........................................................................................................................................58

8 Data and Information ......................................................................................................................................... ..58

8.1 Logical Data Model Reference ......................................................................................................................58

9 Environment Details .............................................................................................................................................58

9.1.1 File System ............................................................................................................................................59

9.1.2 Enterprise Staging Area Files ................................................................................................................ .59

10 Logging/Auditing ................................................................................................................................................59

11 Performance Considerations ..................................................................................................................... ........59

12 Reporting ...........................................................................................................................................................60

13 Security ..............................................................................................................................................................60

14 Deployment Details ............................................................................................................................................60

14.1.1 Clear Case Reference ..........................................................................................................................60

14.1.2 Deployment Inventory ...........................................................................................................................60

14.1.3 Package List.........................................................................................................................................60

14.1.4 Special Considerations .........................................................................................................................60




3/63


15 Scheduling .........................................................................................................................................................60

16 SLA ....................................................................................................................................................................61

17 Special Considerations ......................................................................................................................................61

18 Other Project Specific Requirements .................................................................................................................61

19 Appendix ............................................................................................................................................................61

19.1 Architectural Design Decisions Reference ..................................................................................................6119.2 Definitions, Acronyms, and Abbreviations ...................................................................................................61

19.3 References ..................................................................................................................................................62

20 Approvals ...........................................................................................................................................................62



Document Revision History

Version No. Revision Date Change Description Author

1.0


4/63


1 Overview

EODS will acquire, update and store Personal Insurance Legal entity data for a policy data from PI Client. PIClient would provide the data in a file.

This document describes the process to read files sent by PI Client, convert them to canonical format, storein Enterprise Staging Area and finally load them to EODS database. This detail design is for loading Legal entityinformation from PI Client Only. Payor Role data (Billing Account) will be filtered and would be written to a filewhich will be used by Master Billing Account Setup Process.

The design demonstrated holds for the requirements attached in the appendix. Any change in therequirements 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 subsectionsbelow.

3.1 Process Flow Diagram




5/63




Move all the files in CDM format to Enterprise Staging Area

PI Scrubbed Data

EODS Master Legal Entity data Processing

Split the file into different files

based on the transaction types .

New or Renewal Business

processing

Endorsements processing

(Legal entity changes)

No

EODS

Database

Canonical Data model Conversion

Move input customer data files to

Archive and work folder

Apply transfromations to convert the

input Customer data in work folder to

Canonical Data model format

Customer

Data

LEBA_TYP =

PO

Save the data in temporary

dataset which would be used

for Master Billing accountdata processing.

YesRead the CDM converted file

from ESA

Join the data with the common

reference file generated while

Master Policy data processing

which contains the database

internal ids


6/63


3.2 Process Flow Description

1. Customer data files from PI Client will be available in source directory everyday by Time. MasterLegal Entity Data Load process reads Customer data from Source directory copy them to work folder andmove to Archive folder.

2. Read the customer data files from Work folder and convert each one of them to Canonical format. Storethis file in Enterprise Staging Area.

3. Read CDM converted files from Enterprise Staging Area, and join the filtered records with the globalreference dataset generated during the Master policy data, to get the database ids generated duringcreating policies in EODS

4. Check if the records whose LEBA_TYP = PO. If so save those records into a temporary file which wouldbe used for Master Billing account processing. Else, filter those records which would be processed infurther steps.

5. Join the filtered records with the global reference dataset generated during the Master policy data, to getthe database ids generated during creating policies in EODS.

6. Split the file into different streams based on the Transaction type. The different streams will beNew and renewal polices Processed togetherEndorsements Legal entity changes

7. For New and Renewal Policies, legal entities would be added to the existing legal entities of EODSdatabase. 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 ACTIONtable to track the endorsements applied on the EODS database. If we have multiple endorsements for asame 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 EODSbefore this process starts.

We will be running Master Policy data processingpreceding Legal entity data processing.

2 PI Client will send all roles on a Policy without

dropping any roles for New and RenewalTransactions.

All Roles on a Policy would be sent to EODS for New

and Renewal transactions.

3 EODS will NOT perform any data Validation. EODS will redirect any data issues if they are notassociated with transformations to the Billing andLegacy systems to coordinate to fix.

4 EODS receive a file from PI Client everyday toload Customer data.

EODS will check for the file at a specified time.




7/63


4.2 Dependencies

# Dependency Comments

1 Master Legal entity data inserts in the EODSdatabase would be performed after thecorresponding Master Policy data is available

in EODS.

Master policy data processing would insert data intopolicy tables for new policies which would be used inthis process.

4.3 Constraints

# Constraint or Issues Impact

N/A

4.4 Risks

# Risk Mitigation Strategy

1 Data discrepancies in PI Client will exist inEODS.

All data in-consistencies should be fixed at PI Clientend.




8/63


5 Data Mapping

Mapping for converting data from source to Canonical format

EODS_Master_PI_PROCESSING_MAPPING_Sr

Mapping for converting data from Canonical format to EODS database

EODS_Master_PROCESSING_MAPPING_MDR_

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




9/63


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 fieldsin the table.

Job Parameters:

The following steps describe the Process flow in the job:

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:



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_DBServerName String Database Server Name DEDS0D01

Step Description

1 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)

LAST_UPD_TS to Current System Timestamp


10/63


This Job will transform the input PI customer data into Canonical data model format by applying thetransformation rules as said in the mapping document..


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 dataprocessing, 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/

2 G_S_Cdm_Master_Dir String Master Staging Area /esa/eods/master/canonical

Step Description

1 Read the flat file received from PI client.

2 Implement transformations as mentioned in the data mapping sheet.

3Impement mapping between (LEAD_TYP, SUB-CLT-REL-TYPE) and (BA_ENTRY_SYS_CD, SUB-ORIGINATING-SYST) as mentioned in the data mapping sheet.

4 Derive LEAR_TYP and LEBA_TYP. Refer Mapping sheet for the transformation.

5Store the transformed data into a temporary dataset DS_PI_MDR.ds and a temporary CSV fileSeq_PI_MDR.csv for further processing.


1 G_S_Wrk_Dir String Work Directory /Staging/eods/work/


11/63


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 temporarydatasets which would be used to load ADDRESS and PHYSICAL_LOCATION_SAR_ASSN tables in thesubsequent jobs.

Job Parameters:




Step Description

1 Read all the records from the DS_PI_MDR.ds.

2

Join the records in step 1 and the records in the dataset DS_AgreementGlobalRef.ds, generatedduring Master policy Data processing using the POL_ID

3 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 Accountdata processing. For all those records which do not have LEBA_TYP use them in next step.Create a Temp data for all records having LEAR_TYP roles.

4 Save all the records which are matching and has the UBA_TYP as ISS andUBA_RSN_CD = NEW or RENEWAL into DS_CutomerNew.ds

Save all the records which are matching and has the UBA_TYP as END andUBA_RSN_CD = CHGNM, CHGAD, CHGBN into DS_CustomerEndorsement.ds


1 G_S_Wrk_DataSet_Dir String Work Directory /Staging/eods/dst/

Step Description

1 Read the records in the dataset DS_CustomerNew.ds.

2 Filter all the records which have LEAD_TYP as PRIR (LEAD_TYP derived in CDM Conversionprocess.)

3 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 intoADDRESS table.

To Populate CANP_CD perform the following transformation.If CTRY_CD=CAN then Populate ST_CD else NULL

4

For all the filtered records from step 2, we need to create an entry inPHYSICAL_LOCATION_SAR_ASSN table. Create system generated sequence number andassign it to PLOC_SYS_ID.

Use the ADDR_SYS_ID from step 3 and lookup the input data with data from step 4 usingSAR_TYP as lookup key and get the SAR_SYS_ID and save all the contents into a temporarydataset DS_PI_InsertPLOC according to the data mapping document. This dataset would beused for inserting data into PHYSICAL_LOCATION_SAR_ASSN table.


12/63


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. BulkLoad will be used to load the data into the database.

Job Parameters:


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:


Job #7 Put_PHY_LOC_SAR_ASSN_EODS_LOAD_RA_00









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.






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.


13/63


Purpose:

The purpose of this job is to read the dataset DS_PI_InsertPLOC and populate thePHYSICAL_LOCATION_SAR_ASSN table. Bulk Load will be used to load the data into the database.

Job Parameters:


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 belowjob 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 fromLEGAL_ENTITY table.

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.







Step Description

1 Execute the following query in DB2

SELECT LGLE_SYS_ID,

LGLE_ID,

LGLE_EFF_DT

FROM LEGAL_ENTITY

WHERE LGLE_EXP_DT >= #Current_Processing_Date#

2 Use Dataset stage and load all the contents from step 1 into dataset DS_LGLEDB.ds


14/63


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 theinput 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 legalentities which are not present in EODS. This dataset would be used to insert into LEGAL_ENTITY table.

Job Parameters:


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 toload the EODS

Job Parameters:






Step Description

1 Read all the records in the dataset DS_CustomerNew.ds.

2 Filter all the records which have the LEAR_TYP in (NIN , MT, SMT , LEN, OPER,CI ) AND LEAD_TYP"PRIR"

3 Join the records from step 2 and dataset DS_LGLEDB.ds (target dataset of jobXfm_EODS_Legal_Entities_PI_AR_01) using LGLE_ID as joining key. Data will be partitioned andsorted on LGLE_ID in DataStage environment.

4 All the non matching records should be inserted into LEGAL_ENTITY table. Create a system generatedsequence number and assign it to LGLE_SYS_ID and save the data into a temp datasetDS_InsertLGLE.ds

5 For all the matching records, get the LGLE_SYS_ID from the step 3.

6 Merge these details into a temporary dataset DS_PI_Customer_LGLE.ds. This dataset will be used asa reference to get LGLE_SYS_ID.




15/63


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_ENTITYtable. Bulk Load will be used to load the data into the database.

Job Parameters:



Step Description

1 Read all the records from the dataset DS_PI_Customer_LGLE.ds.

2 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 generatedsequence number and assign to BEN_SYS_ID and write the input data into a temporary datasetDS_BENInsert.ds according to the data mapping document.

If LGLE_TYP is IN create an entry in INDIVIDUAL_PERSON_NAME table. Create a systemgenerated sequence number and assign it to IPN_SYS_ID and write the input data into atemporary 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 systemgenerated sequence number and assign it to LEAR_SYS_ID and write the input data into atemporary 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 inCLIENT_BANK_ASSN table. Create a system generated sequence number and assign it toCB_SYS_ID and write the input data into a temporary dataset DS_CBInsert.ds according tothe data mapping document.

If input LEAD_TYP = INHA or BSM, then create an entry in ADDRESS table. Create a systemgenerated sequence number and assign it to ADDR_SYS_ID and write the input data into atemporary dataset DS_PI_AddrInsert.ds according to the data mapping document.

For all the records inserted into ADDRESS table, an entry should be made inLEGAL_ENTTY_ADDRESS_ASSN table. Create a system generated sequence number andassign it to LEAD_SYS_ID and write the input data into a temporary datasetDS_LEADInsert.ds according to the data mapping document.


16/63



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_ROLEtable. Bulk Load will be used to load the data into the database.

Job Parameters:


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.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.




3 G_S_Password String Database Password **********4 G_S_DBServerName String Database Server Name DEDS0D01


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.


17/63



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_NAMEtable. Bulk Load will be used to load the data into the database.

Job Parameters:


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 theLEGAL_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_BENInsert.ds file.

2 Use DB2 stage and load all the contents from step 1 into BUSINESS_ENTITY table.







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.


18/63



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.Bulk Load will be used to load the data into the database.

Job Parameters:


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 Loadwill be used to load the data into the database.

Job Parameters:









Step Description

1 Use dataset stage to read the DS_LEARInsert.dsfile.

2 Use DB2 stage and load all the contents from step 1 into LEGAL_ENTITY_AGREEMENT_ROLE table.







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.


19/63



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 theLEGAL_ENTTY_ADDRESS_ASSN table. Bulk Load will be used to load the data into the database.

Job Parameters:


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 issplit into two jobs

1) Xfm_EODS_PI_END_RA_Transform_00 and

2) Xfm_EODS_PI_END_RA_Transform_01









Step Description

1 Use dataset stage to read the DS_PI_AddrInsert.ds file.








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.


20/63


Here Xfm_EODS_PI_END_RA_Transform_00 output dataset DS_CutomerEndorsement_NewBa.ds, Thesedataset 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 forloading the tables.

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.dsNote 2: Here Subject_At_Risk Operation is not required








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


21/63


Job #20 Put_EODS_PI_END_RA_BA_Insert

Purpose:

This job would insert data into BUSINESS_ACTION table from the datasetDS_CutomerEndorsement_NewBa.ds.




Step Description

1 Read the input dataset DS_CutomerEndorsement.ds and filter all the records which have UBA_TYP =END and UBA_RSN_CD = CHGADDR, DELGARG, CHGGARG, ADDGARG and LEAD_TYP as PRIR

2 Execute the following query in database

SELECT BA_ID,

MAX(BA_SEQ_NBR),

BA_EFF_DT

FROM BUSINESS_ACTION

GROUP BY BA_ID, BA_EFF_DT

3Lookup all the records from step1 in the data in dataset DS_BusinessAction_Agg.ds using BA_ID,BA_EFF_DT as join key and get the BA_SEQ_NBR.

4 For all the records from step 3, we should insert data into BUSINESS_ACTION table. So insert intothe table by incrementing the BA_SEQ_NBR. Please refer the data mapping sheet for a detailedmapping. 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 systemgenerated number and assign the value to ADDR_SYS_ID. Save the contents from the input file toa temporary dataset DS_RA_ADDRInsert.ds according to the data mapping document. UseBA_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 intoSUBJECT_AT_RISK table. Create a system generated sequence number and assign it toSAR_SYS_ID. Save the contents from the input file to a temporary dataset DS_RA_SARInsert.dsaccording to the data mapping document. Use BA_ID, BA_EFF_DT and BA_SEQ_NBR fromprevious sub step.

For all the records from step 3, we should insert data into PRIMARY_SAR_LOCATION_ASSNtable. Create a system generated number and assign the value to PLOC_SYS_ID. Save thecontents from the input file to a temporary dataset DS_RA_PLOSInsert.ds according to the datamapping document. Use Business action information and subject at risk information from previous

sub steps.








22/63


Job #19 Put_EODS_PI_END_RA_update (RA-Risk Address) This is for Physical Location Sar AssociationUpdate.

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 therecords which have changes in risk address.




Step Description

1 Read the input dataset DS_CutomerEndorsement_NewBa.ds.

2 For all the records, insert into BUSINESS_ACTION table.








23/63


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.


Job #22 Put_EODS_PI_END_RA_SAR_Insert (Deleted this job)



Step Description

1 Read the input dataset DS_CutomerEndorsement_NewBa.ds and filter all the records which haveUBA_TYP = END and UBA_RSN_CD = CHGADDR, DELGARG, CHGGARG, ADDGARG and LEAD_TYPas 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 TableFollowing columns would be updated:

ADDR_EXP_DT

UPDATED_DT

UPDATED_BY

ACT_INSUPD_TS

REC_STUS_CD







Step Description

1 Read the input dataset DS_RA_ADDRInsert.ds .

2 For all the records, insert into ADDRESS table.


24/63


Purpose:

This job would insert data into SUBJECT_AT_RISK table from the dataset DS_RA_SARInsert.ds.


Job #23 Put_EODS_PI_END_RA_PLOC_Insert

Purpose:

This job would insert data into PHYSICAL_LOCATION_SAR_ASSN table from the datasetDS_RA_PLOSInsert.ds.


7.1.2.7 Endorsements Legal entity ADD

Job #24 Xfm_PI_EODS_END_Transform_24 (END - Endorsements)

Purpose:









Step Description

1 Read the input dataset DS_RA_SARInsert.ds .2 For all the records, insert into SUBJECT_AT_RISK table.







Step Description

1 Read the input dataset DS_RA_PLOSInsert.ds .

2 For all the records, insert into PHYSICAL_LOCATION_SAR_ASSN table.


25/63


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:


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 thesucceeding jobs.

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 datasetDS_Cust_End_ADD_LE.ds

If the UBA_TYP = END and UBA_RSN_CD is CHGNM, CHGAD, CHGBA then there is achange 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 entityshould be expired in EODS, write this data into a temp dataset DS_Cust_End_Del_LE.ds








26/63


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 succeedingjobs.

Job Parameters:




Step Description

1

Use the following query to get the BUSINESS_ACTION table

SELECT

BA_ID,

BA_EFF_DT,

BA_SEQ_NBR


WHERE BA_EXP_DT > Scheduled job run date

2

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

MAX(BA_SEQ_NBR)

3 Save the above data in a dataset DS_BusinessAction_Agg.ds







Step Description

1

Use the following query to get the LEGAL_ENTITY table

SELECT

LGLE_ID,LGLE_EFF_DT,

LGLE_SYS_ID

FROM LEGAL_ENTITY

2 Save the above data in a dataset DS_LegalEntity.ds


27/63


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 ofXfm_EODS_LE_END_Transform_26_00 isDS_Cust_End_ADD_LE_With_Ba.ds . This Dataset is input to theXfm_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 savethe data into temporary datasets which would be further used for loading into tables.

Job Parameters:







28/63





29/63




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 thecolumns 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 thedetails in a temporary dataset DS_Cust_BAInsert.ds. Detailed mapping is present in the datamapping sheet.

For all the records in step1, check if Legal Entity already exists in LEGAL_ENTITY Table. If itexists get LGLE_SYS_ID else we need to insert records into LEGAL_ENTITY table. Create asystem generated sequence number and assign it to LGLE_SYS_ID. Save all the contents thatare to be saved in LEGAL_ENTITY table, according to the data mapping document, in atemporary dataset DS_Cust_LGLEInsert.ds. Use the BUSINESS_ACTION details to be addedfrom 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 thecontents 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_ACTIONdetails 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 asystem generated sequence number and assign it to BEN_SYS_ID. Save all the contents thatare to be saved in BUSINESS_ENTITY table, according to the data mapping document, in atemporary 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 contentsthat are to be saved in INDIVIDUAL_PERSON_NAME table, according to the data mappingdocument, in a temporary dataset DS_Cust_IPNInsert.ds. Use the BUSINESS_ACTIONdetails, LEGAL_ENTITY details and LEGAL_ENTITY_ROLE details from the previous substeps.

For every record from step 1, where LEAR_TYP is present, we have to make an entry inLEGAL_ENTITY_AGREEMENT_ROLE table. Create a system generated sequence numberand assign it to LEAR_SYS_ID. Save all the contents that are to be saved inLEGAL_ENTITY_AGREEMENT_ROLE table, according to the data mapping document, in atemporary dataset DS_Cust_LEARInsert.ds. Use the BUSINESS_ACTION details,LEGAL_ENTITY details and LEGAL_ENTITY_ROLE details from the previous sub steps.

For all the records from step 1, if LEAR_TYP is MT or SMT or TMT and if there is value inLOAN_NBR, then we need to create an entry in CLIENT_BANK_ASSN table. Create a systemgenerated sequence number and assign it to CB_SYS_ID. Save all the contents that are to besaved in CLIENT_BANK_ASSN table, according o the data mapping document, in a temporarydataset DS_CustCBInsert.ds. Use the BUSINESS_ACTION details, LEGAL_ENTITY detailsand LEGAL_ENTITY_ROLE details from the previous sub steps.

For all the records where the LEAD_TYP = INHA or BSM then we need to create an entry inADDRESS table. Create a system generated sequence number and assign that value toADDR_SYS_ID. Save all the contents that are to be saved in ADDRESS table, according to themapping document, in a temporary dataset DS_CustADDRInsert.ds. Use theBUSINESS_ACTION details, LEGAL_ENTITY details and LEGAL_ENTITY_ROLE details fromthe previous sub steps.

For all the records where the LEAD_TYP = INHA or BSM then we need to create an entry inLEGAL_ENTITY_ADDRESS_ASSN table. Create a system generated sequence number andassign that value to LEAD_SYS_ID. Save all the contents that are to be saved inLEGAL_ENTITY_ADDRESS_ASSN table, according to the mapping document, in a temporarydataset DS_CustLEADInsert.ds. Use the ADDRESS details, BUSINESS_ACTION details,LEGAL_ENTITY details and LEGAL_ENTITY_ROLE details from the previous sub steps.


30/63


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_ACTIONtable. Bulk Load will be used to load the data into the database.

Job Parameters:


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.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_BAInsert.ds file.

2 Use DB2 stage and load all the contents from step 1 into BUSINESS_ACTION table.







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.


31/63


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_ROLEtable. Bulk Load will be used to load the data into the database.

Job Parameters:


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 theLEGAL_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_LERLInsert.ds file.








Step Description

1 Use dataset stage to read the DS_Cust_LEARInsert.ds file.

2

Join this data with Billing Account data (LEBA_TYP=PO) on LGLE_ID and if we find a match then setLEAR_PAYOR_IND=Y Else N



32/63


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 theINDIVIDUAL_PERSON_NAME table. Bulk Load will be used to load the data into the database.

Job Parameters:


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_ENTITYtable. Bulk Load will be used to load the data into the database.

Job Parameters:


Job #33 Put_LEGAL_CLIENT_BANK_ASSN_LOAD_LE_END_33

Purpose:









Step Description

1 Use dataset stage to read the DS_Cust_IPNInsert.ds file.

2 Use DB2 stage and load all the contents from step 1 into INDIVIDUAL_PERSON_NAME table.







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.


33/63


The purpose of this job is to read the dataset DS_CustCBInsert.ds and populate the CLIENT_BANK_ASSNtable. Bulk Load will be used to load the data into the database.

Job Parameters:


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. BulkLoad will be used to load the data into the database.

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.








34/63


35/63



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 withDS_Cust_End_ADD_LE_With_Ba_Data.ds It will get the BUSINESS_ACTION Load Data.

Job Parameters:


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 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.



Step Description

1 Use dataset stage to read the DS_Cust_End_Del_LE.ds file.

2 Join this data with Legal Entity Add data on BA_ID and if we find a New records loaded into a temporarydatasets

3 Save the Step 2 data Into a DS_Cust_End_Del_BAInst.ds, DS_Cust_End_Del_LE_with_BA.ds








36/63




Step Description

1 Read the data from the dataset DS_Cust_End_Del_LE_with_BA.ds

2Join the data from step 1 with data from dataset DS_CustLEARReference.ds on AGMT_SYS_ID,AGMT_EFF_DT

3Use BUSINESS_ACTION table keys inserted in Put_EODS_CUST_LE_Del_BA_Load_36_02 Job forall the tables below.

3

For the records in step2

Update (expire) LEGAL_ENTITY_AGREEMENT_ROLE table. Following columns would be updated:

LEAR_EXP_DT

BA_IDBA_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

Detailed mapping is found in the mapping document

4

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


6

Update (expire) LEGAL_ENTITY_ADDRESS_ASSN table. Following columns would be updated:

LEAD_EXP_DTBA_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 fromstep2 for the update.

Following columns would be updated:


37/63



Note : Deleted the below description step 1,2,&3

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 theLegal Entity Roles and legal entity IDs for an agreement.

Job Parameters:




Step Description

1 Use dataset stage to read the DS_Cust_End_Del_BAInst.ds


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

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_DTincrement the BA_SEQ_NBR by one and insert the same in BUSINESS_ACTION table. Detailedmapping is present in the data mapping sheet.

Also save the new BA_SEQ_NBR along with the columns from step1 inDS_Cust_End_Del_LE_with_BA.ds





4 G_S_DBServerName String Database Server Name DEDS0D015 G_s_Work_DataSet_Dir String Work Directory /Staging/eods/dst/


38/63


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:


NOTE : In this Job Step 5 is deleted

Job # Put_EODS_CUST_LE_Del_LEAR_Update_38_02(New Job)

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.

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

WHERE LEAR_EXP_DT > #Scheduled run date#

2 Get the data from step1 and write into a temp Dataset DS_CustLEARReference.ds








39/63



Job # Put_EODS_CUST_LE_Del_LERL_Update_38_03 (New Job)

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_ROLE.

Job Parameters:


Job # Put_EODS_CUST_LE_Del_LEAD_Update_38_04 (New Job)

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_ADDRESS_ASSN.

Job Parameters:









Step Description

1 Use dataset stage to read the data from DS_LEAR_Upd.ds








Step Description

1 Use dataset stage to read the data from DS_LERL_Upd.ds









40/63


41/63


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 table ADDRESS

Job Parameters:


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 andDS_Cust_End_ADD_LE_With_Ba_Data.dspopulate the data into DatasetDS_Cust_End_Del_LE_With_Ba_data.ds. Because these Dataset is used in the succeeding jobs in a LegalEntity Change.

Job Parameters:


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 isCHGAD,CHGNM and CHGBA and these are loaded into a temporary datasets.








Step Description

1 Use DB2 stage to read the data from LEGAL_ENTITY_ADDRESS_ASSN




Step Description

1

Use dataset stage to read the data from DS_Cust_End_Del_BAInst.ds,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


42/63


Job Parameters:


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 joiningthe Change Name Endorsement to Business action DataSet. And the DataSetDS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds would be populated with the new Ba_SEQ_NBR andBA_EFF_DT.

Job Parameters:


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.ds file.

2 Join this data with DS_CustLEARReference.ds on AGMT_SYS_ID,AGMT_EFF_DT and if we find aNew records and filter the records into a temporary datasets

3 Save the Step 2 data Into a DS_Cust_End_Chng_LE_Addr_Chng.ds,DS_Cust_End_Chng_LE_Nm_Chng.ds, DS_Cust_End_Chng_LE_CB_Chng.ds



Step Description

1 Use dataset stage to read the DS_Cust_End_Chng_LE_Addr_Chng.ds file.

2

Join this data with DS_Cust_End_Del_LE_With_Ba_data on BA_ID and if we find a New records andloaded into a temporary datasets

3 Save the Step 2 data Into a, DS_Cust_End_Chng_LE_Addr_Chng_Ba_Inst.ds,DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds








43/63



Note : Here Step 1,2 & 3 is Deleted.

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 associationfor all the legal entities which have been changed.

Job Parameters:


Job # Put_EODS_Cust_LE_Addr_Chng_ADDR_Update_40_03 (New Job)



Step Description

1 Use dataset stage to read the DS_Cust_End_Chng_LE_Addr_Chng_Ba_Inst.ds


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

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_DTincrement the BA_SEQ_NBR by one and insert the same in BUSINESS_ACTION table. Detailedmapping is present in the data mapping sheet.

Also save the new BA_SEQ_NBR along with the columns from step1 inDS_Cust_End_Chg_LE_with_BA.ds







Step Description

1 Use dataset stage to read the DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds

2 Use DB2 stage and load all the contents from step 1 into LEGAL_ENTITY_ADDRESS_ASSN table.


44/63




Step Description

1 Read all the record from the dataset DS_Cust_End_Chg_LE_with_BA.ds

2Join the data from step 1 with the data with the data from dataset DS_LGLESysIds.ds onAGMT_SYS_ID, AGMT_EFF_DT

3

If the UBA_RSN_CD = CHGAD then use ADDR_SYS_ID, ADDR_EFF_DT and update theADDRESS table (expire the old records). Following columns would be updated

ADDR_EXP_DT

BA_ID

BA_EFF_DT

BA_SEQ_NBRUPDATED_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 theLEGAL_ENTITY_ADDRESS_ASSN table (expire the old records). Following columns would beupdated

LEAD_EXP_DT

BA_ID

BA_EFF_DT

BA_SEQ_NBRUPDATED_DT

UPDATED_BY

ACT_INSUPD_TS

REC_STUS_CD

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 thedataset DS_LGLEBenSysIDs.ds on AGMT_SYS_ID, AGMT_EFF_DT and update theBUSINESS_ENTITY_NAME table (expire the old records). Following columns would beupdated.

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 thedataset DS_LGLEIPNSysIDs.ds on AGMT_SYS_ID, AGMT_EFF_DT and update theINDIVIDUAL_PERSON_NAME table (expire the old records). Following columns would beupdated.

IPN_EXP_DT

UPDATED_DT

UPDATED_BY

ACT_INSUPD_TSREC_STUS_CD


5

If the UBA_RSB_CD = CHGBA then join the input dataset with the dataset DS_LGLESysIds.ds onAGMT_SYS_ID, AGMT_EFF_DT and update the CLIENT_BANK_ACCOUNT_ASSN table (expirethe old records), Following columns would be updated.

CB_EXP_DT

CB_LOAN_ID

UPDATED_DT

UPDATED_BY

ACT_INSUPD_TS

REC_STUS_CD



45/63


Purpose :

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

Job Parameters:


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 andgenerate the sequence for the following tables ADDRESS and LEGAL_ENTITY_ADDRESS_ASSN andloaded the data into temporary datasets.

Job Parameters:










Step Description

1 Use dataset stage to read the DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds and join withupdated LEGAL_ENTITY_ADDRESS_ASSN table








Step Description

1 Read all the record fomr the dataset DS_Cust_End_Chng_LE_Addr_Chng_NewBa.ds

2 we have to insert data into DS_Cust_End_Chng_LE_Addr_Chng_LeadInst.ds dataset. Create a systemgenerated sequence number and assign it to LEAD_SYS_ID column. Insert intoLEGAL_ENTITY_ADDRESS_ASSN table according to the data mapping document.

3 we have to insert data into DS_Cust_End_Chng_LE_Addr_Chng_AddrInst.ds dataset. Create a systemgenerated sequence number and assign it to ADDR_SYS_ID column. Insert into ADDRESS tableaccording to the data mapping document.


46/63


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:


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 h

EODS Master Customer Data Processing ETL Design Specification v1.1

Documents

Transcript of EODS Master Customer Data Processing ETL Design Specification v1.1