acu crisp 8865 cat claim requirements implementation document

CAT Claim Requirement

Technical Specification

CRISP 8665 - SN30203815

ACE US

Version: 4.1

Issue Date: 28th Feb 2014

Copyright Information© Xchanging 2014

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical photocopying, recording, or otherwise, without the prior permission of Xuber – An Xchanging Company.

Confidential – do not copy or forward on. The document and the information it contains is restricted and the circulation list is controlled by the author who should be identified in the document.

Note only signed hard copies and electronic masters of documents will be controlled. Any other copy may not be current.

Trademark InformationCompany, product, or brand names mentioned in this document, may be the trademarks of their owners.

Approved Distribution List

Name Title

Gayle Sixsmith Xuber Programme Manager

Technical SpecificationCAT Claim RequirementsCRISP 8665, ACUVersion 4.0

Contents

1 Overview 5

2 Functional Requirement 6

3 Technical Approach 6

3.1 TS01 – Create new system parameter 6

3.2 TS02 – Create new Claim Additional Edit Screen6

3.3 TS03 – Create a new Claim Additional Display screen 6

3.4 TS04 – Validate Claim Lost Area Code 6

3.5 TS05 – Update Claim Master to Claim Addtional Details 6

3.6 TS06 – Update Claim Addtional Details to Claim Master 6

3.7 TS07 – Create function to validate the ‘Occurrence Location’ presence 7

3.8 TS08 – Validate ‘Occurrence Location’ – Finalise Claim 7

3.9 TS09 – Validate ‘Occurrence Location’ – Finalise Last Claim Section 7

3.10 TS10 – Validate ‘Occurrence Location’ – Final Indemnity Payment 7

3.11 TS11 – Validate ‘Occurrence Location’ – Final Indemnity Payment (Multi-CS)7

3.12 TS12 – Auto trigger New Claim Additional Details 7

3.13 TS13 – Change ‘Work With Claim’ to add calling point to user hook 7

3.14 TS14 – Create ‘Crt Claim Plug-in 2’ new user hook 7

3.15 TS15 – Create ACU version of ‘Crt Claim Plug-in 2’ user hook 8

3.16 TS16 – Change ‘Crt Claim Master Rcd’ to add calling point to user hook 8

3.17 Process Flow 9

3.18 Functional Areas Affected 9

Business Components/Objects Affected 9

3.19 9

3.20 Data Model Changes 9

4 Chosen Technical Approach 10

5 Assumptions and Limitations 10

6 Technical Implementation 12

6.1 TS01 – New System Parameter 12

6.1.1Definition 12

6.1.2Help Text 12

6.2 Configuration Items 13

© Xchanging 2014 – Confidential Document uncontrolled once printed of 48

http://sharepoint.xchanging.com/sites/ISW/Projects/ACEUS/XPERT Phases/G. Design/Technical Specifications/


6.3 TS02 – Create ‘Edit Claim Addtl Dtls ACU’ (CCUKxx) 14

6.3.1Overview 14

6.3.2Definition 14

6.3.3Screen Layout 14

6.3.4Processing Details 16

6.4 TS03 – Create ‘Disp Claim Addtl Dtls ACU’ (CCUKxx) 23

6.4.1Overview 23

6.4.2Definition 23

6.4.3Screen Layout 23

6.5 TS04 – Create ‘User Spec. CM Val 2 ACU’ (GUMA07CU) 27

6.5.1Overview 27

6.5.2Definition 27


6.6 TS05 – Create ‘User Spec. CM Update ACU’ (GKUH31CU) 28

6.6.1Overview 28

6.6.2Definition 28


6.7 TS06 – Create ‘Crt / Chg Clm Add Dtl ACU’ (GKUH72CU) 29

6.7.1Overview 29

6.7.2Definition 29


6.8 TS07 – Create ‘ACU Val Occurrence Loc’ (RTVOBJ) 30

6.8.1Overview 30

6.8.2Definition 30


6.9 TS08 – Create ‘Claim FNZ User Val ACU’ (GKKXC9CU) 31

6.9.1Overview 31

6.9.2Definition 31


6.10 TS09 – Change ‘Claim Sc FNZ User Val ACU’ (GKUH19CU) 32

6.10.1 Overview 32

6.10.2 Definition 32

6.10.3 Processing Details 32

6.11 TS10 – Change ‘User Spec. Enter Amts ACU’ (GKKX1ACU) 33




6.11.1 Overview 33


6.12 TS11 – Create ‘User Spec. Enter Clm ACU’ (GKUH16CU) 34

6.12.1 Overview 34



6.13 TS12 – Create ‘Work With Claim UH AGR’ (GKUH90CU) 35

6.13.1 Overview 35



6.14 TS13 – Change ‘Work With Claim’ (GKKM24) 36

6.14.1 Overview 36


6.15 TS14 – Create ‘Crt Claim Plug-in 2’ (GKKMxx) 37

6.15.1 Overview 37



6.16 TS15 – Create ‘Crt Claim Plug-in 2 ACU’ (GKKMxxCU) 38

6.16.1 Overview 38



6.17 TS16 – Change ‘Crt Claim Master Rcd’ (GKKM27) 40

6.17.1 Overview 40


6.18 Impact Analysis 41

6.19 Testing Requirements 41

7 Glossary 42

8 Issue List 42

9 Appendix A – Estimation Proposal 42

10 Appendix B – Requirements Traceability Matrix 43

11 Appendix C – Implementation Notes 44

12 Document Control 46

12.1 Document Information 46

12.2 Revision History 46




1 OverviewAt ACE, the CRISP supports the ability for ACE to respond to regulatory reporting requirements known as State Data Calls. It specifically addresses the need to respond to State Data Calls for catastrophe (CAT) claims.

In order to support this business need, ACE requires new fields categorized as “Occurrence Location” to be added in Genius Claims and JWALK at the claim Master level. Additionally, some cross-screen validations and a new hard edit (error message) are required to prevent the Claim Processor from settling the claim if the Data Calls/Occurrence Location fields are not populated.

These distinct “Occurrence Location” fields will then enable a Claim Processor to record CAT event/Occurrence Location details of Place Name (City), Political Division (State/Province), Zip/Postal Code, and Political Sub Division (County) on the claim file. Usage for the new fields will be optional and while the “Occurrence Location” fields may and will be used for many different types of claims when the Claim Processor attempts to settle / close a CAT claim then and only then will entry be mandatory if the field values are not already present.

Further details on this requirement can be found in the SAP Service notification notes: Ref – 300203815 or can be found link:

http://sharepoint.xchanging.com/sites/ISW/Projects/ACEUS/XPERT Phases/F. Analysis/Business Specifications/CRISP 8665 - CAT Claim Requirements – Final BRD.doc

The E1 Estimate document can be found at:http://sharepoint.xchanging.com/sites/ISW/Projects/ACEUS/XPERT Phases/F. Analysis/Business Specifications/Estimates/EST E1 ACU CRISP 8865 CAT Claim Requirements v1.0.doc

This document provides the detailed technical solution for the modification.



http://sharepoint.xchanging.com/sites/ISW/Projects/ACEUS/XPERT%20Phases/F.%20Analysis/Business%20Specifications/Estimates/EST%20E1%20ACU%20CRISP%208865%20CAT%20Claim%20Requirements%20v1.0.doc



http://sharepoint.xchanging.com/sites/ISW/Projects/ACEUS/XPERT%20Phases/F.%20Analysis/Business%20Specifications/CRISP%208665%20-%20CAT%20Claim%20Requirements%20-%20Final%20BRD.doc

http://sharepoint.xchanging.com/sites/ISW/Projects/ACEUS/XPERT%20Phases/F.%20Analysis/Business%20Specifications/CRISP%208665%20-%20CAT%20Claim%20Requirements%20-%20Final%20BRD.doc


2 Functional RequirementACE USA would like to make modification in order to maintain ‘Occurrence Location’ fields within the Claim Additional Details processing and entails the required validation of these new fields within other Claim Maintenance screens (for CAT claims only).

3 Technical Approach

3.1 TS01 – Create new system parameter

Create a new system parameter to indicate if we going to call the new ACU specific Claim Additional Details automatically upon completion of the existing ‘Edit Claim Master 1 Details’ (GKKM21) and ‘Claims Additional Detail’ (GGKM1H) screens.

3.2 TS02 – Create new Claim Additional Edit Screen

Create a new ACU specific Claim Additional Details screen to maintain the new ‘Occurence Location’ related fields.

3.3 TS03 – Create a new Claim Additional Display screen

Create a new ACU specific Claim Additional Details screen to display the new ‘Occurence Location’ related fields maintained through the edit screen mentioned above.

3.4 TS04 – Validate Claim Loss Area Code

A new ACU specific user hook function will be created to validate the Claim Loss Area Code against the value list created for ‘Occurrence Location Political Division’ (State) – Claim Addl Code 10 before they are being synced and updated.

3.5 TS05 – Update Claim Master to Claim Addtional Details

The existing AGR version of the user hook User Spec. CM Update ACU’ (GKUH31AG) which is triggered from GKKM21, will need to be copied to ACU specific and modified to incorporate an update from Claim Master’s Clm Loss Area Code within the Edit Claim Master screen (GKKM21) to Occurrence Location’s Political Division’ (State) which will be maintained using the new Edit Claim Additional Details screen mentioned above.

3.6 TS06 – Update Claim Addtional Details to Claim Master

An ACU version of the user hook function GKUH31 will be created incorporate an update from ‘Political Division’ (State) maintained using the new Edit Claim Additional Details screen mentioned above, to both Claim Master’s Clm Loss Area Code an ClM U/A 2nd Area Code.



Sucharita Ghosh, 02/24/14,

(Cognizant) 2-24- No default is required in Political sub-division (county) field in the new claim additioanl deatil screen from claim master screen. It will be selected by the user from the value list in the new screen. Also please note that the value in Clm U/A 2nd area code will be same as Clm Loss area code when the claim loss area code is a state/US territory in claim master screen.


3.7 TS07 – Create function to validate the ‘Occurrence Location’ presence

This new ACU specific retrieve object function will be created to validate the presence of ‘Occurrence Location’ data when a claim is defined as ‘CAT Claim’.

3.8 TS08 – Validate ‘Occurrence Location’ – Finalise Claim

An ACU version of the user hook function GKKXC9 will be created to call the new function created (in TS05) above that validates the presence of ‘Occurrence Location’ data during Finalise Claim when a claim is defined as ‘CAT Claim’.

3.9 TS09 – Validate ‘Occurrence Location’ – Finalise Last Claim Section

The ACU version of the user hook function GKUH19 will be created to call the new function created (in TS05) above that validates the presence of ‘Occurrence Location’ data during Finalising the Last Claim Section when a claim is defined as ‘CAT Claim’.

3.10 TS10 – Validate ‘Occurrence Location’ – Final Indemnity Payment

The ACU version of the user hook function GKKX1A will be changed to call the new function created (in TS05) above that validates the presence of ‘Occurrence Location’ data during Final Indemnity Payment when a claim is defined as ‘CAT Claim’.

3.11 TS11 – Validate ‘Occurrence Location’ – Final Indemnity Payment (Multi-CS)

The AGR version of the user hook GKUH16 will need to be copied as a new ACU version of the user hook. This ACU version will then be modified to call the new function created (in TS05) above that validates the presence of ‘Occurrence Location’ data during Final Indemnity Payment (Multi-Claim Section) when a claim is defined as ‘CAT Claim’.

3.12 TS12 – Auto trigger New Claim Additional Details

The ‘Work With Claim UH – Product Process’ (GKUH90) will be copied from the existing AGR version to an ACU version in order to auto-trigger the new Claim Additional Details screen if defined with the Product Claim and the new system parameter (as defined in Section 3.1) is turned on. Once defined and the system parameter turned ‘ON’, the new screen will be called upon completion of the Claim Master (GKKM21) screen and as well after the completion of the existing Claim Additional Detail screen.

3.13 TS13 – Change ‘Work With Claim’ to add calling point to user hook

The ‘Work With Claim’ (GKKM24) currently calls the above user hook (GKUH90) during ‘Initialise Program’ only. In order to process the auto-trigger as mentioned above, new calling point to GKUH90 will be added in order to process the auto-trigger of the new Claim Additional Detail.

3.14 TS14 – Create ‘Crt Claim Plug-in 2’ new user hook

Processing is needed to call the new Claim Additional Detail screen during claim creation. This user wook will be called from the same GKKM27 but at different user point.




3.15 TS15 – Create ACU version of ‘Crt Claim Plug-in 2’ user hook

A new ACU version of the above user hook will be created so that during claim creation, upon completion of the Edit Claim Master (GKKM21) screen, the new Claim Additional Detail screen need to be called before the existing Claim Additional Detail screen (GKKM1H).

3.16 TS16 – Change ‘Crt Claim Master Rcd’ to add calling point to user hook

This function is called from GKKM21 during claim creation and new processing requirement is to call the new Claim Additional Detail screen before the current Claim Additional Detail screen. In ‘Crt Claim Master Rcd’ (GKKM27), we can use and modify the exsiting user hook ‘Crt Claim Plug-in – Claim Master’ (GKKM2A), however we need to modified all other customer versions (including AGR version) of this user hook for this new processing to work. Thus, in order to avoid this and testing them, a new similar user hook will be introduced and implemented.




3.17 Process Flow

Not applicable

3.18 Functional Areas Affected

Claims Maintenance

3.19 Business Components/Objects Affected

3.20Data

Model Changes

None.



Object ID Description

CCUKxx Edit Claim Addtl Dtls ACU

CCUKxx Disp Claim Addtl Dtls ACU

GKUH31CU User Spec. CM Update ACU

GKUH72CU Crt / Chg Clm Add Dtl ACU

GKKXC9CU Claim FNZ User Val ACU

GKUH19CU Claim Sc FNZ User Val ACU

GKKX1ACU User Spec. Enter Amts ACU

GKUH16CU User Spc Enter MS Clm ACU

GKUH90CU Work With Claim UH ACU

GKKM24 Work With Claim

GUMA07CU User Spec. CM Val 2 ACU

GKKMxx Crt Claim Plug-in 2

GKKMxxCU Crt Claim Plug-in 2 ACU

GKKM27 Crt Claim Master Rcd


4 Chosen Technical ApproachTheirs is only one chosen technical approach as outlined in the estimate document of this modification.

5 Assumptions and Limitations1. No GGI changes are required for this modification.

2. The ‘Zip/Postal Code’ (Zip Code) will have it’s ‘Postcode Area Surrogate’ 11aintained in the Claim Addiotional Details file in the form of Post Code. A Postal Code will then determine the Postal Third Area and it’s Third Area Description and they will be displayed in the edit or display screens. As such, the ‘Zip/Postal Code’ will not have a default set for ‘Claim Addl Text 01 (CAX2)‘ under Product Claim Additional Details as it’s not feasible to store the ‘Postcode Area Surrogate’ which is a numeric undescriptive field.

3. The ‘Political Division’ (State/Province) and ‘Political Sub Division’ (County) fields will use the defined values lists selection/validation process.

4. The spare code/fields suggested to store the ‘Occurrence Location’ related fields are not in use by ACE though Genius or any other external systems used in ACE. However, these spare code/fields can be defined and used within other Claim Additional Detail edit screens other than GKKM1H. ACE should ensure that no other claim additional detail edit screen apart from GKKM1H to be used. Otherwise, there is a possibility of duplicate usage of these spare code/fields which means that this mod may not to work as intended.

5. The mapping for the Claim Additional Details to maintain the ‘Occurrence Location’ fields will be as follows:

Claim Additional Details Fields ‘Occurrence Location’ Fields

Claim Addl Text 01 Place Name(City)

Claim Addl Code 10 Political Division (State)

Claim Addl Text 02 Zip/Postal Code

Claim Addl Code 11 Political Sub-Division (County)

6. Setting the system parameter CCUFNCSZOS (Finalise Claim Sections if O/S reduced to zero?) will set the O/S Adjustment Type of ‘Z’ (Zerorise) to ‘F’ (Finalised) and finalise the claim summary for a section during Outstanding entry. This happens regardless of Movement Type 1 Code of ‘IND’. As closure of claim summary is not the scope of this mod, this processing will be ignored for further changes.




7. The domestic CAT (i.e CAT Claims) is identified with the presence of FAFA2C (ClM Lvl 2 Cat Code) within the Claim Master (ZKFA). If a value present then, this is considered a CAT Claim.

8. The new claim additional screen(CCUKxx) will be triggered from the following point:

Create Claim

(auto trigger based on the new system parameter CCUCMAUCAD)

GKKM21 (Edit Claim Master 1 Details)↓

GKKM1H (Claim Master Additional Details)↓

CCUKxx (New Claim Additional Details)↓

GKKM22 (Edit Claim Contacts)

Amend Claim

(auto trigger based on the new system parameter CCUCMAUCAD)

GKKM24 (Work with Claims)↓

GKKM21 (Edit Claim Master 1 Details)↓

GKKM22 (Edit Claim Contacts)↓

CCUKxx (New Claim Additional Details)

Amend Claim

(Using option ‘2 – Edit’ on the existing Claim Additional Detail screen – GKKM1H)

GKKM1H (Claim Master Additional Details)↓

CCUKxx (New Claim Additional Details)

Amend Claim

(Using option ‘2’ on the new claim additional screen – CCUKxx)

Will directly call the new screen:CCUKxx (New Claim Additional Details)

9. It is assumed that another version of Edit Claim Master (GKKM23) which is designed for Unattached claims is not being used by ACE currently.

10. When defaulting Political division/state code from new Claim additional detail screen to Clm Loss Area code in Claim master screen, the same value should be defaulted to Clm U/A 2nd area code also.




6 Technical Implementation

6.1 TS01 – New System Parameter

6.1.1 Definition

A new customer specific system parameters is required to indicate if we going to call the new ACU specific Claim Additional Details automatically upon during create and amend claim.

Parameter ID Description Type Len Sel/Val Pgm

Init Val

C/B Vers

?

Group

CCUCMAUCAD Auto Trigger New Claim Additional Detail Screen?

CDE 1 GGAP09 N Y *CLAIMS

6.1.2 Help Text

6.1.2.1 CCUCMAUCAD

System Parameter Type Length

CCUCMAUCAD CDE 1

Auto Trigger New Claim Additional Detail Screen?

This parameter controls if the newly defined Claims Additional Detail screen will be called after the existing ‘Edit Claim Master 1 Details’ (GKKM21) and ‘Claims Additional Detail’ (GGKM1H) screens. Both these existing screens are defined within the ‘Work With Product Process’ screen as ‘MST – Master’ and ‘CM2 – Claim Master Add Dtls’ respectively . The new ‘Claims Additional Detail’ screen are defined as ‘CM3 – Master Add Dtls Ext’.

If the system parameter is set to ‘Y’, then the new Claim Additional Details will be called automatically during create and amend claim, otherwise the new screen will not be called.

This system parameter may be versioned by company/branch and qualified by product code.

Possible Values: Y – Yes

N – No

Delivery Value : N

Maintenance: User




6.2 Configuration Items

Create an *After program to create a new enquiry option for:

To create the new system parameter.

Create a new enquiry Option for ACU to display Claim Additional Details using command ‘GCRTENQDEF CMDOPT(Z9) PGMCDE(‘CCUKxx’ as per section 6.4 ) LONGNM(‘Display Claim Master Addtl Details’) SHRTNM(*DERIVE) CUSTSP(Y)

Update the new ‘Additional details edit program’ created in section 6.3 in the ‘Program’ file so that it could be used within Genius Product set-up. This could be achieved by the following statement..

CALL PGM(GUMT32) PARM(‘ ‘ ‘7’ ‘CCUKxx’ ‘Edit Claim Additional Details’

‘Edit Claim Additional Details ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘).

Create new qualifier type ‘PRODUCT’ using the following command:

CRTQUALTYP CODE(PRODUCT) DESC(‘Product Code’) LABEL(‘Product’)

SLABEL(‘Prod.’) ALABEL(‘Prd’) COL1(‘Product’) COL2(‘Product’) SELVAL(GGAP10)

Add the new qualifier type created above to the new system parameter CCUCMAUCAD created in section 6.1.2.1 using the following command:

ADDQPARDEF PARAMETER(CCUCMAUCAD) Q1(1/PRODUCT)




6.3 TS02 – Create ‘Edit Claim Addtl Dtls ACU’ (CCUKxx)

6.3.1 Overview

Create this edit record function to maintain the ‘Occurrence Location’ related fields.

6.3.2 Definition

Object Name : Edit Claim Addtl Dtls ACUOther Definition : Same as ‘GKKM1H’

6.3.3 Screen Layout

Create a new screen as follows:

*PROGRAM *SCREEN ID OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO DD/MM/YY HH:MM:SSOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOType details, press Enter. Occurence Location: OOOOOOOOOOOOOOO ______________________________ OOOOOOOOOOOOOOO ________ OOOOOOOOOOOOO OOOOOOOOOOOOOOO _______________ OOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOO ________ OOOOOOOOOOOOO

F3=Exit F12=Previous F15=Enquiry

CCUKxx 12/07/13 17:13:20 Amend Claim Period . . . : 04/01/13 – 04/01/14 Policy . . . : D08689575 001 CRISP_9768_002 Claim File ID : JY13J0004015 CRISP_9768_002Type details, press Enter.Occurrence Location:City . . . . .: Pennsylvania___________________State/Province: PHILA __ PhiladelphiaZip Code . . .: PA 19106-3640 PHID Philadephila Mid-WestCounty . . .. : #USA____ U.S.A





Field Length Usage Notes

Variable Screen Title 40 O Row 01

Claim Heading 1 78 O Row 02



Clm Addl Text 01 Ttl 15 O Row 07 – Field 1

Claim AddlText 01 30 I Row 07 – Field 2 (City)

Claim Addl Code 10 Title 15 O Row 08 – Field 1

Claim Addl Code 10 8 I Row 08 – Field 2 (State)

Value Code 8 Shrt Nme 1 15 O Row 08 – Field 3

Claim Addl Text 02 Title 15 O Row 09 – Field 1

Post Code 8 I Row 09 – Field 2 (Zip Code)

Third Area Code 5 O Row 09 – Field 3

Third Area Description 15 O Row 09 – Field 4


Claim Addl Code 11 8 O Row 10 – Field 2 (County)


Claim Addl Code 10 Grp 2 H N/A





6.3.4 Processing Details

6.3.4.1 USER: Initialize program

Same as GKKM1H except ‘Initialise fields’ routine.

6.3.4.2 USER: Initialize detail screen (new record)

Get the Claim Additional Fields usages by calling RTVOBJ function ‘Rtv Prod Clm Add Dtl All – Product Clm Add Dtls’. Pass in the PAR context of Cl Product Code and Cl Product Sequence and pass out all other fields to LCL context.

Get the ‘ClM Loss Area Code’ from Claim Master by calling RTVOBJ function ‘Rtv Clm Loss Area Code – Claim Master’. Pass in the PAR context of Cl Product Code and Cl Product Sequence and pass out all other fields to LCL context.

Insert a sequence (IS) and setup the input fields as follows (name this routine as ‘Setup screen fields – Occurrence Location’):

Default Place Name – City (Claim Addl Text 01)

If LCL.Clm Addl Text 01 Usg is ‘Display/Mand/Opt’, then:

Set DTL.Clm Addl Text 01 Ttl as LCL.Clm Addl Text 01 Ttl

Set DTL.Claim Addl Text 01 as LCL.Clm Addl Text 01 Dft

Otherwise blank out the following fields if field usage is ‘hide’:

DTL.Clm Addl Text 01 Ttl, DTL.Claim Addl Text 01.

Default Political Division – State (Claim Addl Code 10)

If LCL.Clm Addl Code10 Usg is ‘Display/Mand/Opt’, then:

Set DTL.Clm Addl Code 10 Title as LCL. Claim Addl Code 10 Title

If LCL.ClM Loss Area Code is ‘Not Blank’, then set DTL.Claim Addl Code 10 as LCL.ClM Loss Area Code, otherwise set DTL.Claim Addl Code 10 as LCL. Claim Addl Code10 Dft .

Set DTL.Claim Addl Code 10 Grp as LCL.Claim Addl Code10 Dft Grp.

Retrieve the Description for the defaulted value. Call the function ‘ZRtv Val Code 8 rec – Value Code 8’, passing in the DTL Claim Addl Code 10 Grp and DTL. Claim Addl Code 10 as the input parameters in sequence. Pass out the Value Code 8 Short Name to DTL. Value Code 8 Shrt Nme 1.


DTL.Claim Addl Code 10 Title, DTL.Claim Addl Code 10 and DTL.Claim Addl Code 10 Grp.




Default Political Sub-Division – County (Claim Addl Code 11)



Set DTL.Claim Addl Code 11 as LCL. Claim Addl Code11 Dft .





Default Zip/Postal Code (Claim Addl Text 02)

Now setup the ‘Claim Addl Text 02’ to denote the Zip/Postal Code’. To do this check if LCL. Clm Addl Text 02 Usg is ‘Display/Mand/Opt’, then set DTL. Clm Addl Text 02 Ttl as LCL. Clm Addl Text 02 Ttl.

6.3.4.3 USER: Initialize detail screen (existing record)

Get the Claim Additional Fields usages by calling RTVOBJ function ‘Rtv Prod Clm Add Dtl All – Product Clm Add Dtls’. Pass in the PAR context of Cl Product Code and Cl Product Sequence and pass out all other fields to LCL context.

Retrieve existing Claim Additional details by calling RTVOBJ function ‘Rtv Claim Addl Dtls (all) – Claim Additional Details’. Pass in the PAR context of Claim Master Code and pass out all other fields to LCL context.

Insert a sequence (IS) and setup the used fields as follows (name this routine as ‘Setup screen fields – Occurrence Location’):

Set Place Name – City (Claim Addl Text 01)

If LCL.Clm Addl Text 01 Usg is ‘Display/Mand/Opt’, then:


Set DTL.Claim Addl Text 01 as LCL.Clm Addl Text 01.


DTL.Clm Addl Text 01 Ttl, DTL.Claim Addl Text 01.




Set Political Division – State (Claim Addl Code 10)


Set DTL.Clm Addl Code 10 Title as LCL. Claim Addl Code 10 Title.

Set DTL.Claim Addl Code 10 as LCL. Claim Addl Code10.





Set Political Sub-Division – County (Claim Addl Code 11)



Set DTL.Claim Addl Code 11 as LCL. Claim Addl Code11.





Set Zip/Postal Code (Claim Addl Text 02)

Now setup the ‘Claim Addl Text 02’ to denote the Zip/Postal Code’. To do this check if LCL. Clm Addl Text 02 Usg is ‘Display/Mand/Opt’, then set DTL. Clm Addl Text 02 Ttl as LCL. Clm Addl Text 02 Ttl. Set the

Call function ’Rtv using Postcode Srgt – Postcode Area Link’ passing in LCL. Claim Addl Text 02 and output the First Area Code and Second Area Code to DTL. Post Code and DTL. Third Area Code respectively.

If LCL.Ex? Postcode Area Link is Exist, call the function ‘Rtv Area Long Name – Area’ passing in Third Area Code and pass out the DTL. Third Area Description.




Store initial values of Edit Claim Additional Details

Set WRK.Edt Clm Addl Dtl-before1 and WRK.Edt Clm Addl Dtl-before2 as ‘BLANK’

Set WRK.Edt Clm Addl Dtl-before1 using retrieve message on message ‘Edit Clm Addl Dtl fields4’, passing in DTL.Claim Addl Text 02,10 and 11.

Set WRK.Edt Clm Addl Dtl-before2 using retrieve message on message ‘Edit Clm Addl Dtl fields7’, passing in DTL.Claim Addl Text 01.

6.3.4.4 USER: Process key screen request

Same as GKKM1H.

6.3.4.5 USER: Validate detail screen fields

If F15 is selected, call the normal enquiry screen internal function ‘Enter Enquiry System. – Command Option’. Set the input and output parameter same as function GKKM1H.

Validate Default Value/Description for the used fields as follows:

Validate Place Name (Claim Addl Text 01)

Check if value entered if usage is mandatory. To do this check if DTL.Claim Addl Text 01 is ‘Blank’ and LCL.Clm Addl Text 01 Usg is ‘Mandatory’ and perform the following if it’s true:

Set WRK.Clm Addl Text 01 Ttl as DTL.Clm Addl Text 01 Ttl

Use the utility function ‘G/Strip SAA padding – Utilities’ using WRK. Clm Addl Text 02 Ttl.

Send error message ‘Mandatory field’ (EPG2222) using WRK Clm Addl Text 01 Ttl and DTL Claim Addl Text 01.

Validate Political Division (Claim Addl Code 10)

If DTL. Claim Addl Code 10 is ‘Select’, call the function ‘G/Slt Value Code 8 long – Value Code 8’ passing in the DTL Claim Addl Code 10 Grp and DTL Claim Addl Code 10. Pass out the value of ‘Value Code 8 Short Name’ to DTL. Value Code 8 Shrt Nme 1 and set the PGM.*Defer confirm as ‘Defer confirm’.

Check the value entered if usage is mandatory. To do this check if DTL. Claim Addl Code 10 is ‘Blank’ and LCL.Claim Addl Code10 Usg is ‘Mandatory’ and perform the following if it’s true:

Set WRK. Claim Addl Code 10 Title as DTL. Claim Addl Code 10 Title

Use the utility function ‘G/Strip SAA padding – Utilities’ using WRK. Claim Addl Code 10 Title.




Send error message ‘Mandatory field’ (EPG2222) using WRK Claim Addl Code 10 Title and DTL Claim Addl Code 10.

Set the DTL. Value Code 8 Shrt Nme 1 as ‘*BLANK’

Retrieve the Political Division Description if value entered. To do this check if DTL. Claim Addl Code 10 is NOT ‘Select’ and DTL.Claim Addl Code 10 is ‘Not Blank’ and perform the following if it’s true:

Call the function ‘ZRtv Val Code 8 rec – Value Code 8’, passing in the DTL Claim Addl Code 10 Grp and DTL. Claim Addl Code 10 as the input parameters in sequence. Pass out the Value Code 8 Short Name to DTL. Value Code 8 Shrt Nme 1.

If WRK.Ex? Value Code 8 is ‘Does not exist’, then send error message – ‘Value not found.’ (GGN2133) passing in DTL. Claim Addl Code 10.

Validate Sub-Division – County (Claim Addl Code 11)

If DTL. Claim Addl Code 11 is ‘Select’, call the function ‘G/Slt Value Code 8 long – Value Code 8’ passing in the DTL Claim Addl Code 11 Grp and DTL Claim Addl Code 11. Pass out the value of ‘Value Code 8 Short Name’ to DTL. Value Code 8 Shrt Nme 1 and set the PGM.*Defer confirm as ‘Defer confirm’.

Check the value entered if usage is mandatory. To do this check if DTL. Claim Addl Code 11 is ‘Blank’ and LCL.Claim Addl Code11 Usg is ‘Mandatory’ and perform the following if it’s true:

Set WRK. Claim Addl Code 11 Title as DTL. Claim Addl Code 11 Title

Use the utility function ‘G/Strip SAA padding – Utilities’ using WRK. Claim Addl Code 11 Title.

Send error message ‘Mandatory field’ (EPG2222) using WRK Claim Addl Code 11 Title and DTL Claim Addl Code 11

Set the DTL. Value Code 8 Shrt Nme 2 as ‘*BLANK’

Retrieve the Political Division Description if value entered. To do this check if DTL. Claim Addl Code 11 is NOT ‘Select’ and DTL.Claim Addl Code 11 is ‘Not Blank’ and perform the following if it’s true:

Call the function ‘ZRtv Val Code 8 rec – Value Code 8’, passing in the DTL Claim Addl Code 11 Grp and DTL. Claim Addl Code 11 as the input parameters in sequence. Pass out the Value Code 8 Short Name to DTL. Value Code 8 Shrt Nme 2.

If WRK.Ex? Value Code 8 is ‘Does not exist’, then send error message – ‘Value not found.’ (GGN2133) passing in DTL. Claim Addl Code 11.

Validate Zip/Postal Code (Claim Addl Text 02)




Post Code must be entered if usage is mandatory, to do this, check if DTL.Post Code is ‘Blank’ and LCL. Clm Addl Text 02 Usg is ‘Mandatory’ and perform the following is it’s true:

Set WRK. Clm Addl Text 02 Ttl as DTL. Clm Addl Text 02 Ttl

Use the utility function ‘G/Strip SAA padding – Utilities’ using WRK. Clm Addl Text 02 Ttl.

Send error message ‘Mandatory field’ (EPG2222) using WRK Clm Addl Text 02 Ttl and DTL. Post Code.

Set the DTL.Third Area Code and DTL.Third Area Description as ‘*BLANK’.

Retrieve Post Code if value entered, to do this, check if DTL. Post Code is not Blank and perform the following:

Check if select has been requested. To do this, check if DTL.Post Code is Select Request, the do the following is true:

Call function ‘Z/Remove ? from field – Utilities’ using DTL. Post Code.

Call the function ‘Select Postcode – Postcode Area Link’ passing the DTL. Claim Addl Text 02 as the Postcode Area Surrogate and pass out Post Code as DTL. Post Code. Set the PGM.*Defer confirm as ‘Defer confirm’.

Call function ’Rtv using Postcode – Postcode Area Link’ passing in DTL. Post Code and output the DTL. Third Area Code.

If LCL.Ex? Postcode Area Link is Does Not Exist, send error message – ‘Postcode Invalid’ (GGN5994). Otherwise, call the function ‘Rtv Area Long Name – Area’ passing in Third Area Code and pass out the DTL. Third Area Description.

Call User Hook

Set LCL.Claim Addl Text 01 Err as ‘No’. Do the same for Claim Addl Code 10 Err, Claim Addl Code 11 Err and Claim Addl Text 02 Err.

Call the user hook ‘UsrSpc Edt Clm Add DtlGNS – Claim Additional’ (GKUH23) as how being called in GKKM1H.

Highlight Claim Additional Details fields in error. To do this, check LCL.Claim Addl Text 01 Err is Yes, then call function ‘Highlight Field – Utilities’ for DTL.Claim Addl Text 01. To this step for Claim Addl Code 10 Err, Claim Addl Code 11 Err and Claim Addl Text 02 Err as well.

If LCL.Exit Code is ‘Error’, then set PGM.*Defer confirm as ‘Defer confirm’.




6.3.4.6 USER: Create DBF record

Call function ‘EXT Crt/Chg Clm Addtl Dtl – Claim Additional Details’ (GKKM4P) as how being called in GKKM1H.

6.3.4.7 USER: Change DBF record

Call function ‘EXT Crt/Chg Clm Addtl Dtl – Claim Additional Details’ (GKKM4P) as how being called in GKKM1H.

6.3.4.8 USER: Exit program processing

Same as GKKM1H.




6.4 TS03 – Create ‘Disp Claim Addtl Dtls ACU’ (CCUKxx)

6.4.1 OverviewThis is a new ACU specific Claim Additional Details display screen to display ‘Occurrence Location’ fields as maintained Edit Claim Additional screen program created in section Error:Reference source not found6.3 above.

6.4.2 DefinitionSame as GEKM52

6.4.3 Screen Layout

*PROGRAM *SCREEN ID OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO DD/MM/YY HH:MM:SSCmd Opt = __ OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOccurence Location: OOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOO OOOOOOOO OOOOOOOOOOOOO OOOOOOOOOOOOOOO OOOOOOOOOOOOOOO OOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOO OOOOOOOO OOOOOOOOOOOOO

F3=Exit F12=Previous

NWSCRN 12/07/13 17:13:20 Amend Claim Period . . . : 04/01/13 – 04/01/14 Policy . . . : D08689575 001 CRISP_9768_002 Claim File ID : JY13J0004015 CRISP_9768_002Type details, press Enter.Occurrence Location:City . . . . .: PennsylvaniaState/Province: PHILA PhiladelphiaZip Cod . . . : PA 19106-3640 PHID Philadephila Mid-WestCounty . . .. : #USA U.S.A





Field Length Usage Notes

Variable Screen Title 40 O Row 01

Next Cmd Opt 2 I Row 02




Clm Addl Text 01 Ttl 15 O Row 07 – Field 1

Claim Addl Text 01 30 O Row 07 – Field 2 (City)

County code description 15 O Row 07 – Field 3


Claim Addl Code 10 8 O Row 08 – Field 2 (State)


Claim Addl Text 02 Title 15 O Row 09 – Field 1

Post Code 8 O Row 09 – Field 2 (Zip Code)

Third Area Code 5 O Row 09 – Field 3

Third Area Description 15 O Row 09 – Field 4


Claim Addl Code 11 8 O Row 10 – Field 2 (County)







6.4.3.1 USER: Initialize program

Similar to GEKM52.

6.4.3.2 USER: Load detail screen from DBF record

Construct Claim enquiry header by calling GEKM00.

Get the Claim Additional Fields usages by calling RTVOBJ function ‘Rtv Prod Clm Add Dtl All – Product Clm Add Dtls’. Pass in the PAR context of Product Code and Product Sequence and pass out all other fields to LCL context.

Insert a sequence (IS) and setup the used fields as follows (name this routine as ‘Setup screen fields – Occurrence Location’):

Set City Name (Claim Addl Text 01)

If LCL.Clm Addl Text 02 Usg is ‘Hide’, then:

Blank out DTL.Clm Addl Text 01 Ttl, DTL.Claim Addl Text 01.

Otherwise:


Set DTL.Claim Addl Text 01 as LCL.Claim Addl Text 01

Set Political Division – State (Claim Addl Code 10)

If LCL.Clm Addl Code10 Usg is ‘Hide’, then:

Set DTL.Claim Addl Code 10 and DTL.Claim Addl Code 10 Grp as *BLANK.


Set DTL.Clm Addl Code 10 Title as WRK. Claim Addl Code 10 Title.

Retrieve the Description for the defaulted value. Call the function ‘Rtv Val Code 8 rec – Value Code 8’, passing in the DTL Claim Addl Code 10 Grp and DTL. Claim Addl Code 10 as the input parameters in sequence. Pass out the Value Code 8 Short Name to DTL. Value Code 8 Shrt Nme 1.

.

Set Political Sub-Division – County (Claim Addl Code 11)

If LCL.Clm Addl Code11 Usg is ‘Hide’, then:

Set DTL.Claim Addl Code 11 and DTL.Claim Addl Code 11 Grp as *BLANK.





Set DTL.Clm Addl Code 11 Title as WRK. Claim Addl Code 11 Title.

Retrieve the Description for the defaulted value. Call the function ‘Rtv Val Code 8 rec – Value Code 8’, passing in the DTL Claim Addl Code 10 Grp and DTL. Claim Addl Code 11 as the input parameters in sequence. Pass out the Value Code 8 Short Name to DTL. Value Code 8 Shrt Nme 2.

Set Zip/Postal Code (Claim Addl Text 02)

Now setup the ‘Claim Addl Text 02’ to denote the Zip/Postal Code’. To do this check if LCL. Clm Addl Text 02 Usg is ‘Hide’, then blank out DTL.Claim Addl Text 02 Title and DTL.Claim Addl Text 02. Otherwise, then set DTL. Clm Addl Text 02 Ttl as LCL. Clm Addl Text 02 Ttl.

Call function ’ Rtv using Postcode Srgt – Postcode Area Link’ passing in LCL. Claim Addl Text 01 and output the DTL. Third Area Code.

If LCL.Ex? Postcode Area Link is Exist, call the function ‘Rtv Area Long Name – Area’ passing in Third Area Code and pass out the DTL. Third Area Description.

6.4.3.3 USER: Process key screen request

Same as GEKM52

6.4.3.4 USER: Validate detail screen

Same as GEKM52

6.4.3.5 USER: Process command keys

Same as GEKM52

6.4.3.6 USER: Exit program processing

Same as GEKM52




6.5 TS04 – Create ‘User Spec. CM Val 2 ACU’ (GUMA07CU)

6.5.1 OverviewThe AGR version of the user hook GUMA07 will need to be copied as a new ACU version of the user hook. This ACU version will then be modified to validate the Claim Loss Area Code against the value list created for ‘Occurrence Location Political Division’ (State) – Claim Addl Code 10 before they are being synced and updated.

6.5.2 Definition

Object Name : User Spec. CM Val 2 ACUOther Definition : Same as ‘GUMA07AG’

6.5.3 Processing DetailsCheck if PAR.User Validation Type is ‘After Validation’ . If true, check that we do not proceed if processing is being triggered from GGI. To do this checking, call function ‘GGI Trans Srgt Handler – GGI Transaction’ (GUGI8J), using the condition ‘Get’ for the ‘Array Handler Action ‘. If LCL GGI Trans Surrogate is ‘Zero’ (Non-GGI) then do the following:

If PAR.ClM Lvl 2 Cat Code (CAT Code) is Not Blank AND PAR.ClM Loss Area Code (Loss Location Area Code) is Not Blank:

Get the Claim Additional Fields usages by calling RTVOBJ function ‘Rtv Prod Clm Add Dtl All – Product Clm Add Dtls’. Pass in the PAR context of Product Code and Product Sequence and pass out all other fields to LCL context.

Call the function ‘ZRtv Val Code 8 rec – Value Code 8’, passing in the LCL. Claim Addl Code 10 Grp Dft and PAR. ClM Loss Area Code as the input parameters in sequence.

If WRK.Ex? Value Code 8 is ‘Does not exist’:

Then send new error message – ‘Claim Loss Area not found in value list &1’ passing in PAR. ClM Loss Area Code. &1 will be the LCL. Claim Addl Code 10 Grp Dft which need to passed in as well.

Set PAR.Loss Area W/E flag as CND.Error

Set PAR.QRY Message ID as CND.Error.




6.6 TS05 – Create ‘User Spec. CM Update ACU’ (GKUH31CU)

6.6.1 OverviewThis ACU version of the user hook function will need to be created to synchronize the existing ’Event Location’ field on with the new ‘Occurrence Location Political Division’ (State) field which will now be maintained through the Claim Additional Screen above. In other words, whenever the value ‘Event Location’ changes then value of ‘Occurrence Location Political Division’ (State) also changes and vice versa; both fields will always reflect the same value.

6.6.2 Definition

Object Name : User Spec. CM Update ACUOther Definition : Same as ‘GKUH31’

6.6.3 Processing DetailsAdd performance enhancement code.

Check if (PAR.Claim Update Mode .X is ‘Change Claim – Batch’ OR ‘Create – Interactive’ OR ‘Change Edit 2/3’) AND PAR.User Validation Type is After Update. If true, do the following:

If PAR.ClM Lvl 2 Cat Code (CAT Code) is Not Blank AND PAR.ClM Loss Area Code (Loss Location Area Code) is Not Blank:

Set the LCL. Claim Addl Code 10 as PAR. Loss Area Code.

Now, create and call a new retrieve object on ‘Claim Additional Details’ file. Pass in the LCL. Claim Addl Code 10 only to be updated/created. Within this retrieve object, call the default create object if no record found and change object if otherwise. All other values should be as per it is, except Claim Addl Code 10 which should be updated from the passed in PAR context.

Send a information message saying ‘Claim Master’s data has been updated to ‘Occurrence Location’ within Claim Additional Details.’




6.7 TS06 – Create ‘Crt / Chg Clm Add Dtl ACU’ (GKUH72CU)

6.7.1 OverviewThis ACU version of the user hook function will be created to synchronize the new ‘Political Division’ (State) maintained through the new maintenance screen defined in section 6.3 with the Claim Master’s Loss Area Code and Clm U/A 2nd Area Code. In other words, whenever the value ‘Political Division’ (State) changes, then Claim Master’s Loss Area Code and Clm U/A 2nd Area Code are also updated so that both fields will always reflect the same value.

6.7.2 Definition

Object Name : Crt / Chg Clm Add Dtl ACUOther Definition : Same as ‘GKUH72’


Check if PAR.User Validation Type is ‘After Create’ OR ‘After Update’. If true, then create and call a new change object (similar to ‘G/Change ClM Loss Area Cd – Claim Master’) that updates the ‘ClM Loss Area Code’ and ‘Clm U/A 2nd Area Code’ with ‘Claim Addl Code 10’.

Send a information message saying ‘Occurrence Location’s data has been updated to Claim Master’.




6.8 TS07 – Create ‘ACU Val Occurrence Loc’ (RTVOBJ)

6.8.1 OverviewThis new ACU specific retrieve object function will be created to validate the presence of ‘Occurrence Location’ data when a claim is defined as ‘CAT Claim’.

6.8.2 DefinitionObject Name : ACU Val Occurrence LocFunction Type : Retrieve ObjectFunction File : Claim Additional DetailsAccess Path : RTV All flds

Parameter Usage CommentClaim Master Code IClM Lvl 2 Cat Code IValidation Errors B

6.8.3 Processing Details

6.8.3.1 USER: Initialize routine

Set the PAR.Validation Errors as ‘No’.

6.8.3.2 USER: Processing if Data record not found

If PAR.ClM Lvl 2 Cat Code is Not Blank, set the PAR.Validation Errors as ‘Yes’.

6.8.3.3 USER: Process Data record

If PAR.ClM Lvl 2 Cat Code is Not Blank, then if DB1.Claim Addl Code 10/11 is Blank OR DB1.Claim Addl Text 01/02 is Blank, then set PAR.Validation Errors as ‘Yes’.

6.8.3.4 USER: Exit processing

If PAR.Validation Errors is ‘Yes’, send error message ‘Occurrence Location fields are required entries before closing of CAT claim is allowed.’




6.9 TS08 – Create ‘Claim FNZ User Val ACU’ (GKKXC9CU)

6.9.1 OverviewThis ACU version of the user hook function will be created to call the retrieve object function that validates the presence of ‘Occurrence Location’ data during Finalise Claim when a claim is defined as ‘CAT Claim’.

6.9.2 Definition

Object Name : Claim FNZ User Val ACUOther Definition : Same as ‘GKKXC9’


Call the new function created in section 6.8 (TS07 – Create ‘ACU Val Occurrence Loc’ (RTVOBJ)) and pass in all available parameters from PAR context. Pass out the ‘Validation Errors’ to LCL context.

If LCL. Validation Errors is ‘Yes’, set the PAR.Claim Finalis’n Exit Sts as ‘Error’.




6.10 TS09 – Change ‘Claim Sc FNZ User Val ACU’ (GKUH19CU)

6.10.1 OverviewThis ACU version of the user hook function will be created to call the retrieve object function that validates the presence of ‘Occurrence Location’ data during Finalising the Last Claim Section when a claim is defined as ‘CAT Claim’.

6.10.2 Definition

Object Name : Claim Sc FNZ User Val ACUOther Definition : Same as ‘GKUH19’


Set the LCL.Claim Finalis’n Exit Sts as ‘No Error’ and set PAR.Claim Finalis’n Exit Sts as LCL.Claim Finalis’n Exit Sts.

Create a new retrieve object based on Claim Section file (restrict by Claim Master Code only) that does the following:

For each record read for the entire Claim, add a count if Claim Section Status is ‘Open’. Check if the counter reaches more than 1, if yes, set new flag ‘Last Clm Sec to be Fnlsd?’ as ‘No’ on the PAR context and quit. In the ‘USER: Exit processing’ user point, if the count is 1, set the ‘Last Clm Sec to be Fnlsd?’ on the PAR context as ‘Yes’.

If the returned LCL. Last Clm Sec to be Fnlsd? Is ‘Yes’, continue processing as follows:

Call to function ‘Rtv All – Claim Master’ to retrieve the ‘ClM Lvl 2 Cat Code’ and pass it out to LCL context.

Now, call the new function created in section 6.8 (TS07 – Create ‘ACU Val Occurrence Loc’ (RTVOBJ)) and pass in all available parameters from PAR /LCL context. Pass out the ‘Validation Errors’ to LCL context.

If LCL. Validation Errors is ‘Yes’, set the LCL.Claim Finalis’n Exit Sts as ‘Error’.

Pass the LCL.Claim Finalis’n Exit Sts to PAR..Claim Finalis’n Exit Sts.




6.11 TS10 – Change ‘User Spec. Enter Amts ACU’ (GKKX1ACU)

6.11.1 OverviewThis ACU version of the user hook function will be modified to call the retrieve object function that validates the presence of ‘Occurrence Location’ data during Final Indemnity Payment when a claim is defined as ‘CAT Claim’.

6.11.2 Processing DetailsWithin the case ‘Before Validate SFL RCD’, add the following after all existing processing if the LCL. Claim Section Status is ‘Open’:

If PAR.Movement Type 1 Code .W is ‘Indemnity’ AND PAR.O/S Adjustment Type is ‘Zero’ then do the following:

Get ‘ClM Lvl 2 Cat Code’ from Claim Master and move the value to LCL context.

Call the new function created in section 6.8 (TS07 – Create ‘ACU Val Occurrence Loc’ (RTVOBJ)) and pass in all available parameters from PAR/LCL context. Pass out the ‘Validation Errors’ to LCL context.

If LCL. Validation Errors is ‘Yes’, set the PAR.Error/Warning? As ‘Error’.




6.12 TS11 – Create ‘User Spec. Enter Clm ACU’ (GKUH16CU)

6.12.1 OverviewThe AGR version of the user hook GKUH16 will need to be copied as a new ACU version of the user hook. This ACU version will then be modified to call the retrieve object function that validates the presence of ‘Occurrence Location’ data during Final Indemnity Payment (Multi-Claim Section) when a claim is defined as ‘CAT Claim’.

6.12.2 Definition

Object Name : User Spec. Enter Clm ACUOther Definition : Same as ‘GKUH16’

6.12.3 Processing DetailsWithin the case condition ‘PAR.User Validation Type is Before Validate SFL RCD’, add the following after all existing processing if the LCL. Claim Section Status is ‘Open’:

If PAR.Movement Type 1 Code .W is ‘Indemnity’ AND PAR.O/S Adjustment Type is ‘Zero’ then do the following:

Get ‘ClM Lvl 2 Cat Code’ from Claim Master and move the value to LCL context.

Call the new function created in section 6.8 (TS07 – Create ‘ACU Val Occurrence Loc’ (RTVOBJ)) and pass in all available parameters from PAR/LCL context. Pass out the ‘Validation Errors’ to LCL context.

If LCL. Validation Errors is ‘Yes’, set the PAR.Error/Warning? As ‘Error’.




6.13 TS12 – Create ‘Work With Claim UH AGR’ (GKUH90CU)

6.13.1 OverviewThe AGR version of the user hook GKUH90 will need to be copied as a new ACU version of the user hook. This ACU version will then be modified to call the new Claim Additional Details, upon completion of the Claim Master (GKKM21) screen and as well after the completion of the existing Claim Additional Detail screen.

6.13.2 Definition

Object Name : Work With Claim UH AGROther Definition : Same as ‘GKUH90AG’

6.13.3 Processing DetailsCopy the exisiting ‘Work With Claim UH AGR’ (GKUH90AG) and make the following change after all existing processing:

Add a new case condition ‘Processing SFL – PreConfirm’ and do the following if PAR.User Validation Type is ‘Process SFL Rcd(Pre Conf) :

If (PAR. Process Type is ‘Claim Master’ OR PAR. Process Type is ‘Claim Master Add Dtls’, then do the following:

Get the auto trigger flag defined in the new system parameter CCUCMAUCAD using the ‘Access Parameter API – Utilities’ (G#UTP5), using best match and pass in PAR. Cl Product Code as the Qualifier 1. Pass out the value to a new user field ‘Auto trigger Cl Addl Dtl?’.

If LCL. Auto trigger Cl Addl Dtl? Is ‘Yes’ then do the following:

Call the function ‘Get Program Code – Product Process’ to check if Process Type ‘CM3’ is defined to trigger the new Claim Additional Details. Pass in PAR context for the Product related parameters. Set condition for Process Type as ‘Claim Master Add Dtls Ext’ (add this new condition as ‘110’ with display value ‘CM3’) and pass out the value of ‘Process Edit Program Code’ to LCL.

If LCL. Process Edit Program Code is ‘Not Blank’, then call ‘Call Edit Pgm – Clm – Product Process’ (GUPXE2) using PAR values where available and LCL for others. Use LCL for ‘Process Edit Program Code’ as well.




6.14 TS13 – Change ‘Work With Claim’ (GKKM24)

6.14.1 OverviewThis core screen function currently calls the above user hook (GKUH09) during ‘Initialise Program’ only. In order to process the auto-trigger of the new Claim Additional Detail screen, a new calling point to GKUH09 will be added in order to process the auto-trigger processing.

6.14.2 Processing DetailsUSER: Process subfile record (Pre-confirm)

Copy the call to GKUH90 within the use point ‘USER: Initialize program’ to the user point ‘USER: Process subfile record (Pre-confirm)’, right after the ‘Revise or Display’ routine. Pass in PAR context.




6.15 TS14 – Create ‘Crt Claim Plug-in 2’ (GKKMxx)

6.15.1 OverviewProcessing is needed to call the new Claim Additional Details screen during claim creation. This core user hook will be introduced and will be called from GKKM27 to trigger processing required after he calling of Claim Master Screen (GKKM21) but before the calling of the existing Claim Additional Detail screen.

6.15.2 Definition

Object Name : Crt Claim Plug-in 2 Other Definition : Same as ‘GKKM2A’

6.15.3 Processing DetailsThis is a core user hook and no processing required.




6.16 TS15 – Create ‘Crt Claim Plug-in 2 ACU’ (GKKMxxCU)

6.16.1 OverviewThe ACU version of new user hook will be created to call the new Claim Additional Details screen, upon completion of the Claim Master (GKKM21) screen and as well after the completion of the existing Claim Additional Detail screen.

6.16.2 Definition

Object Name : Crt Claim Plug-in 2 ACUOther Definition : Same as ‘GKKM2A’

6.16.3 Processing DetailsAdd performance enhancement processing.

If PAR.Exit Code is Continue List the perform the following:

Get the auto trigger flag defined in the new system parameter CCUCMAUCAD using the ‘Access Parameter API – Utilities’ (G#UTP5), using best match and pass in PAR. Cl Product Code as the Qualifier 1. Pass out the value to a new user field ‘Auto trigger Cl Addl Dtl?’.

If LCL. Auto trigger Cl Addl Dtl? Is ‘Yes’ then do the following:

Call the function ‘Get Program Code – Product Process’ to check if Process Type ‘CM3’ is defined to trigger the new Claim Additional Details. Pass in PAR context for the Product related parameters. Set condition for Process Type as ‘Claim Master Add Dtls Ext’ (add this new condition as ‘110’ with display value ‘CM3’) and pass out the value of ‘Process Edit Program Code’ to LCL.

If LCL. Process Edit Program Code is ‘Not Blank’, then call ‘Call Edit Pgm – Clm – Product Process’ (GUPXE2) using PAR values where available and LCL for others. Use LCL for ‘Process Edit Program Code’ as well.

Create a routine called ‘Process Exit Code’ and perform the following:

If PAR.Exit Code is Exit, call function ‘G/Exit – Quit #01 – Utilities’

If PAR.Exit Code is Previous AND WRK.Process Edit Program Code is Not Blank, then create routine called ‘Take into account bypass master’ and do the following:

If LCL.Bypass Master? Is Yes




IF LCL.Display Clm Sect Attach ? is No, call G/Exit – Previous #01 – Utilities’, otherwise set WRK.Next program to call as CND.First.

Otherwise, set the WRK.Next program to call as CND.Third.

If PAR.Exit Code is Previous AND WRK.Process Edit Program Code is Blank, then create a routine called ‘Processing for F12’ and do the following:

If LCL.Bypass Master? Is Yes

IF LCL.Display Clm Sect Attach ? is No, call G/Exit – Previous #01 – Utilities’, otherwise set WRK.Next program to call as CND.First.

Otherwise, set the WRK.Next program to call as CND.Third.

If PAR.Exit Code is Continue List, then set WRK.Next program to call as CND.Fourth.




6.17 TS16 – Change ‘Crt Claim Master Rcd’ (GKKM27)

6.17.1 OverviewThis core screen function will be modified to call the new user hook (GKKMxx) as defined in section 6.15 in order to process the auto-trigger of the new Claim Additional Detail screen.

6.17.2 Processing DetailsRight after the call to ‘Edit Claim Master 1 – Claim Master’ and it’s ‘Process Exit Code’ routine, insert a call to ‘TS14 – Create ‘Crt Claim Plug-in 2’ (GKKMxx)’ passing in the same paramaters defined on the call to GKKM2A from this main function.




6.18 Impact Analysis

This Core Genius modification will allow user to maintain the ‘Occurence Location’ related fields and validate the claim maintenance accordingly.

6.19 Testing Requirements

Testing should be done in ACU environment for green screen as follows:

1. Check that the ‘Occurrence Location’ can be maintained according to the requirement.

2. Check that the maintained ‘Occurrence Location’ data can be displayed through Genius

Enquiry system.

3. Check that the Claim Master’s Event Location and are always synced with Claim

Additional Detail’s (Occurrence Location) Political Division .

4. Check that if the absent of ‘Occurrence Location’ data, a claim defined as ‘CAT’ claim will

be validated and informed while processing the following:

Finalise Claim

Finalise Last Section Claim

Final Indemnity Payment

Final Indemnity Payment (Multi Claim Section)

5. Check that during claim creation, the new Claim Addititional Detail screen gets called automatically soon after the Edit Claim Master (GKKM21) screen and before the existing Claim Additional Detail screen.

6. Check that during claim amend, the new Claim Addititional Detail screen gets called automatically after the Edit Claim Contacts (GKKM22).




7 Glossary

Term Definition

8 Issue List

Issue Owner Priority Comments Status

9 Appendix A – Estimation Proposal




10 Appendix B – Requirements Traceability Matrix

CRISP 8865

TS01

TS02

TS03

TS04

TS05

TS06

TS06

TS07

TS08

TS09

TS10

TS11

TS12

TS13

TS14

TS15

TS16




11 Appendix C – Implementation NotesIn order to use the new Claim Additional Details screen (e.g. CCUKxx in this example) we will need to define it as follows under the Product Process:

GPPMC7 Work with Product Process 20/01/14 9:27:56 Product . . . : SWSQBH QBE Test Product – Fcode (Hid) Version . . . : 001 1/01/00 – 31/12/39 Status . . . : Current Proc category : C Claims Type options, press Enter. 2=Change 4=Delete Op Seq Typ Description Edit Command Program Option 10 USR User Option CAGK07 10 CMS Master 20 CSC Amounts and Sections 25 USR NCCI Reporting Codes GWCK04 30 LIT Litigations 40 REC Recoveries 50 CNI Name Involvement 60 CRC Related Claims 70 CDC Documents 80 CM2 Additional Details GKKM1H 90 CM3 Claim Master Add Dtls CCUKxx BottomF3=Exit F6=Add F8=Narrative F12=Previous

GPPMA2 Edit Product Process 20/01/14 9:31:34 Product . . . : SWSQBH QBE Test Product – Fcode (Hid) Version . . . : 001 1/01/00 – 31/12/39 Status . . . : Current Type details, press Enter. Proc category : C Claims Process Type . : CM3 Long Name . . : Claim Additional Detail Ext Short Name . . : Clm Add Dtl Ext Sequence . . . : 90 Edit Program . : CCUKXX Command Option : F3=Exit F12=Previous




Note that Genius only allows one process type of ‘CM2’, thus the new screen would need to be defined as process type ‘CM3’. This ‘USR’ process type is a user define process, thus it will not be automatically triggered/called during claims creation. User intervention is required to use option ‘2=Change’ against the new user option in order to maintain the new Claim Additional Details, in which in this case will be the new ‘Occurrence Location’ fields.

The new ‘Occurrence Location’ fields will be optional entries and may be used by the Claim Processor (business user) for any type of claim entered into Genius and at any time during the claim lifecycle.




12 Document Control

12.1 Document Information

Prepared by: Seliyan Swaminathan

Project Manager: Gayle Sixsmith

Programme Manager: Gayle Sixsmith

12.2 Revision History

Version Date Author Description

0.1 19/09/2013 Seliyan Swaminathan Draft

0.2 26/09/2013 Seliyan Swaminathan After review by Shan Gurusamy

1.0 26/09/2013 Shan Gurusamy Authorised

1.1 20/01/2014 Seliyan Swaminathan Changes in requirement from ACE

1.2 23/12/2014 Seliyan Swaminathan After review by Shan Gurusamy

2.0 24/12/2014 Shan Gurusamy Authorised (Pending answers from ACE converted as assumptions)

2.1 12/02/2014 Seliyan Swaminathan Changes to Screen Flow

3.0 12/02/2014 Shan Gurusamy Auth version

3.1 26/02/2014 Seliyan Swaminathan Final updates on assumptions and synchorization of Clm U/A 2nd Area Code.

4.0 28/02/2014 Seliyan Swaminathan Authorized Version after review and confirmation from ACE.

4.1 05/03/2014 Seliyan Swaminathan Changes During PUT (Appendix

