You are on page 1of 652

Claims Applications Convergence

Web GUI Functional Specification

Change Control Log:-

Release Date Changed SIRS/TP Description of Changes Made Screen(s)


By No. involved

2.0. 02/02/2004 DTW N/a Initial Version N/a

2.1. 10/02/2004 N/a N/a No On-Line Changes in this release N/a

2.3. 01/03/2004 N/a N/a Change to general character All


validation – to disallow double
quotes in all fields.

2.4. 04/03/2004 DTW 37546 changes have been made to LY34 to Claim Details
pass back a value of spaces in the
Adjuster/Lawyer Name and
Reference to the GUI with an
associated Attribute of 'S'
(Suppressed) for all internally
created claims. The process
description has been changed to
hide the Adjuster/Lawyer Names
and their associated prompts if the
attribute is ‘S’.

Xchanging Ins-sure Services • Ins-sure House • Trinity Road • Folkestone • Kent • CT20 2RJ • UK
Fax : 01303 252858 • www.xchanging.com
Xchanging cost for value..........resource for service
- 19/03/2004 SJB N/a Verified ‘CICS Transactions’ for Various
each screen.

29/03/04 DAS 36170 When using navigation bar to go Bulk Component


from the bulk component selection Selection /
screen to the bulk component Component de-
confirmation screen , if a component selection
has been de-selected and the user Confirmastion
answers ‘no’ when asked if they message
want to de-select the component the
bulk component selection screen
should be rebuilt using LY64.
01/01/07 AMC TP 310086 ECF Phase 6 changes
Changes to include ‘ECF Claim’ on ‘Claim Transaction
‘CTC screen’. Creation screen’

Changes to include ‘Broker TR’ and ‘Financial Details


‘Broker TR Qual’ on the ‘Financial Control screen’
Details Control’ screen

Changes to validation of UCR and Copy from UCR’


TR on ‘Copy from UCR’ screen screen

04/01/07 AMC TP 332465 XCS Enhancements Phase 1 ‘Breakdown –


SCM Advice’
Change to include ‘Direct Report’ screen
and ‘Claim in Litigation’ on the
‘Breakdown – SCM Advice’ screen
XCS CLASS 29/08/07 DTW XCS/0024 XCS Enhancements Phase 3 ‘Expert Fees
Enh. 3.0 Breakdown’
Addition of new ‘Expert Fees screen
Breakdown’ screen, accessed from
the ‘SCM Advice (Breakdown)’
Screen. ‘Breakdown –
(Section 4.41) SCM Advice’
screen
Changes to SCM Advice screen to
add processing for new “Expert
Fees Breakdown” button.
(Section 4.17)

Changes to SCM Advice Screen, to


change prompt for the
Adjuster/Lawyer fields
(Section 4.17)
XCS CLASS 13/09/2007 DTW XCS/0024 Amendments required following ‘Expert Fees
Enh 3.0 review of Functional Design Breakdown’
screen

‘Breakdown –
SCM Advice’
screen

Xchanging Ins-sure Services • Ins-sure House • Trinity Road • Folkestone • Kent • CT20 2RJ • UK
Fax : 01303 252858 • www.xchanging.com
Xchanging cost for value..........resource for service
XCS CLASS 17/09/2007 DTW XCS/0024 Amend Commarea fields for Expert ‘Expert Fees
Enh 3A (Org) Name and Expert Contact Breakdown’
Name. screen’
XCS CLASS 20/09/2007 DTW XCS/0024 Add additional validation (E689) ‘Expert Fees
Enh 3A Amend Error Situation for Error Breakdown’
E678 screen
Amend Screen Images for Expert
Fees Breakdown scree – to show
correct format for PTD and PTT
totals at top of screen.
XCS CLASS 24/09/2007 DTW XCS/0024 XCS/0024 - New Validation added to ‘Expert Fees
Enh 3A ensure that the experts flagged for Breakdown’
inclusion on SCM are valid experts screen
(I.e. are present on VGLFEEA1).
XCS CLASS 08/10/2007 DTW XCS/0024 (1)Ensure that processing only ‘Expert Fees
Enh 3A insists on experts being flagged Breakdown’
for advising on SCM if at least screen
one of them is still valid.
(2)An overall indicator is required in
the commarea - to indicate
whether PTD should be
unprotected on new experts.
(3)The GUI validation against PTD
should be removed. This
validation is also performed by
the mainframe, where warnings
can be issued.
(4)If an Expert Type has been
entered, the Expert Name drop
down list should be filtered
accordingly.
XCS CLASS 12/10/2007 DTW XCS/0024 A new GUI error is required, on ‘Expert Fees
Enh 3A pressing the 'Expert Fees Breakdown’
Breakdown' link. This will force the screen
removal of decimal places for JPY -
before the user goes to the Expert
Fees Breakdown screen. Also, the
processing of PTT amounts should
be consistent between teh two
screen - so GUI validation is
required against the PTT amount on
the Expert screen as well (i.e. to
reject decimal places for JPY).
XCS CLASS 14/11/2007 DTW XCS/0021b Add a new Claims Coverage CCVC Screen
Enh 3B Validation Check (CCVC) screen.
XCS CLASS 26/11/2007 DTW XCS/0045 Display of Original Broker Code:- - Policy/Risk Details
Enh 3B XCS/0003 Changed format of Policy/Risk Screen
XCS/0008 Details screen, FDC Screen, Loss - Financial Details
Details Screen Control Screen
Add Commas to Financial Amount:- - Loss Details
Changed formatting of financials on Screen
Policy/Risk and FDC
Peer Review on FDC:-
Changed FDC screen to include
enterable Peer Review Code

Xchanging Ins-sure Services • Ins-sure House • Trinity Road • Folkestone • Kent • CT20 2RJ • UK
Fax : 01303 252858 • www.xchanging.com
Xchanging cost for value..........resource for service
XCS CLASS 21/12/2007 DTW XCS/0045 Display of Original Broker Code:- - Subsequ
Enh 3B Changed format of Subsequent ent Advice
Advice Schedule Screen Schedule
Screen

XCS CLASS 27/12/2007 DTW XSC/0045 Display of Original Broker Code - Market Details
Enh 3B Changed the format of the following Screen
screens:- - Non-Settlement
- Market Details Summary
- Non-Settlement Summary - Conclusion of
- Conclusion of Bulk Bulk Settlement
Settlement - Transaction
- Transaction History History
- Movement History - Movement
- Claim Details Screen History
- Find Claim
Certificate of Insurance No. - Claim Details
Included new Certificate of Screen
Insurance No. field, and associated
processing, on the following
screens:-
- Find Claim
- Claim Details Screen

Cause Code
Included new Cause Code field and
associated processing on the Claim
Details screen
XCS CLASS 09/01/2008 DTW XCS/0021b – CCVC Questionnaire - CCVC Screen
Enh 3B Correct wording of Special Payment
question on the screen image

XCS CLASS 21/01/2008 DTW XCS/0045 – Display Original CCVC Screen


Enh 3B Broker
1) The prompt for the
CCVC screen said "Curr
Bkr:" - all other screens
show "Current Bkr:"
CCVC screen changed.

XCS/0021b – CCVC
Questionnaire
1) The name of the ‘Clear
Form’ button has been
changed to ‘Reset
Form’.

XCS ECF 05/03/2008 DBP ECF Classifiaction on CTC:- Claim Transaction


Classification Changed CTC screen to include Creation screen
enterable ECF Classification Code (Section 4.9)

Xchanging Ins-sure Services • Ins-sure House • Trinity Road • Folkestone • Kent • CT20 2RJ • UK
Fax : 01303 252858 • www.xchanging.com
Xchanging cost for value..........resource for service
XCS CLASS 26/08/2008 DBP TP631646 CR4 – Advanced Search
Phase 4 See separately held CLB910 and Selection screen
CLB920 specs for changes to the
Additional Claim Search Extract Advanced Search
programs Results screen

See Advanced Search spec for Exit Process


changes to
Advanced Search Selection screen Group Ref/Broker
UCR Search
CR5 – See Advanced Search spec Results screen
For changes to
Advanced Search Results screen OSND Search
and changes to add SCR045 to the Results screen
Exit process
Subsequent
CR6 – See sections Advice Schedule
4.6 OSND Search Results screen screen
4.7 Group Ref/Broker UCR Search
Results screen Policy/Risk Details
4.20 Subsequent Advice Schedule screen
screen
SCM Advice
CR7 - See Sections (Breakdown)
4.12 Policy/Risk Details screen screen
4.17 SCM Advice (Breakdown)
screen

XCS CLASS 14/10/2008 DBP TP631646 CR8 – Segmentation See Section SCM Advice
Phase 4 4.17 Breakdown SCM Advice screen (Breakdown)
screen

Xchanging Ins-sure Services • Ins-sure House • Trinity Road • Folkestone • Kent • CT20 2RJ • UK
Fax : 01303 252858 • www.xchanging.com
Xchanging cost for value..........resource for service
1. Introduction

1.1. Purpose of Document

The project to converge the Claims Applications


includes the development of a Web GUI front-end to
provide the functionality within the converged CLASS
environment that was previously provided within COSS.

1.1.1. This Functional Specification which will document


the front-end functionality in sufficient detail to
allow software design and development to be
undertaken.

1.2. Project Background

As part of Xchanging Ins-sure Services long-term


strategic policy to increase efficiency and reduce costs
it has been decided that the functionality provided by
the COSS system, used by the Lloyds Syndicate market,
should be incorporated into the CLASS system,
currently used by the IUA Company market. The need
for this convergence is further highlighted by the fact
that the platform on which the COSS system is written
is no longer supported and any technical problems with
this could prove extremely costly, both to Xchanging
Ins-sure Services and the Syndicate market.

The most important difference between CLASS and


COSS is that CLASS is primarily designed to facilitate
the agreement of claims by company claims adjusters,
with fully automated settlement of agreed amounts,
whereas COSS processes already agreed claims in
order to provide underwriters with technical claims
information and to produce statutory and regulatory
accounts and reports, with separate entry of related
claim settlement amounts. Hence the data structures
for the two systems are significantly different. The
major problem that has had to be resolved in the
converged system is enabling the data to be stored and
retrieved at the correct level to enable Xchanging Ins-
sure Services to continue to support technical claims
output to syndicates and regulatory/statutory reporting

David Willcocks 6 May 2002


Xchanging Ins-sure Services Ltd
obligations to Lloyd’s underwriters. A data model for
the converged system is included in the Appendices.

This functional specification details the functionality


required within the Web-enabled GUI front-end that will
be used by Xchanging In-sure Services and Xchanging
Claims Services technicians to create, maintain and
review claims within the Lloyds Syndicate market. This
GUI will also be used to supplement claims that have
been entered by brokers on the existing ‘CLASS for
Lloyds’ system, in order to fulfil regulatory/statutory
reporting obligations.

The batch dependencies, such as the SCM Message


extract, CTF File extract to LIDS and Data Warehouse
feeds, will be dealt with in separate documents –
although this On-line Functional Specification has taken
these dependencies into account in the design of the
data structure.

1.3. References

A list of the documents that are referred to in the


Functional Specification. This is expected to
include:

- The Web GUI Software Infrastructure Design


Document with particular emphasis on site /
page design guidelines and templates
- The data model for the converged system
- Separate business process definitions ?

2. Business Requirements

This section provides definitions of the business processes


which are the subject of the front-end functionality to be
provided by the web GUI. In addition, this section includes
an explanation of any business terminology used in these
definitions or referred to in the detailed specification of
associated functionality.

2.1. Business Processes

David Willcocks 7 May 2002


Xchanging Ins-sure Services Ltd
The key business processes are defined here and are
expressed in a high level diagrammatic form.
Each process is divided into a series of sub-processes
represented by a series of boxes. For each sub-process
box the corresponding system screens to achieve that
process are listed. This enables the mapping between
the business processes and system screens to be easily
understood.
Screen Navigation in section 3 takes these same
processes and shows at a further level of detail how the
screen flows will work to implement the processes.

Only three key processes have been identified at


this point. It is intended to extend this to cover
more processes.

2.1.1. Login

David Willcocks 8 May 2002


Xchanging Ins-sure Services Ltd
Login

Access System
Change
Password

System Access
Home
Granted

Login

2.1.2. Xchanging Created Claim – First Advice

David Willcocks 9 May 2002


Xchanging Ins-sure Services Ltd
Review Claim File Home

Policy / Risk
Find Claim
Details
OSND
Market
Search
Review Policy & Results
Details

Claim Details Group


Search Claim Details
Results
Claim Financial
Transaction Details
Creation Control

Sub Advice
SCM Advice
Schedule
Single Claim
Binder
Create Breakdown Schedule
Loss
Reserves
Select Items
RI Schedule for Bulk
Settlement

Conclusion of
Bulk Sett

Review & Summary -


Non
Complete Claim
Broker Created Claim Settlement
Summary -
- & Subsequent Advice on Settlement
All Claims

Prepare For Next Home


Claim

David Willcocks 10 May 2002


Xchanging Ins-sure Services Ltd
2.1.1 Broker Created Claim & Subsequent Advice on All
Claims

Review Claim File Home

Policy / Risk
Find Claim
Details
OSND
Market
Search
Review Policy & Results
Details

Claim Details Group


Search Claim Details
Results
Claim Financial
Transaction Details
Creation Control

Sub Advice
SCM Advice
Schedule
Single Claim
Binder
Create Breakdown Schedule
Loss
Reserves
Select Items
RI Schedule for Bulk
Settlement

Conclusion of
Bulk Sett

Review & Summary -


Non
Complete Claim
Broker Created Claim Settlement
Summary -
- & Subsequent Advice on Settlement
All Claims

Prepare For Next Home


Claim

David Willcocks 11 May 2002


Xchanging Ins-sure Services Ltd
2.2. Business Definitions

Fig 2.2.1. A glossary of all relevant business definitions


used in this specification, arranged in alphabetical
order

Business Definition
Terminology
CLASS Claims Loss Advice and Settlement
System. System currently used by brokers
to advise claims and supply details of
claim settlements within the IUA
Company market, and by Companies to
agree claims. Either the bureau leader
can agree on behalf of the whole market
(ILU) or the each company can agree
their own share (LIRMA).
CLASS for Lloyds This gives the ability for brokers to advise
claims and supply details of claim
settlements in the Lloyds Syndicate
market. It also facilitates the agreement
of these claims by either syndicates, XIS
or XCS. The XIS/XCS agreement
functionality will provided within the new
Web GUI.
COR Claims Office Reference. A unique
reference, assigned by the system,. At the
Lloyds Loss/Statistical Split level.

COSS Claims system used by XIS or XCS


technicians to process already agreed
claims in order to provide underwriters
with technical claims information and to
produce statutory and regulatory
accounts and reports, with separate entry
of related claim settlement amounts.

CTF Completed Claims Transaction File. This


is a file of completed settlement
transactions extracted from the new
converged Claims system and processed
by LIDS.
LIDS
OSND Original Signing Number and Date. This

David Willcocks 12 May 2002


Xchanging Ins-sure Services Ltd
Business Definition
Terminology
reference identifies the policy to which
the claim relates.
SCM Syndicate Claims Message. A message
sent daily to syndicates providing them
with details of technical claims
information at COR level.
TDN Taking Down Number. A unique system
generated number (including a date and a
sequence number) which identifies a
particular monetary transaction. This
number will be stored at ‘collection’ level
in the CLASS data structure and also on
the LIDS database.
FIL Code
DTI Code
TF Code Trust Fund Code. This applies to US and
Canadian business only.
NAIC Code The ‘National Association of Insurance
Commissioners’ Code

3. Screen Navigation

This section contains screen navigation diagrams for the key


business processes as described in Section 2.1. The screen
names used allow cross-referencing with the appropriate
Functional Definitions in Section 4.

Each diagram shows only the main processing routes and


therefore not every possible navigation path is shown. Full
navigation paths are described in the Functional Definitions
in Section 4.

The diagrams are in Appendix A – Screen Navigation.

David Willcocks 13 May 2002


Xchanging Ins-sure Services Ltd
4. Functional Definitions

This section provides detailed functional definitions of all


screens involved in the new application. This includes ‘mock-
up’ screen layouts, field derivation and a description of the
actions to be taken for each Control on the screen.

Note 1:- if the current browser session (either the main session or any of the
sub-sessions – i.e. associated with Bulks, Grouping or History) are closed
down using the ‘X’ buton in the top right-hand corner, call CICS transaction
LY01 (see Appendix C.1) using COMMAREA C004 (see Appendix D) to log-off and
delete the Session Record.

Note 2:- The ‘Create New Claim’ button should be protected on all screens if
the user uses the ‘XCHE’ Account Code to log into the system – as this is an
enquiry-only account code.

David Willcocks 14 May 2002


Xchanging Ins-sure Services Ltd
4.1. Logon Screen

4.1.1. Screen Layout

Below is a copy of the logon screen of the new


application.

Fig 4.1.1.1. ‘Login Screen’ Layout

4.1.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY02 Validate Login Details

David Willcocks 15 May 2002


Xchanging Ins-sure Services Ltd
4.1.3. Process Description

This window will be displayed to the user on first entry


into the new application. They will need to enter their
user details in order to progress to the ‘home page’. A
drop down list of available Account Codes will be
provided for them, as they may have to work for
different departments.

Fig 4.1.3.1. Field/Command Processing for Login Screen

Field / Attributes Data Type


Description
Command
Account Network Account Code, indicating the Mandatory Alphanumeric
Code company/department the user is working in. Field (4 chars)

A drop down list of available account codes should


be provided. This will have to be a ‘hard-coded’ list,
as the full list available on the Security Table
includes external Account Codes.

The list should include the following Account


Codes: To Be Confirmed

User Id. This is the users personal user Id. Mandatory Alphanumeric
Field (8 Chars)
Password The password associated with the Account Mandatory Alphanumeric
Code/User Id. combination entered. Field (8 Chars)

Each letter typed must appear as asterisks for


security reasons.
Section The Section that the user is working in. A section Optional N/a
code will be associated with each user, and this will Field
be used if the user leaves this field set to ‘(default)’.
However, on a particular day, the user may be
required to do work for a different section. If this is
the case they will be able to select a section code
from a drop down list.

This drop down list should contain all codes (with


their associated names) held on the Section Code
table (TGLSCTA).

OK Ensure that all fields have been completed and call Command
CICS transaction LY01 (see Appendix C.1) – using
Commarea C002 (see Appendix D).

On return from CICS,

David Willcocks 16 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(i) check the C002-PROG-STATUS field – If this is
set to 9, display any errors returned in the
commarea in the Error Screen (see Appendix B)

(ii) check the ‘Login status code’:

1) If set to ‘N’, the details entered are invalid –


display the Error Screen (see Appendix B).
2) If set to ‘C’, display the ‘Change Password
Screen’ – see section 4.2.
3) If set to ‘Y’, the user has logged in successfully
and should be navigated to the ‘Home Page’ – see
section 4.3.

Note:- If ‘Login Status Code’ is ‘Y’ or ‘C’ – System


will return a Unique Session No. which should be
passed in the Commarea in all future calls to CICS.

Cancel Close Window – user is not logged in to converged Command


claims system.

David Willcocks 17 May 2002


Xchanging Ins-sure Services Ltd
4.2. Change Password Screen

4.2.1. Screen Layout

Below is a ‘mock-up’ of the logon screen required for


the new application.

Fig. 4.2.1.1. ‘Change Password’ screen layout

Change Password

Your password has expired - please enter/confirm your new password

New Password

Confirm Password

OK Cancel

4.2.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY03 Change Password
LY04 Log-off

4.2.3. Process Description

This window will be displayed to the user if their


password has expired. Passwords must be changed
every month. This screen allows them to enter their
new password and to confirm their entry to ensure
accuracy of typing.

Fig 4.2.3.1. Field/Command Processing for ‘Change Password’ screen

Field / Attributes Data Type


Description
Command
New New Password for Account Code/User Id. Mandatory Alphanumeric

David Willcocks 18 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Password combination entered on Login Screen. Field (8 chars)

New Password must be at least 5 characters long –


if not display Error ‘E009’ (see Appendix E).

New Password must not contain embedded spaces –


if this is the case, display Error ‘E010’ (see
Appendix E)

Confirm Confirmation of New Password. Mandatory Alphanumeric


Password Field (8 chars)
Must be identical to that entered in ‘New Password’
field.

OK Ensure that all fields have been completed and call Command
CICS transaction LY01 (see Appendix C.1) – using
COMMAREA C003 (see Appendix D).

On return from CICS,

(i) check the C003-PROG-STATUS field – If this is


set to 9, display any errors returned in the
commarea in the Error Screen (see Appendix B)

(ii) check the ‘Login status code’:

1) If set to ‘N’, the new password entered is invalid


– display the error screen (see Appendix B)
2) If set to ‘Y’, the user has logged in successfully
and should be navigated to the ‘Home Page’ – see
section 4.3.

Cancel Call CICS transaction LY01 (see Appendix C.1) – Command


using COMMAREA C004 (see Appendix D).

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, redisplay the ‘Login Screen’ with


details prefilled as previously entered.

David Willcocks 19 May 2002


Xchanging Ins-sure Services Ltd
4.3. Home Page

4.3.1. Screen Layout

Below is the ‘Home Page’.

Fig 4.3.1.1. ‘Home Page’ screen layout

4.3.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY10 Update Session Record
LY71 Set-up Group Session Record
LY87 Build Diary List

David Willcocks 20 May 2002


Xchanging Ins-sure Services Ltd
4.3.3. Field/Command Derivation

The fields on the screen will be derived as follows:-

Field Type Source


A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C087 (see
Appendix D) . This transaction will return the data that should appear on this screen.

On return, check the Program Status in the usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

Note:- the fields on the screen should be displayed in tabular format. All fields are
protected.

User Name Field C087-USER-NAME


UCR (n) Field C087-UCR (n)
Name 1 (n) Field C087-NAME-1 (n)
Name 2 (n) Field C087-NAME-2 (n)
Broker Field C087-BKR-REF-1 (n)
Reference 1 (n)
Date Of Loss Field C087-LOSS-DATE-FROM (n)
From (n)
Date of Loss To Field C087-LOSS-DATE-TO (n)
(n)
B. Commands

The following button should only be visable on this screen for certain users.
Scheme Comman If C087-SCHEME-CAN-ATTR = ‘P’
Canada Errors d (Protected), this button should be
protected or preferably not shown.

4.3.4. Process Description

This will be the first screen the user will see on entry to
the new application. Options available in the
‘Navigation Bar’ (left of screen) and Functions available
(top of screen) will be fixed for the ‘Home Page’.
Therefore, CICS transactions will not need to be called
in order to decide what should be available.

David Willcocks 21 May 2002


Xchanging Ins-sure Services Ltd
This screen will display a list of claims for which the
technician has set the diary date to the current date.
The technician has the ability, when enquiring on a
particular claim, to set a diary date. This is the date on
which the technician wishes to be reminded to review
the claim. They may set diary dates for as many claims
as they wish and these dates will apply only to their
user-id. On entry into the Home Page, they will be
shown all claims with todays diary date – or earlier
diary dates if this is the first time they have logged on
for a few days. These claims are displayed as a
reminder only and cannot be selected at this point.

Fig 4.3.4.1. Field/Command Processing for Home Page

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D).

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, close all windows.

Scheme This button will invoke the Scheme Canada Error Command
Canada Screen. This will only be available to certain users.
Errors For details see the Scheme Canada Functional
Specification.
Account Link to Account Enquiry (method needs to be Command
Enquiry identified)
Repository Link to Repository (method needs to be identified) Command
Data Link to Data Warehouse (method needs to be Command
Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry

User should select one of these options:-

Note:- ‘Clicking’ on one of the ‘Grouping’ options


should open up a new ‘window’ – associated with

David Willcocks 22 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
its own entry on the Session Table (i.e. a new
Session No.). Once the user has finished Group
processing, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
Grouping session - using Commarea C071
(see Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

Create New When user selects this option, the Session Record Command
Claim should be updated and they should be navigated to
‘Create Claim Screen’ (see Section 4.4)

(i) The Session Record should be updated by


calling CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C010 (see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

David Willcocks 23 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
On return, check the Program Status in the usual
way, reporting errors if they exist in the Error
Screen (see Appendix B)

(ii) Navigate the user to the ‘Create Claim Screen’


(see Section 4.4)

Find Claim When user selects this option, the Session Record Command
should be updated and they should be navigated to
‘Find Claim’ (see Section 4.5)

(i) The Session Record should be updated by


calling CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C010 (see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

(ii) Navigate the user to the ‘Find Claim Screen’


(see Section 4.5)

B. FIELDS
User Name The name of the current system user. Display Alphanumeric
Only Field (30 Chars)
UCR The Unique Claim Reference, if entered by the Display Alphanumeric
broker on the class for Lloyds system, or the Only Field (17 Chars)
Xchanging Claim Reference, if entered by internal
technicians.

Should be displayed in the following format:-

‘X / XXXX / XXXXXXXXXXXX’

Name 1 Name 1 and Name 2 will be Display Alphanumeric


populated with two of the following Only Field (50 Chars)

David Willcocks 24 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
fields (in the order quoted)
(i) Reinsured
(ii) Insured
(iii) Cover Holder
(iv) Original Insured
(v) Vessel

E.g. If Insured and Cover Holder are


spaces, but Reinsured and Origiginal
Insured are non-spaces: Name 1 will
be set to Reinsured and Name 2 will
be set to Original insured.

Name 2 See above Display Alphanumeric


Only Field (50 Chars)
Broker The Brokers own reference as entered on ‘CLASS Display Alphanumeric
Reference 1 for Lloyds’ or as supplied on the claim file. Only Field (12 Chars)

Loss Date The date of loss or the first date of a period of loss. Display Date
From Only Field (DD/MM/CCYY)
Loss Date The last date of a period of loss. Display Date
To Only Field (DD/MM/CCYY)

David Willcocks 25 May 2002


Xchanging Ins-sure Services Ltd
4.4. Create Claim Screen

4.4.1. Screen Layout

Below is a ‘mock-up’ of the ‘Create Claim’ screen.

Fig 4.4.1.1. ‘Create Claim’ screen layout

4.4.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY05 Policy Check
LY06 Claim Search (by OSND)
LY10 Update Session Record
LY71 Set up Group Session Record
LZ01 Create Skeleton Initial Claim
Transaction

4.4.3. Process Description

This screen allows the user to select either the OSND


(Original Signing Number and Date) against which they
wish to raise a claim or one of the associated AP SND’s
(Additional Premium Signing Numbers and Dates). The
purpose of this is twofold. Firstly it will initiate a search
of the Policy Database (LIDS), to identify whether the

David Willcocks 26 May 2002


Xchanging Ins-sure Services Ltd
policy is straight-forward or whether it involves a
number of combinations of key fields. Secondly, it will
enable a list of all claims that have been raised against
the policy to be presented to the user, allowing them to
check that the claim they are proposing to create has
not already been created by another user.

Fig 4.4.3.1. Field/Command Processing for ‘Create Claim Screen’

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D).

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, close all windows.

Account Link to Account Enquiry (method needs to be Command


Enquiry identified)
Repository Link to Repository (method needs to be identified) Command
Data Link to Data Warehouse (method needs to be Command
Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry

User should select one of these options:-

Note:- ‘Clicking’ on one of the ‘Grouping’ options


should open up a new ‘window’ – associated with
its own entry on the Session Table (i.e. a new
Session No.). Once the user has finished Group
processing, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
Grouping session - using Commarea C071
(see Appendix D).

David Willcocks 27 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

Find Claim When user selects this option from the Navigation Command
Bar, the Session Record should be updated and they
should be navigated to ‘Find Claim’ (see Section
4.5)

(i) The Session Record should be updated by


calling CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C010 (see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

(ii) Navigate the user to the ‘Find Claim Screen’


(see Section 4.5)

B. Fields (Main Screen)

David Willcocks 28 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
OSND Original Signing Number and Date. Optional Alphanumeric
Must comply with the following basic format:- Field (15 Chars)

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date


And SSSSS is numeric.

If the OSND does not conform to this format,


display the error E190 (see Appendix E) in the
error window (see Appendix B)

AP SND Additional Premium Signing Number and Date. Optional Alphanumeric


Field (15 Chars)
If APSND has been completed, the OSND must
also be completed. If not display error E059 (see
Appendix E) in the Error Screen (see Appendix
B).

Must comply with the following basic format:-

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date


And SSSSS is numeric.

If the APSND does not conform to this format,


display the error E191 (see Appendix E) in the
error window (see Appendix B)

C. Commands (Main Screen)


Create New If the OSND and APSND have been left blank:- Command
Advice
The user is going to create a claim against an
unsigned risk - display a warning window (see
Appendix I). The user will need to confirm that this
is the action they wish to take:-

If they click ‘OK’ in this warning window,


(i) Call CICS transaction LY01 (see
Appendix C.1) – using COMMAREA
C100 (see Appendix D) to set up a
skeleton ‘unclosed initial advice’
transaction on the system. (This
transaction will also update the Session
Record with the UCR-TR-SYS-REF
assigned to the transaction)

David Willcocks 29 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
On return, check the program status in
the usual way and report any
errors/warnings in the Error/Warning
window (see Appendix B).

(ii) Navigate the user to the ‘Claim


Creation’ screen (see Section 4.9).

If they click ‘CANCEL’ in the warning window, the


should remain in the current screen.

If OSND and/or APSND are completed:-

Call CICS transaction LY01 (see Appendix C.1) –


using COMMAREA C005 (see Appendix D) to
perform the Policy Check.

On return from CICS, check the C005-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) If set to zero, call CICS transaction LY01 (see


Appendix C.1) – using COMMAREA C006 (see
Appendix D) to perform the Claim Search (by
OSND). Ensure that C006-PREV-SCREEN-ID is
set to ‘SCR004’. On return from CICS, check the
C006-PROG-STATUS field:-
(a) If set to 9, display any errors returned in
the commarea in the Error Screen (see
Appendix B)
(b) If set to zero, the user should be
navigated to the ‘Search Results’ screen
(see section 4.6)

N.B. Ensure that the OSND and APSND entered on


this screen are stored, as they will need to be passed
in the C100 Commarea if the user elects to
‘Continue With New Advice’ in the ‘OSND Search
Results’ Screen (See Section 4.6.).
Cancel User should be navigated to the ‘Home Page’. Command

David Willcocks 30 May 2002


Xchanging Ins-sure Services Ltd
4.5. Find Claim Screen

4.5.1. Screen Layout

Below is a ‘mock-up’ of the ‘Find Claim’ screen.

Fig 4.5.1.1. ‘Find Claim’ screen layout

4.5.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY06 Claim Search (by OSND)
LY07 Find Specific Claim
LY08 Claim Search (by Group Ref.)
LY09 Check for Security Notes
LY10 Update Session Record
LY71 Set up Group Session Record

4.5.3. Process Description

David Willcocks 31 May 2002


Xchanging Ins-sure Services Ltd
This screen allows the user to enter selection criteria
by which to search for claims at either UCR or COR
level. One or more fields may be entered. This function
is used either for enquiry purposes only, to find a claim
on which the user wishes to add a subsequent
transaction or to find a specific claim transaction with a
view to either creating a Rate of Exchange Adjustment,
creating a Contra Correction or adding Taking Down
Numbers.

Fig 4.5.3.1. Field/Command Processing for ‘Find Claim Screen’

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D).

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, close all windows.

Account Link to Account Enquiry (method needs to be Command


Enquiry identified)
Repository Link to Repository (method needs to be identified) Command
Data Link to Data Warehouse (method needs to be Command
Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry

User should select one of these options:-

Note:- ‘Clicking’ on one of the ‘Grouping’ options


should open up a new ‘window’ – associated with
its own entry on the Session Table (i.e. a new
Session No.). Once the user has finished Group
processing, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the

David Willcocks 32 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Grouping session - using Commarea C071
(see Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

Create New When user selects this option from the Navigation Command
Claim Bar, the Session Record should be updated and they
should be navigated to ‘Create Claim Screen’ (see
Section 4.4)

(i) The Session Record should be updated by


calling CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C010 (see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

(ii) Navigate the user to the ‘Create Claim Screen’


(see Section 4.4)

David Willcocks 33 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

B. Fields (Main Screen)


UCR/XCR Unique Claim Reference, for claims entered by the Optional Alphanumeric
broker on the ‘CLASS for Lloyds’ system, or Field (17 Chars)
Xchanging Claim Reference, for claims entered by
internal technicians.

Must conform to the following general format:-


‘X9999XXXXXXXXXXXX’
(i.e. 1 Char – alphanumeric
4 Char – numeric
12 Char – aplhanumeric )

If UCR entered:-
Broker UCR, COR, OSND, TDN, Certificate of
Insurance No. and Group ref. Must be spaces
(see below for specific errors)

TR Transaction Reference. Optional Alphanumeric


Must conform to the following general format:- Field (17 Chars)
‘X9999XXXXXXXXXXXX’
(i.e. 1 Char – alphanumeric
4 Char – numeric
12 Char – aplhanumeric )

If TR entered:-
UCR must have been entered as well – If not,
display Error ‘E013’ (see Appendix E).

Broker UCR This field enables the user to search on the Brokers Alphanumeric
UCR, even on internally created claims. (17 Chars)

Must conform to the following general format:-


‘X9999XXXXXXXXXXXX’
(i.e. 1 Char – alphanumeric
4 Char – numeric
12 Char – aplhanumeric )

If entered, all other fields should be spaces. If not,


display error ‘E163’ (see Appendix E).

COR Claims Office Reference. Optional Alphanumeric


Field (15 Chars)
We cannot validate the basic format of the COR , as
the technicians use different formats for different
types of business and sometimes include slashes
and spaces and sometimes not.

David Willcocks 34 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
N.B. Slashes and spaces should be removed before
passing this field in the CICS Commarea.

COR can only be entered if UCR/TR are left blank


– if not display Error ‘E014’ (see Appendix E).

OSND Original Signing Number and Date. Optional Numeric?


Must comply with the following general format:- Field

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date


And SSSSS is numeric.

If the OSND does not conform to this format,


display the error E190 (see Appendix E) in the
error window (see Appendix B)

OSND can only be entered if UCR, TR, Certificate


of Insurance No. and COR are left blank – if not,
display Error ‘E015’ (see Appendix E).

TDN Taking Down Number and Date. Optional Numeric?


Must comply with the following general format:- Field

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date


And SSSSS is numeric.

If the TDN does not conform to this format, display


the error E192 (see Appendix E) in the error
window (see Appendix B)

TDN can only be entered if UCR, TR, Certificate


of Insurance No. and OSND are left blank – if not,
display Error ‘E016’ (see Appendix E).

Group Ref. Group Reference – Identifies either an Aggregate or Optional Alphanumeric


non-Aggregate group. Field (10 Chars)
Must comply with the following general format:-

‘LSSS/NNMMYY’

Where L = ‘L’

David Willcocks 35 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
SSS is numeric
NN is numeric
MMYY is a valid month and year

If the Group Reference entered does not conform to


this basic format, display the error E193 (see
Appendix E) in the error window (see Appendix
B).

Group Ref. Can only be entered if UCR, TR, COR,


OSND, Certificate of Insurance No. and TDN are
left blank – if not, display Error ‘E017’ (see
Appendix E).

Certificate Certificate of Insurance number. There may be Conditinoal Free Format


of multiple Certificate of Insurance numbers for a Field (20 Chars)
Insurance particular XCR/UCR. Note:- a particular Certificate
No. of Insurance Number cannot relate to more than one
open XCR/UCR.

Certificate of Insurance No. Can only be entered if


UCR, TR, COR, OSND, Group Ref. and TDN are
left blank – if not, display Error ‘ E700’ (see
Appendix E).
C. Commands (Main Screen)
Claim If UCR or UCR/TR or COR or TDN or Certificate Command
Search of Insurance No. entered:-

Call CICS transaction LY01 (see Appendix C.1) to


search for a specific claim – using COMMAREA
C007 (see Appendix D).

On return from CICS, check the C007-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) If set to zero, call CICS transaction LY01 (see


Appendix C.1) to check whether Security Notes
exist for the selected claim – using COMMAREA
C009 (see Appendix D).
On return from CICS, check the C009-
PROG-STATUS field:-
(a) If set to 9, display any errors returned in the
commarea in the Error Screen (see
Appendix B).
(b) If set to 2, display the ‘Security Notes’

David Willcocks 36 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Screen (see Section 4.8)
(c) If set to zero, navigate the user to the screen
indicated by C007-NEXT-PROG.

Note: LY07 (Specific Claim Search) will have


updated the Session Record with the necessary key
information

If OSND entered:-
Call CICS transaction LY01 (see Appendix C.1) –
using COMMAREA C006 (see Appendix D).

Ensure that C006-PREV-SCREEN-ID is set to


‘SCR005’. On return from CICS, check the C006-
PROG-STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) If set to zero, the user should be navigated to the


‘OSND Search Results’ screen (see section 4.6)

If Group Reference or Broker UCR entered:-


Call CICS transaction LY01 (see Appendix C.1) –
using COMMAREA C008 (see Appendix D).

On return from CICS, check the C008-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) If set to zero, the user should be navigated to the


‘Group/Broker UCR Search Results’ screen (see
section 4.7)

Cancel User should be navigated to the ‘Home Page’. Command

David Willcocks 37 May 2002


Xchanging Ins-sure Services Ltd
4.6. OSND Search Results Screen

Change Control Log

Release Date Changed TP No. Description of Changes Made


By
XCS 26/08/2008 DBP TP631646 CR6-FS2:- Screen will need to be amended to
CLASS display Outstanding Qualifier for each COR.
Phase 4

4.6.1. Screen Layout

Below is a ‘mock-up’ of the ‘OSND Search Results’


screen.

The new version of the screen including the changes for XCS Class Phase 4 is
shown below:

David Willcocks 38 May 2002


Xchanging Ins-sure Services Ltd
New version of screen including O/S Qualifier

David Willcocks 39 May 2002


Xchanging Ins-sure Services Ltd
4.6.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY06 Claim Search (by OSND)
LY09 Check for Security Notes
LY10 Update Session Record
LY11 Navigation Program
LZ01 Create Skeleton Initial Claim
Transaction

4.6.3. Field Derivation

Each of the fields on this tabular screen will be derived


as follows:-

Field Type Source


OSND Field C006-SEARCH-OSND
COR (n) Field C006-COR (n)
UCR (n) Field C006-UCR (n)
Name 1 (n) Field C006-NAME-1 (n)
Name 2 (n) Field C006-NAME-2 (n)
DOL From (n) Field C006-LOSS-DATE-FROM (n)
DOL To (n) Field C006-LOSS-DATE-TO (n)
State Code (n) Field C006-STATE-CODE (n)
Broker Ref 1 Field C006-BKR-REF-1 (n)
(n)
O/S Qualifier Field C006-OUTST-TOT-QL (n)
‘CONTINUE Comman This command should only be
WITH NEW d displayed if the user was navigated
ADVICE’ to this screen from the ‘Create New
Claim’ screen. i.e. If C006-CONT-
ATTR = ‘P’, this command should be
protected or preferable not shown.

David Willcocks 40 May 2002


Xchanging Ins-sure Services Ltd
4.6.4. Process Description

This screen is displayed to the user on selection of an


OSND/AP SND from the ‘Create New Claim’ screen or
selection of an OSND from the ‘Find Claim’ screen.

If the user has been navigated here from the ‘Create


New Claim’ screen, this screen allows the user to check
that the claim they are planning to create has not
already been created by another user – they may select
claims for enquiry to assist them in their check. Once
the user is confident that the claim does not already
exist, they are able to continue creating the claim by
clicking on the ‘CONTINUE WITH NEW ADVICE’
button.

If the user has been navigated here from the ‘Find


Claim’ screen, this screen allows the user to select a
claim for enquiry – possibly with a view to creating a
subsequent advice on the claim in question. The
‘CONTINUE WITH NEW ADVICE’ button will not
appear if the user has come from the ‘Find Claim’
screen.

David Willcocks 41 May 2002


Xchanging Ins-sure Services Ltd
Fig 4.6.4.1. Field/Command Processing for ‘OSND Search Results’
Screen

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D) to log-
off the system and delete the Session Record.

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, close all windows.

Account Link to Account Enquiry (method needs to be Command


Enquiry identified)
Repository Link to Repository (method needs to be identified) Command
Data Link to Data Warehouse (method needs to be Command
Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry

User should select one of these options:-

Note:- ‘Clicking’ on one of the ‘Grouping’ options


should open up a new ‘window’ – associated with
its own entry on the Session Table (i.e. a new
Session No.). Once the user has finished Group
processing, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
Grouping session - using Commarea C071
(see Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user

David Willcocks 42 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

Find Claim When user selects this option, the Session Record Command
should be updated and they should be navigated to
‘Find Claim’ (see Section 4.5)

(i) The Session Record should be updated by


calling CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C010 (see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

(ii) Navigate the user to the ‘Find Claim Screen’


(see Section 4.5)
Create New When user selects this option, the Session Record Command
Claim should be updated and they should be navigated to
‘Create Claim Screen’ (see Section 4.4)

(i) The Session Record should be updated by


calling CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C010 (see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session

David Willcocks 43 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

(ii) Navigate the user to the ‘Create Claim Screen’


(see Section 4.4)

B. Fields (Main Screen)


OSND Original Signing Number and Date Display Alphanumeric
only Field (15 Chars)
COR Claims Office Reference. This field is display only. Display Alphanumeric
However the user should be able to click on it in Only Field (15 Chars)
order to display details of the associated claim.
Therefore, this field is also listed as a Command
(see below).
UCR Unique Claim Reference, for claims entered by the Display Alphanumeric
broker on the ‘CLASS for Lloyds’ system, or Only Field (17 Chars)
Xchanging Claim Reference for internally created
claims.

Name 1 Name 1 will be set to the first non-space field in the Display Alphanumeric
following list:- Only Field (50 Chars)

(i) Reinsured
(ii) Insured
(iii) Cover Holder
(iv) Original Insured
(v) Vessel

Name 2 Name 2 will be set to the second non-space field in Display Alphanumeric
the following list:- Only Field (50 Chars)

(i) Reinsured
(ii) Insured
(iii) Cover Holder
(iv) Original Insured
(v) Vessel

David Willcocks 44 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
DOL From Date of Loss From Display Date
Only Field (DD/MM/CCYY)
DOL To Date of Loss To Display Date
Only Field (DD/MM/CCYY)
State Code State Code Display Alphanumeric
Only Field (2 Chars)
Broker Ref 1 First Broker Reference Display Alphanumeric
Only Field (16 Chars)
O/S Qualifier associated with the Total Outstanding Display Alphanumeric
Qualiifier Amount for the Claim Only field (1 Char)
C. Commands (Main Screen)
< PREV This button should be shown, but protected, if Command
C006-MORE-PREV not = ‘Y’.

If pressed:-

Call CICS transaction LY01 (see Appendix C.1) –


using COMMAREA C006 (see Appendix D) to
show the previous 20 claims. Ensure that C006-
PREV-SCREEN-ID is set to ‘SCR006’.

On return from CICS, check the C006-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) If set to zero, rebuild the ‘OSND Search


Results’ screen using the data contained in the
Commarea.

NEXT > This button should be shown, but protected, if Command


C006-MORE-NEXT not = ‘Y’

If pressed:-

Call CICS transaction LY01 (see Appendix C.1) –


using COMMAREA C006 (see Appendix D) to
show the next 20 claims. Ensure that C006-PREV-
SCREEN-ID is set to ‘SCR006’.

On return from CICS, check the C006-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

David Willcocks 45 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(ii) If set to zero, rebuild the ‘OSND Search
Results’ screen using the data contained in the
Commarea.

CONTINUE (i) Call CICS transaction LY01 (see Command


WITH NEW Appendix C.1) – using COMMAREA
ADVICE C100 (see Appendix D) to set up a
skeleton ‘unclosed initial advice’
transaction on the system. (This
transaction will also update the Session
Record with the UCR-TR-SYS-REF
assigned to the transaction). Note:- The
OSND and APSND entered in the
‘Create New Claim’ screen (See
Section 4.4.)should be passed in the
C100 Commarea.

On return, check the program status in


the usual way and report any errors/
warnings in the Error/Warning window
(see Appendix B).

(ii) The user should be navigated to the


‘Claim Creation’ screen (see
Section 4.9)

COR (i) The Session Record should be updated Command


(select) by calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C008-UCR-TR-SYS-REF
C008-CURR-NO
C008-SDN-NO
C008-STAT-SPLIT-NO
C008-BREAKDOWN-NO

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(ii) If no errors have been found while updating


the session record, call CICS transaction
LY01 (see Appendix C.1) to determine

David Willcocks 46 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
whether Security Notes are present for the
selected claim – using COMMAREA C009
(see Appendix D).

On return from CICS, check the C009-


PROG-STATUS field:-

(a) if set to 9, display any errors returned in


the commarea in the Error Screen (see
Appendix B)

(b) If set to 2, display the ‘Security Notes’


Screen (see Section 4.8).

(iii) If no erros returned from LY09, Call the


CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.
(Ensure that C011-EXIT-IND is set to ‘N’)

On return, check the Program Status in the


Usual way, reporting errors if they exist in
The Error Screen (see Appendix B)

(iv) If no errors returned from LY11, navigate


the user to the program indicated by C011-
NEXT-PROGRAM (see Appendix N).

Cancel (i) Call the CICS transaction LY01 (see Command


Appendix C.1) – using COMMAREA C011
(see Appendix D). This will invoke the
‘Navigation’ program, which decides on the
next program the user should be navigated
to. (Ensure that C011-EXIT-IND is set to
‘Y’)

On return, check the Program Status in the


Usual way, reporting errors if they exist in
The Error Screen (see Appendix B)

(ii) If no errors returned from LY11, navigate


the user to the program indicated by C011-
NEXT-PROGRAM (see Appendix N).

David Willcocks 47 May 2002


Xchanging Ins-sure Services Ltd
David Willcocks 48 May 2002
Xchanging Ins-sure Services Ltd
4.7. Group/Broker UCR Search Results Screen

Change Control Log

Release Date Changed TP No. Description of Changes Made


By
XCS 26/08/2008 DBP TP631646 1) CR6-FS1:- Screen will be amended to display
CLASS Outstanding Qualifier for each COR.
Phase 4

4.7.1. Screen Layout

Below is a ‘mock-up’ of the ‘Group/Broker UCR Search


Results’ screen. (Note:- there are two images of this
screen, as the technician may need to scroll right to

view some of the details on the screen).

David Willcocks 49 May 2002


Xchanging Ins-sure Services Ltd
David Willcocks 50 May 2002
Xchanging Ins-sure Services Ltd
For XCS CLASS Phase 4 The new screen layout will be

David Willcocks 51 May 2002


Xchanging Ins-sure Services Ltd
CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY08 Claim Search (by Group Ref.)
LY09 Check for Security Notes
LY10 Update Session Record
LY11 Navigation Program
LY71 Set up Group Session Record

4.7.2. Field Derivation

Each of the fields on this tabular screen will be derived


as follows:-

Field Type Source


Group Ref. Field C008-SEARCH-GRP-REF
Broker UCR Field C008-SEARCH-BKR-UCR
COR (n) Field C008-COR (n)
Reinsured/Loss Field C008-REINS-LOSS (n)
Name (n)
Broker Ref 1 Field C008-BKR-REF-1 (n)
(n)
TF Code (n) Field C008-TF-CODE (n)
State Code (n) Field C008-STATE-CODE (n)
DOL From (n) Field C008-LOSS-DATE-FROM (n)
DOL To(n) Field C008-LOSS-DATE-TO (n)
Cat Code (n) Field C008-CAT-CODE (n)
PCS Cat (n) Field C008-PCS-CAT-CODE (n)
NAIC Code (n) Field C008-NAIC-CODE (n)
NAIC Qual (n) Field C008-NAIC-QUAL (n)
Orig Curr Field C008-ORIG-CURR (n)
Paid To Date Field C008-PTD-AMT (n)
(n)
Outstanding (n) Field C008-OUTST-AMT (n)
O/S Qualifier Field C008-OUTST-TOT-QL(n)

David Willcocks 52 May 2002


Xchanging Ins-sure Services Ltd
4.7.3. Process Description

This screen is displayed to the user on selection of


either a Group Reference or Broker UCR from the ‘Find
Claim’ screen. It allows the user to enquire on all
claims that either belong to a particular Group or have
the same Broker UCR. The user is able to select Claims
Office References from the list to enquire upon,
possibly with a view to creating a subsequent advice on
the claim in question.

Fig 4.7.4.1. Field/Command Processing for ‘Group/Broker UCR


Search Results’
Screen

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D) to log-
off the system and delete the Session Record.

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, close all windows.


Account Link to Account Enquiry (method needs to be Command
Enquiry identified)
Repository Link to Repository (method needs to be identified) Command
Data Link to Data Warehouse (method needs to be Command
Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry

User should select one of these options:-

Note:- ‘Clicking’ on one of the ‘Grouping’ options


should open up a new ‘window’ – associated with
its own entry on the Session Table (i.e. a new
Session No.). Once the user has finished Group
processing, the window should be closed and the
Session Record deleted.

David Willcocks 53 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
Grouping session - using Commarea C071
(see Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

Find Claim When user selects this option from the Navigation Command
Bar, the Session Record should be updated and they
should be navigated to ‘Find Claim’ (see Section
4.5)

(i) The Session Record should be updated by


calling CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C010 (see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

David Willcocks 54 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(ii) Navigate the user to the ‘Find Claim Screen’


(see Section 4.5)

Create New When user selects this option from the Navigation Command
Claim Bar, the Session Record should be updated and they
should be navigated to ‘Create Claim Screen’ (see
Section 4.4)

(i) The Session Record should be updated by


calling CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C010 (see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

(ii) Navigate the user to the ‘Create Claim Screen’


(see Section 4.4)

B. Fields (Main Screen)


Group Ref. The Group Reference that identifies the group that Display Alphanumeric
the claims listed belong to (if Group reference was only Field (10 Chars)
the criteria used for the search).
Broker UCR The Broker UCR that applies to the claim listed (if Display Alphanumeric
Broker UCR was the criteria used for the search). Only Field (17 Chars)

Should be displayed in the following format:-


‘X/ XXXX / XXXXXXXXXXXX’

COR Claims Office Reference. This field is display only. Display Alphanumeric
However the user should be able to click on it in Only Field (15 Chars)
order to display details of the associated claim.
Therefore, this field is also listed as a Command
(see below).
Reinsured/ Either Reinsured Name or Loss Name Display Alphanumeric

David Willcocks 55 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Loss Name Only Field (50 Chars)

Bkr Ref. 1 Broker Reference 1 Display Alphanumeric


Only Field (16 Chars)
TF Code Trust Fund Code Display Alphanumeric
Only Field (2 Chars)
State Code State Code Display Alphanumeric
Only Field (2 Chars)
Date of Loss The Date of Loss or the first date of a period of loss. Display Date
From Only Field (DD/MM/CCYY)
Date of Loss The last date of a period of loss Display Date
To Only Field (DD/MM/CCYY)
Cat Code Lloyds Claims Office Catastrophe Code Display Alphanumeric
Only Field (4 Chars)
PCS Cat Property Claims Services Catastrophe Code Display Alphanumeric
Only Field (4 Chars)
NAIC Code National Association of Insurance Commissioners Display Alphanumeric
(NAIC) Code. Only Field (11 Chars)
NAIC Qual Qualifier associated with the National Association Display Alphanumeric
of Insurance Commissioners (NAIC) Code. Only Field (1 Char)
Original The Original (or Estimate Currency) Display Alphanumeric
Currency Only Field (3 Chars)
Paid To Date Amount Paid To Date on claim Display Numeric
Amt. only Field -(13)9.99
Outstanding Outstanding Amount for Claim Display Numeric
Amt. Only Field -(13)9.99
O/S Qualifier associated with the Total Outstanding Display Alphanumeric
Qualifier Amount for the Claim Only field (1 Char)
C. Commands (Main Screen)
< PREV This button should be shown, but protected, if Command
C008-MORE-PREV not = ‘Y’.

If pressed:-

Call CICS transaction LY01 (see Appendix C.1) –


using COMMAREA C008 (see Appendix D) to
obtain the previous 20 claims.

On return from CICS, check the C008-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) If set to zero, rebuild the ‘Group/Broker UCR


Search Results’ screen using the data contained in
the Commarea.

David Willcocks 56 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

NEXT > This button should be shown, but protected, if Command


C008-MORE-NEXT not = ‘Y’

If pressed:-

Call CICS transaction LY01 (see Appendix C.1) –


using COMMAREA C008 (see Appendix D) to
obtain the next 20 claims.

On return from CICS, check the C008-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) If set to zero, rebuild the ‘Group/Broker UCR


Search Results’ screen using the data contained in
the Commarea.
COR (i) The Session Record should be updated Command
(select) by calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C008-UCR-TR-SYS-REF
C008-CURR-NO
C008-SDN-NO
C008-STAT-SPLIT-NO
C008-BREAKDOWN-NO

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(ii) If no errors have been found while updating


the session record, call CICS transaction
LY01 (see Appendix C.1) to determine
whether Security Notes are present for the
selected claim – using COMMAREA C009
(see Appendix D).

On return from CICS, check the C009-


PROG-STATUS field:-

David Willcocks 57 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(a) if set to 9, display any errors returned in
the commarea in the Error Screen (see
Appendix B)

(b) If set to 2, display the ‘Security Notes’


Screen (see Section 4.8).

(iii) If no erros returned from LY09, Call the


CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.
(Ensure that C011-EXIT-IND is set to ‘N’)

On return, check the Program Status in the


Usual way, reporting errors if they exist in
The Error Screen (see Appendix B)

(iii) If no errors returned from LY11, navigate


the user to the program indicated by C011-
NEXT-PROGRAM (see Appendix N).

Cancel (i) Call the CICS transaction LY01 (see Command


Appendix C.1) – using COMMAREA C011
(see Appendix D). This will invoke the
‘Navigation’ program, which decides on the
next program the user should be navigated
to.

On return, check the Program Status in the


Usual way, reporting errors if they exist in
The Error Screen (see Appendix B)

(ii) If no errors returned from LY11, navigate


the user to the program indicated by C011-
NEXT-PROGRAM (see Appendix N).

David Willcocks 58 May 2002


Xchanging Ins-sure Services Ltd
4.8. Security Notes Screen

4.8.1. Screen Layout

Below is the ‘Security Notes’ screen.

4.8.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY10 Update Session Record
LY11 Navigation Program

4.8.3. Field Derivation

Each of the fields on this screen will be derived as


follows:-

Field Type Source


UCR/XCR Field C009-UCR

David Willcocks 59 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
OSND1 Field C009-ORIG-REF-1
OSND2 Field C009-ORIG-REF-2
OSND3 Field C009-ORIG-REF-3
Orig. Broker Field C009-ORIG-BKR-CODE
Security Notes Field C009-NOTES-LINE (1 - n)

(i.e. all occurences of C009-NOTES-


LINE, one line per line in the
‘Security Notes’ window)

4.8.4. Process Description

This screen is displayed to the user on selection of a


specific claim for enquiry or update. This screen should
be shown in a separate (smaller) window over the top of
the screen the user was in prior to this one. This will
enable the user to minimise this window and keep it
available to view whilst processing the claim.
Alternatively, they may wish to exit the claim, in which
case the window can simply be closed, leaving them
where they were before.

Fig 4.8.4.1. Command Processing for ‘Security Notes’


Screen

Field / Attributes Data Type


Description
Command
UCR/XCR This is the Unique Claim Reference (if assigned by Protected Alphanumeric
the broker) or the Xchanging Claim Reference (if Field (19 chars)
system generated for an internally created claim).

This is passed from the mainframe as a 17 character


field and should be displayed with embedded
slashes as shown below:-
‘X/XXXX/XXXXXXXXXXXX’
TR The Transaction Reference that identifies the claim Protected Aplhanumeric
transaction Field (19 chars)

This is passed from the mainframe as a 17 character


field and should be displayed with embedded
slashes as shown below:-
‘X/XXXX/XXXXXXXXXXXX’

A. FIELDS

David Willcocks 60 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
OSDN1 The Original Signing Number and Date that applies Protected Aplhanumeric
to the first currency on the claim. Field (15 chars)

This may or may not be present.


OSDN2 The Original Signing Number and Date that applies Protected Alphanumeric
to the second currency on the claim (if present). Field (15 chars)

This may or may not be present.


OSDN3 The Original Signing Number and Date that applies Protected Alphanumeric
to the first currency on the claim (if present). Field (15 chars)

This may or may not be present.


Orig. Broker This is the broker from whom the claim transaction Protected Aplhanumeric
originated. Field (4 chars)
Security These notes provide the user with essential Protected Alphanumeric
Notes information relating to the claim in question. Field (n Lines x 70
Chars)
These notes should be displayed in a box, with the
ability to scroll up and down.
B. COMMANDS
EXIT This means that whatever was displayed in the Command
CLAIM security notes window was sufficiently important
for the user to decide NOT to proceed with their
claim enquiry.

If this button is pressed, the Session Record


should be updated by calling CICS transaction
LY01 (see Appendix C.1) – using COMMAREA
C010 (see Appendix D).

Note: The following key fields in the C010


Commarea should be set to ZEROES:-
C010-UCR-TR-SYS-REF
C010-CURR-NO
C010-SDN-NO
C010-STAT-SPLIT-NO
C010-BREAKDOWN-NO

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

If no errors have been found while updating the


session record:-

Close the Security Notes window.

David Willcocks 61 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

PROCEED This means that the user has read the Security Notes Command
associated with the claim they have selected and has
decided to proceed.
If this option is selected:-

1) minimise the ‘Security Notes’ screen (so that it


can be consulted whilst the user is processing
the claim).

2) call the CICS transaction LY01 (see Appendix


C.1) – using COMMAREA C011 (see
Appendix D). This will invoke the ‘Navigation’
program, which decides on the next program
the user should be navigated to.

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

3) Navigate the user to whichever program is


identified in C011-NEXT-PROGRAM (see
Appendix N) (could be either ‘Claim Creation’,
‘Loss Reserves’, ‘SCM Advice’, ‘Financial
Details’ or one of the three schedule screens –
depending on the type of claim and the method
of access)

David Willcocks 62 May 2002


Xchanging Ins-sure Services Ltd
4.9. Claim Creation Screen

4.9.1. Screen Layout

Below is the ‘Claim Creation’ screen.

David Willcocks 63 May 2002


Xchanging Ins-sure Services Ltd
4.9.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY10 Update Session Record
LY11 Navigation Program
LY12 Build Screen Navigation Bar
LY13 Build Claim Creation Screen
LY14 Add OSND(s) to Aggregate Group
LY15 Create Non-Aggregate Group
LY16 Check Transaction Status
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY24 Copy Facility Initial Validation

David Willcocks 64 May 2002


Xchanging Ins-sure Services Ltd
Tran Program Description
s. Name
Id.
LY25 Claim Creation Screen Validation
LY27 Claim Creation Screen D/B Update
LY46 Check whether Currency/Transaction
Validn. reqd.
LY68 Set up History Session Record
LY71 Set up Group Session Record
LY88 Build Narrative Details Screen
LY90 Bulk/CCS Correction Initial Validation
LY93 Bring Forward Breakdown from
previous transaction
LY94 Build Commarea for LIDS Interface
LY96 Set File Last Seen Date
LY97 Delete All Breakdowns
LZ02 Create Skeleton Breakdown for
‘CLASS for Lloyds’ initial Claim
Transaction
LZ06 Reset Claim Transaction
LZ11 Create Re-Advice – Initial Validation
4.9.3. Field/Command Derivation

The fields and the navigation bar on this screen will be


derived as follows:-

Field Type Source


A. Navigation Bar
Navigation Bar Comman call the CICS transaction LY01 (see Appendix
d(s) C.1) – using COMMAREA C012 (see Appendix
D) . This will determine what should appear on
the ‘Screen Navigation Bar’ at the left hand side
of the screen.

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

See Appendix F for details of how to process the


information returned from this CICS transaction.

David Willcocks 65 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
B. Fields:-

(i) Call the CICS transaction LY01 (see Appendix C.1) – using
COMMAREA C101 (see Appendix D). This transaction will check to
see whether the current transaction is an initial advice, loaded on the
‘CLASS for Lloyds’ system with a transaction status that indicates that
this is the first time the transaction has been selected by an internal
user since it became fully authorised. If this is the case it will add a
skeleton breakdown to the transaction (one for each currency).

On return, check the Program Status in the usual way, reporting errors
if they exist in the Error Screen (see Appendix B)

(ii) Call the CICS transaction LY01 (see Appendix C.1) – using
COMMAREA C013 (see Appendix D) . This transaction will return
the data that should appear on this screen.

On return, check the Program Status in the usual way, reporting errors
if they exist in the Error Screen (see Appendix B)

XCR Field C013-XCR


(This field should be protected)
UCR Field C013-UCR
(This field should be protected)
TR Field C013-TR
(This field should be protected)
Orig. Broker Field C013-ORIG-BKR
(This field should be protected)
Peer Review Field C013-PEER-REV-IND
(This field should be protected)
Transaction Field C013-TRANS-SYNOPSIS
Synopsis (This field should be protected)
OSND1 Field C013-ORIG-REF (1)

If C013-ORIG-REF-ATTR (1) = ‘P’, then


this field should be protected.
APSND1 Field C013-AP-REF (1)

If C013-AP-REF-ATTR (1) = ‘P’, then


this field should be protected.
Original Field C013-ORIG-CURR (1)
Currency 1
If C013-ORIG-CURR-ATTR (1) = ‘P’,
then this field should be protected.

OSND2 Field C013-ORIG-REF (2)

David Willcocks 66 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source

If C013-ORIG-REF-ATTR (2) = ‘P’, then


this field should be protected.
APSND2 C013-AP-REF (2)

If C013-AP-REF-ATTR (2) = ‘P’, then


this field should be protected.
Original Field C013-ORIG-CURR (2)
Currency 2
If C013-ORIG-CURR-ATTR (2) = ‘P’,
then this field should be protected.
OSND3 Field C013-ORIG-REF (3)

If C013-ORIG-REF-ATTR (3) = ‘P’, then


this field should be protected.
APSND3 C013-AP-REF (3)

If C013-AP-REF-ATTR (3) = ‘P’, then


this field should be protected.
Original Field C013-ORIG-CURR (3)
Currency 3
If C013-ORIG-CURR-ATTR (3) = ‘P’,
then this field should be protected.
Sett/Adv Field Set to ‘Sett’ if C013-SETT-ADV-IND
= ‘S’
Set to ‘Adv’ if C013-SETT-ADV-IND
= ‘A’

If C013-SETT-ADV-ATTR = ‘P’, then this


field should be protected.

Non-SCM Tick-Box Set to ‘TRUE’ (tick-box) if C013-


Advised NON-SCM-ADV = ‘Y’

If C013-NON-SCM-ADV-ATTR = ‘P’,
then this field should be protected.

Bulk Indicator Tick-Box Set to ‘TRUE’ (Tick-Box) if C013-


BULK-IND = ‘Y’.

If C013-BULK-IND-ATTR = ‘P’, then


this field should be protected.
Risk Unsigned Tick-Box Set to ‘TRUE’ (tick-box), if
C013-UNSIGNED-RISK = ‘Y’
David Willcocks 67 May 2002
Xchanging Ins-sure Services Ltd
Field Type Source

If C013-UNSGN-RISK-ATTR = ‘P’, then


this field should be protected.
Treaty Tick-Box Set to ‘TRUE’ (tick-box)
if C013-TREATY-IND = ‘Y’

If C013-TREATY-IND-ATTR = ‘P’, then


this field should be protected.
ECF Claim Tick-Box Set to ‘TRUE’ (tick box)
If C013-ECF-XCR-IND = ‘Y’
Loss Reserve Tick-Box Set to ‘TRUE’ (tick-box)
if C013-LOSS-RESERVE-IND = ‘Y’

If C013-LOSS-RES-ATTR = ‘P’, then


this field should be protected.
L.O.C. Tick-Box Set to ‘TRUE’ (tick-box)
if C013-LOC-IND = ‘Y’

If C013-LOC-IND-ATTR = ‘P’, then this


field should be protected.
Loss Fund Tick-Box Set to ‘TRUE’ (tick-box)
if C013-LOSS-FUND-IND = ‘Y’

If C013-LOSS-FUND-ATTR = ‘P’, then


this field should be protected.
Pay By Cheque Field Set to C013-CHEQUE-PYMT

If C013-CHEQUE-PYMT-ATTR = ‘P’,
then this field should be protected
Charge Type Field Set to C013-CHARGE-TYPE

If C013-CHARGE-TYPE-ATTR = ‘P’,
this field should be protected
Non- Tick-Box C013-NON-CHARGE-IND
Chargeable (If C013-NON-CHG-ATTR = ‘P’, this
Indicator field should be protected)
Previously Tick-Box Set to ‘TRUE’ (Tick-Box) if C013-PREV-
Advised Non- ADV-NON-NET = ‘Y’.
Network
indicator If C013-PREV-ADV-ATTR = ‘P’, this field
should be protected.
Previously Paid Tick-Box Set to ‘TRUE’ (Tick-Box) if C013-PREV-
Indicator PAID-IND = ‘Y’.

If C013-PREV-PAID-IND = ‘P’, this field

David Willcocks 68 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
should be protected.
LOC Drawing Tick-Box Set to ‘TRUE’ (Tick Box) if C013-LOC-
Indicator DRAWING-IND = ‘Y’.

If C013-LOC-DRAWING-ATTR = ‘P’,
this field shouldbe protected.

Scheme Tick-Box Set to ‘TRUE’ (Tick-Box) if C013-


Canada SCHEME-CAN-IND = ‘Y’
Indicator
If C013-SCHEME-CAN-ATTR = ‘P’, this
field should be protected.
Simultaneous Tick-Box Set to ‘TRUE’ (Tick-Box) if C013-SIM-
Reinstatement RI-IND = ‘Y’
Indicator
If C013-SIM-RI-IND-ATTR = ‘P’, this
field should be protected.
CPA Indicator Tick-Box Set to ‘TRUE’ (Tick-Box) if C013-CPA-
IND = ‘Y’

If C013-CPA-IND-ATTR = ‘P’, this field


should be protected.
Direct Tick-Box Set to ‘TRUE’ (Tick-Box) if C013-DIR-
Livestock LSTOCK-IND = ‘Y’
Indicator
If C013-DIR-LSTOCK-ATTR = ‘P’, this
field should be protected.
Presentation Field C013-PRES-DATE
Date (If C013-PRES-DATE-ATTR = ‘P’, this
field should be protected)
Special Tick-Box Set to ‘TRUE’ (Tick-Box) if C013-
Payment SPECIAL-PYMT-IND = ‘Y’
Indicator
If C013-SPECIAL-PYMT-ATTR = ‘P’,
this field should be protected.
ECF Class Field C013-ECF-CLASSIFICATION
(If C013-ECF-CLASSIFICATION-ATTR
= ‘P’, this field should be protected)
C. Commands
Bring Forward Comman If C013-BRING-FWD-ATTR = ‘P’
Breakdown d (Protected), this button should be
protected – or preferably not shown at
all.
Delete Comman If C013-DEL-BDOWN-ATTR = ‘P’
Breakdown d (Protected), this button should be
protected – or preferably not shown at
all.

David Willcocks 69 May 2002


Xchanging Ins-sure Services Ltd
4.9.4. Process Description

This screen is the first ‘Data Entry’ screen displayed to


the user when they create a new claim or when they
create a subsequent advice on an existing claim. In
these situations it is displayed in ‘Update’ mode.
When the user selects a claim from the ‘Find Claim’
selection screen (or associated search results screens)
or they are updating a broker-entered claim, they will
be shown this screen in ‘Enquiry’ mode.
In ‘Update’ mode, this screen allows the user to
enter/add Original Signing Numbers and Dates (and
their asociated Original Currencies) together with the
characteristics of the claim transaction that they are
creating.
In ‘Enquiry’ mode, the OSDN’s and claim transaction
characteristics are displayed to the user for information
purposes.

Fig 4.9.4.1. Field/Command Processing for ‘Claim Creation’


Screen

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D) to log-
off the system and delete the Session Record.

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, close all windows.

Create New (i) Call CICS transaction LY01 (see Appendix Command
Claim C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the

David Willcocks 70 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Create Claim
Screen’ (see Section 4.4)

Find Claim (i) Call CICS transaction LY01 (see Appendix Command
C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

David Willcocks 71 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(ii) If C016-PROG-STATUS set to 5, the
technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Find Claim’ Screen
(see Section 4.5)

Account Link to Account Enquiry (method needs to be Command


Enquiry identified)

Repository Link to Repository (method needs to be identified) Command

Data Link to Data Warehouse (method needs to be Command


Warehouse identified)

David Willcocks 72 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry
Add to Aggregate Group
Create Non-Aggregate Group
Add to Non-Aggregate Group

User should select one of these options.

Note:- ‘Clicking’ on the ‘Maintain Group’,


‘Group Enquiry’ or ‘Add to Non-Aggregate
Group’ options should open up a new ‘window’ –
associated with its own entry on the Session Table
(i.e. a new Session No.). Once the user has finished
Group processing, the window should be closed and
the Session Record deleted.

(i) If either the ‘Maintain Group’, ‘Group


Enquiry’ or ‘Add to Non-Aggregate
Group’ options were selected, call CICS
transaction LY01 (see Appendix C.1) to set
up a new Session Record for the Grouping
session - using Commarea C071 (see
Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iv) On selection of ‘Add to Aggregate


Group’, call CICS transaction LY01

David Willcocks 73 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(see Appendix C.1) to add the OSND’s
associated with this claim to an Aggregate
group – using COMMAREA C014 (see
Appendix D).

On return, check the C014-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the OSND’s
have been added to. (see Appendix G)

(v) On selection of ‘Create Non-Aggregate


Group’, call CICS transaction LY01 (see
Appendix C.1) to add the current claim
to a Non-Aggregate group – using
COMMAREA C015 (see Appendix D).

On return, check the C015-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the claim has
been added to. (see Appendix G)

(vi) On selection of the ‘Add to Non-


Aggregate Group’ option, open new
window, navigating user to ‘Group Enquiry’
screen (see Section 4.28) (a new SESSION-
NO is associated with this window – this
will have been returned by previous
transaction, LY71)

Notes When user clicks on the ‘NOTES’ option at the top Command
of the screen, the following options should be
available on a sub-menu:-
Security Notes
Claim Notes
Loss Details
Policy Details
EURO Conversion Narrative (FME)
Broker Additional Details
Broker Aggregate Details
Slip Lead Comments

David Willcocks 74 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Lead Comments
Lead Additional Details

User should select one of these options.

(i) Whichever option is selected, call CICS


transaction LY01 (see Appendix C.1) to
check whether the selected narrative is
present or not, and return any narrative
present, using COMMAREA C088 (see
Appendix D). N.B. Set C088-FIRST-CALL
to ‘Y’. This call will return lines 1 to 300.

On return, check the C088-PROG-STATUS


and report any errors in the usual way.

(ii) If no errors returned from the first LY88


call and C088-MORE-LINES is set to ‘Y’,
call CICS transaction LY01 (see Appendix
C.1) to check whether the selected narrative
is present or not, and return any narrative
present, using COMMAREA C088 (see
Appendix D). N.B. Set C088-FIRST-CALL
to ‘N’. This call will return lines 301 to
600.

On return, check the C088-PROG-STATUS


and report any errors in the usual way.

(iii) If no errors found in LY88, the user should


be navigated to the Narrative Screen (see
Section 4.35)

Note:- the Narrative screen should be opened up as


a new window, overlaying whichever screen the
user is currently processing. Once the user has
finished enquiring on or updating the narrative, the
window should be closed and the user will be
returned to whichever screen they were processing
originally.

History When the user ‘clicks’ on this option they should be Command
navigated to the ‘Transaction History’ screen.

Note:- ‘Clicking’ on the ‘History’ option should


open up a new ‘window’ – associated with its own
entry on the Session Table (i.e. a new Session No.).
Once the user has finished browsing through

David Willcocks 75 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
history, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
History session - using Commarea C068
(see Appendix D).

On return, check the C068-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) Open new window, navigating user to


‘Transaction History’ screen (see Section
4.25) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY68)

Functions When user clicks on the ‘FUNCTIONS’ option at Command


the top of the screen, the following options should
be available on a sub-menu:-
1.Create Subsequent Advice
2.Create Rate of Exchange Adjustment
3.Create Contra Correction
4.Add Take Down Numbers
5. Copy From UCR
6. ‘CLASS for Lloyds’ Response
7. Set Diary Date
8. Create Bulk/CCS Correction
9. Set ‘File Last Seen’ Date
10. Reset Claim Transaction
11. Create Re-advice

User should select one of these options:-

‘Create Subsequent Advice’ selected

If the user selects ‘Create Subsequent Advice


(Single B/down)’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C020. (see Appendix D).
N.B. Ensure that C020-TRANS-TYPE is set to ‘V’
(Validation Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned from the first call to LY20,

David Willcocks 76 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
call CICS transaction LY01 (see Appendix C.1) to
‘construct’ the skeleton subsequent transaction –
using COMMAREA C020. (see Appendix D). N.B.
Ensure that C020-TRANS-TYPE is set to ‘U’
(Update Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned from the second call to


LY20, redisplay the ‘Claim Creation screen’
(current screen) – but rebuild it from scratch – as
field protection will be different and some field
contents may be different.

‘Create Rate of Exchange Adjustment’ selected

If the user selects ‘Create Rate of Exchange


Adjustment’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C021. (see Appendix D).

On return, check the C021-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Rate of
Exchange Adjustment (see Section 4.29).

‘Create Contra Correction’ selected

If the user selects ‘Create Contra Correction’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C022. (see Appendix D).

On return, check the C022-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Contra
Correction (see Section 4.30).

‘Add Take Down Numbers’ selected

If the user selects ‘Add Take Down Numbers’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using

David Willcocks 77 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
COMMAREA C023. (see Appendix D).

On return, check the C023-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘Settlement Summary’ (see Section
4.22).

‘Copy From UCR’ selected

If the user selects ‘Copy From UCR’, call CICS


transaction LY01 (see Appendix C.1) to perform
any validation necessary – using COMMAREA
C024. (see Appendix D).

On return, check the C024-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘Copy From UCR’ pop-up window
(see Section 4.33).

‘CLASS for Lloyds’ Response selected

If the user selects ‘CLASS for Lloyds Response’,


call CICS transaction LY01 (see Appendix C.1) to
check that the claim transaction is a ‘CLASS for
Lloyds’ claim and that it requires authorisation –
using COMMAREA C083. (see Appendix D).

On return, check the C083-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘CLASS for Lloyds Response’
screen (Note:- screen not available in Phase 1).

‘Set Diary Date’ selected

If the user selects the ‘Set Diary Date’ option, the


‘Set Diary Date’ pop-up window should be
displayed to them (see Section 4.34).

‘Create Bulk/CCS Correction’ selected

This is a special correction facility for use only by

David Willcocks 78 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
authorised technicians. It allows correction of Bulk
Components, converted bulks and pre-
redenomination transactions. The difference
between this type of correction and Contra
Corrections is that the user has the ability to enter a
treasury rate.

If the user selects ‘Create Bulk/CCS Correction’,


call CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C090. (see Appendix D).

On return, check the C090-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the
Bulk/CCS Correction (see Section 4.36).

‘Set File Last Seen Date’ selected

This function allows the user to set the File Last


Seen Date to todays date and generate an advice to
the syndicates without creating a new claim
movement.

If this function is selected, display the ‘File Seen


Confirmation’ window (see Appendix S.2). If the
technician presses ‘YES’ in this window, call CICS
transaction LY01 (see Appendix C.1) to perform
any validation necessary and set up the necessary
logging records – using COMMAREA C096. (see
Appendix D).

On return, check the C096-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up confirmation


window should be displayed (see Appendix S.3.)
for information purposes only.

‘Reset Claim Transaction’ selected

This function will reset the status of a previously


released claim transaction to allow it to be updated
by the claim technician. This will not be allowed if
the claim transaction has been fully advised or if a

David Willcocks 79 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
subsequent transaction exists within the claim.

(i) Call CICS transaction LY01 (see


Appendix C.1), passing the Commarea
C105 (see Appendix D). This will
validate that that the claim transaction
is eligible for update and, if so, reset the
status accordingly.

On return check the Program Status and


report any errors/warnings in the usual
way.

(ii) If no errors returned from LZ06, call


LY01 using Commarea C013 to obtain
the data and field protection for the
current screen.

On return check the Program Status and


report any errors/warnings in the usual
way.

(iii) Rebuild the current screen using the


data returned in the C013 Commarea.

‘Create Re-advice’ selected

This function will allow the user to create a re-


advice of the most recent movement on the claim –
changing only the current narrative.

(i) call CICS transaction LY01 (see Appendix C.1)


to perform any validation necessary – using
COMMAREA C110. (see Appendix D).

On return, check the C110-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Create Re-Advice’ screen (see Section 4.39).

David Willcocks 80 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B. Navigation Options (Left of Screen) - COMMANDS.

If user clicks on the ‘Option Button’ alongside any of the Options on the Navigation Bar, refer to table
returned by transaction LY12 (Build Navigation Bar) in the C012 Commarea. This table should be
stored after building the navigation bar on first entry to the screen for use when the user selects one of
the options on the Navigation Bar.

(i) If C013-SCREEN-MODE = ‘U’(Update), call CICS transaction LY01 (see Appendix C.1) to
validate that the policy details on the screen are correct – using Commarea C026 (see Appendix
D). (N.B. will need to call CICS transaction LY01 (see Appendix C.1) using Commarea C094,
see Appendix D, to build the Commarea that should be passed to LY26)

On return, check the C026-PROG-STATUS and report any errors/warnings in the usual way.

(ii) If C013-SCREEN-MODE = ‘U’ (Update) and no errors are returned from LY26 , call CICS
transaction LY01 (see Appendix C.1) to validate the other details on the screen – using
COMMAREA C025. (see Appendix D).

On return, check the C025-PROG-STATUS and report any errors/warnings in the usual way.

(iii) If C013-SCREEN-MODE = ‘U’ (Update) and no errors are returned from LY25 , check the
commarea returned from LY26 (step 1). If the user is creating a First Advice and the details
have been changed on the screen (compared to what is held on the database), the ‘Policy
Validation’ module (LY26) will return the market that should be loaded on this claim.
Depending on the details entered, there may be more than one market. If this is the case (i.e.
C026-LIDS-MKT-COUNT > 1), the user must select the market using the Market Selection
Screen (see Section 4.11).

(iv) If C013-SCREEN-MODE = ‘U’ (Update) and no errors are returned from LY25 and C094-
LIDS-MKT-COUNT = 0 and C094-PROG-STATUS = 5, this indicates that this is a subsequent
advice (or a subsequent pass through the screen) and differences have been found between the
data currently held on the CLASS database for this claim and the data held on LIDS for the
OSND(s) against which the claim is being made. In this case, display the ‘LIDS Comparison’
Screen (as detailed in Section 4.38)

(v) If C013-SCREEN-MODE = ‘U’ (Update) and no errors are returned from LY25 , call CICS
transaction LY01 (see Appendix C.1) to update the database with the details entered on the
screen – using COMMAREA C027. (see Appendix D).

On return, check the C027-PROG-STATUS and report any errors/warnings in the usual way.

David Willcocks 81 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(vi) If C013-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY27, call CICS
transaction LY01 (see Appendix C.1) – using COMMAREA C046 (see Appendix D) – to check
whether currency/transaction validation needs to be performed. (N.B. the key values returned
from LY12 and stored in the C012-KEY table – for the line on the navigation bar selected –
should be passed in the C046 commarea).

On return, check the C046-PROG-STATUS and report any errors/warnings in the usual way.

(vii) If no errors returned from LY46 or C013-SCREEN-MODE = ‘E’(Enquiry), call CICS


transaction LY01 (see Appendix C.1) to update the Session Record (VCLSESA1) –using
COMMAREA C010. (see Appendix D), (N.B. the key values returned from LY12 and stored in
the C012-KEY table – for the line on the navigation bar selected – should be passed in the C010
commarea)

On return, check the C010-PROG-STATUS and report any errors/warnings in the usual
way.

(viii) If no errors are returned from LY10, the user should be navigated to the screen indicated by
C012-SCREEN-ID for the line in the navigation bar selected (see Appendix N)

C. Fields (Main Screen)

N.B. If any errors are encountered, highlight any field(s) in error by setting the text colour to red.

XCR The Xchanging Claim Reference. This is assigned Display Only Alphanumeric
to claims that are created by internal technicians. It Field (17 Chars)
will always be present for internally created claims,
but not for claims created by the broker on the
‘CLASS for Lloyds’ system.

This field should be displayed in the following


format:-
‘X / XXXX / XXXXXXXXXXXX’

UCR The Unique Claim Reference. This will always be Display Only Alphanumeric
present for claims created by the broker on the Field (17 Chars)
‘CLASS for Lloyds’ system, but may or may not be
present for internally created claims – depending on
whether the broker has quoted it on the claim file.

This field should be displayed in the following


format:-
‘X / XXXX / XXXXXXXXXXXX’

TR The Transaction Reference. This identifies a Display Only Alphanumeric

David Willcocks 82 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
particular transaction within a claim. Field (17 Chars)

This field should be displayed in the following


format:-
‘X / XXXX / XXXXXXXXXXXX’

Originating The code that identifies the Originating Broker. Display Only Alphanumeric
Broker Field (4 Chars)
Peer Review This indicates that the claim is subject to peer Display Only Alphanumeric
Indicator review. Field (1 Char)

Transaction This field will provide a brief (system generated) Display Only Alphanumeric
Synposis overview of the claim transaction. I.e. whether it is Field (2 lines of 70
a settlement or an advice, whether it has been made Chars)
against delinked signings, whether it is a contra,
rateof Echange or Bulk Header/component, etc.

OSND1 The Original Signing Number and Date of the risk Optional Field Alphanumeric
to which this claim attaches. Field
(15 Chars)
This field is not mandatory because it is possible for
a claim to be raised before the risk has signed.
Therefore, this field must be completed if the ‘Risk
Unsigned’ box is not ‘ticked’. Conversely, it must
not be completed if the ‘Risk Unsigned’ box is
‘ticked’.

The format of the field is as follows:-

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date


And SSSSS is numeric.

If the OSND does not conform to this format,


display the error E190 (see Appendix E) in the
error window (see Appendix B)

The OSND cannot be entered without the associated


Original Currency being completed. If it is, display
the error E062 (see Appendix E) in the Error
Window (see Appendix B).

APSND1 The Signing Number and Date of the Additional (or Optional Field Alphanumeric
Refund) Premium. Field
(15 Chars)
The user may enter this reference to identify a
particular market and set of values to which this

David Willcocks 83 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
claim relates.

The format of the field is as follows:-

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date


And SSSSS is numeric.

If the APSND does not conform to this format,


display the error E191 (see Appendix E) in the
error window (see Appendix B)

APSND1 cannot be entered without the associated


OSND1 being completed. If it is, display the error
E064 (see Appendix E) in the Error Window (see
Appendix B).

APSND1 cannot be entered without the associated


‘Original Currency 1’ being completed. If it is,
display the error E063 (see Appendix E) in the
Error Window (see Appendix B).

Original The Original Currency. This is the first of up to Mandatory Alphanumeric


Currency 1 three Original currencies. As there must always be Field Field
at least one currency on the claim, this first currency (3 Chars)
is mandatory.

OSND2 The second Original Signing Number and Date of Optional Field Alphanumeric
the risk to which this claim attaches. This is Field
completed if the claim is to be made in more than (15 Chars)
one currency.

This field must not be completed if the ‘Risk


Unsigned’ box is ‘ticked’.

The format of the field is as follows:-

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date


And SSSSS is numeric.

If the OSND2 does not conform to this format,


display the error E190 (see Appendix E) in the
error window (see Appendix B)

The OSND cannot be entered without the associated

David Willcocks 84 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Original Currency being completed. If it is, display
the error E062 (see Appendix E) in the Error
Window (see Appendix B).

APSND2 The Signing Number and Date of the Additional (or Optional Field Alphanumeric
Refund) Premium. Field
(15 Chars)
The user may enter this reference to identify a
particular market and set of values to which this
claim relates.

The format of the field is as follows:-

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date


And SSSSS is numeric.

If the APSND2 does not conform to this format,


display the error E191 (see Appendix E) in the
error window (see Appendix B)

APSND2 cannot be entered without the associated


OSND2 being completed. If it is, display the error
E064 (see Appendix E) in the Error Window (see
Appendix B).

APSND2 cannot be entered without the associated


‘Original Currency 2’ being completed. If it is,
display the error E063 (see Appendix E) in the
Error Window (see Appendix B).

Original The Original Currency. This is the second of up to Optional Field Alphanumeric
Currency 2 three Original currencies. Field
(3 Chars)
OSND3 The third Original Signing Number and Date of the Optional Field Alphanumeric
risk to which this claim attaches. This is completed Field
if the claim is to be made in more than one (15 Chars)
currency.

This field must not be completed if the ‘Risk


Unsigned’ box is ‘ticked’.

The format of the field is as follows:-

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date

David Willcocks 85 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
And SSSSS is numeric.

If the OSND3 does not conform to this format,


display the error E190 (see Appendix E) in the
error window (see Appendix B)

The OSND cannot be entered without the associated


Original Currency being completed. If it is, display
the error E062 (see Appendix E) in the Error
Window (see Appendix B).

APSND3 The Signing Number and Date of the Additional (or Optional Field Alphanumeric
Refund) Premium. Field
(15 Chars)
The user may enter this reference to identify a
particular market and set of values to which this
claim relates.

The format of the field is as follows:-

‘CCYYMMDDSSSSS’

Where CCYYMMDD is a valid date


And SSSSS is numeric.

If the APSND3 does not conform to this format,


display the error E191 (see Appendix E) in the
error window (see Appendix B)

APSND3 cannot be entered without the associated


OSND3 being completed. If it is, display the error
E064 (see Appendix E) in the Error Window (see
Appendix B).

APSND3 cannot be entered without the associated


‘Original Currency 3’ being completed. If it is,
display the error E063 (see Appendix E) in the
Error Window (see Appendix B).

Original The Original Currency. This is the third of up to Optional Field Alphanumeric
Currency 3 three Original currencies. Field
(3 Chars)
Sett. / Adv. This field indicates whether or not this claim Mandatory n/a
transaction is an ‘Advice’ or an ‘Advice with Field
settlement’, etc. It will be associated with a drop
down list. The user must select one of the options
on the list. The list is as follows:-

David Willcocks 86 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

‘Settlement’
‘Advice’

Non-SCM Indicates that the claim is not to be advised on Tick Box n/a
Advice the SCM.

Bulk This field whether the current claim transaction is a Optional Field n/a
Indicator Bulk Header or not. This field will be protected on
all subsequent transactions.

If the user has ticks the ‘Bulk’ indicator, they must


also have selected ‘Settlement’ in the ‘Sett./Adv.’
Field. If not, display the error E194 (see Appendix
E) in the error window (see Appendix B).

Risk This ‘tick-box’ indicates that the risk to which the Tick Box n/a
Unsigned claim attaches is not yet signed.

Treaty Ind. This ‘tick-box’ indicates that the claim is a treaty. Tick Box n/a

Loss This ‘tick-box’ indicates that the claim is a Loss Tick Box n/a
Reserve reserve.

L.O.C. This ‘tick-box’ indicates that the claim is a Letter of Tick Box n/a
Credit claim.

Loss Fund This ‘tick-box’ indicates that the claim is a Loss Tick Box n/a
Fund.

If the user has indicated that the current claim


transaction is adcvice-only – by selecting ‘Advice’
in the ‘Sett/Adv’ field, this field must not be ticked.
If it is, display the error ‘E375’ in the Error Screen
(see Appendix E).

Pay by This field indicates that the claim is to be paid by Field Alphanumeric
Cheque cheque. (1 char)

The field will initially be set to spaces. The user


will have to enter either ‘Y’ or ‘N’ for transactions
involving settlement.

This field will be associated with a drop-down list.


The values in which are:-

David Willcocks 87 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

‘Y’ = Paid by Cheque


‘N’ = Not Paid by Cheque

Charge Type This field indicates the type of charge that should be MandatoryFiel Alphanumeric
applied to the current claim transaction. d (2 Chars)

This field will be associated with a drop down list,


containing the following options:-

CH – Claims Handling
EP – ECR Purge
EU – ECR Update
ER – ECR Reserve Validation
CP – Settlement of Claims Payable Abroad

Note:- The description should be included in the the


drop down list as well as the code. Also, the user
has to select from list and can’t enter directly into
field.

Non- This tick-box will allow the technician to indicate Tick-Box N/a
Chargea that the current collection is non-chargeable.
ble
Indicator For Contra’s entered on the ‘CLASS for Lloyds’
system, this will be pre-populated with a tick and
protected.

For all other ‘CLASS for Lloyds’ transactions, the


field will non-ticked and protected.

For internally created transactions the box will be


un-protected (unless the transaction is being viewed
in enquiry mode).

Previousl This indicator is set by either the broker or the Tick-Box N/a
y internal technician to advise that the claim has
Advised already been advised outside the CLASS System.
Non- Setting this flag allows a non-zero previously
settled amount to be supplied on an initial advice. It
Network
also allows an initial advice to be a refund or
Indicator recovery.
It can only be ‘ticked’ on first advices. Thereafter, it
is brought forward and protected.
Previousl This indicator can be set by the technician to Tick-Box N/a
y Paid indicate that the settlement attached to the claim
transaction has already been settled outside the

David Willcocks 88 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
indicator system. The transaction is therefore being loaded
purely to advise the syndicates of the settlement in
the SCM – the transaction should not be extracted
in the CTF or advised in the USM.

Letter of This field will be set on the ‘Cash’ UCR related to a Optional Tick- N/a
Credit Letter of Credit claim, to indicate that the settlement Box
(LOC) amounts relate to a Letter of Credit Drawing.
Drawing
Indicator If the user ticks this box, issue errors under the
following circumstances:-
(i) User must have selected ‘Settlement’ in
the ‘Sett/Adv’ field. If not, display the
error ‘E379’ in the Error Screen (see
Appendix E).
(ii) User must not have ticked the LOC
tick-box. If they have, display the error
‘E380’ in the Error Screen (see
Appendix E).

Scheme This tick-box indicates that the claim in question is Optional Tick- N/a
Canada a Scheme Canada claim. Once set to ‘Y’ on a Box
Indicator particular claim, this field will be protected on all
subsequent transactions.

Simultane This tick-box indicates that a Reinstatement Optional Tick- N/a


ous RIP Premium is required before the claim can be settled Box
Indicator and that this premium must be settled at the same
time as the claim.

If the user has indicated that the current claim


transaction is advice-only – by selecting ‘Advice’ in
the ‘Sett/Adv’ field, this field must not be ticked. If
it is, display the error ‘E374’ in the Error Screen
(see Appendix E).

CPA This tick-box indicates that the claim is payable Optional Tick- N/a
Indicator abroad. Box

Direct This indicates that the claim is part of the Direct Optional Tick- N/a
Livestock Livestock Scheme. Box
Indicator
Presentati This is the date the claim file was presented to Mandatory Date
on Date XCS/XIS. This is entered in order to monitor the Field (DD/MM/CCYY)
length of time between presentation of the claim file
and the entry and release of the claim on the
CLASS system.

David Willcocks 89 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
ECF Class Identifies whether a claim is in ECF or not, and Mandatory Alphanumeric
identifies different reasons for claims being In Field (2 Chars)
or Out of ECF passed in the
commareas
plus
Alphanumeric
description (30
chars)
Special This indicator enables users with the necessary Optional Tick- N/a
Payment authority to raise settlement transactions against Box
Indicator claims where on or more syndicates on the market
have opted out of settlement. In this situation, they
are only able to enter Fees, Expenses and VAT.
D. Commands – (Main Screen)
SAVE This key allows the user to save the details they Command
have entered on the screen without being navigated
onto a different screen. Note:- this button should be
disabled if the screen is being viewed in ‘Enquiry’
mode (i.e. C013-SCREEN-MODE = ‘E’)

(i) Call CICS transaction LY01 (see Appendix


C.1) to validate that the policy details are
valid – using Commarea C094 (see
Appendix D). (Note:- LY94 builds the
LIDS Interface Commarea and then calls
the LIDS interface).

On return, check the C094-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) If no errors are returned from LY94, call


CICS Transaction LY01 (see Appendix
C.1.) to validate the other details on the
screen – using Commarea C025 (see
Appendix D).

On return, check the C025-PROG-STATUS


and report any errors/warnings in the usual
way.

(iii) If C013-SCREEN-MODE = ‘U’ (Update)


and no errors are returned from LY25 ,
check the commarea returned from LY94
(step 1). If the user is creating a First
Advice and the details have been changed
on the screen (compared to what is held on
the database), the ‘Policy Validation’

David Willcocks 90 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
module (LY94) will return the market that
should be loaded on this claim. Depending
on the details entered, there may be more
than one market. If this is the case (i.e.
C094-LIDS-MKT-COUNT > 1), the user
must select the market using the Market
Selection Screen (see Section 4.11).

(iv) If C013-SCREEN-MODE = ‘U’ (Update)


and no errors are returned from LY25 and
C094-LIDS-MKT-COUNT = 0 and C094-
PROG-STATUS = 5, this indicates that this
is a subsequent advice (or a subsequent pass
through the screen) and differences have
been found between the data currently held
on the CLASS database for this claim and
the data held on LIDS for the OSND(s)
against which the claim is being made. In
this case, display the ‘LIDS Comparison’
Screen (as detailed in Section 4.38)

(v) If C013-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY25, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C027. (see Appendix D).

If C094-LIDS-MKT-COUNT = 1, set the


market in the C027 Commarea to the values
contained in C094-LIDS-MARKET (1). If
C094-LIDS-MKT-COUNT > 1, set the
market in the C027 Commarea to the one
selected by the user in the ‘Market
Selection Screen’ – see Section 4.11.

On return, check the C027-PROG-STATUS


and report any errors/warnings in the usual
way.

CONTINUE (i) If C013-SCREEN-MODE = Command


‘U’(Update), call CICS transaction
LY01 (see Appendix C.1) to validate
the policy details – using Commarea
C094 (see Appendix D). (Note:- LY94
builds the LIDS Interface Commarea
and then calls the LIDS interface).

David Willcocks 91 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

On return, check the C094-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) If C013-SCREEN-MODE =
‘U’(Update) and no errors returned
from LY94, Call CICS transaction
LY01 (see Appendix C.1) to validate
the other details on the screen – using
COMMAREA C025. (see Appendix
D).

On return, check the C025-PROG-STATUS


and report any errors/warnings in the usual
way.

(iii) If C013-SCREEN-MODE = ‘U’


(Update) and no errors are returned
from LY25 , check the commarea
returned from LY94 (step 1). If the user
is creating a First Advice and the details
have been changed on the screen
(compared to what is held on the
database), the ‘Policy Validation’
module (LY94) will return the market
that should be loaded on this claim.
Depending on the details entered, there
may be more than one market. If this is
the case (i.e. C094-LIDS-MKT-
COUNT > 1), the user must select the
market using the Market Selection
Screen (see Section 4.11).

(iv) If C013-SCREEN-MODE = ‘U’


(Update) and no errors are returned
from LY25 and C094-LIDS-MKT-
COUNT = 0 and C094-PROG-STATUS
= 5, this indicates that this is a
subsequent advice (or a subsequent pass
through the screen) and differences
have been found between the data
currently held on the CLASS database
for this claim and the data held on
LIDS for the OSND(s) against which
the claim is being made. In this case,
display the ‘LIDS Comparison’ Screen
(as detailed in Section 4.38)

David Willcocks 92 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(v) If C013-SCREEN-MODE =
‘U’(Update) and no errors returned
from LY25, Call CICS transaction
LY01 (see Appendix C.1) to update the
database with the details entered on the
screen – using COMMAREA C027.
(see Appendix D).

If C094-LIDS-MKT-COUNT = 1, set the


market in the C027 Commarea to the values
contained in C094-LIDS-MARKET (1). If
C094-LIDS-MKT-COUNT > 1, set the
market in the C027 Commarea to the one
selected by the user in the ‘Market
Selection Screen’ – see Section 4.11.

On return, check the C027-PROG-STATUS


and report any errors/warnings in the usual
way.

(vi) If no errors returned from LY27 or


C013-SCREEN-MODE = ‘E’
(Enquiry), call the CICS transaction
LY01 (see Appendix C.1) – using
COMMAREA C011 (see Appendix D).
This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated
to.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(vii) Navigate the user to whichever program


is identified in C011-NEXT-
PROGRAM (see Appendix N) (should
be either ‘Policy Details’ or ‘Financial
Details’ – depending on whether the
claim is an initial or subsequent advice)

Bring This button is only available for ‘CLASS for Command


Forward Lloyds’ transactions where the previous transaction
Breakdown within the current ‘CLASS for Lloyds’ claim has (at
least) been released for advising on the USM/SCM.
It is necessary because, the breakdown (SCM
Advice) information is not entered on the ‘CLASS

David Willcocks 93 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
for Lloyds’ system and must be brought forward
from the previous transaction within the claim by
the internal technician. This can only be performed
once the breakdown has been satisfactorily
completed on the previous transaction.

(i) Call CICS Transaction LY01 (see


Appendix C.1) using Commarea C093
(see Appendix D). This will bring
forward the breakdown from trhe
previous transaction within the claim.

On return, check the Program Status in


the usual way, reporting errors if they
exist in the Error Screen (see Appendix
B)

(ii) On successful completion, the user


should remain in the Claim Transaction
Creation screen.

Delete This button is only available for ‘CLASS for Command


Breakdown Lloyds’ transactions that are not complete and are
the most recent transaction within the claim. This
button is required in order to allow changes to be
made to the breakdown (SCM Advice) details on
the previous transaction (assuming that the previous
transaction is also not yet complete). Because
changes to the breakdown details on the previous
transaction will need to be reflected on any
subsequent transactions, the user will have to delete
the breakdown on the subsequent transactions,
make any necessary changes to the details on the
earlier transaction and then bring the breakdown
forward again using the ‘Bring Forward
Breakdown’ button (see above).

(i) Call CICS Transaction LY01 (see


Appendix C.1) using Commarea C097
(see Appendix D). This will delete the
breakdown on the current tranbsaction.

On return, check the Program Status in


the usual way, reporting errors if they
exist in the Error Screen (see Appendix

David Willcocks 94 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B)

(ii) On successful completion, the user


should remain in the Claim Transaction
Creation screen.

CANCEL When the technician presses the ‘Cancel’ button, Command


any changes made since the last ‘Save’ will be
removed. The technician will remain in the ‘Claim
Transaction Creation’ screen. Therefore:-

(i) Call the CICS transaction LY01 (see


Appendix C.1) – using COMMAREA
C013 (see Appendix D) . This
transaction will return the data that
should appear on this screen.

On return, check the Program Status in


the usual way, reporting errors if they
exist in the Error Screen (see Appendix
B)

(iii) Rebuild the screen, based on the data


returned in the C013 Commarea.

EXIT This will return the user to whichever screen they Command
initiated the claim from.

(i) Call CICS transaction LY01 (see Appendix C.1)


to check the status of the current transaction –
using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B). If status is zero,
continue at (iv)

(i) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before being navigated to the next
screen. Display the ‘Claim Transaction Options’
pop-up window detailed in Section 4.10 and
perform processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim

David Willcocks 95 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Transaction options’ window, the user should be
left in the current screen.

(iv) If the user did not press ‘Cancel’ or zero


Program Status returned from LY16,
Call the CICS transaction LY01 (see Appendix
C.1) – using COMMAREA C011 (see
Appendix D). This will invoke the ‘Navigation’
program, which decides on the next program the
user should be navigated to. (Note: the
C011-EXIT-IND should be set to ‘Y’)

On return, check the Program Status in the Usual


way, reporting errors if they exist in The Error
Screen (see Appendix B)

(v) If no errors returned from LY11, navigate the


user to the program indicated by
C011-NEXT-PROGRAM (see Appendix N).
If C011-NEXT-PROGRAM is set to 'NONE',
the current window should be closed.

David Willcocks 96 May 2002


Xchanging Ins-sure Services Ltd
4.10. Claim Transaction Options Window

4.10.1. Screen Layout

Below is the ‘Claim Transaction Options’ window.

4.10.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY94 Build Commarea for LIDS Interface

4.10.3. Field Derivation

Each of the fields on this screen will be derived as


follows:-

Field Type Source


UCR/XCR Field C016-UCR
TR Field C016-TR

David Willcocks 97 May 2002


Xchanging Ins-sure Services Ltd
4.10.4. Process Description

This ‘pop-up’ window will be displayed if the user decides to leave a


claim that they had been updating without first ‘Releasing’ the claim
transaction. The window will give them the following options:-

Fig 4.10.4.1. Field/Command Processing for ‘Claim Transaction


Options’ window

Field / Attributes Data Type


Description
Command
CANCEL This option allows the user to cancel Comma
the action that would have caused nd
them to exit the claim and leave them
on the current screen.

- Close the ‘Claim Transaction


Options’ window
YES This option will allow the user to Comma
validate and save the details on the nd
current screen before leaving the
claim transaction. The transaction
will be left in an ‘incomplete’ state –
which means it won’t yet be advised
on the SCM or the USM.

Note:- If the technician was in the ‘Claim


Transaction Creation’ screen prior to this window
being displayed, call CICS transaction LY01 (see
Appendix C.1) to validate that the policy details are
valid – using Commarea C094 (see Appendix D).
On return, check the C026-PROG-STATUS and
report any errors/warnings in the usual way.

(i) Call the ‘LY01’ passing the


Commarea associated with the
CICS transaction that performs
the validation for the screen
the user was in prior to this
window being displayed.

On return, check the program


status and report any

David Willcocks 98 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
error/warnings in the usual
way.

Note(1):- If the technician was in the ‘Claim


Transaction Creation’ screen prior to this window
being displayed (and no errors are returned from
LY25), check the commarea returned from LY94
(see above). If the user is creating a First Advice
and the details have been changed on the screen
(compared to what is held on the database), the
‘Policy Validation’ module (LY94) will return the
market that should be loaded on this claim.
Depending on the details entered, there may be
more than one market. If this is the case (i.e. C094-
LIDS-MKT-COUNT > 1), the user must select the
market using the Market Selection Screen (see
Section 4.11).

(ii) Call ‘LY01’ passing the


Commarea associated with the
CICS transaction that performs
Database Updates that apply to
the screen the user was in prior
to this window being displayed
(see Appendix H)

On return, check the


Program Status and
report any errors in the usual
way.

(iii) Continue with the action the user was


performing before this window was
displayed.

NO This option allows the user to exit the Comma


claim transaction without performing nd
any validation or saving any details
entered on the current screen. This
will leave the claim transaction in an
‘incomplete’ state.

(i) Continue with the action the user was


performing before this window was
displayed.

David Willcocks 99 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

David Willcocks 100 May 2002


Xchanging Ins-sure Services Ltd
4.11. Market Selection Screen

4.11.1. Screen Layout

Below is a ‘mock-up’ of the Market Selection Screen

4.11.2. CICS Transactions

No CICS Transactions are called by this screen

David Willcocks 101 May 2002


Xchanging Ins-sure Services Ltd
4.11.3. 4.11.3. Field/Command Derivation

The fields on this screen will be derived as follows:-

Field Type Source


4. Fields:-

Fields on this screen are derived from the information returned from the Policy
Validation (LY26), in the C094 Commarea. This module was called in the ‘Claim
Creation’ screen and the return of more than one market causes this screen to be
displayed. An entry should be built on the screen for each market returned.

Note:- All fields on this screen should be protected.

Effective Date Field C094-EFFECTIVE-DATE


(n)
No. Of Field C094-MKT-LINE-COUNT
Syndicates (n)
Bureau Line (n) Field C094-BUREAU-LINE
Narrative (n) Field C094-MARKET-NARR

4.11.4. Process Description

This screen will be presented to the user if more than


one effective market is returned from the LIDS
Interface program. This will only occur when the
technician is creating a first advice. The market will
remain the same on all subsequent advices and
reselection will not have to take place. The technician
will have to select one of the markets on this screen –
and will not be able to leave the Claim Creation screen
until they have done so. If further information is
required on each of the available markets in order for
the technician to arrive at a decision, a link is available
to the ‘Account Enquiry’ at the top of the Claim
Creation screen. The technician should simply ‘Cancel’
out of the ‘Market Selection’ screen and ‘click’ on the
‘Account Enquiry’ link at the top of the underlying
screen.

This is a separate window that ‘overlays’ the ‘Claim Creation’ screen


and will simply be closed down once the user has finished selecting the
markets. (Hence it has no navigation bar to the left of the screen or
functions at the top)

David Willcocks 102 May 2002


Xchanging Ins-sure Services Ltd
Fig 4.11.4.1. Field/Command Processing for ‘Market Selection’
Screen

Field / Attributes Data Type


Description
Command

5. Fields (Main Screen)

Select The option button on this screen enables the Option N/A
technician to choose one of the effective markets. button
Effective The date on which the market became effective. Display Date
Date (n) Only Field (DD/MM/CCYY)

No. Of The number of syndicate lines on the market Display Numeric


Syndicates Only Field Z9
(n)
Bureau The total Bureau Line for the market. I.e. the sum of Display Numeric
Line (n) the individual syndicate lines. Only Field ZZ9.9(7)
Narrative Market Narrative to outline the reasons behind the Display Alphanumeric
(n) creation of each effective market. Only (210 Chars)
scrolling
Field

B. Commands – (Main Screen).

OK If the user presses this button check that one of the Command
markets has been selected.

If no market has been selected, display the error


E141 (see Appendix E) in the Error Window (see
Appendix B).

If more than one market has been selected, display


the error E142 (see Appendix E) in the Error
Window (see Appendix B).

If no errors are found, store the selection made,


close the ‘Market Selection’ window and return
control to the Claim Creation screen – continue with
either ‘SAVE’ or ‘CONTINUE’ proocessing, as
defined by Section 4.9.4.

David Willcocks 103 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

Cancel If the user presses this button the ‘Market Selection’


window should be closed – returning the user to the
‘Claim Creation’ screen – redisplay the screen.

4.12. Policy Details Screen

Change Control Log

Release Date Changed TP No. Description of Changes Made


By
XCS 26/08/2008 DBP TP631646 CR7-FS2:- change screen to display new Slip Type
CLASS field, associated with a drop-down list. The
Phase 4 interfaces with mainframe (build, vali8dation and
update) will need amending to include Slip Type in
the commarea.

4.12.1. Screen Layout

Below is the Policy Details Screen.

David Willcocks 104 May 2002


Xchanging Ins-sure Services Ltd
David Willcocks 105 May 2002
Xchanging Ins-sure Services Ltd
The Policy screen will be changed for XCS CLASS Phase 4 to add Slip Type:

David Willcocks 106 May 2002


Xchanging Ins-sure Services Ltd
David Willcocks 107 May 2002
Xchanging Ins-sure Services Ltd
4.12.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY10 Update Session Record
LY11 Navigation Program
LY12 Build Screen Navigation Bar
LY14 Add OSND(s) to Aggregate Group
LY15 Create Non-Aggregate Group
LY16 Check Transaction Status
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY28 Build Policy/Risk Details Screen
LY29 Policy/Risk Details Screen Validation
LY30 Policy/Risk Details Screen D/B Update
LY46 Check whether Currency/Transaction
Validn. reqd.
LY68 Create History Session Record
LY71 Set up Group Session Record
LY83 ‘CLASS for Lloyds’ Response – Initial
Validation
LY88 Build Narrative Details Screen
LY90 Bulk/CCS Correction Initial Validation
LY96 Set File Last Seen Date
LZ06 Reset Claim Transaction
LZ11 Create Re-Advice – Initial Validation

4.12.3. Field/Command Derivation

The fields and the navigation bar on this screen will be


derived as follows:-

Field Type Source


A. Navigation Bar

David Willcocks 108 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Navigation Bar Comman call the CICS transaction LY01 (see Appendix
d(s) C.1) – using COMMAREA C012 (see Appendix
D) . This will determine what should appear on
the ‘Screen Navigation Bar’ at the left hand side
of the screen.

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

See Appendix F for details of how to process the


information returned from this CICS transaction.

B. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C028 (see
Appendix D) . This transaction will return the data that should appear on this screen.

On return, check the Program Status in the usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

XCR Field C028-XCR


(This field should be protected)
UCR Field C028-UCR
(This field should be protected)
TR Field C028-TR
(This field should be protected)
OSND1 Field C028-ORIG-REF-1
(This field should be protected)

OSND2 Field C028-ORIG-REF-2


(This field should be protected)
OSND3 Field C028-ORIG-REF-3
(This field should be protected)
Peer Review Field C028-PEER-REV-IND
(If C028-PEER-REV-ATTR = ‘P’, this
field should be protected)
Orig. Broker Field C028-ORIG-BKR
(If C028-ORIG-BKR-ATTR = ‘P’, this
field should be protected)
Curr. Broker Field C028-CURR-BKR
(If C028-CURR-BKR-ATTR = ‘P’, this
field should be protected)
Risk Code Field C028-RISK-CODE
(If C028-RISK-CODE-ATTR = ‘P’,

David Willcocks 109 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
this field should be protected)
Market Code Field C028-MARKET-CODE
(If C028-MKT-CODE-ATTR = ‘P’,
this field should be protected)
Year of Account Field C028-YEAR-OF-ACC
(YOA) (If C028-YOA-ATTR = ‘P’, this field
should be protected)
Interest Field C028-INTEREST
(If C028-INTEREST-ATTR = ‘P’, this
field should be protected)
Ccy (n) Field C028-LIMIT-CURR (n)
(If C028-LIMIT-CURR-ATTR = ‘P’,
this field should be protected)
Limits (n) Field C028-SI-LIMIT (n)
(If C028-SI-LIMIT-ATTR = ‘P’, this
field should be protected)
Excess (n) Field C028-EXCESS-LIMIT (n)
(If C028-EXCESS-LIM-ATTR = ‘P’,
this field should be protected)
Sum Insured Field C028-SI-NARR-1
Narrative 1 (If C028-SI-NARR-ATTR1 = ‘P’, this
field should be protected)
Order 1 Field C028-SLIP-ORDER-1
(If C028-SLIP-ORDER-ATTR1 = ‘P’,
this field should be protected)
Order 2 Field C028-SLIP-ORDER-2
(If C028-SLIP-ORDER-ATTR2 = ‘P’,
this field should be protected)
Perils / Field C028-PERILS-CONDS
Conditions (If C028-PERILS-CONDS-ATTR =
‘P’, this field should be protected)
Location / Field C028-LOCATION-VOYAGE
Voyage of Risk (If C028-LOC-VGE-ATTR = ‘P’, this
field should be protected)
Basis of Loss Field C028-BASIS-OF-LOSS
(If C028-BASIS-OF-LOSS-ATTR =
‘P’, this field should be protected)
Policy/Cert. Field C028-POL-CERT-FROM
Period From (If C028-POL-FROM-ATTR = ‘P’,
this field should be protected)
Policy/Cert. Field C028-POL-CERT-TO
Period To (If C028-POL-TO-ATTR = ‘P’, this
field should be protected)

David Willcocks 110 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Policy/Cert. Field C028-POL-CERT-QUAL
Qualifier (If C028-POL-CERT-Q-ATTR = ‘P’,
this field should be protected)
Policy Period Field C028-POL-PERIOD-NARR
Narrative (If C028-POL-NARR-ATTR = ‘P’, this
field should be protected)
Cover/Lineslip Field C028-COVER-LS-FROM
From (If C028-COVER-FROM-ATTR = ‘P’,
this field should be protected)
Cover/Lineslip Field C028-COVER-LS-TO
To (If C028-COVER-TO-ATTR = ‘P’, this
field should be protected)
Cover/Lineslip Field C028-COVER-LS-QUAL
Qualifier (If C028-COVER-LS-Q-ATTR = ‘P’,
this field should be protected)
War Indicator Field C028-WAR-IND
(If C028-WAR-IND-ATTR = ‘P’, this
field should be protected)
Slip Type Field C028-SLIP-TYPE
(If C028-SLIP-TYPE-ATTR = ‘P’, this
field should be protected)
Unique Market Field C028-UMR
Reference (If C028-UMR-ATTR = ‘P’, this field
(UMR) should be protected)

4.12.4. Process Description

This screen is the Policy/Risk Details screen. When


creating an initial advice, it will be pre-filled with the
Policy/Risk Details obtained from LIDS for the Original
Signing Number(s) and Date(s) entered on the ‘Claim
Creation’ screen. These details will be unprotected and
may be changed by the user, although certain fields
(e.g. Originating Broker Code) can only be changed to
one of a list of valid values that will be returned from
LIDS, and shown in a drop down menu.
On subsequent advices, the contents of this screen will
be pre-filled from the details on the previous
transaction. Hence, if the details held on LIDS are
overwritten on the first transaction within a claim, they
will not need to be overwritten on each subsequent
transaction.

David Willcocks 111 May 2002


Xchanging Ins-sure Services Ltd
If the claim was entered by the broker, then any broker-
supplied details on this screen will be protected. If the
details entered by the broker do not contain sufficient
detail for advice to syndicates, then the information
should be enhanced on the ‘SCM Advice’ screen (see
Section 4.17).
If this screen is being viewed in ‘Enquiry’ mode, then
all fields will be protected.

Fig 4.12.4.1. Field/Command Processing for ‘Policy/Risk Details’


Screen

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D) to log-
off the system and delete the Session Record.

On return from CICS, check the C004-PROG-


STATUS field:-

6. if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix
B)

7. if set to zero, close all windows.

Create New (i) Call CICS transaction LY01 (see Appendix Command
Claim C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

David Willcocks 112 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Create Claim
Screen’ (see Section 4.4)

Find Claim (i) Call CICS transaction LY01 (see Appendix Command
C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

David Willcocks 113 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(iii) If user pressed ‘Cancel’ in the ‘Claim
Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Find Claim’ Screen
(see Section 4.5)

Account Link to Account Enquiry (method needs to be Command


Enquiry identified)

Repository Link to Repository (method needs to be identified) Command

Data Link to Data Warehouse (method needs to be Command


Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry

David Willcocks 114 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Add to Aggregate Group
Create Non-Aggregate Group
Add to Non-Aggregate Group

User should select one of these options.

Note:- ‘Clicking’ on the ‘Maintain Group’,


‘Group Enquiry’ or ‘Add to Non-Aggregate
Group’ options should open up a new ‘window’ –
associated with its own entry on the Session Table
(i.e. a new Session No.). Once the user has finished
Group processing, the window should be closed and
the Session Record deleted.

(i) If either the ‘Maintain Group’, ‘Group


Enquiry’ or ‘Add to Non-Aggregate
Group’ options were selected, call CICS
transaction LY01 (see Appendix C.1) to set
up a new Session Record for the Grouping
session – using Commarea C071 (see
Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iv) On selection of ‘Add to Aggregate


Group’, call CICS transaction LY01
(see Appendix C.1) to add the OSND’s
associated with this claim to an Aggregate
group – using COMMAREA C014 (see

David Willcocks 115 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Appendix D).

On return, check the C014-PROG-


STATUS
and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the OSND’s
have been added to. (see Appendix G)

(v) On selection of ‘Create Non-Aggregate


Group’, call CICS transaction LY01 (see
Appendix C.1) to add the current claim
to a Non-Aggregate group – using
COMMAREA C015 (see Appendix D).

On return, check the C015-PROG-


STATUS
and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the claim has
been added to. (see Appendix G)

(vi) On selection of the ‘Add to Non-


Aggregate Group’ option, open new
window, navigating user to ‘Group Enquiry’
screen (see Section 4.28) (a new SESSION-
NO is associated with this window – this
will have been returned by previous
transaction, LY71)

Notes When user clicks on the ‘NOTES’ option at the top Command
of the screen, the following options should be
available on a sub-menu:-
Security Notes
Claim Notes
Loss Details
Policy Details
EURO Conversion Narrative (FME)
Broker Additional Details
Broker Aggregate Details

David Willcocks 116 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Slip Lead Comments
Lead Comments
Lead Additional Details

User should select one of these options.

(i) Whichever option is selected, call CICS


transaction LY01 (see Appendix C.1) to
check whether the selected narrative is
present or not, and return any narrative
present, using COMMAREA C088 (see
Appendix D). N.B. Set C088-FIRST-
CALL to ‘Y’. This call will return lines
1 to 300.

On return, check the C088-PROG-STATUS


and report any errors in the usual way.

(ii) If no errors returned from the first


LY88 call and C088-MORE-LINES is
set to ‘Y’, call CICS transaction LY01
(see Appendix C.1) to check whether
the selected narrative is present or not,
and return any narrative present, using
COMMAREA C088 (see Appendix D).
N.B. Set C088-FIRST-CALL to ‘N’.
This call will return lines 301 to 600.

On return, check the C088-PROG-STATUS


and report any errors in the usual way.

(i) If no errors found in LY88, the user should


be navigated to the Narrative Screen (see
Section 4.35)

Note:- the Narrative screen should be opened up as


a new window, overlaying whichever screen the
user is currently processing. Once the user has
finished enquiring on or updating the narrative, the
window should be closed and the user will be
returned to whichever screen they were processing
originally.

History When the user ‘clicks’ on this option they should be Command
navigated to the ‘Transaction History’ screen.

Note:- ‘Clicking’ on the ‘History’ option should


open up a new ‘window’ – associated with its own

David Willcocks 117 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
entry on the Session Table (i.e. a new Session No.).
Once the user has finished browsing through
history, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
History session – using Commarea C068
(see Appendix D).

On return, check the C068-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) Open new window, navigating user to


‘Transaction History’ screen (see Section
4.25) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY68)

Functions When user clicks on the ‘FUNCTIONS’ option at Command


the top of the screen, the following options should
be available on a sub-menu:-
1.Create Subsequent Advice
2.Create Rate of Exchange Adjustment
3.Create Contra Correction
4.Add Take Down Numbers
5.‘CLASS for Lloyds’ Response
6.Set Diary Date
7. Create Bulk/CCS Correction
8.Set ‘File Last Seen’ Date
9. Reset Claim Transaction
10. Create Re-advice

User should select one of these options:-

‘Create Subsequent Advice’ selected

If the user selects ‘Create Subsequent Advice


(Single B/down)’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C020. (see Appendix D).
N.B. Ensure that C020-TRANS-TYPE is set to ‘V’
(Validation Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

David Willcocks 118 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
If no errors are returned from the first call to LY20,
call CICS transaction LY01 (see Appendix C.1) to
‘construct’ the skeleton subsequent transaction –
using COMMAREA C020. (see Appendix D). N.B.
Ensure that C020-TRANS-TYPE is set to ‘U’
(Update Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Claim Transaction Creation screen’ – rebuilding it
from scratch – as field protection will be
different and some field contents may be different.

‘Create Rate of Exchange Adjustment’ selected

If the user selects ‘Create Rate of Exchange


Adjustment’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C021. (see Appendix D).

On return, check the C021-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Rate of
Exchange Adjustment (see Section 4.29).

‘Create Contra Correction’ selected

If the user selects ‘Create Contra Correction’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C022. (see Appendix D).

On return, check the C022-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Contra
Correction (see Section 4.30).

‘Add Take Down Numbers’ selected

If the user selects ‘Add Take Down Numbers’, call


CICS transaction LY01 (see Appendix C.1) to

David Willcocks 119 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
perform any validation necessary – using
COMMAREA C023. (see Appendix D).

On return, check the C023-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘Settlement Summary’ (see Section
4.22).

‘CLASS for Lloyds’ Response selected

If the user selects ‘CLASS for Lloyds Response’,


call CICS transaction LY01 (see Appendix C.1) to
check that the claim transaction is a ‘CLASS for
Lloyds’ claim and that it requires authorisation –
using COMMAREA C083. (see Appendix D).

On return, check the C083-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘CLASS for Lloyds Response’
screen (this functiojn is not available in Phaase 1).

‘Set Diary Date’ selected

If the user selects the ‘Set Diary Date’ option, the


‘Set Diary Date’ pop-up window should be
displayed to them (see Section 4.34).

‘Create Bulk/CCS Correction’ selected

This is a special correction facility for use only by


authorised technicians. It allows correction of Bulk
Components, converted bulks and pre-
redenomination transactions. The difference
between this type of correction and Contra
Corrections is that the user has the ability to enter a
treasury rate.

If the user selects ‘Create Bulk/CCS Correction’,


call CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C090. (see Appendix D).

On return, check the C090-PROG-STATUS and


report any errors/warnings in the usual way.

David Willcocks 120 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the
Bulk/CCS Correction (see Section 4.36).

‘Set File Last Seen Date’ selected

This function allows the user to set the File Last


Seen Date to todays date and generate an advice to
the syndicates without creating a new claim
movement.

If this function is selected, display the ‘File Seen


Confirmation’ window (see Appendix S.2). If the
technician presses ‘YES’ in this window, call CICS
transaction LY01 (see Appendix C.1) to perform
any validation necessary and set up the necessary
logging records – using COMMAREA C096. (see
Appendix D).

On return, check the C096-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up confirmation


window should be displayed (see Appendix S.3.)
for information purposes only.

‘Reset Claim Transaction’ selected

This function will reset the status of a previously


released claim transaction to allow it to be updated
by the claim technician. This will not be allowed if
the claim transaction has been fully advised or if a
subsequent transaction exists within the claim.

(i) Call CICS transaction LY01 (see


Appendix C.1), passing the Commarea
C105 (see Appendix D). This will
validate that that the claim transaction
is eligible for update and, if so, reset the
status accordingly.

On return check the Program Status and


report any errors/warnings in the usual
way.

(ii) If no errors returned from LZ06, call


LY01 using Commarea C028 to obtain

David Willcocks 121 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
the data and field protection for the
current screen.

On return check the Program Status and


report any errors/warnings in the usual
way.

(iii) Rebuild the current screen using the


data returned in the C028 Commarea.

‘Create Re-advice’ selected

This function will allow the user to create a re-


advice of the most recent movement on the claim –
changing only the current narrative.

(i) call CICS transaction LY01 (see Appendix C.1)


to perform any validation necessary – using
COMMAREA C110. (see Appendix D).

On return, check the C110-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Create Re-Advice’ screen (see Section 4.39).

David Willcocks 122 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B. Navigation Options (Left of Screen) – COMMANDS

If user clicks on the ‘Option Button’ alongside any of the Options on the Navigation Bar, refer to
table returned by transaction LY12 (Build Navigation Bar) in the C012 Commarea. This table should
be stored after building the navigation bar on first entry to the screen for use when the user selects
one of the options on the Navigation Bar.

(i) If C028-SCREEN-MODE = ‘U’ (Update), call CICS transaction LY01 (see Appendix C.1)
to validate that any details entered on the screen are valid – using Commarea C029 (see
Appendix D).

On return, check the C029-PROG-STATUS and report any errors/warnings in the usual way.

(ii) If C028-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY29, Call CICS
transaction LY01 (see Appendix C.1) to update the database with the details entered on the
screen – using COMMAREA C030. (see Appendix D).

On return, check the C030-PROG-STATUS and report any errors/warnings in the usual way.

(iii) If C028-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY30, call CICS
transaction LY01 (see Appendix C.1) – using COMMAREA C046 (see Appendix D) – to
check whether currency/transaction validation needs to be performed. (N.B. the key values
returned from LY12 and stored in the C012-KEY table – for the line on the navigation bar
selected – should be passed in the C046 commarea).

On return, check the C046-PROG-STATUS and report any errors/warnings in the usual way.

(iv) If no errors returned from LY46 or C028-SCREEN-MODE = ‘E’ (Enquiry), call CICS
transaction LY01 (see Appendix C.1) to update the Session Record (VCLSESA1) –using
COMMAREA C010. (see Appendix D), (N.B. the key values returned from LY12 and
stored in the C012-KEY table – for the line on the navigation bar selected – should be
passed in the C010 commarea).

On return, check the C010-PROG-STATUS and report any errors/warnings in the usual
way.

(v) If no errors are returned from LY10, the user should be navigated to the screen indicated by
C012-SCREEN-ID for the line in the navigation bar selected. (see Appendix N)

David Willcocks 123 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C. Fields (Main Screen)

N.B. Alphanumeric fields must not contain any characters that are not supported by the EDI
message systems, as these may cause brokers and/or syndicates systems to fall over. Valid ASCII
Characters are as follows:-
space, 0-9, A-Z, a-z, ‘,’, ‘.’, ‘-‘, ‘(‘, ‘)’, ‘/’, ‘=’, ‘’’, ‘*’,’+’, ‘:’, ‘?’, ‘!’,’”’, ‘%’,’&’, ‘;’,’<’, ‘>’.

N.B.2. Pre-population of the fields with values returned from LIDS does not need to be handled
by the GUI, as these values will have been loaded onto the database by the ‘Claim Creation
Screen D/B Update’ module (LY27).

N.B.3 Field Protection will be handled by the ‘Field Attributes’ returned in the C028 Commarea.

N.B.4 If any errors are encountered, highlight any field(s) in error by setting the text colour to red.

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric


to claims that are created by internal technicians. It Only Field (17 Chars)
will always be present for internally created claims,
but not for claims created by the broker on the
‘CLASS for Lloyds’ system.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

UCR The Unique Claim Reference. This will always be Display Alphanumeric
present for claims created by the broker on the Only Field (17 Chars)
‘CLASS for Lloyds’ system, but may or may not be
present for internally created claims – depending on
whether the broker has quoted it on the claim file.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

TR Transaction Reference. Uniquely identifies a Display Alphanumeric


particular transaction within a claim. Only Field (17 chars)

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’
OSND1 Original Signing Number and date (for the first Display Alphanumeric
currency on the claim) Only Field (15 Chars)
OSND2 Original Signing Number and date (for the second Display Alphanumeric
currency on the claim) Only Field (15 Chars)

David Willcocks 124 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
OSND3 Original Signing Number and date (for the third Display Alphanumeric
currency on the claim) Only Field (15 Chars)
Peer The Peer Review Indicator. This field indicates that Field Alphanumeric
Review the claim is subject to peer review. (1 Char)

This field should be associated with a drop down


list with the following values:-

'N' - process only


'D' - delegated lead with peer review
'F' - delegated lead with processing for following
market
'Y' - Peer Review

Orig. Originating Broker. The broker who submitted this Mandatory Alphanumeric
Broker claim transaction. This may vary from one claim to Field (4 chars)
another.
Display-
This will be protected for claims entered by the Only Field
broker.

The Code entered must be a valid BKR-CODE on


the Broker Table (TGLBKRA). (All necessary data
from this table should be stored in the JAVA layer).

Original Broker. This is the broker who submitted


the first ttransaction on the current claim.

It is a display only field.

Curr. Current Broker. The broker who submitted this Mandatory Alphanumeric
Broker claim transaction. This may vary from one claim to Field (4 chars)
another.

This will be protected for claims entered by the


broker.

The Code entered must be a valid BKR-CODE on


the Broker Table (TGLBKRA). (All necessary data
from this table should be stored in the JAVA layer).

Risk Identifies the risk code applicable to the policy. Mandatory Alphanumeric
Code Field (2 chars)
Must be a valid Risk code on the Risk Code table
(name?). If the value entered on the screen is not
present on the table, display the error E186 (see
Appendix E) in the Error Window (see Appendix

David Willcocks 125 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B).

Must be appropriate to the market of the claim. For


certain types of business may be different from the
Risk Code associated with the policy section. (This
validation will be handled by CICS transaction).

Market This identifies the market in which this claim is Mandatory Alphanumeric
Code placed. Field (1 Char)

A drop down list is associated with this field, the


contents of which should be as follows:-

‘A’ = Aviation
‘M’ = Marine
‘N’ = Non-Marine
Year of The Year of Account. Mandatory Numeric
Account Field 9(4)
(YOA) This field will be brought across from LIDS and
protected.

Interest Description of Insurable Interest. Optional Alphanumeric


Field (70 chars)
This is a Free Text Field. It will be pre-populated
from the LIDS database, but may be overwritten.

However, if this claim transaction was entered by


the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made
on the SCM Advice screen (see Section 4.17)

Ccy (n) This is the Original (Estimate) Currency that applies Optional Alphanumeric
to the SI Limits and Excess Limits (See below). Field (3 chars)

This field will be pre-populated from the LIDS


database for claims against signed risks.

This must be a valid currency on the Currency


Table, TGLCURA. (All necessary data from this
table should be stored in the JAVA layer). Any other
more detailed validation will be carried out by the
appropriate CICS transaction.

David Willcocks 126 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
However, if this claim transaction was entered by
the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made
on the SCM Advice screen (see Section 4.17)

Limits This is the Sum Insured Limit (in the currency held Optional Numeric
(n) in CCY field – see above). Field Z(12)9.99

This field will be pre-populated from the LIDS


database for claims against signed risks, but can be
overwritten.

However, if this claim transaction was entered by


the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made
on the SCM Advice screen (see Section 4.17)

Format:- Z,ZZZ,ZZZ,ZZZ,ZZ9.99

Excess This is the Excess Limit (in the currency held in Optional Numeric
(n) CCY field – see above). Field Z(12)9.99

This field will be pre-populated from the LIDS


database for claims against signed risks, but can be
overwritten.

However, if this claim transaction was entered by


the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made
on the SCM Advice screen (see Section 4.17)

Format:- Z,ZZZ,ZZZ,ZZZ,ZZ9.99

Sum The first line of the Sum Insured Narrative. This Display Alphanumeric
Insured details the Sum Insured Limits that were held (as Only Field (50 Chars)
Narrativ text) on the COSS system. These will be protected
e1 and shown for information purposes only. The
individual fields (detailed above should be used for
all new movements on claims).

Order 1 Slip Order 1 (percentage) Optional Numeric


Field Z(2)9.9(7)
This field will be pre-populated from the LIDS
database for claims against signed risks, but can be
overwritten.

David Willcocks 127 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

However, if this claim transaction was entered by


the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made
on the SCM Advice screen (see Section 4.17)

This field must not be greater than 100% - If so,


display error E054 in the Error Screen (see
Appendix B).

Order 2 Slip Order 2 (percentage) Optional Numeric


Field Z(2)9.9(7)
This field will be pre-populated from the LIDS
database for claims against signed risks, but can be
overwritten.

However, if this claim transaction was entered by


the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made
on the SCM Advice screen (see Section 4.17)

This field must not be greater than 100% - if so


display error E055 in the Error Screen (see
Appendix B).

Perils / Any Perils or Conditions that apply to this Risk Optional Alphanumeric
Conditio Field (70 Chars)
ns This is a Free Text Field. It will be pre-populated
from the LIDS database, but may be overwritten.

However, if this claim transaction was entered by


the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made
on the SCM Advice screen (see Section 4.17)

Location Any Perils or Conditions that apply to this Risk Optional Alphanumeric
/ Voyage Field (70 Chars)
of Risk This is a Free Text Field. It will be pre-populated
from the LIDS database, but may be overwritten.

However, if this claim transaction was entered by


the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made

David Willcocks 128 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
on the SCM Advice screen (see Section 4.??)

Basis of This indicates the basis of the limit. I.e. the limit Optional Alphanumeric
Loss applies to either ‘any one accident’, ‘each and every Field (3 Chars)
loss’, any one vessel’, etc.

Valid values are held on the associated reference


table (name ?). If the value entered on the screen is
not present on the table, display the error E172 (see
Appendix E) in the Error Window (see Appendix
B).

Policy/Ce Policy/Certificate Period From Date. Optional Date


rt. Period Field (DD/MM/CCYY)

From This field will be pre-populated from the LIDS


database, but may be overwritten.

However, if this claim transaction was entered by


the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made
on the SCM Advice screen (see Section 4.17)

Either this field or the ‘Policy/Cert Period Qualifier’


must be entered if the Cover/Lineslip Date (or
Qualifier) have been completed. If lineslip period
entered, policy start date must not be outside range
of lineslip. (Handled by CICS transaction)

When entered, must be a valid date. If not, display


the error E056 (see Appendix E) in the Error
Window (see Appendix B).

Policy/Ce Policy/Certificate Period To Date. Optional Date


rt. Period Field (DD/MM/CCYY)

To This field will be pre-populated from the LIDS


database, but may be overwritten.

However, if this claim transaction was entered by


the broker on the ‘CLASS for Lloyds’ system, this
field will be protected. If any changes are required
(for advising purposes) these will have to be made
on the SCM Advice screen (see Section 4.17)

When entered, must be a valid date. If not, display


the error E057 (see Appendix E) in the Error

David Willcocks 129 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Window (see Appendix B).

This field must be completed, if the ‘Policy/Cert


Period From Date’ has been entered. If it is not,
display the error E101 (see Appendix E) in the
Error Window (see Appendix B).

This date must not be entered without the


Policy/Cert Period From Date. If it is, display the
error E058 in the Error Screen (See Appendix B).

This field must be greater than the Policy/Cert


Period From Date. If it is not, display the error
E105 (see Appendix E) in the Error Window (see
Appendix B).

Policy/Ce A Qualifier used to explain the absence of a policy Optional Alphanumeric


rt. period. Field (1 Char)
Qualifier
This will be pre-populated with the value entered by
the technician on the Policy/Risk Details screen (or
pre-populated on the Policy/Risk Details screen, if
entered by the broker on ‘CLASS for Lloyds’)

Must be absent when policy/cert period dates


present – if not, display the error E102 (see
Appendix E) in the Error Window (see Appendix
B).

Must be present when policy/cert period dates


absent – if not, display the error E103 (see
Appendix E) in the Error Window (see Appendix
B).

Valid values are:-


(i) 'T' = To Be Advised
(ii) 'V' = Various
(iii) 'N' = Not Applicable

If the value entered is not one of the above, display


the error E104 (see Appendix E) in the Error
Window (see Appendix B).

Policy Narrative that provides additional information about Optional Alphanumeric


Period the Policy Period or a narrative description of the Field (40 Chars)
policy period where the From and To Dates have

David Willcocks 130 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Narrativ not been supplied.
e
This is a Free Text Field.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected.

Cover/Li Date of inception of a cover or lineslip. Optional Date


neslip Field (DD/MM/CCYY)

From When entered, must be a valid date. If not, display


the error E165 (see Appendix E) in the Error
Window (see Appendix B).

Cover/Li End date of a cover or Lineslip. Optional Date


neslip To Field (DD/MM/CCYY)
When entered, must be a valid date. If not, display
the error E166 (see Appendix E) in the Error
Window (see Appendix B).

This field must be completed, if the ‘Cover/Lineslip


Period From Date’ has been entered. If it is not,
display the error E169 (see Appendix E) in the
Error Window (see Appendix B).

This date must not be entered without the


‘Cover/Lineslip Period From Date’. If it is, display
the error E168 in the Error Screen (See Appendix
B).

This field must be greater than the ‘Cover/Lineslip


Period From Date’. If it is not, display the error
E167 (see Appendix E) in the Error Window (see
Appendix B).

Cover/Li Describes basis of cover or explains absence of Optional Alphanumeric


neslip cover dates. Field (1 Char)
Qualifier
One of the following values must be entered when
corresponding from/to date fields completed:-

C = claims made,
L = losses occurring during,
P = portfolio transfers,
R = risks attaching,

If Cover/Lineslip from and to dates have been


entered, and the qualifier has been left blank,

David Willcocks 131 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
display the error E170 (see Appendix E) in the
Error Window (see Appendix B).

If Cover/Lineslip from and to dates have been


entered and the qualifier entered is not one of the
four listed above, display the error E171 (see
Appendix E) in the Error Window (see Appendix
B).

If the Cover/Lineslip Period From and To dates


have been left blank, one of the following can be
entered:-

T = to be advised,
V = various dates.
If the Cover/Lineslip from and to dates have been
left blank and a value has been entered in the
associated qualifier field that is not one of the two
above, display the error E171 (see Appendix E) in
the Error Window (see Appendix B).

War Indicates whether the claim includes elements of Tick-Box N/a


Indicator War losses.

This field will be pre-populated as detailed below:-


(note this is handled by the appropriate CICS
transactions).

(i) For transactions loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker, and protected.
(ii) For initial advices loaded internally, it will not
be ticked – but will be unprotected.
(iii) For internally created subsequent advices, it
will be pre-populated with the value entered on the
previous transaction – but unprotected.

Slip Type Indicates the type of Business for which the Mandatory Alphanumeric
original policy was written. Field (1 Chars)

This will be pre-populated with the value entered on


LIDS at the time that the claim transaction was
created. The technician will be able to change the
value by selecting from the drop down list
associated with this field.

Must be present – if not, display the error E713 (see


Appendix E) in the Error Window (see Appendix

David Willcocks 132 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B).

Valid values are:-

‘ ’ – value not present


‘M’ - MAIN BUSINESS
‘C’ - COVER
‘E’ - EXCESS OF LOSS
‘X’ - FILE CONVERTED
‘B’ - BINDING AUTHORITY
‘F’ - FACILITY
‘T’ - TREATY
‘Y’ - DUMMY SLIP
‘L’ – LINESLIP

Unique This is the unique market reference that applies to Optional Alphanumeric
Market the Policy. Field (17 Chars)
Referenc
e (UMR) This field may be entered by the broker on the
‘CLASS for Lloyds’ system, in which case it will be
protected.

It will be pre-populated from the LIDS database,


but may be changed by the technician.
D. Commands – (Main Screen)
Save This key allows the user to save the details they Command
have entered on the screen without being navigated
onto a different screen. Note:- this button should be
disabled if the screen is being viewed in ‘Enquiry’
mode (i.e. C028-SCREEN-MODE = ‘E’)

(i) Call CICS transaction LY01 (see Appendix


C.1) to validate that any details entered on
the screen are valid – using Commarea
C029 (see Appendix D).

On return, check the C029-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) If no errors returned from LY29, Call CICS


transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C030.
(see Appendix D).

David Willcocks 133 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

On return, check the C030-PROG-STATUS


and report any errors/warnings in the usual
way.

Continue (i) If C028-SCREEN-MODE = ‘U’(Update), Command


call CICS transaction LY01 (see Appendix
C.1) to validate that any details entered on
the screen are valid – using Commarea
C029 (see Appendix D).

On return, check the C029-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) If C028-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY29, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C030. (see Appendix D).

On return, check the C030-PROG-STATUS


and report any errors/warnings in the usual
way.

(iii) If no errors returned from LY30 or C028-


SCREEN-MODE = ‘E’(Enquiry), call the
CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(iv) Navigate the user to whichever program is


identified in C011-NEXT-PROGRAM (see
Appendix N)

Cancel When the technician presses the ‘Cancel’ button, Command


any changes made since the last ‘Save’ will be
removed. The technician will remain in the
‘Policy/Risk Details Screen’ screen. Therefore:-

(i) Call the CICS transaction LY01 (see

David Willcocks 134 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Appendix C.1) – using COMMAREA C028
(see Appendix D) . This transaction will
return the data that should appear on this
screen.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(ii) Rebuild the screen, based on the data


returned in the C028 Commarea.

EXIT This will return the user to whichever screen they Command
initiated the claim from.

(i) Call CICS transaction LY01 (see Appendix C.1)


to check the status of the current transaction –
using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B). If status is zero,
continue at (iv)

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before being navigated to the next
screen. Display the ‘Claim Transaction Options’
pop-up window detailed in Section 4.10 and
perform processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user should be
left in the current screen.

(iv) If the user did not press ‘Cancel’ or zero


Program Status returned from LY16,
Call the CICS transaction LY01 (see Appendix
C.1) – using COMMAREA C011 (see
Appendix D). This will invoke the ‘Navigation’
program, which decides on the next program the
user should be navigated to. (Note: the
C011-EXIT-IND should be set to ‘Y’)

On return, check the Program Status in the Usual


way, reporting errors if they exist in The Error
Screen (see Appendix B)

David Willcocks 135 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(v) If no errors returned from LY11, navigate the


user to the program indicated by
C011-NEXT-PROGRAM (see Appendix N).
If C011-NEXT-PROGRAM is set to 'NONE',
the current window should be closed.

David Willcocks 136 May 2002


Xchanging Ins-sure Services Ltd
4.13. Market Details Screen

4.13.1. Screen Layout

Below is the Market Details Screen under normal circumstances.

The screen image (overleaf) shows an example of how the


‘Authorisation Details’ appear on the Market Details Screen for claims
that have been created by the broker and have undergone the ‘CLASS
for Lloyds’ agreement process. When the user ‘clicks’ on the Syndicate
Line Number, which will be underlined only for ‘CLASS for Lloyds’
authorisers, the market line will ‘expand’ to reveal details of the
syndicate’s agreement role, the response made and details of the user
who made it.

David Willcocks 137 May 2002


Xchanging Ins-sure Services Ltd
4.13.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY10 Update Session Record
LY11 Navigation Program
LY12 Build Screen Navigation Bar
LY14 Add OSND(s) to Aggregate Group
LY15 Create Non-Aggregate Group
LY16 Check Transaction Status
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY31 Build Market Details Screen
LY32 Market Details Screen Validation
LY33 Market Details Screen D/B Update
David Willcocks 138 May 2002
Xchanging Ins-sure Services Ltd
Tran Program Description
s. Name
Id.
LY46 Check whether Currency/Transaction
Validn. reqd
LY68 Create History Session Record
LY71 Set up Group Session Record
LY83 ‘CLASS for Lloyds’ Response – Initial
Validation
LY88 Build Narrative Details Screen
LY90 Bulk/CCS Correction Initial Validation
LY96 Set File Last Seen Date
LZ06 Reset Claim Transaction
LZ11 Create Re-Advice – Initial Validation

4.13.3. Field/Command Derivation

The fields and the navigation bar on this screen will be


derived as follows:-

Field Type Source


A. Navigation Bar
Navigation Bar Comman call the CICS transaction LY01 (see Appendix
d(s) C.1) – using COMMAREA C012 (see Appendix
D) . This will determine what should appear on
the ‘Screen Navigation Bar’ at the left hand side
of the screen.

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

See Appendix F for details of how to process the


information returned from this CICS transaction.

B. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C031 (see
Appendix D) . This transaction will return the data that should appear on this screen.

On return, check the Program Status in the usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

XCR Field C031-XCR


(This field should be protected)

David Willcocks 139 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
UCR Field C031-UCR
(This field should be protected)
TR Field C031-TR
(This field should be protected)
OSND1 Field C031-ORIG-REF-1
(This field should be protected)

OSND2 Field C031-ORIG-REF-2


(This field should be protected)
OSND3 Field C031-ORIG-REF-3
(This field should be protected)
Current Bkr Field C031-ORIG-BKR
Orig. Broker (This field should be protected)
Signed Tick-Box C031-SIGNED-IND
(This field should be protected)
Peer Review Field C031-PEER-REV-IND
(This field should be protected)
No. of Field C031-NO-SYNDICATES
Syndicates (If C031-NO-SYNDS-ATTR = ‘P’,
this field should be protected)
Total Line Field C031-TOTAL-LINE
(If C031-TOTAL-LINE-ATTR = ‘P’,
this field should be protected)
Market Source Field C031-MKT-SOURCE
(If C031-MKT-SRCE-ATTR = ‘P’, this
field should be protected)
Read through all occurences in the C031-MARKET-DETAILS table. Display the
details in tabular format on the screen.

Note:- If no market details are returned (i.e. C031-NO-SYNDICATES = Zero), set


up the first occurrence as follows (N.B. All Fields, except ‘Line No’, ‘Synd. Opt-
Out Status’ and ‘Synd. Opt-Out Date’ should be unprotected) :-
Line No. (1) = 1
Syndicate No (1) = spaces
Syndicate % (1) = zeroes (blank when zero)
Syndicate Reference (1) = spaces
Synd. Opt-Out Status = spaces
Synd. Opt-Out Date = spaces
Bureau Leader tick-box ‘unticked’
Set C031-SYND-NO-ATTR (1) to ‘U’
Set C031-SYND-LINE-ATTR (1) = ‘U’
Set C031-SYND-REF-ATTR (1) = ‘U’

Line No. (n) Field Sequential Number (i.e. equal to n)

David Willcocks 140 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
(This field should be protected)

N.B. This field should be underlined


and it should be possible for the
user to ‘click’ on it to reveal the
‘CLASS for Lloyds’ response details
if C031-AGREEMENT-ROLE(n) >
spaces
Syndicate No. Field C031-SYNDICATE-NO (n)
(n) (If C031-SYND-NO-ATTR (n) = ‘P’
and C031-MKT-CHANGE-ATTR not
= ‘F’ , this field should be
protected)
Syndicate % (n) Field C031-SYNDICATE-LINE (n)
(If C031-SYND-LINE-ATTR (n) = ‘P’
and C031-MKT-CHANGE-ATTR not
= ‘F’, this field should be protected)
Syndicate Ref. Field C031-SYNDICATE-REF (n)
(n) (If C031-SYND-REF-ATTR (n) = ‘P’
and C031-MKT-CHANGE-ATTR not
= ‘F’, this field should be protected)
Synd. Opt-Out Field C031-OPT-OUT-STATUS (n)
Status (n) (this field should be protected)
Synd. Opt-Out Field C031-OPT-OUT-EFF-DATE (n)
Date (n) (This field should be protected)
Bureau Leader Tick-Box If C031-AGREEMENT-ROLE (n) =
(n) ‘L’,
Set to ‘TRUE’.
(If C031-MKT-CHANGE-ATTR = ‘P’,
this field should be protected)

The remaining fields are only shown when the user ‘expands’ the line by ‘clicking’
on the Syndicate Line Number (above).
Agreement Field C031-AGREEMENT-ROLE
Role (n) (This field should be protected)
Response Code Field C031-SYND-RESP-CODE
(n) (This field should be protected)
User Name (n) Field C031-USER-NAME-AUTH
(This field should be protected)
Response Date Field Date element of C031-RESP-
(n) TIMESTAMP
(Response Timestamp is in the
format:-
‘CCYY-MM-DD-HH.MM.SS.TTTTTT’.

David Willcocks 141 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Therefore date is held in first 10
characters)
(This field should be protected)
Response Time Field Time element of C031-RESP-
(n) TIMESTAMP
(Response Timestamp is in the
format:-
‘CCYY-MM-DD-HH.MM.SS.TTTTTT’.
Therefore date is held in characters
12-16)
(This field should be protected)
C. Commands:-

The derivation for the commands is also returned in the C031


Commarea.
Delete Line (n) Tick-Box If C031-MKT-CHANGE-ATTR = ‘P’,
the Delete Tick-Box should be
protected (or preferably not shown
at all).
Delete Selected Comman If C031-MKT-CHANGE-ATTR = ‘P’,
Lines d this button should be protected (or
preferably not shown at all)
Insert Line Comman If C031-MKT-CHANGE-ATTR = ‘P’,
d this command should be protected
(or preferably not shown at all).

4.13.4. Process Description

This screen is the Market Details Screen.

When creating an ‘unclosed’ advice (i.e. the first advice


on a claim against an unsigned risk) the user will be
able to enter the market details in the screen from
scratch and select the bureau leader.

When creating an initial advice against a signed risk,


the details on this screen will be pre-filled with the
Market obtained from LIDS for the Original Signing
Number(s) and Date(s) entered on the ‘Claim Creation’
screen. If more than one market is returned from LIDS,
the user will have selected the one they wish to apply to
this claim in the earlier ‘Market Selection’ screen. The

David Willcocks 142 May 2002


Xchanging Ins-sure Services Ltd
market may be changed by the user. Lines may be
removed from or inserted into the market at this stage.
The Syndicate References can also be updated. Again,
the bureau leader should be selected.

On subsequent advice’s, the contents of this screen will


be pre-filled from the details on the previous
transaction. Hence, if the details held on LIDS are
overwritten on the first transaction within a claim, they
will not need to be overwritten on each subsequent
transaction. On subsequent advices the market (or the
bureau leader) cannot be changed, although Syndicate
References may be updated if required.

If the claim was entered by the broker, then any broker-


supplied details on this screen will be protected,
regardless of whether this is the first advice on the
claim or not.

If this screen is being viewed in ‘Enquiry’ mode, then


all fields will be protected, include ‘delete’ and ‘insert’
buttons.

An additional feature of this screen will allow the user to view the
authorisation details for claims that have undergone the ‘CLASS for
Lloyds’ agreement process. If the user clicks on the Syndicate Line
Number for one of the ‘CLASS for Lloyds’ agreement parties, details
of their agreement role and the response made should be shown,
together with the details of who made the response and when. These
should be shown in an expanded area -similar to that illustrated in the
second ‘mock-up’ screen layout.

Fig 4.13.4.1. Field/Command Processing for ‘Market Details’


Screen

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D) to log-
off the system and delete the Session Record.

On return from CICS, check the C004-PROG-


STATUS field:-

(i) If set to 9, display any errors returned in the

David Willcocks 143 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
commarea in the Error Screen (see
Appendix B)

(ii) If set to zero, close all windows.

Create New (i) Call CICS transaction LY01 (see Appendix Command
Claim C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

David Willcocks 144 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(v) If the user did not press Cancel in the
‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Create Claim
Screen’ (see Section 4.4)

Find Claim (i) Call CICS transaction LY01 (see Appendix Command
C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

David Willcocks 145 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Find Claim’ Screen
(see Section 4.5)

Account Link to Account Enquiry (method needs to be Command


Enquiry identified)

Repository Link to Repository (method needs to be identified) Command

Data Link to Data Warehouse (method needs to be Command


Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry
Add to Aggregate Group
Create Non-Aggregate Group
Add to Non-Aggregate Group

User should select one of these options.

Note:- ‘Clicking’ on the ‘Maintain Group’,


‘Group Enquiry’ or ‘Add to Non-Aggregate
Group’ options should open up a new ‘window’ –
associated with its own entry on the Session Table
(i.e. a new Session No.). Once the user has finished
Group processing, the window should be closed and
the Session Record deleted.

(i) If either the ‘Maintain Group’, ‘Group


Enquiry’ or ‘Add to Non-Aggregate
Group’ options were selected, call CICS
transaction LY01 (see Appendix C.1) to set
up a new Session Record for the Grouping
session - using Commarea C071 (see
Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’

David Willcocks 146 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iv) On selection of ‘Add to Aggregate


Group’, call CICS transaction LY01
(see Appendix C.1) to add the OSND’s
associated with this claim to an Aggregate
group – using COMMAREA C014 (see
Appendix D).

On return, check the C014-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the OSND’s
have been added to. (see Appendix G)

(v) On selection of ‘Create Non-Aggregate


Group’, call CICS transaction LY01 (see
Appendix C.1) to add the current claim
to a Non-Aggregate group – using
COMMAREA C015 (see Appendix D).

On return, check the C015-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the claim has
been added to. (see Appendix G)

(vi) On selection of the ‘Add to Non-


Aggregate Group’ option, open new
window, navigating user to ‘Group Enquiry’
screen (see Section 4.28) (a new SESSION-

David Willcocks 147 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
NO is associated with this window – this
will have been returned by previous
transaction, LY71)

Notes When user clicks on the ‘NOTES’ option at the top Command
of the screen, the following options should be
available on a sub-menu:-
Security Notes
Claim Notes
Loss Details
Policy Details
EURO Conversion Narrative (FME)
Broker Additional Details
Broker Aggregate Details
Slip Lead Comments
Lead Comments
Lead Additional Details

User should select one of these options.

(i) Whichever option is selected, call CICS


transaction LY01 (see Appendix C.1) to
check whether the selected narrative is
present or not, and return any narrative
present, using COMMAREA C088 (see
Appendix D). N.B. Set C088-FIRST-
CALL to ‘Y’. This call will return lines
1 to 300.

On return, check the C088-PROG-STATUS


and report any errors in the usual way.

(ii) If no errors returned from the first


LY88 call and C088-MORE-LINES is
set to ‘Y’, call CICS transaction LY01
(see Appendix C.1) to check whether
the selected narrative is present or not,
and return any narrative present, using
COMMAREA C088 (see Appendix D).
N.B. Set C088-FIRST-CALL to ‘N’.
This call will return lines 301 to 600.

On return, check the C088-PROG-STATUS


and report any errors in the usual way.

(iii) If no errors found in LY88, the user


should be navigated to the Narrative

David Willcocks 148 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Screen (see Section 4.35)

Note:- the Narrative screen should be opened up as


a new window, overlaying whichever screen the
user is currently processing. Once the user has
finished enquiring on or updating the narrative, the
window should be closed and the user will be
returned to whichever screen they were processing
originally.

History When the user ‘clicks’ on this option they should be Command
navigated to the ‘Transaction History’ screen.

Note:- ‘Clicking’ on the ‘History’ option should


open up a new ‘window’ – associated with its own
entry on the Session Table (i.e. a new Session No.).
Once the user has finished browsing through
history, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
History session - using Commarea C068
(see Appendix D).

On return, check the C068-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) Open new window, navigating user to


‘Transaction History’ screen (see Section
4.25) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY68)

Functions When user clicks on the ‘FUNCTIONS’ option at Command


the top of the screen, the following options should
be available on a sub-menu:-
1.Create Subsequent Advice
2.Create Rate of Exchange Adjustment
3.Create Contra Correction
4.Add Take Down Numbers
5. ‘CLASS for Lloyds’ Response
6. Set Diary Date
7. Create Bulk/CCS Correction
8. Set ‘File Last Seen’ Date
9. Reset Claim Transaction
10. Create Re-advice

David Willcocks 149 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

User should select one of these options:-

‘Create Subsequent Advice’ selected

If the user selects ‘Create Subsequent Advice


(Single B/down)’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C020. (see Appendix D).
N.B. Ensure that C020-TRANS-TYPE is set to ‘V’
(Validation Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned from the first call to LY20,


call CICS transaction LY01 (see Appendix C.1) to
‘construct’ the skeleton subsequent transaction –
using COMMAREA C020. (see Appendix D). N.B.
Ensure that C020-TRANS-TYPE is set to ‘U’
(Update Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Claim Transaction Creation screen’ – rebuilding it
from scratch – as field protection will be
different and some field contents may be different.

‘Create Rate of Exchange Adjustment’ selected

If the user selects ‘Create Rate of Exchange


Adjustment’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C021. (see Appendix D).

On return, check the C021-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Rate of
Exchange Adjustment (see Section 4.29).

‘Create Contra Correction’ selected

David Willcocks 150 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
If the user selects ‘Create Contra Correction’, call
CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C022. (see Appendix D).

On return, check the C022-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Contra
Correction (see Section 4.30).

‘Add Take Down Numbers’ selected

If the user selects ‘Add Take Down Numbers’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C023. (see Appendix D).

On return, check the C023-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘Settlement Summary’ (see Section
4.22).

‘CLASS for Lloyds’ Response selected

If the user selects ‘CLASS for Lloyds Response’,


call CICS transaction LY01 (see Appendix C.1) to
check that the claim transaction is a ‘CLASS for
Lloyds’ claim and that it requires authorisation –
using COMMAREA C083. (see Appendix D).

On return, check the C083-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘CLASS for Lloyds Response’
screen (This function is not available in Phase 1).

‘Set Diary Date’ selected

If the user selects the ‘Set Diary Date’ option, the


‘Set Diary Date’ pop-up window should be
displayed to them (see Section 4.34).

‘Create Bulk/CCS Correction’ selected

David Willcocks 151 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

This is a special correction facility for use only by


authorised technicians. It allows correction of Bulk
Components, converted bulks and pre-
redenomination transactions. The difference
between this type of correction and Contra
Corrections is that the user has the ability to enter a
treasury rate.

If the user selects ‘Create Bulk/CCS Correction’,


call CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C090. (see Appendix D).

On return, check the C090-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the
Bulk/CCS Correction (see Section 4.36).

‘Set File Last Seen Date’ selected

This function allows the user to set the File Last


Seen Date to todays date and generate an advice to
the syndicates without creating a new claim
movement.

If this function is selected, display the ‘File Seen


Confirmation’ window (see Appendix S.2). If the
technician presses ‘YES’ in this window, call CICS
transaction LY01 (see Appendix C.1) to perform
any validation necessary and set up the necessary
logging records – using COMMAREA C096. (see
Appendix D).

On return, check the C096-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up confirmation


window should be displayed (see Appendix S.3.)
for information purposes only.

‘Reset Claim Transaction’ selected

David Willcocks 152 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
This function will reset the status of a previously
released claim transaction to allow it to be updated
by the claim technician. This will not be allowed if
the claim transaction has been fully advised or if a
subsequent transaction exists within the claim.

(i) Call CICS transaction LY01 (see


Appendix C.1), passing the Commarea
C105 (see Appendix D). This will
validate that that the claim transaction
is eligible for update and, if so, reset the
status accordingly.

On return check the Program Status and


report any errors/warnings in the usual
way.

(ii) If no errors returned from LZ06, call


LY01 using Commarea C031 to obtain
the data and field protection for the
current screen.

On return check the Program Status and


report any errors/warnings in the usual
way.

(iii) Rebuild the current screen using the


data returned in the C031 Commarea.

‘Create Re-advice’ selected

This function will allow the user to create a re-


advice of the most recent movement on the claim –
changing only the current narrative.

(i) call CICS transaction LY01 (see Appendix C.1)


to perform any validation necessary – using
COMMAREA C110. (see Appendix D).

On return, check the C110-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Create Re-Advice’ screen (see Section 4.39).

David Willcocks 153 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B. Navigation Options (Left of Screen) - COMMANDS

If user clicks on the ‘Option Button’ alongside any of the Options on the Navigation Bar, refer to
table returned by transaction LY12 (Build Navigation Bar) in the C012 Commarea. This table should
be stored after building the navigation bar on first entry to the screen for use when the user selects
one of the options on the Navigation Bar.

(i) If C031-SCREEN-MODE = ‘U’ (Update), call CICS transaction LY01 (see Appendix C.1)
to validate that any details entered on the screen are valid – using Commarea C032 (see
Appendix D).

On return, check the C032-PROG-STATUS and report any errors/warnings in the usual way.

(ii) If C031-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY32, Call CICS
transaction LY01 (see Appendix C.1) to update the database with the details entered on the
screen – using COMMAREA C033. (see Appendix D).

On return, check the C033-PROG-STATUS and report any errors/warnings in the usual way.

(iii) If C031-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY33, call CICS
transaction LY01 (see Appendix C.1) – using COMMAREA C046 (see Appendix D) – to
check whether currency/transaction validation needs to be performed. (N.B. the key values
returned from LY12 and stored in the C012-KEY table – for the line on the navigation bar
selected - should be passed in the C046 commarea).

On return, check the C046-PROG-STATUS and report any errors/warnings in the usual way.

(iv) If no errors returned from LY46 or C031-SCREEN-MODE = ‘E’ (Enquiry), Call CICS
transaction LY01 (see Appendix C.1) to update the Session Record (VCLSESA1) –using
COMMAREA C010. (see Appendix D), (N.B. the key values returned from LY12 and
stored in the C012-KEY table – for the line on the navigation bar selected - should be passed
in the C010 commarea)

On return, check the C010-PROG-STATUS and report any errors/warnings in the usual
way.

(v) If no errors are returned from LY10, the user should be navigated to the screen indicated by
C012-SCREEN-ID for the line in the navigation bar selected. (see Appendix N)

David Willcocks 154 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C. Fields (Main Screen)

N.B. Alphanumeric fields must not contain any characters that are not supported by the EDI
message systems, as these may cause brokers and/or syndicates systems to fall over. Valid ASCII
Characters are as follows:-
space, 0-9, A-Z, a-z, ',', '.', '-', '(', ')', '/', '=', ''', '*','+', ':', '?', '!','"', '%','&', ';','<', '>'.

N.B.2. Pre-population of the fields with values returned from LIDS does not need to be handled
by the GUI, as these values will have been loaded onto the database by the ‘Claim Creation
Screen D/B Update’ module (LY27).

N.B.3 Field Protection will be handled by the ‘Field Attributes’ returned in the C031 Commarea.

N.B.4 If any errors are encountered, highlight any field(s) in error by setting the text colour to red.

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric


to claims that are created by internal technicians. It Only Field (17 Chars)
will always be present for internally created claims,
but not for claims created by the broker on the
‘CLASS for Lloyds’ system.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

UCR The Unique Claim Reference. This will always be Display Alphanumeric
present for claims created by the broker on the Only Field (17 Chars)
‘CLASS for Lloyds’ system, but may or may not be
present for internally created claims – depending on
whether the broker has quoted it on the claim file.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

TR Transaction Reference. Uniquely identifies a Display Alphanumeric


particular transaction within a claim. Only Field (17 chars)

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’
OSND1 Original Signing Number and date (for the first Display Alphanumeric
currency on the claim) Only Field (15 Chars)
OSND2 Original Signing Number and date (for the second Display Alphanumeric
currency on the claim) Only Field (15 Chasr)

David Willcocks 155 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
OSND3 Original Signing Number and date (for the third Display Alphanumeric
currency on the claim) Only Field (15 Chars)
Current The Originating Current Broker (i.e. the broker Display Alphanumeric
Bkr who submitted this claim transaction). Only Field (4 chars)
Orig.
Broker
Signed Signed Indicator. This indicates whether or not the Display
(Y/N) risk against which this claim is being made has been Only
signed or not. Tick-Box
Peer This indicates whether the claim is subject to peer Display Alphanumeric
Review review. Only (1 Char)
Field
No. of This is the total number of lines on the market. It is Display Numeric
Syndicat a display only field. Only Field Z(2)9.
es
If the user is entering the market for an ‘unclosed
advice’ (i.e. a claim against an unsigned policy),
this will need to be incremented each time the user
inserts a new line on the market.

For initial (non-broker entered) advices, where the


market has been prefilled from the LIDS database,
we will need to reduce this number by 1 each time
the user deletes a line from the market.

For subsequent advices, the market cannot be


changed. Therefore the value of this field will be
fixed.

Total This is the total of all the Syndicate Percentages on Display Numeric
Line the market. Only Field Z(2)9.9(7)

If the user is entering the market for an ‘unclosed


advice’ (i.e. a claim against an unsigned policy) or
amending the market for a claim against a signed
risk, this will need to be maintained by totalling
each of the syndicate percentages entered by the
user (up to 170), excluding any flagged for deletion.
If, at any stage, the Total Line exceeds 100%,
display the error E060 (see Appendix E) in the
Error Window (see Appendix B).

For initial (non-broker entered) advices, where the


market has been prefilled from the LIDS database,
we will need to subtract the syndicate percentage

David Willcocks 156 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
for any lines deleted by the user and add that for
any lines inserted.

For subsequent advices, the market cannot be


changed. Therefore the value of this field will be
fixed.

Market The Market Source indicates whether the market Display Alphanumeric
Source was keyed or derived from LIDS. Only Field (1 Char)
Line No. This is a sequential line number assigned to each Display Numeric
(n) line on the market. Only Field (max 150)

It will need to be incremented by one for each line


inserted on an ‘unclosed’ advice (i.e. the first advice
of a claim against an unsigned risk).

For initial (non-broker entered) advices, where the


market has been prefilled from the LIDS database,
we will need to renumber lines whenever the user
deletes a line from the market.

For subsequent advices, the market cannot be


changed. Therefore the value of this field will be
fixed.

For agreement parties on ‘CLASS for Lloyds’ claim


transactions (identified by C031-AGREEMENT-
ROLE > spaces), this field will be underlined (and
probably a different colour). Clicking on it will
expand the line revealing the authorisation details.

Syndicat The Syndicate Number identifies a particular Optional Alphanumeric


e No. (n) syndicate in the Lloyds market. Field (4 chars)

When enterable, it should be validated against the


Company/Syndicate Code Table (TGLCOYA). The
Syndicate Number must be present on the table (in
the TGLCOYA-COY-CODE field). This table
should be held in the JAVA layer.

When the user inserts a line, this field must be


entered.
Syndicat The Syndicate Line. This is a percentage and should Optional Numeric
e % (n) be displayed as such. Field Z(2).9(7)

When entered (for initial advices on claims against


unsigned risks), it must be between 0 and 100%. If

David Willcocks 157 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
not, display the error E061 (see Appendix E) in the
Error Window (see Appendix B).

If the user inserts a line onto the market, this field


must be entered.

Syndicat The Syndicate Reference. This is the syndicates Optional Alphanumeric


e Ref. (n) claim reference. Field (15 chars)

When processing an unadvised transaction, it is


possible to update this field on all lines on the
market, regardless of whether the current
transaction is an initial advice or not.

If the user inserts a line onto the market, this field


must be entered.
Synd. This field indicates whether the syndicate has opted Display Alphanumeric
Opt-Out out of settlement for one or more of the OSND’s on Only Field (7 Chars)
Status this claim.
(n)
This field will always be protected and is shown for
information only.

Synd. This field shows the exact date that the syndicate Display Alphanumeric
Opt-Out withdrew from settlement on the policy to which Only Field (8 Chars)
Date (n) this claim attaches.

It is shown in DD/MM/YY format


Bureau This is a ‘tick-box’ that indicates which syndicate Tick-Box N/a
Leader on the market is acting as leader on behalf of the
(n) Lloyds market.

For non-broker entered initial advices the values of


C031-MKT-CHANGE-ATTR will indicate that all
the ‘Bureau Leader’ tick-boxes should be
unprotected. If this is the case, the user must select
one syndicate (and one syndicate only) to act as
leader.

On subsequent advices, all ‘tick-boxes’ will be


protected.
Agreeme This is the agreement role (i.e. Lead, Follower, etc.) Display Alphanumeric
nt Role of all parties involved in the ‘CLASS for Lloyds’ Only Field (1 Char)
(n) agreement process.

Respons This is the response made by a particular ‘CLASS Dis[play Alphanumeric


for Lloyds’ agreement party (i.e. AUT, QUE, etc.) Only Field (3 chars)

David Willcocks 158 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
e Code
(n)
User This is the name of the system user who made the Display Alphanumeric
Name (n) response on the ‘CLASS for Lloyds’ system. Only Field (30 chars)

Respons The date that the agreement party made their Display Date
e Date ‘CLASS for Lloyds’ response. Only Field (DD/MM/CCYY)

(n)
Respons The time that the agreement party made their Display Time
e Time ‘CLASS for Lloyds’ response. Only Field (HH:MM)
(n)

D. Commands - (Main Screen)


Insert When the technician presses this button, a row of Command
blank unprotected fields should be added to the
bottom of the market, allowing the user to enter
details as required.

i.e. Line No. (1) = Line No. for prev. line + 1


Sysndicate No (1) = spaces
Syndicate % (n) = zeroes (blank when zero)
Syndicate Reference (1) = spaces
Bureau Leader tick-box ‘unticked’
Set C031-SYND-NO-ATTR (1) to ‘U’
Set C031-SYND-LINE-ATTR (1) = ‘U’
Set C031-SYND-REF-ATTR (1) = ‘U’

i.e.. All fields should be unprotected, except


Line No.

Note:- Insertion is not allowed unless all fields on


the previous line on the market have been
completed. If either the Syndicate Number,
Syndicate Percentage or Syndicate Reference have
not been completed, display the error E173 (see
Appendix E) in the Error Window (see Appendix
B).

Delete This key will display an ‘Are you sure ?’ window to


Selected the user. Assuming they are happy with the
Lines selections made, it will validate other details on the
screen, update the database and rebuild the screen
with the selected lines removed.

(i) If no lines have been selected for deletion,

David Willcocks 159 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
display the error E181 (see Appendix E)
in the Error Window (see Appendix B).

(ii) Display the ‘Are you sure ?’ window (see


Appendix P). If the user presses ‘NO’,
return them to the screen without
performing the following processing.
Otherwise, if the user selects ‘YES’,
continue with the following processing.

(iii) If user pressed ‘YES’ in the confirmation


window, call CICS transaction LY01 (see
Appendix C.1) to validate that any details
entered on the screen are valid – using
Commarea C032 (see Appendix D).

On return, check the C032-PROG-STATUS


and report any errors/warnings in the usual
way.

(iv) If no errors returned from LY32, Call CICS


transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C033.
(see Appendix D).

On return, check the C033-PROG-STATUS


and report any errors/warnings in the usual
way.

(v) call the CICS transaction LY01 (see


Appendix C.1) – using COMMAREA C031
(see Appendix D) . This transaction will
return the data that should appear on this
screen.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(vi) Rebuild the screen from scratch using


the details returned in the C031
Commarea.

Save This key allows the user to save the details they Command
have entered on the screen without being navigated
onto a different screen. Note:- this button should be

David Willcocks 160 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
disabled if the screen is being viewed in ‘Enquiry’
mode (i.e. C031-SCREEN-MODE = ‘E’). Using
this option will also rebuild the screen from scratch
– this is because the user may have inserted or
deleted lines and will expect to see this reflected on
the screen after saving the details.

(i) If any Delete Option-buttons have been


selected, display the error E180 (see
Appendix E) in the Error Window (see
Appendix B).

(i) If no lines selected for deltion, call CICS


transaction LY01 (see Appendix C.1) to
validate that any details entered on the
screen are valid – using Commarea C032
(see Appendix D).

On return, check the C032-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) If no errors returned from LY32, Call CICS


transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C033.
(see Appendix D).

On return, check the C033-PROG-STATUS


and report any errors/warnings in the usual
way.

(iii) call the CICS transaction LY01 (see


Appendix C.1) – using COMMAREA C031
(see Appendix D) . This transaction will
return the data that should appear on this
screen.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(iv) Rebuild the screen from scratch using


the details returned in the C031
Commarea.

Continue (v) If C031-SCREEN-MODE = ‘U’(Update), Command

David Willcocks 161 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
call CICS transaction LY01 (see Appendix
C.1) to validate that any details entered on
the screen are valid – using Commarea
C032 (see Appendix D).

On return, check the C032-PROG-STATUS


and report any errors/warnings in the usual
way.

(vi) If C031-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY32, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C033. (see Appendix D).

On return, check the C033-PROG-STATUS


and report any errors/warnings in the usual
way.

(vii) If no errors returned from LY33 or C031-


SCREEN-MODE = ‘E’(Enquiry), call the
CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(viii) Navigate the user to whichever program is


identified in C011-NEXT-PROGRAM (see
Appendix N)

Cancel When the technician presses the ‘Cancel’ button, Command


any changes made since the last ‘Save’ will be
removed. The technician will remain in the ‘Market
Details’ screen. Therefore:-

(i) Call the CICS transaction LY01 (see


Appendix C.1) – using COMMAREA C031
(see Appendix D) . This transaction will
return the data that should appear on this
screen.

On return, check the Program Status in the

David Willcocks 162 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(ii) Rebuild the screen, based on the data


returned in the C031 Commarea.

EXIT This will return the user to whichever screen they Command
initiated the claim from.

(i) Call CICS transaction LY01 (see Appendix C.1)


to check the status of the current transaction –
using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B). If status is zero,
continue at (iv)

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before being navigated to the next
screen. Display the ‘Claim Transaction Options’
pop-up window detailed in Section 4.10 and
perform processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user should be
left in the current screen.

(iv) If the user did not press ‘Cancel’ or zero


Program Status returned from LY16,
Call the CICS transaction LY01 (see Appendix
C.1) – using COMMAREA C011 (see
Appendix D). This will invoke the ‘Navigation’
program, which decides on the next program the
user should be navigated to. (Note: the
C011-EXIT-IND should be set to ‘Y’)

On return, check the Program Status in the Usual


way, reporting errors if they exist in The Error
Screen (see Appendix B)

(v) If no errors returned from LY11, navigate the


user to the program indicated by
C011-NEXT-PROGRAM (see Appendix N).
If C011-NEXT-PROGRAM is set to 'NONE',
the current window should be closed.

David Willcocks 163 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

4.14. Claim Details Screen

Change Control Log

Release Date Changed SIRS Description of Changes Made


By No.

2.4. 04/03/2004 DTW 37546 changes have been made to LY34 to pass back a value of
spaces in the Adjuster/Lawyer Name and Reference to the GUI
with an associated Attribute of 'S' (Suppressed) for all internally
created claims. The Field Protection processing in the GUI
needs to be changed so that the Adjuster/Lawyer fields and their
prompts are hidden if the associated attribute fields are ‘S’
(Suppressed).

David Willcocks 164 May 2002


Xchanging Ins-sure Services Ltd
4.14.1. Screen Layout

Below is a ‘mock-up’ of the Claim Details Screen.

David Willcocks 165 May 2002


Xchanging Ins-sure Services Ltd
David Willcocks 166 May 2002
Xchanging Ins-sure Services Ltd
4.14.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY10 Update Session Record
LY11 Navigation Program
LY12 Build Screen Navigation Bar
LY14 Add OSND(s) to Aggregate Group
LY15 Create Non-Aggregate Group
LY16 Check Transaction Status
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY31 Build Market Details Screen
LY34 Build Claim Details Screen
LY35 Claim Details Screen Validation
LY36 Claim Details Screen D/B Update

David Willcocks 167 May 2002


Xchanging Ins-sure Services Ltd
Tran Program Description
s. Name
Id.
LY68 Create History Session Record
LY71 Set up Group Session Record
LY83 ‘CLASS for Lloyds’ Response – Initial
Validation
LY88 Build Narrative Details Screen
`
LY90 Bulk/CCS Correction Initial Validation
LY96 Set File Last Seen Date
LZ06 Reset Claim Transaction
LZ11 Create Re-Advice – Initial Validation

4.14.3. Field/Command Derivation

The fields and the navigation bar on this screen will be


derived as follows:-

Field Type Source


A. Navigation Bar
Navigation Bar Comman call the CICS transaction LY01 (see Appendix
d(s) C.1) – using COMMAREA C012 (see Appendix
D) . This will determine what should appear on
the ‘Screen Navigation Bar’ at the left hand side
of the screen.

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

See Appendix F for details of how to process the


information returned from this CICS transaction.

B. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C034 (see
Appendix D) . This transaction will return the data that should appear on this screen.

On return, check the Program Status in the usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

XCR Field C034-XCR


(This field should be protected)
UCR Field C034-UCR

David Willcocks 168 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
(This field should be protected)
TR Field C034-TR
(This field should be protected)
OSND1 Field C034-ORIG-REF-1
(This field should be protected)

OSND2 Field C034-ORIG-REF-2


(This field should be protected)
OSND3 Field C034-ORIG-REF-3
(This field should be protected)
Current Bkr Field C034-ORIG-BKR
Orig. Broker (This field should be protected)
Signed Tick-Box C034-SIGNED-IND
(This field should be protected)
Peer Review Field C034-PEER-REV-IND
(This field should be protected)
Broker Contact Field C034-BKR-CNTCT
(If C034-BKR-CNTCT-ATTR = ‘P’,
this field should be protected)
Broker Phone Field C034-BKR-CNTCT-PHONE
Number (If C034-BKR-PHONE-ATTR = ‘P’,
this field should be protected)
Broker Claim Field C034-BKR-REF-1
Reference 1 (If C034-BKR-REF-ATTR1 = ‘P’, this
field should be protected)
Broker Claim Field C034-BKR-REF-2
Reference 2 (If C034-BKR-REF-ATTR2 = ‘P’, this
field should be protected)
Broker UCR Field C034-BROKER-UCR
(If C034-BROKER-UCR-ATTR = ‘P’,
this field should be protected)
Original Field C034-ORIG-INSURED
Insured (If C034-ORIG-INS-ATTR = ‘P’, this
field should be protected)
Insured Field C034-INSURED
(If C034-INSURED-ATTR = ‘P’, this
field should be protected)
Reinsured Field C034-REINSURED
(If C034-REINSURED-ATTR = ‘P’,
this field should be protected)
Cover Holder Field C034-COVER-HOLDER
(If C034-COV-HOLD-ATTR = ‘P’, this
field should be protected)

David Willcocks 169 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Claimant Field C034-CLAIMANT
(If C034-CLAIMANT-ATTR = ‘P’, this
field should be protected)
Other Name Field C034-OTHER-NAME
(If C034-OTHER-NAME-ATTR = ‘P’,
this field should be protected)
Loss Name Field C034-LOSS-NAME
(If C034-LOSS-NAME-ATTR = ‘P’,
this field should be protected)
Vessel/Aircraft Field C034-VESSEL-AIRCRAFT
(If C034-VESS-AIR-ATTR = ‘P’, this
field should be protected)
Date of Loss Field C034-LOSS-DATE-FROM
From (If C034-DOL-FROM-ATTR = ‘P’,
this field should be protected)
Date of Loss To Field C034-LOSS-DATE-TO
(If C034-DOL-TO-ATTR = ‘P’, this
field should be protected)
Date of Loss Field C034-LOSS-DATE-QUAL
Qualifier (If C034-DOL-QUAL-ATTR = ‘P’, this
field should be protected)
Date Claim Field C034-DCM-DOD-FROM
Made From (If C034-DCM-FROM-ATTR = ‘P’,
this field should be protected)
Date Claim Field C034-DCM-DOD-TO
Made To (If C034-DCM-TO-ATTR = ‘P’, this
field should be protected)
Date Claim Field C034-DCM-DOD-QUAL
Made Qualifier (If C034-DCM-QUAL-ATTR = ‘P’,
this field should be protected)
Date of Loss Field C034-LOSS-DATE-NARR
Narrative (If C034-DOL-NARR-ATTR = ‘P’, this
field should be protected)
Loss Location Field C034-LOSS-LOCATION
(If C034-LOSS-LOCATION-ATTR =
‘P’, this field should be protected)
Voyage Field C034-VOYAGE
(If C034-VOYAGE-ATTR = ‘P’, this
field should be protected)
Cat Code Field C034-CAT-CODE
(If C034-CAT-ATTR = ‘P’, this field
should be protected)
PCS Cat Code Field C034-PCS-CAT-CODE

David Willcocks 170 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
(If C034-PCS-CAT-ATTR = ‘P’, this
field should be protected)
Claim/Risk Field C034-CLM-RISK-TYPE
Type (If C034-CLM-RISK-ATTR = ‘P’, this
field should be protected)
Claim Field C034-LOSS-DETAILS
Narrative (If C034-LOSS-DETS-ATTR = ‘P’,
this field should be protected)
Adjuster/Surve Field C034-ADJUSTER-NAME
yor Name (If C034-ADJ-NAME-ATTR = ‘P’, this
field should be visible but protected.
If C034-ADJ-NAME-ATTR = ‘S’
(Suppressed), this field and its
prompt should not be shown at all.)
Adjuster/Surve Field C034-ADJUSTER-REF
yor Reference (If C034-ADJ-REF-ATTR = ‘P’, this
field should be visible but protected.
If C034-ADJ-REF-ATTR = ‘S’
(Suppressed), this field and its
prompt should not be shown at all.)
Lawyer Name Field C034-LAWYER-NAME
(If C034-LAW-NAME-ATTR = ‘P’,
this field should be visible but
protected.
If C034-LAW-NAME-ATTR = ‘S’
(Suppressed), this field and its
prompt should not be shown at all.)
Lawyer Field C034-LAWYER-REF
Reference (If C034-LAW-REF-ATTR = ‘P’, this
field should be visible but protected.
If C034-LAW-REF-ATTR = ‘S’
(Suppressed), this field and its
prompt should not be shown at all.)
Cause Code 1 Field C034-CAUSE-CODE (1)
(If C034-CAUSE-CODE-ATTR (1) =
‘P’, this field should be protected)
Cause Code 2 Field C034-CAUSE-CODE (2)
(If C034-CAUSE-CODE-ATTR (2) =
‘P’, this field should be protected)
Cause Code 3 Field C034-CAUSE-CODE (3)
(If C034-CAUSE-CODE-ATTR (3) =
‘P’, this field should be protected)
Cause Code 4 Field C034-CAUSE-CODE (4)
(If C034-CAUSE-CODE-ATTR (4) =

David Willcocks 171 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
‘P’, this field should be protected)
Cause Code 5 Field C034-CAUSE-CODE (5)
(If C034-CAUSE-CODE-ATTR (5) =
‘P’, this field should be protected)
Cause Code 6 Field C034-CAUSE-CODE (6)
(If C034-CAUSE-CODE-ATTR (6) =
‘P’, this field should be protected)
Cause Code Field C034-CAUSE-CODE
(If C034-CAUSE-CODE-ATTR = ‘P’,
this field should be protected)
Finder Code 1 Field C034-FINDER-CODE (1)
(If C034-FIND-CODE-ATTR (1) =
‘P’, this field should be protected)
Finder Code 2 Field C034-FINDER-CODE (2)
(If C034-FIND-CODE-ATTR (2) =
‘P’, this field should be protected)
Finder Code 3 Field C034-FINDER-CODE (3)
(If C034-FIND-CODE-ATTR (3) =
‘P’, this field should be protected)
Cover Holder Field C034-CH-CLM-REF
Claim (If C034-CH-CLM-REF-ATTR = ‘P’,
Reference this field should be protected)
Certificate of Field C034-CERT-INS-NO (1)
Insurance No. (If C034-CERT-NO-ATTR (1) = ‘P’, this
1 field should be protected)
Certificate of Field C034-CERT-INS-NO (2)
Insurance No. (If C034-CERT-NO-ATTR (2) = ‘P’, this
1 field should be protected)
Certificate of Field C034-CERT-INS-NO (3)
Insurance No. (If C034-CERT-NO-ATTR (3) = ‘P’, this
1 field should be protected)
Certificate of Field C034-CERT-INS-NO (4)
Insurance No. (If C034-CERT-NO-ATTR (4) = ‘P’, this
1 field should be protected)
Certificate of Field C034-CERT-INS-NO (5)
Insurance No. (If C034-CERT-NO-ATTR (5) = ‘P’, this
1 field should be protected)

4.14.4. Process Description

This screen is the Claim Details Screen.

David Willcocks 172 May 2002


Xchanging Ins-sure Services Ltd
When creating an initial advice, all fields will be
unprotected and will require completion.
On subsequent advices, the contents of this screen will
be pre-filled from the details on the previous
transaction.
If the claim was entered by the broker, then any broker-
supplied details on this screen will be protected. If the
details entered by the broker do not contain sufficient
detail for advice to syndicates, then the information
should be enhanced on the ‘SCM Advice’ screen (see
Section 4.17).
If this screen is being viewed in ‘Enquiry’ mode, then
all fields will be protected.

Fig 4.14.4.1. Field/Command Processing for ‘Claim Details’


Screen

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D) to log-
off the system and delete the Session Record.

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, close all windows.

Create New (i) Call CICS transaction LY01 (see Appendix


Claim C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

David Willcocks 173 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Create Claim
Screen’ (see Section 4.4)

Find Claim (i) Call CICS transaction LY01 (see Appendix


C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform

David Willcocks 174 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Find Claim’ Screen
(see Section 4.5)

Account Link to Account Enquiry (method needs to be Command


Enquiry identified)

Repository Link to Repository (method needs to be identified) Command

Data Link to Data Warehouse (method needs to be Command


Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry
Add to Aggregate Group

David Willcocks 175 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Create Non-Aggregate Group
Add to Non-Aggregate Group

User should select one of these options.

Note:- ‘Clicking’ on the ‘Maintain Group’,


‘Group Enquiry’ or ‘Add to Non-Aggregate
Group’ options should open up a new ‘window’ –
associated with its own entry on the Session Table
(i.e. a new Session No.). Once the user has finished
Group processing, the window should be closed and
the Session Record deleted.

(i) If either the ‘Maintain Group’, ‘Group


Enquiry’ or ‘Add to Non-Aggregate
Group’ options were selected, call CICS
transaction LY01 (see Appendix C.1) to set
up a new Session Record for the Grouping
session - using Commarea C071 (see
Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iv) On selection of ‘Add to Aggregate


Group’, call CICS transaction LY01
(see Appendix C.1) to add the OSND’s
associated with this claim to an Aggregate
group – using COMMAREA C014 (see
Appendix D).

On return, check the C014-PROG-STATUS

David Willcocks 176 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the OSND’s
have been added to. (see Appendix G)

(v) On selection of ‘Create Non-Aggregate


Group’, call CICS transaction LY01 (see
Appendix C.1) to add the current claim
to a Non-Aggregate group – using
COMMAREA C015 (see Appendix D).

On return, check the C015-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the claim has
been added to. (see Appendix G)

(vi) On selection of the ‘Add to Non-


Aggregate Group’ option, open new
window, navigating user to ‘Group Enquiry’
screen (see Section 4.28) (a new SESSION-
NO is associated with this window – this
will have been returned by previous
transaction, LY71)

Notes When user clicks on the ‘NOTES’ option at the top Command
of the screen, the following options should be
available on a sub-menu:-
Security Notes
Claim Notes
Loss Details
Policy Details
EURO Conversion Narrative (FME)
Broker Additional Details
Broker Aggregate Details
Slip Lead Comments
Lead Comments
Lead Additional Details

User should select one of these options.

Whichever option is selected:-

David Willcocks 177 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(i) Call CICS Transaction LY01 (see


Appendix C.1), using Commarea C036
(see Appendix D), to update the
database with any details entered on the
Claim Details screen.

On return, check the C036-PROG


-STATUS and report any errors in the
usual way.

(ii) Call CICS transaction LY01 (see


Appendix C.1) to check whether the
selected narrative is present or not, and
return any narrative present, using
COMMAREA C088 (see Appendix D).
N.B. Set C088-FIRST-CALL to ‘Y’.
This call will return lines 1 to 300.

On return, check the C088-PROG


-STATUS and report any errors in the
usual way.

(iii) If no errors returned from the first


LY88 call and C088-MORE-LINES is
set to ‘Y’, call CICS transaction LY01
(see Appendix C.1) to check whether
the selected narrative is present or not,
and return any narrative present, using
COMMAREA C088 (see Appendix D).
N.B. Set C088-FIRST-CALL to ‘N’.
This call will return lines 301 to 600.

On return, check the C088-PROG


-STATUS and report any errors in the
usual way.

(iv) If no errors found in LY88, the user


should be navigated to the Narrative
Screen (see Section 4.35)

Note:- the Narrative screen should be opened up as


a new window, overlaying whichever screen the
user is currently processing. Once the user has
finished enquiring on or updating the narrative, the
window should be closed and the user will be
returned to whichever screen they were processing

David Willcocks 178 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
originally.

History When the user ‘clicks’ on this option they should be Command
navigated to the ‘Transaction History’ screen.

Note:- ‘Clicking’ on the ‘History’ option should


open up a new ‘window’ – associated with its own
entry on the Session Table (i.e. a new Session No.).
Once the user has finished browsing through
history, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
History session - using Commarea C068
(see Appendix D).

On return, check the C068-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) Open new window, navigating user to


‘Transaction History’ screen (see Section
4.25) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY68)

Functions When user clicks on the ‘FUNCTIONS’ option at Command


the top of the screen, the following options should
be available on a sub-menu:-
1.Create Subsequent Advice
2.Create Rate of Exchange Adjustment
3.Create Contra Correction
4.Add Take Down Numbers
5. ‘CLASS for Lloyds’ Response
6. Set Diary Date
7. Create Bulk/CCS Correction
8. Set ‘File Last Seen’ Date
9. Reset Claim Transaction
10. Create Re-advice

User should select one of these options:-

‘Create Subsequent Advice’ selected

If the user selects ‘Create Subsequent Advice


(Single B/down)’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary

David Willcocks 179 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
– using COMMAREA C020. (see Appendix D).
N.B. Ensure that C020-TRANS-TYPE is set to ‘V’
(Validation Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned from the first call to LY20,


call CICS transaction LY01 (see Appendix C.1) to
‘construct’ the skeleton subsequent transaction –
using COMMAREA C020. (see Appendix D). N.B.
Ensure that C020-TRANS-TYPE is set to ‘U’
(Update Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Claim Transaction Creation screen’ – rebuilding it
from scratch – as field protection will be
different and some field contents may be different.

‘Create Rate of Exchange Adjustment’ selected

If the user selects ‘Create Rate of Exchange


Adjustment’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C021. (see Appendix D).

On return, check the C021-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Rate of
Exchange Adjustment (see Section 4.29).

‘Create Contra Correction’ selected

If the user selects ‘Create Contra Correction’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C022. (see Appendix D).

On return, check the C022-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Contra

David Willcocks 180 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Correction (see Section 4.30).

‘Add Take Down Numbers’ selected

If the user selects ‘Add Take Down Numbers’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C023. (see Appendix D).

On return, check the C023-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘Settlement Summary’ (see Section
4.22).

‘CLASS for Lloyds’ Response selected

If the user selects ‘CLASS for Lloyds Response’,


call CICS transaction LY01 (see Appendix C.1) to
check that the claim transaction is a ‘CLASS for
Lloyds’ claim and that it requires authorisation –
using COMMAREA C083. (see Appendix D).

On return, check the C083-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘CLASS for Lloyds Response’
screen (This function is not available in Phase 1).

‘Set Diary Date’ selected

If the user selects the ‘Set Diary Date’ option, the


‘Set Diary Date’ pop-up window should be
displayed to them (see Section 4.34).

‘Create Bulk/CCS Correction’ selected

This is a special correction facility for use only by


authorised technicians. It allows correction of Bulk
Components, converted bulks and pre-
redenomination transactions. The difference
between this type of correction and Contra
Corrections is that the user has the ability to enter a
treasury rate.

If the user selects ‘Create Bulk/CCS Correction’,

David Willcocks 181 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
call CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C090. (see Appendix D).

On return, check the C090-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the
Bulk/CCS Correction (see Section 4.36).

‘Set File Last Seen Date’ selected

This function allows the user to set the File Last


Seen Date to todays date and generate an advice to
the syndicates without creating a new claim
movement.

If this function is selected, display the ‘File Seen


Confirmation’ window (see Appendix S.2). If the
technician presses ‘YES’ in this window, call CICS
transaction LY01 (see Appendix C.1) to perform
any validation necessary and set up the necessary
logging records – using COMMAREA C096. (see
Appendix D).

On return, check the C096-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up confirmation


window should be displayed (see Appendix S.3.)
for information purposes only.

‘Reset Claim Transaction’ selected

This function will reset the status of a previously


released claim transaction to allow it to be updated
by the claim technician. This will not be allowed if
the claim transaction has been fully advised or if a
subsequent transaction exists within the claim.

(i) Call CICS transaction LY01 (see


Appendix C.1), passing the Commarea
C105 (see Appendix D). This will
validate that that the claim transaction
is eligible for update and, if so, reset the
status accordingly.

David Willcocks 182 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

On return check the Program Status and


report any errors/warnings in the usual
way.

(ii) If no errors returned from LZ06, call


LY01 using Commarea C034 to obtain
the data and field protection for the
current screen.

On return check the Program Status and


report any errors/warnings in the usual
way.

(iii) Rebuild the current screen using the


data returned in the C034 Commarea.

‘Create Re-advice’ selected

This function will allow the user to create a re-


advice of the most recent movement on the claim –
changing only the current narrative.

(i) call CICS transaction LY01 (see Appendix C.1)


to perform any validation necessary – using
COMMAREA C110. (see Appendix D).

On return, check the C110-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Create Re-Advice’ screen (see Section 4.39).

David Willcocks 183 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B. Navigation Options (Left of Screen) – COMMANDS

If user clicks on the ‘Option Button’ alongside any of the Options on the Navigation Bar, refer to table
returned by transaction LY12 (Build Navigation Bar) in the C012 Commarea. This table should be
stored after building the navigation bar on first entry to the screen for use when the user selects one of
the options on the Navigation Bar.

(i) If C034-SCREEN-MODE = ‘U’ (Update), call CICS transaction LY01 (see Appendix C.1) to
validate that any details entered on the screen are valid – using Commarea C035 (see
Appendix D).

On return, check the C035-PROG-STATUS and report any errors/warnings in the usual way.

(ii) If C034-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY35, Call CICS
transaction LY01 (see Appendix C.1) to update the database with the details entered on the
screen – using COMMAREA C036. (see Appendix D).

On return, check the C036-PROG-STATUS and report any errors/warnings in the usual way.

(iii) If C034-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY36, call CICS
transaction LY01 (see Appendix C.1) – using COMMAREA C046 (see Appendix D) – to
check whether currency/transaction validation needs to be performed. (N.B. the key values
returned from LY12 and stored in the C012-KEY table – for the line on the navigation bar
selected - should be passed in the C046 commarea).

On return, check the C046-PROG-STATUS and report any errors/warnings in the usual way.

(iv) If no errors returned from LY46 or C034-SCREEN-MODE = ‘E’ (Enquiry), Call CICS
transaction LY01 (see Appendix C.1) to update the Session Record (VCLSESA1) –using
COMMAREA C010. (see Appendix D), (N.B. the key values returned from LY12 and stored
in the C012-KEY table – for the line on the navigation bar selected - should be passed in the
C010 commarea).

On return, check the C010-PROG-STATUS and report any errors/warnings in the usual
way.

(v) If no errors are returned from LY10, the user should be navigated to the screen indicated by
C012-SCREEN-ID for the line in the navigation bar selected (see Appendix N)

David Willcocks 184 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C. Fields (Main Screen)

N.B. Alphanumeric fields must not contain any characters that are not supported by the EDI message
systems, as these may cause brokers and/or syndicates systems to fall over. Valid ASCII Characters are
as follows:-
space, 0-9, A-Z, a-z, ',', '.', '-', '(', ')', '/', '=', ''', '*','+', ':', '?', '!','"', '%','&', ';','<', '>'.

N.B.2. Pre-population of the fields with values returned from LIDS does not need to be handled by
the GUI, as these values will have been loaded onto the database by the ‘Claim Creation Screen
D/B Update’ module (LY27).

N.B.3 Field Protection will be handled by the ‘Field Attributes’ returned in the C034 Commarea.

N.B.4 If any errors are encountered, highlight any field(s) in error by setting the text colour to red.

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric


to claims that are created by internal technicians. It Only Field (17 Chars)
will always be present for internally created claims,
but not for claims created by the broker on the
‘CLASS for Lloyds’ system.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

UCR The Unique Claim Reference. This will always be Display Alphanumeric
present for claims created by the broker on the Only Field (17 Chars)
‘CLASS for Lloyds’ system, but may or may not be
present for internally created claims – depending on
whether the broker has quoted it on the claim file.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

TR Transaction Reference. Uniquely identifies a Display Alphanumeric


particular transaction within a claim. Only Field (17 chars)

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’
OSND1 Original Signing Number and date (for the first Display Alphanumeric
currency on the claim) Only Field (15 Chars)
OSND2 Original Signing Number and date (for the second Display Alphanumeric

David Willcocks 185 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
currency on the claim) Only Field (15 Chars)
OSND3 Original Signing Number and date (for the third Display Alphanumeric
currency on the claim) Only Field (15 Chars)
Current The Originating Current Broker (i.e. the broker who Display Alphanumeric
Bkr submitted this claim transaction). Only Field (4 chars)
Orig.
Broker
Signed Signed Indicator. This indicates whether or not the Display
(Y/N) risk against which this claim is being made has been Only
signed or not. Tick-Box
Peer This indicates whether the claim is subject to peer Display Alphanumeric
Review review. Only (1 Char)
Field
Broker The Broker Contact. Mandatory Alphanumeric
Contact Field (15 chars)
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Broker The Phone Number of the Broker Contact. Mandatory Alphanumeric


Phone Field (15 chars)
Number This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Broker The Brokers first claim reference. Mandatory Alphanumeric


Claim Field (12 chars)
Reference This is a free-text field subject only to ASCII

David Willcocks 186 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
1 validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Broker The Brokers second claim reference. Mandatory Alphanumeric


Claim Field (12 chars)
Reference This is a free-text field subject only to ASCII
2 validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Broker The Brokers Unique Claim reference. This will Optional Alphanumeric
UCR always be present for claims entered by the broker Field (17 Chars)
on the ‘CLASS for Lloyds’ system, but is optional
for internally created claims.

Once entered it will brought forward onto


subsequent transactions, but will remain
unprotected.

It is a 17 character field which should be displayed


in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

Original The Original Insured. Optional Alphanumeric


Insured Field (50 chars)
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

David Willcocks 187 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Insured The Insured. Optional Alphanumeric


Field (50 chars)
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or, for internally created claims, it will be
pre-populated from the LIDS database but may be
overwritten.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Reinsured The Reinsured. Optional Alphanumeric


Field (50 chars)
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or, for internally created claims, it will be
pre-populated from the LIDS database but may be
overwritten.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Cover The name of the cover holder. Optional Alphanumeric


Holder Field (50 Chars)
This is a free-text field subject only to ASCII
validation, described above.

This field cannot be entered on ‘CLASS for Lloyds’


and will therefore be unprotected on ‘CLASS for

David Willcocks 188 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Lloyds’ transactions.

Claimant The Claimant. Optional Alphanumric


Field (50 Chars)
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Other This is an extra field that allows the user to enter Optional Alphanumeric
Name any other name that may apply to this claim that is Field (50 Chars)
not classed as the Reinsured, Insured, Cover Holder,
Original Insured or Vessel.

This is a free-text field subject only to ASCII


validation, described above.

Loss The Loss Name. Mandatory Alphanumeric


Name Field (20 chars)
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Vessel/ The name of the Vessel, Aircraft or Conveyance. Optional Alphanumeric


Aircraft Field (50 Chars)
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

David Willcocks 189 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Date of The Date of Loss (From). Optional Date


Loss From Field
This is either entered by the broker on ‘CLASS for
Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Note:- Partial Dates may be entered in this field.


Therefore the following may be allowed and the
date elements validated accordingly:

1) Century and Year only


2) Century, Year and Month only
3) Full Date

Date of The Date of Loss (To). Optional Date


Loss To Field
This is either entered by the broker on ‘CLASS for
Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

N.B. This field may not be entered unless the DAY


element of the Loss Date From is entered.

If this field is entered without the Loss Date From


being completed, display the error E065 (see
Appendix E) in the Error Window (see Appendix
B).

If this field is entered and is less than or equal to the

David Willcocks 190 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Loss Date From, display the error E066 (see
Appendix E) in the Error Window (see Appendix
B).

Date of The Loss Date Qualifier. This is entered if the Loss Optional Alphanumeric
Loss Date is left blank to explain its absence. Field (1 char)
Qualifier
If this claim transaction was entered by the broker
on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

If entered internally, valid qualifiers are:-

'N' = not applicable


'T' = to be advised
'V' = various
‘S’ = Loss Date Narrative supplied

Note:- Other qualifiers may be entered by the


broker on the ‘CLASS for Lloyds’ system.

Date The Date the Claim was made (From). Optional Date
Claim Field
Made This can be entered by the broker on ‘CLASS for
From Lloyds’ in the ‘Loss Date From’ field, by using a
Loss Date Qualifier of ‘C’. For internally created
claims it will be entered by technicians as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Note:- Partial Dates may be entered in this field.


Therefore the following may be allowed and the
date elements validated accordingly:

1) Century and Year only


2) Century, Year and Month only
3) Full Date

Date The Date the Claim was made (To). Optional Date
Claim Field
This can be entered by the broker on ‘CLASS for

David Willcocks 191 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Made To Lloyds’ in the ‘Loss Date To’ field, by using a Loss
Date Qualifier of ‘C’. For internally created claims
it will be entered by technicians as it appears on the
claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

N.B. This field may not be entered unless the DAY


element of the Claim Date From is entered.

If this field is entered without the ‘Date Claim


Made From’ being completed, display the error
E067 (see Appendix E) in the Error Window (see
Appendix B).

If this field is entered and is less than or equal to the


Loss Date From, display the error E068 (see
Appendix E) in the Error Window (see Appendix
B).

Date Qualifier that explains the absence of the ‘Date Optional Alphanumeric
Claim Claim Made’. Field (1 char)
Made
Qualifier Qualifiers allowed are:-

'N' = not applicable


'T' = to be advised
'V' = various.

Date of This is a narrative description of the Loss Date, Optional Alphanumeric


Loss entered if the Loss Date Qualifier is set to ‘S’. Field (30 chars)
Narrative
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM

David Willcocks 192 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Advice screen (see Section 4.17)

If the Loss Date Qualifier is set to ‘S’, this field


must be completed. If not, display the error E069
(see Appendix E) in the Error Window (see
Appendix B).

Loss The Location of the Loss. Optional Alphanumeric


Location Field (50 chars)
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Voyage The Voyage of Loss. Optional Alphanumeric


Field (30 chars)
This is a free-text field subject only to ASCII
validation, described above.

This field is not entered by the broker on the


‘CLASS for Lloyds’ system and will therefore be
unprotected on all unadvised claim transactions.

Cat Code The Catastrophe Code relating to the loss. Optional Alphanumeric
Field (4 chars)
This is either entered by the broker on ‘CLASS for
Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

It should be validated against the Catastrophe Code


table (name ?). If not present on the table, display
the error E070 (see Appendix E) in the Error
Window (see Appendix B).

David Willcocks 193 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
PCS Cat The PCS (Property Claims Service) Catastrophe Optional Alphanumeric
Code Code relating to the loss. Field (4 chars)

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

It should be validated against the Catastrophe Code


table (name ?). If not present on the table, display
the error E071 (see Appendix E) in the Error
Window (see Appendix B).

Claim/Risk Identifies type of Marine claim. Optional Alphanumeric


Type Field (3 Chars)
Valid values for Claim Type Code:
CGO - Cargo
CPA - Claims paid abroad
CXL - Company Excess of Loss
ERI - Energy Reinsurance
G/A - General Average
HLL - Hull
HRI - Hull Reinsurance
LBY - Liability
LOE - Loss of Earnings
LOH - Loss of Hire
MII - Mortgagees Interest Insurance
OIL - Oil
R/I - Reinsurance
SXL - Syndicate Excess of Loss
TTY - Marine Treaty
X/L - Excess of Loss

These should be available in a drop down list.

Mandatory for Marine Claims (handled by CICS


Transaction).
Claim The Narrative associated with this claim. (Also Mandatory Alphanumeric
Narrative known as Loss Details). Field (350 chars)

This is a free-text field subject only to ASCII


validation, described above.

David Willcocks 194 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
This is either entered by the broker on ‘CLASS for
Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Adjuster/ The Name of the Adjuster/Surveyor handling this Optional Alphanumeric


Surveyor claim. Field (20 chars)
Name
This field will be protected if the claim was loaded
by the broker on the ‘CLASS for Lloyds’ system.

Where the field attribute passed from the build


program is not ‘P’ (Protected), a drop down list will
be available for this field. Details for this list will be
obtained from the Expert Table (TGLFEEA). The
list should be in alphabetical order. If the user enters
a partial name, the list should start from this point
(although software limitations may mean that this is
not possible). Adjuster Codes are identified in the
TGLFEEA table by an EXPERT-TYPE of ‘A’. The
drop down list must be limited to records with this
value.

Adjuster/ The Adjuster’s or Surveyor’s Reference. Optional Alphanumeric


Surveyor Field (15 chars)
Reference This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Lawyer The Name of the Lawyer that may be associated Optional Alphanumeric
Name with this claim. Field (20 chars)

David Willcocks 195 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
This field will be protected if the claim was loaded
by the broker on the ‘CLASS for Lloyds’ system.

Where the field attribute passed from the build


program is not ‘P’ (Protected), a drop down list will
be available for this field. Details for this list will be
obtained from the Expert Table (TGLFEEA). The
list should be in alphabetical order. If the user enters
a partial name, the list should start from this point
(although software limitations may mean that this is
not possible). Lawyer Codes are identified in the
TGLFEEA table by an EXPERT-TYPE of ‘L’. The
drop down list must be limited to records with this
value.

Lawyer The Lawyer’s Reference. Optional Alphanumeric


Reference Field (15 chars)
This is a free-text field subject only to ASCII
validation, described above.

This is either entered by the broker on ‘CLASS for


Lloyds’ or is entered by the technician as it appears
on the claim file.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected. If any changes are required (for advising
purposes) these will have to be made on the SCM
Advice screen (see Section 4.17)

Cause Cause of Loss Code 1. The first of up to six codes Optional Alphanumeric
Code 1 used to identify the cause of loss. Field (2 Chars)

This field may or may not be populated by either


the lead/follower syndicate or the XIS/XCS
technicians during the ‘CLASS for Lloyds’
authorisation process. It is not however entered by
the broker, so will not be protected on this screen.

It should be validated against the Cause Code Table


(name ?). If not present on this table, display the
error E074 (see Appendix E) in the Error Window
(see Appendix B).

Cause Cause of Loss Code 2. The second of up to six Optional Alphanumeric


Code 2 codes used to identify the cause of loss. Field (2 Chars)

This field may or may not be populated by either

David Willcocks 196 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
the lead/follower syndicate or the XIS/XCS
technicians during the ‘CLASS for Lloyds’
authorisation process. It is not however entered by
the broker, so will not be protected on this screen.

It should be validated against the Cause Code Table


(name ?). If not present on this table, display the
error E074 (see Appendix E) in the Error Window
(see Appendix B).

Cause Cause of Loss Code 3. The third of up to six codes Optional Alphanumeric
Code 3 used to identify the cause of loss. Field (2 Chars)

This field may or may not be populated by either


the lead/follower syndicate or the XIS/XCS
technicians during the ‘CLASS for Lloyds’
authorisation process. It is not however entered by
the broker, so will not be protected on this screen.

It should be validated against the Cause Code Table


(name ?). If not present on this table, display the
error E074 (see Appendix E) in the Error Window
(see Appendix B).

Cause Cause of Loss Code 4. The fourth of up to six codes Optional Alphanumeric
Code 4 used to identify the cause of loss. Field (2 Chars)

This field may or may not be populated by either


the lead/follower syndicate or the XIS/XCS
technicians during the ‘CLASS for Lloyds’
authorisation process. It is not however entered by
the broker, so will not be protected on this screen.

It should be validated against the Cause Code Table


(name ?). If not present on this table, display the
error E074 (see Appendix E) in the Error Window
(see Appendix B).

Cause Cause of Loss Code 5. The fifth of up to six codes Optional Alphanumeric
Code 5 used to identify the cause of loss. Field (2 Chars)

This field may or may not be populated by either

David Willcocks 197 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
the lead/follower syndicate or the XIS/XCS
technicians during the ‘CLASS for Lloyds’
authorisation process. It is not however entered by
the broker, so will not be protected on this screen.

It should be validated against the Cause Code Table


(name ?). If not present on this table, display the
error E074 (see Appendix E) in the Error Window
(see Appendix B).

Cause Cause of Loss Code 6. The last of six codes used to Optional Alphanumeric
Code 6 identify the cause of loss. Field (2 Chars)

This field may or may not be populated by either


the lead/follower syndicate or the XIS/XCS
technicians during the ‘CLASS for Lloyds’
authorisation process. It is not however entered by
the broker, so will not be protected on this screen.

It should be validated against the Cause Code Table


(name ?). If not present on this table, display the
error E074 (see Appendix E) in the Error Window
(see Appendix B).

Cause Cause of Loss Code 6. The last of six codes used to Optional Alphanumeric
Code identify the cause of loss. Field (4 Chars)

This field is associated with a drop-down list – built


from reference data passed from the mainframe
code table.

Note :- the field on the screen also contains the


description, but only the code is passed to/from the
mainframe.

Finder Finder Code 1. Optional Alphanumeric


Code 1 Field (1 Char)
The 3 finder codes are used to identify claims with
common features. 3 are required because one claim
could belong to 3 sets, but only one set of each type
(identified by Finder Code number).

It should be validated against the Finder Code Table


(name ?). If not present on this table, display the
error E075 (see Appendix E) in the Error Window
(see Appendix B). N.B. Must be identified as a
valid type 1 code.

David Willcocks 198 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Finder Finder Code 2. Optional Alphanumeric
Code 2 Field (1 Char)
The 3 finder codes are used to identify claims with
common features. 3 are required because one claim
could belong to 3 sets, but only one set of each type
(identified by Finder Code number).

It should be validated against the Finder Code Table


(name ?). If not present on this table, display the
error E075 (see Appendix E) in the Error Window
(see Appendix B). N.B. Must be identified as a
valid type 2 code.

Finder Finder Code 3. Optional Alphanumeric


Code 3 Field (1 Char)
The 3 finder codes are used to identify claims with
common features. 3 are required because one claim
could belong to 3 sets, but only one set of each type
(identified by Finder Code number).

It should be validated against the Finder Code Table


(name ?). If not present on this table, display the
error E075 (see Appendix E) in the Error Window
(see Appendix B). N.B. Must be identified as a
valid type 3 code.

Cover This is the Claim Reference that identifies claims Optional Alphanumeric
Holder entered via the Scheme Canada system. Field (8 Characters)
Claim
Reference This field is alphanumeric and may be up to 8
characters in length.
Certificate Certificate of Insurance number. There may be Optional Free Format
of multiple Certificate of Insurance numbers for a Field (20 Chars)
Insurance particular XCR/UCR. Note:- a particular Certificate
No. of Insurance Number cannot relate to more than one
open XCR/UCR.

D. Commands - (Main Screen)


Save This key allows the user to save the details they Command
have entered on the screen without being navigated
onto a different screen. Note:- this button should be
disabled if the screen is being viewed in ‘Enquiry’
mode (i.e. C034-SCREEN-MODE = ‘E’)

(i) Call CICS transaction LY01 (see Appendix


C.1) to validate that any details entered on
the screen are valid – using Commarea

David Willcocks 199 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C035 (see Appendix D).

On return, check the C035-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) If no errors returned from LY35, Call CICS


transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C036.
(see Appendix D).

On return, check the C036-PROG-STATUS


and report any errors/warnings in the usual
way.

Continue (iii) If C034-SCREEN-MODE = ‘U’(Update), Command


call CICS transaction LY01 (see Appendix
C.1) to validate that any details entered on
the screen are valid – using Commarea
C035 (see Appendix D).

On return, check the C035-PROG-STATUS


and report any errors/warnings in the usual
way.

(iv) If C034-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY35, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C036. (see Appendix D).

On return, check the C036-PROG-STATUS


and report any errors/warnings in the usual
way.

(v) If no errors returned from LY36 or C034-


SCREEN-MODE = ‘E’(Enquiry), call the
CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.

On return, check the Program Status in the

David Willcocks 200 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(vi) Navigate the user to whichever program is


identified in C011-NEXT-PROGRAM (see
Appendix N)

Cancel When the technician presses the ‘Cancel’ button, Command


any changes made since the last ‘Save’ will be
removed. The technician will remain in the ‘Claim
Details’ screen. Therefore:-

(i) Call the CICS transaction LY01 (see


Appendix C.1) – using COMMAREA C034
(see Appendix D) . This transaction will
return the data that should appear on this
screen.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(ii) Rebuild the screen, based on the data


returned in the C034 Commarea.

EXIT This will return the user to whichever screen they Command
initiated the claim from.

(i) Call CICS transaction LY01 (see Appendix C.1)


to check the status of the current transaction –
using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B). If status is zero,
continue at (iv)

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before being navigated to the next
screen. Display the ‘Claim Transaction Options’
pop-up window detailed in Section 4.10 and
perform processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user should be
left in the current screen.

David Willcocks 201 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(iv) If the user did not press ‘Cancel’ or zero


Program Status returned from LY16,
Call the CICS transaction LY01 (see Appendix
C.1) – using COMMAREA C011 (see
Appendix D). This will invoke the ‘Navigation’
program, which decides on the next program the
user should be navigated to. (Note: the
C011-EXIT-IND should be set to ‘Y’)

On return, check the Program Status in the Usual


way, reporting errors if they exist in The Error
Screen (see Appendix B)

(v) If no errors returned from LY11, navigate the


user to the program indicated by
C011-NEXT-PROGRAM (see Appendix N).
If C011-NEXT-PROGRAM is set to 'NONE',
the current window should be closed.
4.15. Financial Details Control Screen

4.15.1. Screen Layout

Below is the Financial Details Control Screen.

David Willcocks 202 May 2002


Xchanging Ins-sure Services Ltd
4.15.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY10 Update Session Record
LY11 Navigation Program
LY12 Build Screen Navigation Bar
LY14 Add OSND(s) to Aggregate Group
LY15 Create Non-Aggregate Group
LY16 Check Transaction Status
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY37 Build Claim Details Screen
LY38 Claim Details Screen Validation
LY39 Claim Details Screen D/B Update
LY46 Check whether Currency/Transaction
Validn. reqd.
LY68 Create History Session Record
LY71 Set up Group Session Record
LY83 ‘CLASS for Lloyds’ Response – Initial
Validation
LY88 Build Narrative Details Screen
LY90 Bulk/CCS Correction Initial Validation
LY96 Set File Last Seen Date
LZ06 Reset Claim Transaction
LZ11 Create Re-Advice – Initial Validation

4.15.3. Field/Command Derivation

The fields and the navigation bar on this screen will be


derived as follows:-

David Willcocks 203 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
A. Navigation Bar
Navigation Bar Comman call the CICS transaction LY01 (see Appendix
d(s) C.1) – using COMMAREA C012 (see Appendix
D) . This will determine what should appear on
the ‘Screen Navigation Bar’ at the left hand side
of the screen.

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

See Appendix F for details of how to process the


information returned from this CICS transaction.

B. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C037 (see
Appendix D) . This transaction will return the data that should appear on this screen.

On return, check the Program Status in the usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

XCR Field C037-XCR


(This field should be protected)
UCR Field C037-UCR
(This field should be protected)
TR Field C037-TR
(This field should be protected)
OSND1 Field C037-ORIG-REF-1
(This field should be protected)

OSND2 Field C037-ORIG-REF-2


(This field should be protected)
OSND3 Field C037-ORIG-REF-3
(This field should be protected)
Current Bkr Field C037-ORIG-BKR
(This field should be protected)
Signed Tick-Box C037-SIGNED-IND
(This field should be protected)
Peer Review Field C037-PEER-REV-IND
(This field should be protected)
Payee Broker Field C037-PAYEE-BKR-CODE
(If C037-PAYEE-BKR-ATTR = ‘P’, this
field should be protected)
Payee Broker Field C037-PAYEE-BKR-PSEUD
Pseudonym (If C037-PAY-BKR-PSD-ATTR = ‘P’, this

David Willcocks 204 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
field should be protected)
Re- Field C037-REDENOM-IND
denomination (If C037-REDENOM-ATTR = ‘P’, this
Indicator field should be protected)
Broker TR Field C037-BKR-TR
(If C037-BKR-TR-ATTR = ‘P’, this field
should be protected)
Broker TR Qual Drop- C037-BKR-TR-QL
down list (If C037-BKR-TR-QL-ATTR = ‘P’, this
field should be protected)
The following values should be
included in the ‘Drop down’ list:

 space
 B - Queried Broker advice
 C – Correction
 D – Direct advice or settlement
 F – First advice with settlement
 I – Individual/Block claim
 – Other

 V – Various
Peer Review Field C037-PEER-REV-IND
(If C037-ORIG-CURR-ATTR = ‘P’, this
field should be protected)
Original Field C037-ORIG-CURR
Currency (If C037-ORIG-CURR-ATTR = ‘P’, this
field should be protected)
Paid To Date Field C037-PAYED-TO-DATE
Amount (If C037-PTD-ATTR = ‘P’, this field
should be protected)
Paid This Time Field C037-PAYED-THIS-TIME
Amount (If C037-PTT-ATTR = ‘P’, this field
should be protected)
Outstanding Field C037-OUTST-AMT
Amount (If C037-OUTST-AMT-ATTR = ‘P’, this
field should be protected)
Outstanding Field C037-OUTST-QUAL
Amount (If C037-OUTST-QUAL-ATTR = ‘P’, this
Qualifier field should be protected)
Settlement Field C037-SETT-CURR
Currency (If C037-SETT-CURR-ATTR = ‘P’, this
field should be protected)
Settlement Tick-Box Set to ‘TRUE’ if C037-SETT-IND = ‘Y’.
Indicator (If C037-SETT-IND-ATTR = ‘P’, this

David Willcocks 205 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
field should be protected)
Settlement Field C037-EXCH-RATE
Rate of (If C037-EXCH-RATE-ATTR = ‘P’, this
Exchange field should be protected)
Settled in Field C037-CLAIM-AMT-SETT
Settlement (If C037-CLM-AMT-SETT-ATTR = ‘P’,
Currency this field should be protected)
Total Line Field C037-TOTAL-LINE
(If C037-TOTAL-LINE-ATTR = ‘P’, this
field should be protected)
Bureau Field C037-BUR-PROP-AMT
Proportion (If C037-BUR-PROP-ATTR = ‘P’, this
Amount field should be protected)
100% VAT Field C037-HPC-VAT-AMT
Amount (If C037-VAT-AMT-ATTR = ‘P’, this field
should be protected)
War Amount Field C037-WAR-AMT
(If C037-WAR-AMT-ATTR = ‘P’, this
field should be protected)
Incurred Field C037-INCURRED-AMT
Amount (If C037-INCURRED-ATTR = ‘P’, this
field should be protected)

David Willcocks 206 May 2002


Xchanging Ins-sure Services Ltd
4.15.4. Process Description

This screen is the Financial Details Control Screen.


This screen allows the user to enter the total amounts
for a particular currency. This screen will be visited
once for each currency on the claim (up to 3). The
amounts entered on this screen are entered for Control
purposes. Amounts will also be entered on the ‘SCM
Advice’ screen. Once all breakdowns have been
entered, the system will validate that the amounts
entered at the breakdown level total those entered on
this screen.

If the current transaction is a subsequent advice, the


Paid To Date and Outstanding amounts will be pre-filled
from those held on the previous transaction within the
claim. The user will be able to change these amounts if
required.

If the current transaction was entered by the broker on


the ‘CLASS for Lloyds’ system, then all broker entered
fields will be protected. If the technician believes that
any amounts are incorrect, the broker must be asked to
resubmit the transaction.

Fig 4.15.4.1. Field/Command Processing for ‘Financial Details


Control’ Screen

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D) to log-
off the system and delete the Session Record.

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, close all windows.

Create New (i) Call CICS transaction LY01 (see Appendix


Claim C.1) to check the status of the current

David Willcocks 207 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Create Claim
Screen’ (see Section 4.4)

Find Claim (i) Call CICS transaction LY01 (see Appendix

David Willcocks 208 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Find Claim’ Screen
(see Section 4.5)

David Willcocks 209 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Account Link to Account Enquiry (method needs to be Command
Enquiry identified)

Repository Link to Repository (method needs to be identified) Command

Data Link to Data Warehouse (method needs to be Command


Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry
Add to Aggregate Group
Create Non-Aggregate Group
Add to Non-Aggregate Group

User should select one of these options.

Note:- ‘Clicking’ on the ‘Maintain Group’,


‘Group Enquiry’ or ‘Add to Non-Aggregate
Group’ options should open up a new ‘window’ –
associated with its own entry on the Session Table
(i.e. a new Session No.). Once the user has finished
Group processing, the window should be closed and
the Session Record deleted.

(i) If either the ‘Maintain Group’, ‘Group


Enquiry’ or ‘Add to Non-Aggregate
Group’ options were selected, call CICS
transaction LY01 (see Appendix C.1) to set
up a new Session Record for the Grouping
session - using Commarea C071 (see
Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user

David Willcocks 210 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iv) On selection of ‘Add to Aggregate


Group’, call CICS transaction LY01
(see Appendix C.1) to add the OSND’s
associated with this claim to an Aggregate
group – using COMMAREA C014 (see
Appendix D).

On return, check the C014-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the OSND’s
have been added to. (see Appendix G)

(v) On selection of ‘Create Non-Aggregate


Group’, call CICS transaction LY01 (see
Appendix C.1) to add the current claim
to a Non-Aggregate group – using
COMMAREA C015 (see Appendix D).

On return, check the C015-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the claim has
been added to. (see Appendix G)

(vi) On selection of the ‘Add to Non-


Aggregate Group’ option, open new
window, navigating user to ‘Group Enquiry’
screen (see Section 4.28) (a new SESSION-
NO is associated with this window – this
will have been returned by previous
transaction, LY71)

Notes When user clicks on the ‘NOTES’ option at the top Command
of the screen, the following options should be
available on a sub-menu:-
Security Notes

David Willcocks 211 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Claim Notes
Loss Details
Policy Details
Formatted Narrative (FMT)
EURO Conversion Narrative (FME)
Broker Additional Details
Broker Aggregate Details
Slip Lead Comments
Lead Comments
Lead Additional Details

User should select one of these options.

(i) Whichever option is selected, call CICS


transaction LY01 (see Appendix C.1) to
check whether the selected narrative is
present or not, and return any narrative
present, using COMMAREA C088 (see
Appendix D). N.B. Set C088-FIRST-
CALL to ‘Y’. This call will return lines
1 to 300.

On return, check the C088-PROG


-STATUS and report any errors in the
usual way.

(ii) If no errors returned from the first


LY88 call and C088-MORE-LINES is
set to ‘Y’, call CICS transaction LY01
(see Appendix C.1) to check whether
the selected narrative is present or not,
and return any narrative present, using
COMMAREA C088 (see Appendix D).
N.B. Set C088-FIRST-CALL to ‘N’.
This call will return lines 301 to 600.

On return, check the C088-PROG


-STATUS and report any errors in the
usual way.

(iii) If no errors found in LY88, the user


should be navigated to the Narrative
Screen (see Section 4.35)

Note:- the Narrative screen should be opened up as


a new window, overlaying whichever screen the
user is currently processing. Once the user has
finished enquiring on or updating the narrative, the

David Willcocks 212 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
window should be closed and the user will be
returned to whichever screen they were processing
originally.

History When the user ‘clicks’ on this option they should be Command
navigated to the ‘Transaction History’ screen.

Note:- ‘Clicking’ on the ‘History’ option should


open up a new ‘window’ – associated with its own
entry on the Session Table (i.e. a new Session No.).
Once the user has finished browsing through
history, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
History session - using Commarea C068
(see Appendix D).

On return, check the C068-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) Open new window, navigating user to


‘Transaction History’ screen (see Section
4.25) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY68)

Functions When user clicks on the ‘FUNCTIONS’ option at Command


the top of the screen, the following options should
be available on a sub-menu:-
1.Create Subsequent Advice
2.Create Rate of Exchange Adjustment
3.Create Contra Correction
4.Add Take Down Numbers
5. ‘CLASS for Lloyds’ Response
6. Set Diary Date
7. Create Bulk/CCS Correction
8. Set ‘File Last Seen’ Date
9. Reset Claim Transaction
10. Create Re-advice

User should select one of these options:-

‘Create Subsequent Advice’ selected

If the user selects ‘Create Subsequent Advice

David Willcocks 213 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(Single B/down)’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C020. (see Appendix D).
N.B. Ensure that C020-TRANS-TYPE is set to ‘V’
(Validation Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned from the first call to LY20,


call CICS transaction LY01 (see Appendix C.1) to
‘construct’ the skeleton subsequent transaction –
using COMMAREA C020. (see Appendix D). N.B.
Ensure that C020-TRANS-TYPE is set to ‘U’
(Update Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Claim Transaction Creation screen’ – rebuilding it
from scratch – as field protection will be
different and some field contents may be different.

‘Create Rate of Exchange Adjustment’ selected

If the user selects ‘Create Rate of Exchange


Adjustment’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C021. (see Appendix D).

On return, check the C021-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Rate of
Exchange Adjustment (see Section 4.29).

‘Create Contra Correction’ selected

If the user selects ‘Create Contra Correction’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C022. (see Appendix D).

On return, check the C022-PROG-STATUS and


report any errors/warnings in the usual way.

David Willcocks 214 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Contra
Correction (see Section 4.30).

‘Add Take Down Numbers’ selected

If the user selects ‘Add Take Down Numbers’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C023. (see Appendix D).

On return, check the C023-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘Settlement Summary’ (see Section
4.22).

‘CLASS for Lloyds’ Response selected

If the user selects ‘CLASS for Lloyds Response’,


call CICS transaction LY01 (see Appendix C.1) to
check that the claim transaction is a ‘CLASS for
Lloyds’ claim and that it requires authorisation –
using COMMAREA C083. (see Appendix D).

On return, check the C083-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘CLASS for Lloyds Response’
screen (This function will not be available in Phase
1)

‘Set Diary Date’ selected

If the user selects the ‘Set Diary Date’ option, the


‘Set Diary Date’ pop-up window should be
displayed to them (see Section 4.34).

‘Create Bulk/CCS Correction’ selected

This is a special correction facility for use only by


authorised technicians. It allows correction of Bulk
Components, converted bulks and pre-
redenomination transactions. The difference
between this type of correction and Contra

David Willcocks 215 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Corrections is that the user has the ability to enter a
treasury rate.

If the user selects ‘Create Bulk/CCS Correction’,


call CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C090. (see Appendix D).

On return, check the C090-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Bulk/
CCS Correction (see Section 4.36).

‘Set File Last Seen Date’ selected

This function allows the user to set the File Last


Seen Date to todays date and generate an advice to
the syndicates without creating a new claim
movement.

If this function is selected, display the ‘File Seen


Confirmation’ window (see Appendix S.2). If the
technician presses ‘YES’ in this window, call CICS
transaction LY01 (see Appendix C.1) to perform
any validation necessary and set up the necessary
logging records – using COMMAREA C096. (see
Appendix D).

On return, check the C096-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up confirmation


window should be displayed (see Appendix S.3.)
for information purposes only.

‘Reset Claim Transaction’ selected

This function will reset the status of a previously


released claim transaction to allow it to be updated
by the claim technician. This will not be allowed if
the claim transaction has been fully advised or if a
subsequent transaction exists within the claim.

(i) Call CICS transaction LY01 (see


Appendix C.1), passing the Commarea
C105 (see Appendix D). This will

David Willcocks 216 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
validate that that the claim transaction
is eligible for update and, if so, reset the
status accordingly.

On return check the Program Status and


report any errors/warnings in the usual
way.

(ii) If no errors returned from LZ06, call


LY01 using Commarea C037 to obtain
the data and field protection for the
current screen.

On return check the Program Status and


report any errors/warnings in the usual
way.

(iii) Rebuild the current screen using the


data returned in the C037 Commarea.

‘Create Re-advice’ selected

This function will allow the user to create a re-


advice of the most recent movement on the claim –
changing only the current narrative.

(i) call CICS transaction LY01 (see Appendix C.1)


to perform any validation necessary – using
COMMAREA C110. (see Appendix D).

On return, check the C110-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Create Re-Advice’ screen (see Section 4.39).

David Willcocks 217 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B. Navigation Options (Left of Screen) - COMMANDS

If user clicks on the ‘Option Button’ alongside any of the Options on the Navigation Bar, refer to table
returned by transaction LY12 (Build Navigation Bar) in the C012 Commarea. This table should be
stored after building the navigation bar on first entry to the screen for use when the user selects one of
the options on the Navigation Bar.

(i) If C037-SCREEN-MODE = ‘U’ (Update), call CICS transaction LY01 (see Appendix C.1) to
validate that any details entered on the screen are valid – using Commarea C038 (see
Appendix D).

On return, check the C038-PROG-STATUS and report any errors/warnings in the usual way.

(ii) If C037-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY38, Call CICS
transaction LY01 (see Appendix C.1) to update the database with the details entered on the
screen – using COMMAREA C039. (see Appendix D).

On return, check the C039-PROG-STATUS and report any errors/warnings in the usual way.

(iii) If C037-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY39, call CICS
transaction LY01 (see Appendix C.1) – using COMMAREA C046 (see Appendix D) – to
check whether currency/transaction validation needs to be performed. (N.B. the key values
returned from LY12 and stored in the C012-KEY table – for the line on the navigation bar
selected - should be passed in the C046 commarea).

On return, check the C046-PROG-STATUS and report any errors/warnings in the usual way.

(iv) If no errors returned from LY46 or C037-SCREEN-MODE = ‘E’ (Enquiry), Call CICS
transaction LY01 (see Appendix C.1) to update the Session Record (VCLSESA1) –using
COMMAREA C010. (see Appendix D), (N.B. the key values returned from LY12 and stored
in the C012-KEY table – for the line on the navigation bar selected - should be passed in the
C010 commarea).

On return, check the C010-PROG-STATUS and report any errors/warnings in the usual
way.

(v) If no errors are returned from LY10, the user should be navigated to the screen indicated by
C012-SCREEN-ID for the line in the navigation bar selected. (see Appendix N)

David Willcocks 218 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C. Fields (Main Screen)

N.B. Alphanumeric fields must not contain any characters that are not supported by the EDI message
systems, as these may cause brokers and/or syndicates systems to fall over. Valid ASCII Characters are
as follows:-
space, 0-9, A-Z, a-z, ',', '.', '-', '(', ')', '/', '=', ''', '*','+', ':', '?', '!','"', '%','&', ';','<', '>'.

N.B.2. Pre-population of the fields with values returned from LIDS does not need to be handled by
the GUI, as these values will have been loaded onto the database by the ‘Claim Creation Screen
D/B Update’ module (LY27).

N.B.3 Field Protection will be handled by the ‘Field Attributes’ returned in the C037 Commarea.

N.B.4 If any errors are encountered, highlight any field(s) in error by setting the text colour to red.

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric


to claims that are created by internal technicians. It Only Field (17 Chars)
will always be present for internally created claims,
but not for claims created by the broker on the
‘CLASS for Lloyds’ system.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

UCR The Unique Claim Reference. This will always be Display Alphanumeric
present for claims created by the broker on the Only Field (17 Chars)
‘CLASS for Lloyds’ system, but may or may not be
present for internally created claims – depending on
whether the broker has quoted it on the claim file.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

TR Transaction Reference. Uniquely identifies a Display Alphanumeric


particular transaction within a claim. Only Field (17 chars)

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’
OSND1 Original Signing Number and date (for the first Display Alphanumeric
currency on the claim) Only Field (15 Chars)
OSND2 Original Signing Number and date (for the second Display Alphanumeric

David Willcocks 219 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
currency on the claim) Only Field (15 Chars)
OSND3 Original Signing Number and date (for the third Display Alphanumeric
currency on the claim) Only Field (15 Chars)
Current The Current Broker (i.e. the broker who submitted Display Alphanumeric
Bkr this claim transaction). Only Field (4 chars)
Signed Signed Indicator. This indicates whether or not the Display N/a
(Y/N) risk against which this claim is being made has been Only
signed or not. Tick-Box
Peer This indicates whether the claim is subject to peer Display Alphanumeric
Review review. Only (1 Char)
Field
Payee This is the code that identifies the broker to which Mandatory Numeric
Broker the money is to be paid. Field 9(4)

If the claim was entered on the ‘CLASS for Lloyds’


system, this will be set to the broker who raised the
claim.

If this claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected.

If the code is entered by the technician on an


internally created claim, it should be validated
against the Broker Code table (TGLBKRA). If not
present on this table, display the error E076 (see
Appendix E) in the Error Window (see Appendix
B).

Payee This is the three character pseudonym for the broker Optional Alphanumeric
Broker code entered in the Payee Broker field. Field (3 chars)
Pseudony
m If the claim transaction was entered by the broker
on the ‘CLASS for Lloyds’ system, this field is not
required and will be protected.

If unprotected, and the Payee Broker Code has been


completed, this field must be entered. If not, display
the error E080 (see Appendix E) in the Error
Window (see Appendix B).

If the Payee Broker Pseudonym is entered by the


technician on an internally created claim, it should
be validated against the Broker Code table
(TGLBKRA). It must equal the value of
TGLBKRA-BKR-PSEUD associated with the
Payee Broker Code. If not, display the error E077

David Willcocks 220 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(see Appendix E) in the Error Window (see
Appendix B).

Re- This Field indicates that the claim has been re- Optional Alphanumeric
denominat denominated at some stage in the past. Field (1 Char)
ion
Indicator If set on an earlier transaction, this box will be set
and protected on the current transaction. If not it
will be unprotected.

For ‘CLASS for Lloyds’ transactions it will always


be protected, but may be ticked if an earlier
internally created transaction re-denominated the
broker created claim.

If set, must be set to ‘S’ (Settlement Currency). It


may be set to ‘B’ on converted claims, but only ‘S’
or spaces is allowed going forward. If entered and
not set to ‘S’, display the error ‘E373’ (see
Appendix E) in the Error Window (see Appendix
B). .

Broker TR For decoupled ECF claims, this field is set to the Conditional Char(17)
equivalent TR on the associated broker UCR. Field

Broker TR For a decoupled ECF claim transaction - Conditional Char(1)


Qual if a Broker TR has not been provided, Field
this qualifier indicates why the TR has
not been entered.

The following values should be included


in the ‘Drop down’ list:

 space
 B - Queried Broker advice
 C – Correction
 D – Direct advice or settlement
 F – First advice with settlement
 I – Individual/Block claim
 O – Other

 V – Various

David Willcocks 221 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Peer The Peer Review Indicator. This field indicates that Mandatory Alphanumeric
Review the claim is subject to peer review. Field (1 Char)

This field should be associated with a drop down


list with the following values:-

'N' - process only


'D' - delegated lead with peer review
'F' - delegated lead with processing for following
market
'Y' - Peer Review

Original The Original (or Estimate) currency that applies to Mandatory Alphanumeric
Currency this claim transaction. Field (3 chars)

This can either be entered by the broker on the


‘CLASS for Lloyds’ system or by internal
technicians.

If the claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected.

The Original Currency must exist on the Currency


Code table (TGLCURA). If not, display the error
E078 (see Appendix E) in the Error Window (see
Appendix B).

Further, more detailed, validation will be carried out


using the ‘EURO Modules’ called by the ‘Financial
Details Control Screen Validation’ transaction.

Paid To The Paid To Date amount is the sum of all Display Numeric
Date previously settled amounts and the Paid This Time Only Field -(13)9.99
Amount amount on the current transaction. It is a 100%
amount.

It will be initialised to the value held on the


previous transaction for this currency.

The broker is able to enter this field on the ‘CLASS


for Lloyds’ system. If not as expected, a warning is
issued – but technicians should be aware that the
Paid To Date may not be correct for ‘CLASS for
Lloyds’ transactions. If technicians believe the
figure should be corrected, they must contact the
broker and get them to resubmit the transaction.

David Willcocks 222 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Format:- --,---,---,---,--9.99

Paid This This is the amount (in Original Currency) to be Optional Numeric
Time settled on the current claim transaction. It is a 100% Field -(13)9.99
Amount amount.

For claim transactions entered by the broker on the


‘CLASS for Lloyds’ system it will be protected. If
technicians believe the figure to be incorrect, they
must ask the broker to correct it and resubmit the
transaction.

Format:- --,---,---,---,--9.99

Outstandi This is the amount (in Original Currency) Optional Numeric


ng outstanding on the current claim. It is a 100% Field -(13)9.99
Amount amount.

For claim transactions entered by the broker on the


‘CLASS for Lloyds’ system it will be protected. If
technicians believe the figure to be incorrect, they
must ask the broker to correct it and resubmit the
transaction.

Format:- --,---,---,---,--9

Outstandi This is the qualifier associated with the Outstanding Optional Alphanumeric
ng Amount. Field (1 Char)
Amount
Qualifier This field can be entered by the technician or pre-
populated with details supplied by the broker. Any
value entered on this screen must apply to all
breakdowns within this currency.

If the Total Outstanding Amount is equal to zero,


this field must not be spaces. If it is, highlight the
field and display the error ‘E087’ (see Appendix E)
in the Error Window (see Appendix B).

Valid Values are:-


(i) ‘E’ = Expense
(ii) ‘T’ = TBA
(iii) ‘F’ = Fee
(iv) ‘N’ = Nil
(v) ‘R’ = Recovery
(vi) ‘S’ = Subrogation
(vii) ‘V’ = Salvage
(viii) ‘Z’ = Zero recommended reserve.

David Willcocks 223 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(ix) ‘C’ = Closed

If the user enters a value other than the above,


highlight the field and display the error ‘E088’ (see
Appendix E) in the Error Window (see Appendix
B).

Settlemen The Settlement Currency that applies to this claim Optional Alphanumeric
t Currency transaction. Field (3 chars)

This can either be entered by the broker on the


‘CLASS for Lloyds’ system or by internal
technicians.

If the claim transaction was entered by the broker


on the ‘CLASS for Lloyds’ system, this field will be
protected.

The Settlement Currency must exist on the


Currency Code table (TGLCURA). If not, display
the error E079 (see Appendix E) in the Error
Window (see Appendix B).

Further, more detailed, validation will be carried out


using the ‘EURO Modules’ called by the ‘Financial
Details Control Screen Validation’ transaction.

Settlemen The user should tick this box if any of the Optioal N/a
t Indicator breakdowns within this currency are to include Tick-Box
settlement.
Settlemen The Rate of Exchange between the Original and Optional Numeric
t Rate of Settlement currencies that applies to this claim. Field Z(6)9.9(5)
Exchange
A warning will be issued if this rate of exchange is
not equal to the Rate of Exchange held on the
Currency table (within a tolerance).

This value can either be entered by the broker on


‘CLASS for Lloyds’ transactions or by Xchanging
technicians on internally created claims.

If entered by the broker on ‘CLASS for Lloyds’ it


will be protected. If the technician believes that the
wrong Rate of Exchange has been used, they will
need to contact the broker and get the broker to
correct the rate and resubmit the claim entry.

David Willcocks 224 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

Format:- ZZ,ZZ9.9999999

Settled in This is the 100% Paid This Time Amount converted Display Numeric
Settlemen into the Settlement currency. It is shown here for Only Field -(13)9.99
t Currency display purposes only. The reason being that the
broker enters this amount on the ‘CLASS for
Lloyds’ system. Therefore, for ‘CLASS for Lloyds’
claims, the technician will need to ensure that the
Settlement Amounts entered on the breakdowns
total the amount supplied by the broker. This field is
displayed here for this reason.

Format:- --,---,---,---,--9.99

Total Line This is the Total Bureau Line that is to be applied to Display Numeric
the 100% Settlement Amount in order to obtain the Only Field Z(2)9.9(5)
Bureau Proportion Amount. It is shown here for
display purposes only.

Format:- ZZ9.9999999

Bureau This is the Bureau proportion of the 100% Optional Numeric


Proportion Settlement Amount (in Settlement Currency). Field -(13)9.99
Amount
This is entered as a control and is only enterable for
internally created claims.

For claim transactions that have been created by the


broker on the ‘CLASS for Lloyds’ system, this field
will be calculated and displayed on this screen
(protected).

Format:- --,---,---,---,--9.99

100% VAT This field represents that part of the 100% Claim Optional Numeric
Amount Amount (Paid This Time), in Settlement Currency, Field -(13)9.99
that is VAT.

The VAT Amount can be entered by the broker on


‘CLASS for Lloyds’. However, they do not always
do so reliably. It is possible for the ‘CLASS for
Lloyds’ authorisers to update the VAT entered by
the broker when they authorise the claim.
Xchanging technicians supplementing the claim
details on the GUI should also be able to update the
VAT amount. Therefore, this field will be
unprotected regardless of whether an internal claim

David Willcocks 225 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
transaction is being created or a ‘CLASS for
Lloyds’ transaction is being supplemented.

Format:- --,---,---,---,--9.99

War War Amount (in Settlement). Optional Numeric


Amount Field -(13)9.99
This cannot be entered by the broker on ‘CLASS
for Lloyds’. It will therefore be unprotected,
regardless of whether the technician is creating a
new transaction or supplementing a broker-created
transaction.

Format:- --,---,---,---,--9.99

Incurred The Incurred Amount (or Current Estimate). Optional Numeric


Amount Field -(13)9.99
This represents the sum of the Paid To Date and
Outstanding Amounts.

For internally created claims, this is entered for


control purposes and must be equal to the ‘Paid To
Date Amount’ plus the ‘Outstanding Amount’.

For claim transactions that have been entered by the


broker on the ‘CLASS for Lloyds’ system, this field
should be derived and protected.

Format:- --,---,---,---,--9.99

D. Commands - (Main Screen)


Save This key allows the user to save the details they Command
have entered on the screen without being navigated
onto a different screen. Note:- this button should be
disabled if the screen is being viewed in ‘Enquiry’
mode (i.e. C037-SCREEN-MODE = ‘E’)

(i) Call CICS transaction LY01 (see Appendix


C.1) to validate that any details entered on
the screen are valid – using Commarea
C038 (see Appendix D).

On return, check the C038-PROG-STATUS


And report any errors/warnings in the usual
Way.

(ii) If no errors returned from LY38, Call CICS

David Willcocks 226 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C039.
(see Appendix D).

On return, check the C039-PROG-STATUS


and report any errors/warnings in the usual
way.

Continue (i) If C037-SCREEN-MODE = ‘U’(Update), Command


call CICS transaction LY01 (see Appendix
C.1) to validate that any details entered on
the screen are valid – using Commarea
C038 (see Appendix D).

On return, check the C038-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) If C037-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY38, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C039. (see Appendix D).

On return, check the C039-PROG-STATUS


and report any errors/warnings in the usual
way.

(iii) If no errors returned from LY39 or C037-


SCREEN-MODE = ‘E’(Enquiry), call the
CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(iv) Navigate the user to whichever program is


identified in C011-NEXT-PROGRAM (see
Appendix N).

Cancel When the technician presses the ‘Cancel’ button, Command


any changes made since the last ‘Save’ will be

David Willcocks 227 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
removed. The technician will remain in the
‘Financial Details Control’ screen. Therefore:-

(i) Call the CICS transaction LY01 (see


Appendix C.1) – using COMMAREA C037
(see Appendix D) . This transaction will
return the data that should appear on this
screen.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(ii) Rebuild the screen, based on the data


returned in the C037 Commarea.

EXIT This will return the user to whichever screen they Command
initiated the claim from.

(i) Call CICS transaction LY01 (see Appendix C.1)


to check the status of the current transaction –
using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B). If status is zero,
continue at (iv)

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before being navigated to the next
screen. Display the ‘Claim Transaction Options’
pop-up window detailed in Section 4.10 and
perform processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user should be
left in the current screen.

(iv) If the user did not press ‘Cancel’ or zero


Program Status returned from LY16,
Call the CICS transaction LY01 (see Appendix
C.1) – using COMMAREA C011 (see
Appendix D). This will invoke the ‘Navigation’
program, which decides on the next program the
user should be navigated to. (Note: the
C011-EXIT-IND should be set to ‘Y’)

David Willcocks 228 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

On return, check the Program Status in the Usual


way, reporting errors if they exist in The Error
Screen (see Appendix B)

(v) If no errors returned from LY11, navigate the


user to the program indicated by
C011-NEXT-PROGRAM (see Appendix N).
If C011-NEXT-PROGRAM is set to 'NONE',
the current window should be closed.

David Willcocks 229 May 2002


Xchanging Ins-sure Services Ltd
4.16. Loss Reserve Details Screen

4.16.1. Screen Layout

Below is a ‘mock-up’ of the Loss Reserve Details Screen.

4.16.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY10 Update Session Record
LY11 Navigation Program
LY12 Build Screen Navigation Bar
LY14 Add OSND(s) to Aggregate Group
LY15 Create Non-Aggregate Group
LY16 Check Transaction Status
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY40 Build Single Claim Loss Reserve
Screen
LY41 Single Claim Loss Reserve Screen
Validation
LY42 Single Claim Loss Reserve Screen D/B
Update

David Willcocks 230 May 2002


Xchanging Ins-sure Services Ltd
Tran Program Description
s. Name
Id.
LY46 Check whether Currency/Transaction
Validn. reqd.
LY68 Create History Session Record
LY71 Set up Group Session Record
LY88 Build Narrative Details Screen
LY90 Bulk/CCS Correction Initial Validation
LY96 Set File Last Seen Date
LZ06 Reset Claim Transaction
LZ10 Allow Creation of New Movement
LZ11 Create Re-Advice – Initial Validation

4.16.3. Field/Command Derivation

The fields and the navigation bar on this screen will be


derived as follows:-

Field Type Source


A. Navigation Bar
Navigation Bar Comman call the CICS transaction LY01 (see Appendix
d(s) C.1) – using COMMAREA C012 (see Appendix
D) . This will determine what should appear on
the ‘Screen Navigation Bar’ at the left hand side
of the screen.

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

See Appendix F for details of how to process the


information returned from this CICS transaction.

B. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C040 (see
Appendix D) . This transaction will return the data that should appear on this screen.

On return, check the Program Status in the usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

XCR Field C040-XCR


(This field should be protected)
UCR Field C040-UCR

David Willcocks 231 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
(This field should be protected)
TR Field C040-TR
(This field should be protected)
OSND Field C040-ORIG-REF
(This field should be protected)

Current Bkr Field C040-ORIG-BKR


(This field should be protected)
Signed Tick-Box C040-SIGNED-IND
(This field should be protected)
Peer Review Field C040-PEER-REV-IND
(This field should be protected)
Original Field C040-ORIG-CURR
Currency (This field should be protected)
Claims Office Field C040-COR
Reference (This field should be protected)
(COR)
Letter of Credit Tick-Box C040-LOC-IND
Indicator (This field should be protected)
Movement Field C040-MOVE-REF
Reference / (This field should be protected)
Date
Loss Reserve Field C040-LR-ADJ-DATE
Adjustment as ( If C040-LR-ADJ-DATE-ATTR = ‘P’, this
at (date) field should be protected)
Refunded Loss Field C040-LR-REFUNDED
Reserve (If C040-LR-REFUND-ATTR = ‘P’, this
field should be protected)
Paid Claim Field C040-LR-PAID-CLAIM
(If C040-LR-PD-CLM-ATTR = ‘P’, this
field should be protected)
Loss Reserve Field C040-LR-ADVANCED
Advanced (If C040-LR-ADV-ATTR = ‘P’, this field
should be protected)
Interest Field C040-LR-INTEREST
(If C040-LR-INT-ATTR = ‘P’, this field
should be protected)
Tax Field C040-LR-TAX
(If C040-LR-TAX-ATTR = ‘P’, this field
should be protected)
Net Amount Field C040-LR-NET-AMT
(If C040-LR-NET-ATTR = ‘P’, this field
should be protected)
Outstanding Field C040-LR-OUTST-AMT

David Willcocks 232 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Amount (If C040-LR-OUTST-ATTR = ‘P’, this
field should be protected)
Outstanding Field C040-LR-OUTST-QUAL
Amount (If C040-LR-OUTST-QL-ATTR = ‘P’, this
Qualifier field should be protected)

C. Commands
Create New Comman If C040-NEW-MOVE-ATTR = ‘P’, this
Movement d button should not be displayed

4.16.4. Process Description

This screen is the Single Claim Loss Reserve Screen.


This screen is only displayed for Loss Reserves (as
indicated by the user on the ‘Claim Creation’ screen).

Loss reserves are a means of pre-funding claims. They


are only used with convertible currency non-marine
claims. An amount of money is advanced to a (usually)
overseas intermediary out of which claims and
expenses may be paid. Interest earned by the money
may be payable to the underwriters or used to reduce
the amount collected from underwriters.

This screen will be displayed prior to each ‘SCM Advice


Screen’ for a particular claim (i.e. once for each
breakdown on the claim). The details on the screen are
not entered by the broker on ‘CLASS for Lloyds’ and
will not therefore be pre-filled on ‘CLASS for Lloyds’
claims. The Xchanging technician must fill in the
required fields before proceeding to the ‘SCM Advice’
screen. The fields entered on this screen will then be
used to calculate and pre-fill the amounts on the ‘SCM
Advice’ screen.

David Willcocks 233 May 2002


Xchanging Ins-sure Services Ltd
Fig 4.16.4.1. Field/Command Processing for ‘Single Claim Loss
Reserves’ Screen

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D) to log-
off the system and delete the Session Record.

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

(ii) if set to zero, close all windows.

Create New (i) Call CICS transaction LY01 (see Appendix


Claim C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session

David Willcocks 234 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Create Claim
Screen’ (see Section 4.4)

Find Claim (i) Call CICS transaction LY01 (see Appendix


C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in

David Willcocks 235 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the


‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Find Claim’ Screen
(see Section 4.5)

Account Link to Account Enquiry (method needs to be Command


Enquiry identified)

Repository Link to Repository (method needs to be identified) Command

Data Link to Data Warehouse (method needs to be Command


Warehouse identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry
Add to Aggregate Group
Create Non-Aggregate Group
Add to Non-Aggregate Group

User should select one of these options.

Note:- ‘Clicking’ on the ‘Maintain Group’,


‘Group Enquiry’ or ‘Add to Non-Aggregate
Group’ options should open up a new ‘window’ –
associated with its own entry on the Session Table
(i.e. a new Session No.). Once the user has finished
Group processing, the window should be closed and
the Session Record deleted.

David Willcocks 236 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(i) If either the ‘Maintain Group’, ‘Group


Enquiry’ or ‘Add to Non-Aggregate
Group’ options were selected, call CICS
transaction LY01 (see Appendix C.1) to set
up a new Session Record for the Grouping
session - using Commarea C071 (see
Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iv) On selection of ‘Add to Aggregate


Group’, call CICS transaction LY01
(see Appendix C.1) to add the OSND’s
associated with this claim to an Aggregate
group – using COMMAREA C014 (see
Appendix D).

On return, check the C014-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the OSND’s
have been added to. (see Appendix G)

(v) On selection of ‘Create Non-Aggregate


Group’, call CICS transaction LY01 (see
Appendix C.1) to add the current claim
to a Non-Aggregate group – using
COMMAREA C015 (see Appendix D).

David Willcocks 237 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

On return, check the C015-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the claim has
been added to. (see Appendix G)

(vi) On selection of the ‘Add to Non-


Aggregate Group’ option, open new
window, navigating user to ‘Group Enquiry’
screen (see Section 4.28) (a new SESSION-
NO is associated with this window – this
will have been returned by previous
transaction, LY71)

Notes When user clicks on the ‘NOTES’ option at the top Command
of the screen, the following options should be
available on a sub-menu:-
Security Notes
Claim Notes
Loss Details
Policy Details
Settlement Narrative
EURO Conversion Narrative (FME)
Broker Additional Details
Broker Aggregate Details
Slip Lead Comments
Lead Comments
Lead Additional Details

User should select one of these options.

(i) Whichever option is selected, call CICS


transaction LY01 (see Appendix C.1) to
check whether the selected narrative is
present or not, and return any narrative
present, using COMMAREA C088 (see
Appendix D). N.B. Set C088-FIRST-
CALL to ‘Y’. This call will return lines
1 to 300.

On return, check the C088-PROG


-STATUS and report any errors in the
usual way.

David Willcocks 238 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(ii) If no errors returned from the first
LY88 call and C088-MORE-LINES is
set to ‘Y’, call CICS transaction LY01
(see Appendix C.1) to check whether
the selected narrative is present or not,
and return any narrative present, using
COMMAREA C088 (see Appendix D).
N.B. Set C088-FIRST-CALL to ‘N’.
This call will return lines 301 to 600.

On return, check the C088-PROG


-STATUS and report any errors in the
usual way.

(iii) If no errors found in LY88, the user


should be navigated to the Narrative
Screen (see Section 4.35)

Note:- the Narrative screen should be opened up as


a new window, overlaying whichever screen the
user is currently processing. Once the user has
finished enquiring on or updating the narrative, the
window should be closed and the user will be
returned to whichever screen they were processing
originally.

History When the user ‘clicks’ on this option they should be Command
navigated to the ‘Movement History’ screen.

Note:- ‘Clicking’ on the ‘History’ option should


open up a new ‘window’ – associated with its own
entry on the Session Table (i.e. a new Session No.).
Once the user has finished browsing through
history, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
History session – using Commarea C068
(see Appendix D).

On return, check the C068-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) Open new window, navigating user to


‘Movement History’ screen (see Section
4.26) (a new SESSION-NO is associated

David Willcocks 239 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
with this window – this will have been
returned by previous transaction, LY68)

Functions When user clicks on the ‘FUNCTIONS’ option at Command


the top of the screen, the following options should
be available on a sub-menu:-
1.Create Subsequent Advice
2.Create Rate of Exchange Adjustment
3.Create Contra Correction
4.Add Take Down Numbers
5. Set Diary Date
6. Create Bulk/CCS Correction
7. Set ‘File Last Seen’ Date
8. Reset Claim transaction
9. Create Re-advice

User should select one of these options:-

‘Create Subsequent Advice’ selected

If the user selects ‘Create Subsequent Advice


(Single B/down)’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C020. (see Appendix D).
N.B. Ensure that C020-TRANS-TYPE is set to ‘V’
(Validation Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned from the first call to LY20,


call CICS transaction LY01 (see Appendix C.1) to
‘construct’ the skeleton subsequent transaction –
using COMMAREA C020. (see Appendix D). N.B.
Ensure that C020-TRANS-TYPE is set to ‘U’
(Update Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Claim Transaction Creation screen’ – rebuilding it
from scratch – as field protection will be
different and some field contents may be different.

‘Create Rate of Exchange Adjustment’ selected

David Willcocks 240 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

If the user selects ‘Create Rate of Exchange


Adjustment’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C021. (see Appendix D).

On return, check the C021-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Rate of
Exchange Adjustment (see Section 4.29).

‘Create Contra Correction’ selected

If the user selects ‘Create Contra Correction’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C022. (see Appendix D).

On return, check the C022-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Contra
Correction (see Section 4.30).

‘Add Take Down Numbers’ selected

If the user selects ‘Add Take Down Numbers’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C023. (see Appendix D).

On return, check the C023-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘Settlement Summary’ (see Section
4.22).

‘Set Diary Date’ selected

If the user selects the ‘Set Diary Date’ option, the


‘Set Diary Date’ pop-up window should be
displayed to them (see Section 4.34).

David Willcocks 241 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
‘Create Bulk/CCS Correction’ selected

This is a special correction facility for use only by


authorised technicians. It allows correction of Bulk
Components, converted bulks and pre-
redenomination transactions. The difference
between this type of correction and Contra
Corrections is that the user has the ability to enter a
treasury rate.

If the user selects ‘Create Bulk/CCS Correction’,


call CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C090. (see Appendix D).

On return, check the C090-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Bulk/
CCS Correction (see Section 4.36).

‘Set File Last Seen Date’ selected

This function allows the user to set the File Last


Seen Date to todays date and generate an advice to
the syndicates without creating a new claim
movement.

If this function is selected, display the ‘File Seen


Confirmation’ window (see Appendix S.2). If the
technician presses ‘YES’ in this window, call CICS
transaction LY01 (see Appendix C.1) to perform
any validation necessary and set up the necessary
logging records – using COMMAREA C096. (see
Appendix D).

On return, check the C096-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up confirmation


window should be displayed (see Appendix S.3.)
for information purposes only.

‘Reset Claim Transaction’ selected

This function will reset the status of a previously


released claim transaction to allow it to be updated

David Willcocks 242 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
by the claim technician. This will not be allowed if
the claim transaction has been fully advised or if a
subsequent transaction exists within the claim.

(i) Call CICS transaction LY01 (see


Appendix C.1), passing the Commarea
C105 (see Appendix D). This will
validate that that the claim transaction
is eligible for update and, if so, reset the
status accordingly.

On return check the Program Status and


report any errors/warnings in the usual
way.

(ii) If no errors returned from LZ06, call


LY01 using Commarea C040 to obtain
the data and field protection for the
current screen.

On return check the Program Status and


report any errors/warnings in the usual
way.

(iii) Rebuild the current screen using the


data returned in the C040 Commarea.

‘Create Re-advice’ selected

This function will allow the user to create a re-


advice of the most recent movement on the claim –
changing only the current narrative.

(i) call CICS transaction LY01 (see Appendix C.1)


to perform any validation necessary – using
COMMAREA C110. (see Appendix D).

On return, check the C110-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Create Re-Advice’ screen (see Section 4.39).

David Willcocks 243 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B. Navigation Options (Left of Screen) - COMMANDS

If user clicks on the ‘Option Button’ alongside any of the Options on the Navigation Bar, refer to table
returned by transaction LY12 (Build Navigation Bar) in the C012 Commarea. This table should be
stored after building the navigation bar on first entry to the screen for use when the user selects one of
the options on the Navigation Bar.

(i) If C040-SCREEN-MODE = ‘U’ (Update), call CICS transaction LY01 (see Appendix C.1) to
validate that any details entered on the screen are valid – using Commarea C041 (see
Appendix D).

On return, check the C041-PROG-STATUS and report any errors/warnings in the usual way.

(ii) If C040-SCREEN-MODE = ‘U’ and no errors returned from LY41, Call CICS transaction
LY01 (see Appendix C.1) to update the database with the details entered on the screen – using
COMMAREA C042. (see Appendix D).

On return, check the C042-PROG-STATUS and report any errors/warnings in the usual way.

(iii) If no errors returned from LY42 or SCREEN-MODE = ‘E’ (Enquiry), call CICS
transaction LY01 (see Appendix C.1) – using COMMAREA C046 (see Appendix D) – to
check whether currency/transaction validation needs to be performed. (N.B. the key values
returned from LY12 and stored in the C012-KEY table – for the line on the navigation bar
selected - should be passed in the C046 commarea).

On return, check the C046-PROG-STATUS and report any errors/warnings in the usual way.

(iv) If no errors returned from LY46, Call CICS transaction LY01 (see Appendix C.1) to update
the Session Record (VCLSESA1) –using COMMAREA C010. (see Appendix D), (N.B. the
key values returned from LY12 and stored in the C012-KEY table – for the line on the
navigation bar selected - should be passed in the C010 commarea).

On return, check the C010-PROG-STATUS and report any errors/warnings in the usual
way.

(v) If no errors are returned from LY10, the user should be navigated to the screen indicated by
C012-SCREEN-ID for the line in the navigation bar selected. (see Appendix N)

David Willcocks 244 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C. Fields (Main Screen)

N.B. Alphanumeric fields must not contain any characters that are not supported by the EDI message
systems, as these may cause brokers and/or syndicates systems to fall over. Valid ASCII Characters are
as follows:-
space, 0-9, A-Z, a-z, ',', '.', '-', '(', ')', '/', '=', ''', '*','+', ':', '?', '!','"', '%','&', ';','<', '>'.

N.B.2. Pre-population of the fields with values returned from LIDS does not need to be handled by
the GUI, as these values will have been loaded onto the database by the ‘Claim Creation Screen
D/B Update’ module (LY27).

N.B.3 Field Protection will be handled by the ‘Field Attributes’ returned in the C040 Commarea.

N.B.4 If any errors are encountered, highlight any field(s) in error by setting the text colour to red.

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric


to claims that are created by internal technicians. It Only Field (17 Chars)
will always be present for internally created claims,
but not for claims created by the broker on the
‘CLASS for Lloyds’ system.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

UCR The Unique Claim Reference. This will always be Display Alphanumeric
present for claims created by the broker on the Only Field (17 Chars)
‘CLASS for Lloyds’ system, but may or may not be
present for internally created claims – depending on
whether the broker has quoted it on the claim file.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

TR Transaction Reference. Uniquely identifies a Display Alphanumeric


particular transaction within a claim. Only Field (17 chars)

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’
OSND Original Signing Number and date (for the first Display Alphanumeric
currency on the claim) Only Field (15 Chars)

David Willcocks 245 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Current The Current Broker (i.e. the broker who submitted Display Alphanumeric
Bkr this claim transaction). Only Field (4 chars)
Signed Signed Indicator. This indicates whether or not the Display N/a
(Y/N) risk against which this claim is being made has been Only
signed or not. Tick-Box
Peer This indicates whether the claim is subject to peer Display Alphanumeric
Review review. Only (1 Char)
Field
Original This is the Original currency to which the current Display Alphanumeric
Currency breakdown (SCM Advice) relates. There may be up Only Field (3 Chars)
to three original currencies on a particular CLASS
transaction. However, a particular breakdown will
be associated with only one of these.

This field is part of the header and is protected.


Claims The Claims Office Reference that has been assigned Display Alphanumeric
Office to the current breakdown. This is system generated. Only Field (15 Chars)
Reference
(COR) This field is part of the header and is protected.
LOC The Letter of Credit indicator. Display N/a
indicator Only Tick-
For Letter of Credit transactions, each Claims Box
Office Reference will either be Cash or Letter of
Credit. This ‘tick-box’ indicates whether the current
breakdown is Letter of Credit or not.
Movement The Movement Reference associated with this claim Display Alphanumeric
Reference breakdowm. This field will initially be set to the Only Field (6 Chars)
/ Date movemenet reference brought forward from the
previous transaction. If the user updates any details
for this breakdown, a new movement reference will
be assigned when the claim is released. This will be
displayed on re-entry to the claim for update or
enquiry purposes.

The movement reference should be shown in the


following format:-

XX / MMYY

Loss Loss Reserve Adjustment as at (date). Mandatory Date


Reserve Field
Adjustmen
t as at
(date)
Refunded Amount of loss reserve refunded Optional Numeric
Loss Field -(13)9.99

David Willcocks 246 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Reserve Format:- --,---,---,---,--9.99

Paid Claim Amount of claim paid on loss reserve Optional Numeric


Field -(13)9.99
Format:- --,---,---,---,--9.99

Loss The amount of loss reserve retained this time Optional Numeric
Reserve Field -(13)9.99
Advanced Format:- --,---,---,---,--9.99

Interest Amount of interest on Loss reserve Optional Numeric


Field -(13)9.99
Format:- --,---,---,---,--9.99

Tax Rate of Tax on Loss Reserve Optional Numeric


Field Z(2)9.9(7)
Net The Net Loss Reserve – This is the amount to be Optional Numeric
Amount paid this time for the current breakdown. Field -(13)9.99

Format:- --,---,---,---,--9.99

Outstandi The Outstanding Amount Optional Numeric


ng Field -(13)9.99
Amount Format:- --,---,---,---,--9

Outstandi The Outstanding Amount Qualifier. Optional Alphanumeric


ng Field (1 Char)
Amount Valid Values are:-
Qualifier
T = To Be Advised
R = Recovery
N = Nil O/S & File Closed

If any values other than these are entered, display


the error E188 (see Appendix E) in the Error
Window (see Appendix B).

D. Commands - (Main Screen)


Create New On first entry to the screen, the details will be Command
Movement protected. The user will then need to indicate their
intention of creating a new movement by pressing
the ‘Create New Movement’ button. This will have
the effect of unprotecting the screen.

(i) Call CICS transaction LY01 (see Appendix

David Willcocks 247 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C.1) to open up the screen and allow entry
of a new movement – using Commarea
C109 (see Appendix D).

On return, check the C109-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) Call the CICS transaction LY01 (see


Appendix C.1) – using COMMAREA C040
(see Appendix D) . This transaction will
return the data that should appear on this
screen.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(iii) Rebuild the screen, based on the data


returned in the C040 Commarea.

Save This key allows the user to save the details they Command
have entered on the screen without being navigated
onto a different screen. Note:- this button should be
disabled if the screen is being viewed in ‘Enquiry’
mode (i.e. C040-SCREEN-MODE = ‘E’)

(iv) Call CICS transaction LY01 (see Appendix


C.1) to validate that any details entered on
the screen are valid – using Commarea
C041 (see Appendix D).

On return, check the C041-PROG-STATUS


And report any errors/warnings in the usual
Way.

(v) If no errors returned from LY41, Call CICS


transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C042.
(see Appendix D).

On return, check the C042-PROG-STATUS


And report any errors/warnings in the usual
way.

Continue (vi) If C040-SCREEN-MODE = ‘U’(Update), Command


call CICS transaction LY01 (see Appendix

David Willcocks 248 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C.1) to validate that any details entered on
the screen are valid – using Commarea
C041 (see Appendix D).

On return, check the C041-PROG-STATUS


and report any errors/warnings in the usual
way.

(vii) If C040-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY41, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C042. (see Appendix D).

On return, check the C042-PROG-STATUS


and report any errors/warnings in the usual
way.

(viii) If no errors returned from LY42 or C040-


SCREEN-MODE = ‘E’(Enquiry), call the
CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(ix) Navigate the user to whichever program is


identified in C011-NEXT-PROGRAM (see
Appendix N).

Cancel When the technician presses the ‘Cancel’ button, Command


any changes made since the last ‘Save’ will be
removed. The technician will remain in the ‘Single
Claim Loss Reserve’ screen. Therefore:-

(x) Call the CICS transaction LY01 (see


Appendix C.1) – using COMMAREA C040
(see Appendix D) . This transaction will
return the data that should appear on this
screen.

On return, check the Program Status in the

David Willcocks 249 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(xi) Rebuild the screen, based on the data


returned in the C040 Commarea.

EXIT This will return the user to whichever screen they Command
initiated the claim from.

(i) Call CICS transaction LY01 (see Appendix C.1)


to check the status of the current transaction –
using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B). If status is zero,
continue at (iv)

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before being navigated to the next
screen. Display the ‘Claim Transaction Options’
pop-up window detailed in Section 4.10 and
perform processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user should be
left in the current screen.

(iv) If the user did not press ‘Cancel’ or zero


Program Status returned from LY16,
Call the CICS transaction LY01 (see Appendix
C.1) – using COMMAREA C011 (see
Appendix D). This will invoke the ‘Navigation’
program, which decides on the next program the
user should be navigated to. (Note: the
C011-EXIT-IND should be set to ‘Y’)

On return, check the Program Status in the Usual


way, reporting errors if they exist in The Error
Screen (see Appendix B)

(v) If no errors returned from LY11, navigate the


user to the program indicated by
C011-NEXT-PROGRAM (see Appendix N).
If C011-NEXT-PROGRAM is set to 'NONE',
the current window should be closed.

David Willcocks 250 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

David Willcocks 251 May 2002


Xchanging Ins-sure Services Ltd
4.17. Breakdown - SCM Advice Screen

Change Control Log

Release Date Changed TP No. Description of Changes Made


By
XCS 29/08/2008 DBP TP631646 CR7-FS3:- Change enquiry-only version of screen
CLASS to display Slip Type in the Policy Details area.
Phase 4
XCS 14/10/2008 DBP TP631646 CR8
CLASS
Phase 4

4.17.1. Screen Layout

CR7-FS3:- Change enquiry-only version of screen to display Slip Type in the Policy
Details area.
Below is the Breakdown (SCM Advice) Screen.

The following images are for the UPDATE version:-

David Willcocks 252 May 2002


Xchanging Ins-sure Services Ltd
David Willcocks 253 May 2002
Xchanging Ins-sure Services Ltd
For XCS Phase 4 Service Type shown as a text description has been added to
theClaim Details section of the Enquiry version
of the screen

David Willcocks 254 May 2002


Xchanging Ins-sure Services Ltd
David Willcocks 255 May 2002
Xchanging Ins-sure Services Ltd
The following images are for the ENQUIRY version:-

David Willcocks 256 May 2002


Xchanging Ins-sure Services Ltd
For XCS Phase 4 Service Type shown as a text description has been added to the
Claim Details section of the Enquiry version of the screen

David Willcocks 257 May 2002


Xchanging Ins-sure Services Ltd
For XCS Phase 4 a change has been made to the Enquiry version of the screen to add
a new field Slip Type as shown below:

David Willcocks 258 May 2002


Xchanging Ins-sure Services Ltd
David Willcocks 259 May 2002
Xchanging Ins-sure Services Ltd
4.17.2. CICS Transactions

The following CICS transactions are called by this


program (via GUI/CICS Interface Program).

Tran Program Description


s. Name
Id.
LY04 Log-off
LY10 Update Session Record
LY11 Navigation Program
LY12 Build Screen Navigation Bar
LY14 Add OSND(s) to Aggregate Group
LY15 Create Non-Aggregate Group
LY16 Check Transaction Status
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY43 Build Breakdown (SCM Advice) Screen
LY44 Breakdown (SCM Advice) Screen
Validation
LY45 Breakdown (SCM Advice) Screen D/B
Update
LY46 Check whether Curr/Trans. Validation
Reqd.
LY47 Create New Breakdown
LY68 Create History Session Record
LY71 Set up Group Session Record
LY88 Build Narrative Details Screen
LY90 Bulk/CCS Correction Initial Validation
LY94 Build Commarea for LIDS Interface
LY96 Set File Last Seen Date
LZ06 Reset Claim Transaction
LZ10 Allow Creation of New Movement
LZ11 Create Re-Advice – Initial Validation

4.17.3. Field/Command Derivation

The fields and the navigation bar on this screen will be


derived as follows:-

Field Type Source


David Willcocks 260 May 2002
Xchanging Ins-sure Services Ltd
Field Type Source
Navigation Bar Comman call the CICS transaction LY01 (see Appendix
d(s) C.1) – using COMMAREA C012 (see Appendix
D) . This will determine what should appear on
the ‘Screen Navigation Bar’ at the left hand side
of the screen.

On return, check the Program Status in the usual


way, reporting errors if they exist in the Error
Screen (see Appendix B)

See Appendix F for details of how to process the


information returned from this CICS transaction.

B. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C043 (see
Appendix D) . This transaction will return the data that should appear on this screen.

On return, check the Program Status in the usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

XCR Field C043-XCR


(This field should be protected)
UCR Field C043-UCR
(This field should be protected)
TR Field C043-TR
(This field should be protected)
OSND Field C043-ORIG-REF
(This field should be protected)

Orig. Broker Field C043-ORIG-BKR


(This field should be protected)
Signed Tick-Box Set to ‘TRUE’, if C043-SIGNED-IND
= ‘Y’
(This field should be protected)
Peer Review Field C043-PEER-REV-IND
(This field should be protected)
Original Field C043-ORIG-CURR
Currency (This field should be protected)

Claims Office Field C043-COR


Reference (This field should be protected)
(COR)
Letter of Credit Tick-Box Set to ‘TRUE’ if C043-LOC-IND = ‘Y’
Indicator (This field should be protected)
Payee Broker Field C043-PAYEE-BKR-CODE

David Willcocks 261 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Code (This field should be protected)

Redenominated Field C043-REDENOM-IND


Indicator (This field should be protected)

Movement Field C043-MOVE-REF


Reference / (This field should be protected)
Date
Claim/Refund/ Field C043-CLM-REF-REC
Recovery code (If C043-CLM-REF-REC-ATTR = ‘P’,
this field should be protected)

Original Field C043-ORIG-CURR


Currency (If C043-ORIG-CURR-ATTR = ‘P’, this
field should be protected)

Paid To Date Field C043-PTD-LOSS


(Loss (If C043-PTD-LOSS-ATTR = ‘P’, this
breakdown) field should be protected)

Paid To Date Field C043-PTD-EXP


(Expenses (If C043-PTD-EXP-ATTR = ‘P’, this field
Breakdown) should be protected)

Paid To Date Field C043-PTD-FEE


(Fees (If C043-PTD-FEE-ATTR = ‘P’, this field
Breakdown) should be protected)

Paid To Date Field C043-PTD-TOTAL


(Total) (If C043-PTD-TOTAL-ATTR = ‘P’, this
field should be protected)

Paid This Time Field C043-PTT-LOSS


(Loss (If C043-PTT-LOSS-ATTR = ‘P’, this
Breakdown) field should be protected)

Paid This Time Field C043-PTT-EXP


(Expenses (If C043-PTT-EXP-ATTR = ‘P’, this field
Breakdown) should be protected)

Paid This Time Field C043-PTT-FEE


(Fees (If C043-PTT-FEE-ATTR = ‘P’, this field
Breakdown) should be protected)

Paid This Time Field C043-PTT-TOTAL


(Total) (If C043-PTT-TOTAL-ATTR = ‘P’, this
field should be protected)

David Willcocks 262 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source

Outstanding Field C043-OUTST-LOSS


Loss Amount (If C043-OUTST-LOSS-ATTR = ‘P’, this
field should be protected)

Outstanding Field C043-OUTST-LOSS-QUAL


Loss Qualifier (If C043-OUT-LOSS-Q-ATTR = ‘P’, this
field should be protected)

Outstanding Field C043-OUTST-EXP


Expense (If C043-OUTST-EXP-ATTR = ‘P’, this
Amount field should be protected)

Outstanding Field C043-OUTST-FEE


Fees Amount (If C043-OUTST-FEE-ATTR = ‘P’, this
field should be protected)

Outstanding Field C043-OUTST-FEE-QUAL


Fees Qualifier (If C043-OUT-FEE-Q-ATTR = ‘P’, this
field should be protected)

Total Field C043-OUTST-TOT


Outstanding (If C043-OUTST-TOT-ATTR = ‘P’, this
Amount field should be protected)

Total Field C043-OUTST-TOT-QUAL


Outstanding (If C043-OUT-TOT-Q-ATTR = ‘P’, this
Amount field should be protected)
Qualifier
Settlement Field C043-SETT-CURR
Currency (If C043-SETT-CURR-ATTR = ‘P’, this
field should be protected)

Exchange Rate Field C043-EXCH-RATE


(If C043-EXCH-RATE-ATTR = ‘P’, this
field should be protected)

Paid To Date in Field C043-PTD-SETT-AMT


Settlement (If C043-PTD-SETT-ATTR = ‘P’, this
Currency field should be protected)
100% Field C043-CLAIM-AMT-SETT
Settlement (If C043-SETT-AMT-ATTR = ‘P’, this
Amount field should be protected)

Total Bureau Field C043-BUREAU-LINE


Line (If C043-BUR-LINE-ATTR = ‘P’, this
field should be protected)

David Willcocks 263 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source

Bureau Field C043-BUR-PROP-AMT


Proportion of (If C043-BUR-PROP-ATTR = ‘P’, this
100% field should be protected)
Settlement
Amount
100% VAT Field C043-HPC-VAT-AMT
Amount (If C043-VAT-AMT-ATTR = ‘P’, this field
should be protected)

100% War Field C043-WAR-AMT


Amount (If C043-WAR-AMT-ATTR = ‘P’, this
field should be protected)

Narrative Code Field C043-NARR-CODE-1


1 (If C043-NARR-CODE-ATTR1 = ‘P’, this
field should be protected)

Narrative Code Field C043-NARR-CODE-2


2 (If C043-NARR-CODE-ATTR2 = ‘P’, this
field should be protected)

Current Field C043-SETT-NARR-1


Narrative 1 (If C043-SETT-NARR-ATTR1 = ‘P’, this
field should be protected)

Current Field C043-SETT-NARR-2


Narrative 2 (If C043-SETT-NARR-ATTR2 = ‘P’, this
(part 1) field should be protected)

Current Field C043-SETT-NARR-3


Narrative 2 (If C043-SETT-NARR-ATTR3 = ‘P’, this
(part 2) field should be protected)

Subrogation Tick-Box C043-SUBROGATION


(If C043-SUBROG-ATTR = ‘P’, this field
should be protected)

XCS Recovery Field C043-XCS-REC-REF


Reference (If C043-XCS-REC-REF-ATTR = ‘P’, this
field should be protected)

Highest Field C043-HIGHEST-EST


Estimate (If C043-HIGHEST-EST-ATTR = ‘P’, this
(Highest field should be protected)
Incurred)
Incurred Field C043-INCURRED-AMT

David Willcocks 264 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Amount (or (If C043-INCURRED-ATTR = ‘P’, this
Current field should be protected)
Estimate)
Outstanding Field C043-RATE-EXCH-OUTST
Rate of (If C043-OUTST-ROE-ATTR = ‘P’, this
Exchange field should be protected)

Finder Code 1 Field C043-FINDER-CODE-1


(If C043-FIND-CODE-ATTR1 = ‘P’, this
field should be protected)

Finder Code 2 Field C043-FINDER-CODE-2


(If C043-FIND-CODE-ATTR2 = ‘P’, this
field should be protected)

Finder Code 3 Field C043-FINDER-CODE-3


(If C043-FIND-CODE-ATTR3 = ‘P’, this
field should be protected)

Attachments Tick-Box Set to ‘TRUE’ if C043-ATTACHMENT-


Indicator IND = ‘Y’
(If C043-ATTACH-IND-ATTR = ‘P’, this
field should be protected)

Broker Contact Field C043-BKR-CNTCT


(If C043-BKR-CNTCT-ATTR = ‘P’, this
field should be protected)

Broker Field C043-BKR-CNTCT-PHONE


Contact’s (If C043-BKR-PHONE-ATTR = ‘P’, this
Telephone field should be protected)
Number
N.B. The following Broker Reference fields should be displayed on the
screen as follows:-

Claim: Bkr Ref 1 XXXXXXXXXXXXXXXX Bkr Ref 2


XXXXXXXXXXXXXXXX
Settlement: Bkr Ref 1 XXXXXXXXXXXXXXXX Bkr Ref 2
XXXXXXXXXXXXXXXX

Claim Broker Field C043-CLM-BKR-REF-1


Reference 1 (If C043-CLM-BKR-REF-ATTR1 = ‘P’,
this field should be protected)
Claim Broker Field C043-CLM-BKR-REF-2
Reference 2 (If C043-CLM-BKR-REF-ATTR2 = ‘P’,
this field should be protected)
Settlement Field C043-BKR-REF-1

David Willcocks 265 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Broker (If C043-BKR-REF-ATTR1 = ‘P’, this
Reference 1 field should be protected)

Settlement Field C043-BKR-REF-2


Broker (If C043-BKR-REF-ATTR2 = ‘P’, this
Reference 2 field should be protected)

Country of Field C043-CNTRY-OF-ORIGIN


Origin (If C043-CNTRY-ATTR = ‘P’, this field
should be protected)
Original Field C043-ORIG-INSURED
Insured (If C043-ORIG-INS-ATTR = ‘P’, this
field should be protected)

Insured Field C043-INSURED


(If C043-INSURED-ATTR = ‘P’, this
field should be protected)

Reinsured Field C043-REINSURED


(If C043-REINSURED-ATTR = ‘P’, this
field should be protected)

Cover Holder Field C043-COVER-HOLDER


(If C043-COV-HOLD-ATTR = ‘P’, this
field should be protected)

Claimant Field C043-CLAIMANT


(If C043-CLAIMANT-ATTR = ‘P’, this
field should be protected)

Name of Vessel Field C043-VESSEL-AIRCRAFT


or Aircraft (If C043-VESS-AIR-ATTR = ‘P’, this
field should be protected)

Slip Type Field C043-SLIP-TYPE-DESC


Description (If C043-SLIP-TYPE-DESC-ATTR = ‘P’,
this field should be protected)
Other Name Field C043-OTHER-NAME
(If C043-OTHER-NAME-ATTR = ‘P’,
this field should be protected)
Policy/Cert Field C043-POL-CERT-FROM
Period From (If C043-POL-FROM-ATTR = ‘P’, this
Date field should be protected)

Policy/Cert Field C043-POL-CERT-TO


Period To Date (If C043-POL-TO-ATTR = ‘P’, this field
should be protected)

David Willcocks 266 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Policy/Cert Field C043-POL-CERT-QUAL
Period Qualifier (If C043-POL-QUAL-ATTR = ‘P’, this
field should be protected)

Date of Loss Field C043-LOSS-DATE-FROM


From Date (if C043-DOL-FROM-ATTR = ‘P’, this
field should be protected)

Date of Loss To Field C043-LOSS-DATE-TO


Date (If C043-DOL-TO-ATTR = ‘P’, this field
should be protected)

Date of Loss Field C043-LOSS-DATE-QUAL


Qualifier (if C043-DOL-QUAL-ATTR = ‘P’, this
field should be protected)

Loss Date Field C043-LOSS-DATE-NARR


Narrative (if C043-DOL-NARR-ATTR = ‘P’, this
field should be protected)
Date Claim Field C043-CLAIM-DATE-FROM
Made From (If C043-DCM-FROM-ATTR = ‘P’, this
Date field should be protected)

Date Claim Field C043-CLAIM-DATE-TO


Made To Date (If C043-DCM-TO-ATTR = ‘P’, this field
should be protected)

Date Claim Field C043-CLAIM-DATE-QUAL


Made Qualifier (If C043-DCM-QUAL-ATTR = ‘P’, this
field should be protected)

Catastrophe Field C043-CAT-CODE


Code (If C043-CAT-ATTR = ‘P’, this field
should be protected)

PCS Field C043-PCS-CAT-CODE


Catastrophe (If C043-PCS-CAT-ATTR = ‘P’, this field
Code should be protected)

Currency that Field C043-LIMIT-CURR


applies to (If C043-LIMIT-CURR-ATTR = ‘P’, this
Policy Limits field should be protected)

Sum Insured Field C043-SI-LIMIT


Limit (If C043-SI-LIMIT-ATTR = ‘P’, this field
should be protected)

Excess Limit Field C043-EXCESS-AMT

David Willcocks 267 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
(If C043-EXCESS-AMT-ATTR = ‘P’, this
field should be protected)

Perils/Conditio Field C043-PERILS-CONDS


ns (If C043-PERILS-COND-ATTR = ‘P’,
this field should be protected)

Location of Field C043-LOSS-LOCATION


Loss (If C043-LOSS-LOC-ATTR = ‘P’, this
field should be protected)

Voyage Field C043-VOYAGE


(If C043-VOYAGE-ATTR = ‘P’, this field
should be protected)

Name of Loss Field C043-LOSS-NAME


(If C043-LOSS-NAME-ATTR = ‘P’, this
field should be protected)

Loss/Claim Field C043-CLAIM-DET-LINE (n) (where n =


Details (up to 3 1-3)
lines of 50 (If C043-CLAIM-DETS-ATTR = ‘P’, all
characters) lines of claim details should be
protected)

SCM Lawyer Field C043-LAWYER-NAME


Name (If C043-LAW-NAME-ATTR = ‘P’, this
field should be protected)

SCM Lawyer Field C043-LAWYER-REF


Reference (If C043-LAW-REF-ATTR = ‘P’, this field
should be protected)

SCM Lawyer Field C043-LAWYER-CODE


Code (If C043-LAW-CODE-ATTR = ‘P’, this
field should be protected)

SCM Adjuster Field C043-ADJUSTER-NAME


Name (If C043-ADJ-NAME-ATTR = ‘P’, this
field should be protected)

SCM Adjuster Field C043-ADJUSTER-REF


Reference (If C043-ADJ-REF-ATTR = ‘P’, this field
should be protected)

SCM Adjuster Field C043-ADJUSTER-CODE


Code (If C043-ADJ-CODE-ATTR = ‘P’, this
field should be protected)

David Willcocks 268 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source

Scheme Code Field C043-SCHEME-CODE


(If C043-SCH-CODE-ATTR = ‘P’, this
field should be protected)

Trust Fund Field C043-TF-CODE


Code (if C043-TF-CODE-ATTR = ‘P’, this field
should be protected)

State Code Field C043-STATE-CODE


(If C043-STATE-CODE-ATTR = ‘P’, this
field should be protected)

NAIC Code Field C043-NAIC-CODE


(If C043-NAIC-CODE-ATTR = ‘P’, this
field should be protected)

NAIC Qualifier Field C043-NAIC-QUAL


(If C043-NAIC-QUAL-ATTR = ‘P’, this
field should be protected)

War Indicator Tick-Box Set to ‘TRUE’ if C043-WAR-IND = ‘Y’


(if C043-WAR-IND-ATTR = ‘P’, this field
should be protected)

FIL Code 1 Field C043-FIL-CODE-1


(If C043-FIL-CODE-ATTR1 = ‘P’, this
field should be protected)

FIL Code 2 Field C043-FIL-CODE-2


(If C043-FIL-CODE-ATTR2 = ‘P’, this
field should be protected)

Other TF Code Field C043-OTHER-TF-CODE


(If C043-OTHER-TF-ATTR = ‘P’, this
field should be protected)

DTI Code Field C043-DTI-CODE


(If C043-DTI-CODE-ATTR = ‘P’, this
field should be protected)
USA/Canada Tick-Box ‘Ticked’ if C043-USA-CAN-IND = ‘Y’
Indicator (If C043-USA-CAN-ATTR = ‘P’, this
field should be protected)
Loss Fund Tick-Box ‘Ticked’ if C043-LF-ENTRY-IND = ‘Y’
Entry Indicator (If C043-LF-ENTRY-ATTR = ‘P’, this
field should be protected)
Loss Fund Tick-Box ‘Ticked’ if C043-LF-ADVANCE-IND =
‘Y’

David Willcocks 269 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source
Advance (If C043-LF-ADVANCE-ATTR = ‘P’, this
Indicator field should be protected)
Direct Report Tick Box ‘Ticked’ if C043-DIRECT-REPORT-IND
= ‘Y’
(if C043-DIRECT-REPORT-IND-ATTR =
‘P’, this field should be protected)
Claim in Tick Box ‘Ticked’ if C043-LITIGATION-IND = ‘Y’
Litigation (if C043-LITIGATION-IND-ATTR = ‘P’,
this field should be protected)
Service Type Field C043-SERVICE-TYPE
(If C043-SERVICE-TYPE-ATTR = ‘P’,
this field should be protected)

Block Indicator Tick-Box ‘Ticked’ if C043-BLOCK-IND = ‘Y’


(If C043-BLOCK-IND-ATTR = ‘P’, this
field should be protected)
B.2. Enquiry Fields

A different view of the SCM Advice (Breakdown) Screen is displayed in enquiry mode. This
view contains a number of additional fields. Unfortunately, when this enhancement was
made, this document was not updated.

The following fields have been added to this enquiry view as part of the Syndicate Opt-Out
enhancement:-

The following two fields should be displayed towards the end of the ‘Financials’
section – below the User Id field. The fields should be displayed in both the
Update and Enquiry views

Claim Opt-Out Field Set to C043-CLM-OPT-OUT-STATUS


Status (If C043-CLM-OO-STAT-ATTR = ‘P’,
this field should be protected)
Claim Opt-Out Field Set to C043-CLM-OPT-OUT-DATE
Date (If C043-CLM-OO-DATE-ATTR = ‘P’,
this field should be protected)

The following two fields should be displayed for each line of market details. These fields
will only apply to the Enquiry View of the Screen. They should be displayed on each line
of the market details, between Syndicate Reference and Bureau Leader.

Synd. Opt-Out Field Set to C043-SY-OPT-OUT-STATUS (n)


Status (This field should be protected)
Synd. Opt-Out Field Set to C043-SY-OPT-OUT-DATE (n)
Date (This field should be protected)

David Willcocks 270 May 2002


Xchanging Ins-sure Services Ltd
Field Type Source

C. COMMANDS – Only Commands that may or may not be allowed


under certain circumstances are listed here
VAT Rates Comman If C043-VAT-RATE-ATTR = ‘U’ or C043-
d HPC-VAT-AMT not = zero, this button
should be unprotected.

Otherwise, this button should be


protected or preferably not displayed.
Expert Fees Comman If C043-FEES-BDOWN-ATTR = ‘U’, this
Breakdown d button should be unprotected.

Otherwise, this button should not be


displayed.
End Breakdown Comman If C043-END-BD-ATTR = ‘P’, this
d button should be protected, or
preferably not displayed.
New Comman If C043-NEW-BD-ATTR = ‘P’, this
Breakdown d button should be protected, or
preferably not displayed.
Create Binder Comman If C043-BIND-SCHD-ATTR = ‘P’, this
Schedule d button should be protected, or
praferably not displayed
Create R/I Comman If C043-RI-SCHD-ATTR = ‘P’, this
Schedule d button should be protected, or
preferably not displayed.
Back to Comman If C043-BACK-ATTR = ‘P’, this button
Schedule d should be protected, or preferably not
displayed.
EURO Conv. Comman If C043-EURO-ATTR = ‘P’, this button
Details d should be protected, or preferably not
displayed.
CCS Amounts Comman If C043-CCS-ATTR = ‘P’, this button
d should be protected, or preferably not
displayed.
Create New Comman If C043-NEW-MOVE-ATTR = ‘P’, this
Movement d button should be protected, or
preferably not displayed

4.17.4. Process Description

This screen is the Breakdown (SCM Advice) screen.


This screen allows the user to enter information
relating to a movement on a particular Claims Office
David Willcocks 271 May 2002
Xchanging Ins-sure Services Ltd
Reference. Information on this screen will be pre-
populated either with information entered at CLASS
Claim Transaction level (if this is the first breakdown on
a new advice), details from the previous breakdown (if
this is a subsequent breakdown within a first advice or
a new breakdown on a subsequent advice) or details for
this breakdown from the previous movement (if this is a
subsequent advice and this is not the first movement on
the current Claims Office Reference).

For broker supplied claims, the information at CLASS


Claim Transaction level will have been protected. For
SCM advice purposes, the user will be able to change
the information supplied by the broker on this screen, if
required.

On first entry into this screen, the financial details


relating to this movement will be shown. Should the
user wish to add or amend the claim/policy information,
the screen can be ‘expanded’ to show further non-
financial fields for the user to complete as necessary.

If the details displayed are in EURO and were originally


in a redundant NCU currency which has undergone
conversion, an extra button will be enabled on the
screen – the ‘EURO Conv. Details’ button. If the user
pushes this button, the ‘EURO Conversion Details’ will
be displayed.

Fig 4.17.4.1. Field/Command Processing for ‘Breakdown (SCM


Advice)’ Screen

Field / Attributes Data Type


Description
Command
A. Options (Top of Screen)
Log off Call CICS transaction LY01 (see Appendix C.1) – Command
using COMMAREA C004 (see Appendix D) to log-
off the system and delete the Session Record.

On return from CICS, check the C004-PROG-


STATUS field:-

(i) if set to 9, display any errors returned in the


commarea in the Error Screen (see Appendix B)

David Willcocks 272 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(ii) if set to zero, close all windows.

Create New (i) Call CICS transaction LY01 (see Appendix


Claim C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR004’
(Create New Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

(v) If the user did not press Cancel in the

David Willcocks 273 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Create Claim
Screen’ (see Section 4.4)

Find Claim (i) Call CICS transaction LY01 (see Appendix


C.1) to check the status of the current
transaction – using COMMAREA C016.

On return, check C016-PROG-STATUS


and, if set to 9, report any errors in the Error
Screen (see Appendix B).

(ii) If C016-PROG-STATUS set to 5, the


technician will need to decide whether to
delete, release or hold the current claim
transaction before returning to the ‘Create
New Claim’ screen. Display the ‘Claim
Transaction Options’ pop-up window
detailed in Section 4.10 and perform
processing as described.

(iii) If user pressed ‘Cancel’ in the ‘Claim


Transaction options’ window, the user
should be left in the current screen.

(iv) If the user did not press ‘Cancel’, t he


Session Record should be updated by
calling CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C010
(see Appendix D).

Note: The following fields should be passed in


C010 commarea, when updating the Session
Record:-
C010-UCR-TR-SYS-REF = Zero
C010-CURR-NO = Zero
C010-SDN-NO = Zero
C010-STAT-SPLIT-NO = Zero
C010-BREAKDOWN-NO= Zero
C010-RETURN-SCREEN = ‘SCR005’
(Find Claim)

On return, check the Program Status in the


usual way, reporting errors if they exist in the
Error Screen (see Appendix B)

David Willcocks 274 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(v) If the user did not press Cancel in the
‘Claim Transaction Options’ window and
no errors were returned from LY10,
navigate the user to the ‘Find Claim’ Screen
(see Section 4.5)

Account Link to Account Enquiry (method needs to be Command


Enquiry identified)

Repository Link to Repository (method needs to be identified) Command

Data Warehouse Link to Data Warehouse (method needs to be Command


identified)
Grouping When user clicks on the ‘GROUPING’ option at the Command
top of the screen, the following options should be
available on a sub-menu:-
Maintain Group
Group Enquiry
Add to Aggregate Group
Create Non-Aggregate Group
Add to Non-Aggregate Group

User should select one of these options.

Note:- ‘Clicking’ on the ‘Maintain Group’,


‘Group Enquiry’ or ‘Add to Non-Aggregate
Group’ options should open up a new ‘window’ –
associated with its own entry on the Session Table
(i.e. a new Session No.). Once the user has finished
Group processing, the window should be closed and
the Session Record deleted.

(i) If either the ‘Maintain Group’, ‘Group


Enquiry’ or ‘Add to Non-Aggregate
Group’ options were selected, call CICS
transaction LY01 (see Appendix C.1) to set
up a new Session Record for the Grouping
session - using Commarea C071 (see
Appendix D).

On return, check the C071-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’


option, open new window, navigating user

David Willcocks 275 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
to ‘Maintain Group’ screen (see Section
4.27) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’


option, open new window, navigating user
to ‘Group Enquiry’ screen (see Section
4.28) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY71)

(iv) On selection of ‘Add to Aggregate


Group’, call CICS transaction LY01
(see Appendix C.1) to add the OSND’s
associated with this claim to an Aggregate
group – using COMMAREA C014 (see
Appendix D).

On return, check the C014-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the OSND’s
have been added to. (see Appendix G)

(v) On selection of ‘Create Non-Aggregate


Group’, call CICS transaction LY01 (see
Appendix C.1) to add the current claim
to a Non-Aggregate group – using
COMMAREA C015 (see Appendix D).

On return, check the C015-PROG-STATUS


and report any errors in the usual way.

If no errors are returned, display a pop-up


window, displaying the confirmation
message returned by the CICS transaction
and the Group Reference that the claim has
been added to. (see Appendix G)

(vi) On selection of the ‘Add to Non-


Aggregate Group’ option, open new
window, navigating user to ‘Group Enquiry’
screen (see Section 4.28) (a new SESSION-
NO is associated with this window – this

David Willcocks 276 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
will have been returned by previous
transaction, LY71)

Notes When user clicks on the ‘NOTES’ option at the top Command
of the screen, the following options should be
available on a sub-menu:-
Security Notes
Claim Notes
Loss Details
Policy Details
Settlement Narrative
EURO Conversion Narrative (FME)
Broker Additional Details
Broker Aggregate Details
Slip Lead Comments
Lead Comments
Lead Additional Details

User should select one of these options.

Whichever Option is selected:-

(i) Call CICS Transaction LY01 (see


Appendix C.1), using Commarea C045
(see Appendix D), to update the
database with any details entered on the
SCM Advice screen.

On return, check the C036-PROG


-STATUS and report any errors in the
usual way.

(ii) Call CICS transaction LY01 (see


Appendix C.1) to check whether the
selected narrative is present or not, and
return any narrative present, using
COMMAREA C088 (see Appendix D).
N.B. Set C088-FIRST-CALL to ‘Y’.
This call will return lines 1 to 300.

On return, check the C088-PROG


-STATUS and report any errors in the
usual way.

(iii) If no errors returned from the first


LY88 call and C088-MORE-LINES is
set to ‘Y’, call CICS transaction LY01
(see Appendix C.1) to check whether

David Willcocks 277 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
the selected narrative is present or not,
and return any narrative present, using
COMMAREA C088 (see Appendix D).
N.B. Set C088-FIRST-CALL to ‘N’.
This call will return lines 301 to 600.

On return, check the C088-PROG


-STATUS and report any errors in the
usual way.

(iv) If no errors found in LY88, the user


should be navigated to the Narrative
Screen (see Section 4.35)

Note:- the Narrative screen should be opened up as


a new window, overlaying whichever screen the
user is currently processing. Once the user has
finished enquiring on or updating the narrative, the
window should be closed and the user will be
returned to whichever screen they were processing
originally.

History When the user ‘clicks’ on this option they should be Command
navigated to the ‘Movement History’ screen.

Note:- ‘Clicking’ on the ‘History’ option should


open up a new ‘window’ – associated with its own
entry on the Session Table (i.e. a new Session No.).
Once the user has finished browsing through
history, the window should be closed and the
Session Record deleted.

(i) call CICS transaction LY01 (see Appendix


C.1) to set up a new Session Record for the
History session – using Commarea C068
(see Appendix D).

On return, check the C068-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) Open new window, navigating user to


‘Movement History’ screen (see Section
4.26) (a new SESSION-NO is associated
with this window – this will have been
returned by previous transaction, LY68)

Functions When user clicks on the ‘FUNCTIONS’ option at Command

David Willcocks 278 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
the top of the screen, the following options should
be available on a sub-menu:-
1.Create Subsequent Advice
2.Create Rate of Exchange Adjustment
3.Create Contra Correction
4.Add Take Down Numbers
5. Set Diary Date
6. Create Bulk/CCS Correction
7. Set ‘File Last Seen’ Date
8.Reset Claim Transaction
9. Create Re-advice

User should select one of these options:-

‘Create Subsequent Advice’ selected

If the user selects ‘Create Subsequent Advice


(Single B/down)’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C020. (see Appendix D).
N.B. Ensure that C020-TRANS-TYPE is set to ‘V’
(Validation Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned from the first call to LY20,


call CICS transaction LY01 (see Appendix C.1) to
‘construct’ the skeleton subsequent transaction –
using COMMAREA C020. (see Appendix D). N.B.
Ensure that C020-TRANS-TYPE is set to ‘U’
(Update Only).

On return, check the C020-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Claim Transaction Creation screen’ – rebuilding it
from scratch – as field protection will be
different and some field contents may be different.

‘Create Rate of Exchange Adjustment’ selected

If the user selects ‘Create Rate of Exchange


Adjustment’, call CICS transaction LY01 (see
Appendix C.1) to perform any validation necessary
– using COMMAREA C021. (see Appendix D).

David Willcocks 279 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
On return, check the C021-PROG-STATUS and
report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Rate of
Exchange Adjustment (see Section 4.29).

‘Create Contra Correction’ selected

If the user selects ‘Create Contra Correction’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C022. (see Appendix D).

On return, check the C022-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Contra
Correction (see Section 4.30).

‘Add Take Down Numbers’ selected

If the user selects ‘Add Take Down Numbers’, call


CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C023. (see Appendix D).

On return, check the C023-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, the user should be


navigated to the ‘Settlement Summary’ (see Section
4.22).

‘Set Diary Date’ selected

If the user selects the ‘Set Diary Date’ option, the


‘Set Diary Date’ pop-up window should be
displayed to them (see Section 4.34).

‘Create Bulk/CCS Correction’ selected

This is a special correction facility for use only by

David Willcocks 280 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
authorised technicians. It allows correction of Bulk
Components, converted bulks and pre-
redenomination transactions. The difference
between this type of correction and Contra
Corrections is that the user has the ability to enter a
treasury rate.

If the user selects ‘Create Bulk/CCS Correction’,


call CICS transaction LY01 (see Appendix C.1) to
perform any validation necessary – using
COMMAREA C090. (see Appendix D).

On return, check the C090-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up window should


be displayed, allowing the user to raise the Bulk/
CCS Correction (see Section 4.36).

‘Set File Last Seen Date’ selected

This function allows the user to set the File Last


Seen Date to todays date and generate an advice to
the syndicates without creating a new claim
movement.

If this function is selected, display the ‘File Seen


Confirmation’ window (see Appendix S.2). If the
technician presses ‘YES’ in this window, call CICS
transaction LY01 (see Appendix C.1) to perform
any validation necessary and set up the necessary
logging records – using COMMAREA C096. (see
Appendix D).

On return, check the C096-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, a pop-up confirmation


window should be displayed (see Appendix S.3.)
for information purposes only.

‘Reset Claim Transaction’ selected

This function will reset the status of a previously


released claim transaction to allow it to be updated
by the claim technician. This will not be allowed if
the claim transaction has been fully advised or if a
subsequent transaction exists within the claim.

David Willcocks 281 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(i) Call CICS transaction LY01 (see


Appendix C.1), passing the Commarea
C105 (see Appendix D). This will
validate that that the claim transaction
is eligible for update and, if so, reset the
status accordingly.

On return check the Program Status and


report any errors/warnings in the usual
way.

(ii) If no errors returned from LZ06, call


LY01 using Commarea C043 to obtain
the data and field protection for the
current screen.

On return check the Program Status and


report any errors/warnings in the usual
way.

(iii) Rebuild the current screen using the


data returned in the C043 Commarea.

‘Create Re-advice’ selected

This function will allow the user to create a re-


advice of the most recent movement on the claim –
changing only the current narrative.

(i) call CICS transaction LY01 (see Appendix C.1)


to perform any validation necessary – using
COMMAREA C110. (see Appendix D).

On return, check the C110-PROG-STATUS and


report any errors/warnings in the usual way.

If no errors are returned, navigate the user to the


‘Create Re-Advice’ screen (see Section 4.39).

David Willcocks 282 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B. Navigation Options (Left of Screen) - COMMANDS

If user clicks on the ‘Option Button’ alongside any of the Options on the Navigation Bar, refer to table
returned by transaction LY12 (Build Navigation Bar) in the C012 Commarea. This table should be
stored after building the navigation bar on first entry to the screen for use when the user selects one of
the options on the Navigation Bar.

(i) If C043-SCREEN-MODE = ‘U’ (Update) and the value of C012-SCREEN-ID corresponding to


the users selection is not ‘SCR009’, ‘SCR012’, ‘SCR013’, SCR014’, ‘SCR015’ or ‘SCR016’ -
Call CICS transaction LY01 (see Appendix C.1) to validate that any details entered on the
screen are valid, using Commarea C044 (see Appendix D).

On return, check the C044-PROG-STATUS and report any errors/warnings in the usual way.

(ii) If C043-SCREEN-MODE = ‘U’ (Update) and either no errors returned from LY44 or the
selected screen was one of those listed above, Call CICS transaction LY01 (see Appendix C.1)
to update the database with the details entered on the screen – using COMMAREA C045. (see
Appendix D).

On return, check the C045-PROG-STATUS and report any errors/warnings in the usual way.

(iii) If no errors returned from LY45 or SCREEN-MODE = ‘E’ (Enquiry), call CICS transaction
LY01 (see Appendix C.1) – using COMMAREA C046 (see Appendix D) – to check whether
currency/transaction validation needs to be performed. (N.B. the key values returned from LY12
and stored in the C012-KEY table – for the line on the navigation bar selected - should be
passed in the C046 commarea).

On return, check the C046-PROG-STATUS and report any errors/warnings in the usual way.

(iv) If no errors returned from LY46, Call CICS transaction LY01 (see Appendix C.1) to update
the Session Record (VCLSESA1) –using COMMAREA C010. (see Appendix D), (N.B. the key
values returned from LY12 and stored in the C012-KEY table – for the line on the navigation
bar selected – should be passed in the C010 commarea).

On return, check the C010-PROG-STATUS and report any errors/warnings in the usual
way.

(v) If no errors are returned from LY10, the user should be navigated to the screen indicated by
C012-SCREEN-ID for the line in the navigation bar selected. (see Appendix N)

David Willcocks 283 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C. Fields (Main Screen)

N.B. Alphanumeric fields must not contain any characters that are not supported by the EDI message
systems, as these may cause brokers and/or syndicates systems to fall over. Valid ASCII Characters are
as follows:-
space, 0-9, A-Z, a-z, ',', '.', '-', '(', ')', '/', '=', ''', '*','+', ':', '?', '!','"', '%','&', ';','<', '>'.

N.B.2. Pre-population of the fields with values returned from LIDS does not need to be handled by
the GUI, as these values will have been loaded onto the database by the ‘Claim Creation Screen D/B
Update’ module (LY27).

N.B.3 Field Protection will be handled by the ‘Field Attributes’ returned in the C043 Commarea.

N.B.4 If any errors are encountered, highlight any field(s) in error by setting the text colour to red.

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric


to claims that are created by internal technicians. It Only Field (17 Chars)
will always be present for internally created claims,
but not for claims created by the broker on the
‘CLASS for Lloyds’ system.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

UCR The Unique Claim Reference. This will always be Display Alphanumeric
present for claims created by the broker on the Only Field (17 Chars)
‘CLASS for Lloyds’ system, but may or may not be
present for internally created claims – depending on
whether the broker has quoted it on the claim file.

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

TR Transaction Reference. Uniquely identifies a Display Alphanumeric


particular transaction within a claim. Only Field (17 chars)

This field is shown as part of the header and is


display only. It is a 17 character field which should
be displayed in the following format:-
‘X / XXXX / XXXXXXXXXXXX’
OSND Original Signing Number and date (for the first Display Alphanumeric
currency on the claim) Only Field (15 Chars)
Orig. The Originating Broker (i.e. the broker who Display Alphanumeric
submitted this claim transaction). Only Field (4 chars)

David Willcocks 284 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Broker
Signed Signed Indicator. This indicates whether or not the Display N/a
(Y/N) risk against which this claim is being made has been Only
signed or not. Tick-Box
Peer This indicates whether the claim is subject to peer Display Alphanumeric
Review review. Only (1 Char)
Field
Original This is the Original currency to which the current Display Alphanumeric
Currency breakdown (SCM Advice) relates. There may be up Only Field (3 Chars)
to three original currencies on a particular CLASS
transaction. However, a particular breakdown will
be associated with only one of these.

This field is part of the header and is protected.


Claims The Claims Office Reference that has been assigned Display Alphanumeric
Office to the current breakdown. This is system generated. Only Field (15 Chars)
Reference
(COR) This field is part of the header and is protected.
LOC The Letter of Credit indicator. Display Alphanumeric
indicator Only Tick- (1 Char)
For Letter of Credit transactions, each Claims Box
Office Reference will either be Cash or Letter of
Credit. This ‘tick-box’ indicates whether the current
breakdown is Letter of Credit or not.
Payee This is the code that identifies the broker to which Display Numeric
Broker the money is to be paid. Only Field 9(4)
Code
If the claim was entered on the ‘CLASS for Lloyds’
system, this will be set to the broker who raised the
claim.

For internally created claims, it will be set t the


value entered on the Financial Details Control
Screen.
Redenomin This Field indicates that the claim has been re- Display Alphanumeric
ated denominated at some stage in the past. Only (1 Char)
Indicator Field
If set on an earlier transaction, this field will be set
on all future transactions.

This field is shown as part of the header and cannot


be entered on this screen.

Movement The Movement Reference associated with this claim Display Alphanumeric
Reference / breakdowm. This field will initially be set to the Only Field (6 Chars)
Date movemenet reference brought forward from the

David Willcocks 285 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
previous transaction. If the user updates any details
for this breakdown, a new movement reference will
be assigned when the claim is released. This will be
displayed on re-entry to the claim for update or
enquiry purposes.

The movement reference should be shown in the


following format:-

XX / MMYY

Clm/Ref/Re This code indicates whether or not this movement is Mandatory Alphanumeric
c Code a claim (i.e. has a positive Paid This Time amount) Field (3 Chars)
or a recovery/refund (i.e. has a negative Paid This
Time amount).

Valid Values are ‘CLM’, ‘REF’ or ‘REC’. These


should be displayed to the user in a drop down list –
the user cannot enter the code, but must select it
from the list..

The field is mandatory if unprotected.

Original The Original (or Estimate) currency that applies to Display Alphanumeric
Currency this claim transaction. Only Field (3 chars)

This field will have been entered on the Financial


Details screen (either pre-populated with
information supplied by the broker or entered by
internal technicians). It cannot be changed on this
screen.

Paid To The part of the Paid To Date amount that relates to Display Numeric
Date the ‘Loss’ itself. This is the sum of all previously Only Field -(13)9.99
(Loss settled ‘Loss’ amounts and the Paid This Time
breakdown) ‘Loss’ amount on the current transaction. It is a
100% amount.

It will be initialised to the value held on the


previous transaction for this breakdown or Zero for
initial advices.

Format:- --,---,---,---,--9.99

Paid To The part of the Paid To Date amount that relates to Display Numeric
Date ‘Expenses’. This is the sum of all previously settled Only Field -(13)9.99
(Expenses ‘Expense’ amounts and the Paid This Time
‘Expense’ amount on the current transaction. It is a

David Willcocks 286 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Breakdown) 100% amount.

It will be initialised to the value held on the


previous transaction for this breakdown or Zero for
initial advices.

Format:- --,---,---,---,--9.99

Paid To The part of the Paid To Date amount that relates to Display Numeric
Date ‘Fees’. This is the sum of all previously settled Only Field -(13)9.99
(Fees ‘Fee’ amounts and the Paid This Time ‘Fee’ amount
Breakdown) on the current transaction. It is a 100% amount.

It will be initialised to the value held on the


previous transaction for this breakdown or Zero for
initial advices.

Format:- --,---,---,---,--9.99

Paid To The Paid To Date amount is the sum of all Display Numeric
Date previously settled amounts and the Paid This Time Only Field -(13)9.99
(Total) amount on the current transaction. It is a 100%
amount.

It will be initialised to the value held on the


previous transaction for this breakdown or Zero for
initial advices.

Format:- --,---,---,---,--9.99

Paid This This is the amount (in Original Currency) to be Optional Numeric
Time settled on the current claim transaction in relation to Field -(13)9.99
(Loss the Loss itself. It is a 100% amount.
Breakdown)
It will be initialised to zero.

This field will be protected on advice-only


transactions.

Format:- --,---,---,---,--9.99

Paid This This is the amount (in Original Currency) to be Optional Numeric
Time settled on the current claim transaction in relation to Field -(13)9.99
(Expenses expenses. It is a 100% amount.
Breakdown)
It will be initialised to zero.

This field will be protected on advice-only

David Willcocks 287 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
transactions.

Format:- --,---,---,---,--9.99

Paid This This is the amount (in Original Currency) to be Optional Numeric
Time settled on the current claim transaction in relation to Field -(13)9.99
(Fees expert fees. It is a 100% amount.
Breakdown)
It will be initialised to zero.

This field will be protected on advice-only


transactions.

Format:- --,---,---,---,--9.99

Paid This This is the amount (in Original Currency) to be Display Numeric
Time settled on the current claim transaction. It is a 100% Only Field -(13)9.99
(Total) amount.

This field will be protected on advice-only


transactions.

This field will be protected. It will be derived by


accumulating the Loss, Fee and Expense Paid To
Date breakdown fields.

Format:- --,---,---,---,--9.99

Outstandin This is the amount (in Original Currency), relating Optional Numeric
g Loss to the Loss itself, that is outstanding on the current Field -(13)9.99
Amount claim. It is a 100% amount.

This will be initialised to the value held on the


previous transaction for the current breakdown or
zero for first advices.

Format:- --,---,---,---,--9

Outstandin This is the qualifier associated with the Outstanding Optional Alphanumeric
g Loss Loss Amount. Field (1 Char)
Qualifier
On first advices it will be initialised to spaces. ON
subsequent advices it will be initialised to the value
held on the previous transaction for this breakdown.

If the Outstanding Loss Amount is equal to zero,


this field must not be spaces. If it is, display the

David Willcocks 288 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
error ‘E083’ (see Appendix E) in the Error Window
(see Appendix B).

Valid Values are:-


(i) ‘E’ = Expense
(ii) ‘N’ = NIL
(iii) ‘R’ = Recovery
(iv) ‘S’ = Subrogation
(v) ‘T’ = To Be Advised
(vi) ‘V’ = Salvage
(vii) ‘Z’ = Zero Recommended Reserve.

If the user enters a value other than the above,


display the error ‘E084’ (see Appendix E) in the
Error Window (see Appendix B).

Outstandin This is the amount (in Original Currency), relating Optional Numeric
g Expense to expenses, that is outstanding on the current claim. Field -(13)9.99
Amount It is a 100% amount.

This will be initialised to the value held on the


previous transaction for the current breakdown or
zero for first advices.

Format:- --,---,---,---,--9

Outstandin This is the amount (in Original Currency), relating Optional Numeric
g Fees to fees, that is outstanding on the current claim. It is Field -(13)9.99
Amount a 100% amount.

This will be initialised to the value held on the


previous transaction for the current breakdown or
zero for first advices.

Format:- --,---,---,---,--9

Outstandin This is the qualifier associated with the Outstanding Optional Alphanumeric
g Fees Fees Amount. Field (1 Char)
Qualifier
On first advices it will be initialised to spaces. ON
subsequent advices it will be initialised to the value
held on the previous transaction for this breakdown.

If the Outstanding Fees Amount is equal to zero,


this field must not be spaces. If it is, display the
error ‘E085’ (see Appendix E) in the Error Window
(see Appendix B).

David Willcocks 289 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Valid Values are:-
(i) ‘N’ = NIL
(ii) ‘T’ = To Be Advised

If the user enters a value other than the above,


display the error ‘E086’ (see Appendix E) in the
Error Window (see Appendix B).

Total This is the amount (in Original Currency) to be Display Numeric


Outstandin settled on the current claim transaction. It is a 100% Only Field -(13)9.99
g Amount amount.

This will be initialised to the value held on the


previous transaction for the current breakdown or
zero for first advices.

This field will be protected. It will be derived by


accumulating the Loss, Fee and Expense Paid To
Date breakdown fields.

Format:- --,---,---,---,--9

Total This is the qualifier associated with the Total Optional Alphanumeric
Outstandin Outstanding Amount. Field (1 Char)
g Amount
Qualifier This field is entered by the technician on the
‘Financial Details Control’ Screen or pre-populated
on this screen with details supplied by the broker.

If the Total Outstanding Amount is equal to zero,


this field must not be spaces. If it is, highlight the
field and display the error ‘E087’ (see Appendix E)
in the Error Window (see Appendix B).

Valid Values are:-


(i) ‘E’ = Expense
(ii) ‘T’ = TBA
(iii) ‘F’ = Fee
(iv) ‘N’ = Nil
(v) ‘R’ = Recovery
(vi) ‘S’ = Subrogation
(vii) ‘V’ = Salvage
(viii) ‘Z’ = Zero recommended reserve.
(ix) ‘C’ = Closed

If the user enters a value other than the above,


highlight the field and display the error ‘E088’ (see
Appendix E) in the Error Window (see Appendix

David Willcocks 290 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
B).

Settlement The Settlement Currency that applies to this claim Display Alphanumeric
Currency transaction. Only Field (3 Chars)

This field will have been entered on the Financial


Details screen (either pre-populated with
information supplied by the broker or entered by
internal technicians). It cannot be changed on this
screen.

This field will be protected on advice-only


transactions.

Exchange The Rate of Exchange (between the Original and Display Numeric
Rate Settlement Currencies). Only Field Z(6)9.9(5)

This field will have been entered on the Financial


Details screen (either pre-populated with
information supplied by the broker or entered by
internal technicians). It cannot be changed on this
screen.

This field will be protected on advice-only


transactions.

Format:- Z,ZZZ,ZZ9.99999

Paid To This is an accumulation of all 100% Display Numeric


Date Settlement Amounts (see below) for Only Field -(13)9.99
(in this movement and all previous
Settlement movements on the current
Currency) breakdown.

Note:- if the current transaction is


redenominated – this total will not
include any pre-redenomination
movements.

This amount is not simply the Paid To


Date amount converted into
Settlement Currency, as that will not
reflect what has actually been paid,
due to fluctuations in the rate of
exchange.

David Willcocks 291 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

Format:- --,---,---,---,--9.99

100% The 100% claim amount in the Settlement Optional Numeric


Settlement Currency. Field -(13)9.99
Amount
This should be validated as being equal to the Total
Paid This Time multiplied by the Rate of Exchange
(within a tolerance). If outside the tolerance,
highlight the 100% Settlement Amount field and
display the error E089 (see Appendix E) in the
Error Window (see Appendix B). (see Appendix J
for details about how to calculate tolerance)

This field will be protected on advice-only


transactions.

Format:- --,---,---,---,--9.99

Total The total bureau line. This is equal to the sum of the Display Numeric
Bureau all the syndicate line percentages on the market. Only Field Z(2)9.9(7)
Line
This field is shown for information only.

Bureau This is the Bureau proportion of the 100% Optional Numeric


Proportion Settlement Amount (in Settlement Currency). Field -(13)9.99
of 100%
Settlement This field will be protected on advice-only
transactions.
Amount
This field will be validated as the 100% Settlement
Amount multiplied by the Total Bureau Line (within
a tolerance). If outside the tolerance, highlight the
Bureau Proportion field and display the error E090
(see Appendix E) in the Error Window (see
Appendix B). (see Appendix J for details about
how to calculate tolerance)

Format:- --,---,---,---,--9.99

100% VAT This field represents that part of the 100% Claim Optional Numeric
Amount Amount (Paid This Time), in Settlement Currency, Field -(13)9.99
that is VAT.

This field will be protected on advice-only


transactions.

The 100% VAT Amounts entered for all breakdowns

David Willcocks 292 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
within the current Original Currency must total that
entered on the Financial Details Control Screen.

Format:- --,---,---,---,--9.99

100% War War Amount (in Settlement Currency). Optional Numeric


Amount Field -(13)9.99
This field will be protected on advice-only
transactions.

The War Amounts entered for all breakdowns


within the current Original Currency must total that
entered on the Financial Details Control Screen.

Format:- --,---,---,---,--9.99

Narrative A code that identifies a standard piece of settlement Optional Alphanumeric


Code 1 narrative. Field (3 Chars)

If entered, this code must be present on the


Narrative Code Table (Name ?). If not, highlight
the Narrative Code 1 field and display the error
E095 (see Appendix E) in the Error Window (see
Appendix B).

Narrative A second code to identify a standard piece of Optional Alphanumeric


Code 2 settlement narrative. Field (3 Chars)

If entered, this code must be present on the


Narrative Code Table (Name ?). If not, highlight
the Narrative Code 2 field and display the error
E096 (see Appendix E) in the Error Window (see
Appendix B).

Current Narrative that applies to the claim transaction, if Optional Alphanumeric


Narrative 1 settlement is involved. Field (50 Chars)

If Narrative Code 1 has been entered - when the


user tabs out of the Narrative Code 1 field, read the
Narrative Description Table (Name ?), which should
be held in the JAVA Layer, and pre-populate this
field with the associated Narrative Text.

This text may be overwritten.

Current Narrative that applies to the claim transaction, if Optional Alphanumeric

David Willcocks 293 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Narrative 2 settlement is involved. Field (25 Chars)
(part 1)
If Narrative Code 2 has been entered - when the
user tabs out of the Narrative Code 2 field, read the
Narrative Description Table (Name?), which should
be held in the JAVA Layer, and pre-populate this
field with the associated Narrative Text (first 25
chars).

Current Narrative that applies to the claim transaction, if Optional Alphanumeric


Narrative 2 settlement is involved. Field (25 Chars)
(part 2)
If Narrative Code 2 has been entered - when the
user tabs out of the Narrative Code 2 field, read the
Narrative Description Table (Name?), which should
be held in the JAVA Layer, and pre-populate this
field with the associated Narrative Text (last 25
chars).

Subrogatio This ‘tick-box’ indicates that the claim has the Tick-Box N/a
n potential for subrogation.

XCS This is the XCS Recovery Reference. Optional Alphanumeric


Ref/Rec Field (14 Chars)

Highest This is the highest value of Incurred Amount that Display Numeric
Estimate has been advised on this and all previous Only Field -(13)9.99
(Highest movements for the current breakdown.
Incurred)
It is derived and shown here for display purposes
only.

Format:- --,---,---,---,--9.99

Incurred The Incurred Amount (or Current Estimate). Mandatory Numeric


Amount (or Field -(13)9.99
Current This is entered for control purposes. The system (but can be
Estimate) will validate that the Incurred Amounts entered zero)
across all breakdowns for a particular currency total
the incurred amount entered (or pre-populated for
‘CLASS for Lloyds’ transactions) on the ‘Financial
Details Control’ screen.

The Incurred Amount should be equal to :-

Total Paid To Date Amount +


Total Paid This Time Amount +

David Willcocks 294 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Total Outstanding Amount.

If not, display the error E097 (see Appendix E) in


the Error Window (see Appendix B).

Format:- --,---,---,---,--9.99

Outstandin The Rate of Exchange that should be applied to the Optional Numeric
g Rate of Outstanding Amount. Field Z(6)9.9(5)
Exchange
This field must be entered if the Total Outstanding
Amount is not equal to zero. If not, display the error
E098 (see Appendix E) in the Error Window (see
Appendix B).

Format:- Z,ZZZ,ZZ9.99999

Finder Finder Code 1 (of 3). The first 3 finder codes are Optional Alphanumeric
Code 1 used to identify claims with common features. 3 are Field ? (1 Chars)
required because one claim could belong to 3 sets,
but only one set of each type (identified by Finder
Code number).

Must be a valid code in the Finder Code table


(name ?) and must be identified as a valid type 1
code.

Finder Finder Code 2 (of 3). The first 3 finder codes are Optional Alphanumeric
Code 2 used to identify claims with common features. 3 are Field ? (1 Chars)
required because one claim could belong to 3 sets,
but only one set of each type (identified by Finder
Code number).

Must be a valid code in the Finder Code table


(name ?) and must be identified as a valid type 2
code.

Finder Finder Code 3 (of 3). The first 3 finder codes are Optional Alphanumeric
Code 3 used to identify claims with common features. 3 are Field ? (1 Chars)
required because one claim could belong to 3 sets,
but only one set of each type (identified by Finder
Code number).

Must be a valid code in the Finder Code table


(name ?) and must be identified as a valid type 3
code.

David Willcocks 295 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Attachment Indicates whether there are attachments to be Tick-Box N/A
s Indicator distributed to syndicates.

Broker Contact Name for broker. Mandatory Alphanumeric


Contact Field (?? Chars)
This is a Free Text field. For claims loaded on the
‘CLASS for Lloyds’ system it will be pre-populated
with the information supplied by the broker. For
internally created claims, it will be pre-populated
with the data entered by the technician on the Claim
Details screen.

Broker Telephone Number of the Broker Contact. Optional Alphanumeric


Contact’s Field (?? Chars)
Telephone This is a Free Text field. For claims loaded on the
Number ‘CLASS for Lloyds’ system it will be pre-populated
with the information supplied by the broker. For
internally created claims, it will be pre-populated
with the data entered by the technician on the Claim
Details screen.

Claim First of up to two Broker Claim References. Display Alphanumeric


Broker Only Field (16 Chars)
Reference 1 This field is shown on this screen for enquiry
purposes only. It is the Broker reference that relates
to the claim (and would have been originally
entered on the ‘Claim Details’ screen).

Claim Second of up to two Broker References. Display Alphanumeric


Broker Only Field (16 Chars)
Reference 2 This field is shown on this screen for enquiry
purposes only. It is the second Broker reference that
relates to the claim (and would have been originally
entered on the ‘Claim Details’ screen).

Settlement First of up to two Broker References. Optional Alphanumeric


Broker Field (16 Chars)
Reference 1 This is a Free Text field and is the Broker Reference
that relates to a specific claim settlement. It is only
required on breakdowns that include settlement.

Settlement Second of up to two Broker References. Optional Alphanumeric


Broker Field (16 Chars)
Reference 2 This is a Free Text field and is the Broker Reference
that relates to a specific claim settlement..

David Willcocks 296 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Country of Identifies the country where the claim originated. Mandatory Alphanumeric
Origin Field (2 Chars)
If a range of values for ‘Country of Origin’ was
returned from the LIDS database from CICS
Transaction LY26 (via LY94) in Commarea C094
(see Appendix D), then these values should be
displayed in a ‘drop-down’ menu.

Original Original Insured. Optional Alphanumeric


Insured Field (50 Chars)
This is a Free Text field.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Insured Name of Insured. Optional Alphanumeric


Field (50 Chars)
This is a Free Text field.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a

David Willcocks 297 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Reinsured Name of Reinsured. Optional Alphanumeric


Field (50 Chars)
This is a Free Text field.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
Screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Cover Name of Cover Holder. Optional Alphanumeric


Holder Field (50 Chars)
This is a Free Text field.

This field is not entered by the broker on the


‘CLASS for Lloyds’ system.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For the first breakdown on an initial advice, it


will be pre-populated with the data entered by the
technician on the Claim Details screen.
(ii) For subsequent breakdowns on an initial advice
(or new breakdowns on a subsequent advice), it will
be pre-populated with the data entered for the
previous breakdown.
(iii) For subsequent advices, the field will pre-

David Willcocks 298 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
populated with the value held for this breakdown on
the previous transaction.

Claimant Name of Claimant. Optional Alphanumeric


Field (50 Chars)
This is a Free Text field.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Name of Name of the Vessel or Aircraft to which the claim Optional Alphanumeric
Vessel or applies Field (25 Chars)
Aircraft
This is a Free Text field.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.

(iii) For subsequent breakdowns on an internally


created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-

David Willcocks 299 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
populated with the value held for this breakdown on
the previous transaction.

Slip Type The description associated with the Slip Type of the Display Alphanumeric
Description transaction. This field is obtained from the Policy Only Field (25 Chars)
via the LIDS interface and stored within the CLASS
tables. It can be changed by the technician on the
Policy Details screen. The Slip Type description
only appears on the Enquiry version of the SCM
Breakdown screen. It is not shown on the Update
version.
Other This is an extra Name field that allows the user to
Name enter any other name that may apply to this claim
(i.e. that is not the reinsured, Insured, Cover Holder,
Original Insured or Vessel)

This is a Free Text field.

This field is not entered by the broker on the


‘CLASS for Lloyds’ system.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For the first breakdown on an initial advice, it


will be pre-populated with the data entered by the
technician on the Claim Details screen.
(ii) For subsequent breakdowns on an initial advice
(or new breakdowns on a subsequent advice), it will
be pre-populated with the data entered for the
previous breakdown.
(iii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Policy/Cert Date of inception of a policy or certificate. Optional Date


Period Field (DD/MM/CCYY)

From Date This will be pre-populated with the value entered by


the technician on the Policy/Risk Details screen (or
pre-populated on the Policy/Risk Details screen, if
entered by the broker on ‘CLASS for Lloyds’)

Either this field or the ‘Policy/Cert Period Qualifier’


must be entered if the Cover/Lineslip Date (or
Qualifier) have been completed. If lineslip period
entered, policy start date must not be outside range
of lineslip. (Handled by CICS transaction)

David Willcocks 300 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

When entered, must be a valid date. If not, display


the error E099 (see Appendix E) in the Error
Window (see Appendix B).

Note:- Partial Dates may be entered in this field.


Therefore the following may be allowed and the
date elements validated accordingly:

1) Century and Year only


2) Century, Year and Month only
3) Full Date

Policy/Cert End date of a policy or certificate. Optional Date


Period To Field (DD/MM/CCYY)

Date This will be pre-populated with the value entered by


the technician on the Policy/Risk Details screen (or
pre-populated on the Policy/Risk Details screen, if
entered by the broker on ‘CLASS for Lloyds’)

When entered, must be a valid date. If not, display


the error E100 (see Appendix E) in the Error
Window (see Appendix B).

This field must be completed, if the ‘Policy/Cert


Period From Date’ has been entered. If it is not,
display the error E101 (see Appendix E) in the
Error Window (see Appendix B).

This field must be greater than the Policy/Cert


Period From Date. If it is not, display the error
E105 (see Appendix E) in the Error Window (see
Appendix B).

Note:- Partial Dates may be entered in this field.


Therefore the following may be allowed and the
date elements validated accordingly:

1) Century and Year only


2) Century, Year and Month only
3) Full Date

Policy/Cert A Qualifier used to explain the absence of a policy Optional Alphanumeric


period. Field (1 Char)
Period
Qualifier
This will be pre-populated with the value entered by
the technician on the Policy/Risk Details screen (or

David Willcocks 301 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
pre-populated on the Policy/Risk Details screen, if
entered by the broker on ‘CLASS for Lloyds’)

Must be absent when policy/cert period dates


present – if not, display the error E102 (see
Appendix E) in the Error Window (see Appendix
B).

Must be present when policy/cert period dates


absent – if not, display the error E103 (see
Appendix E) in the Error Window (see Appendix
B).

Valid values are:-


(iv) 'T' = To Be Advised
(v) 'V' = Various
(vi) 'N' = Not Applicable

If the value entered is not one of the above, display


the error E104 (see Appendix E) in the Error
Window (see Appendix B).

Date of Either the date of loss or the first date of a period of Optional Date
Loss From loss. Field (DD/MM/CCYY)

Date
This will be pre-populated with the value entered by
the technician on the Claim Details screen (or pre-
populated on the Claim Details screen, if entered by
the broker on ‘CLASS for Lloyds’)

Either the ‘Date of Loss’ or the ‘Date Claim Made’


must be entered. Either the date(s), or the qualifier
must be entered. Therefore, if the Date Claim Made
From Date, the Date Claim Made Qualifier and the
Date of Loss Qualifier have not been entered – and
this field (Date of Loss From Date) has not been
completed, display the error E106 (see Appendix
E) in the Error Window (see Appendix B).

This field must not be completed if the Date of Loss


Qualifier has been entered. If it is, display the error
E107 (see Appendix E) in the Error Window (see
Appendix B).

Note:- Partial Dates may be entered in this field.


Therefore the following may be allowed and the
date elements validated accordingly:

David Willcocks 302 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
1) Century and Year only
2) Century, Year and Month only
3) Full Date

Date of The last date of a period of loss. Optional Date


Loss To Field (DD/MM/CCYY)

Date This field cannot be entered if the Date of Loss


from has not been entered. If it is, display the error
E108 (see Appendix E) in the Error Window (see
Appendix B).

If entered, this field must be greater than the Date of


Loss From. If it is not, display the error E109 (see
Appendix E) in the Error Window (see Appendix
B).

Note:- Partial Dates may be entered in this field.


Therefore the following may be allowed and the
date elements validated accordingly:

1) Century and Year only


2) Century, Year and Month only
3) Full Date

Date of Qualifier that explains the absence of a Loss Date. Optional Alphanumeric
Loss Field (1 Char)
Qualifier Either the ‘Date of Loss’ or the ‘Date Claim Made’
must be entered. Either the date(s), or the qualifier
must be entered. Therefore, if the Date Claim Made
From Date, the Date Claim Made Qualifier and the
Date of Loss From Date have not been entered –
and this field (Date of Loss Qualifier) has not been
completed either, display the error E106 (see
Appendix E) in the Error Window (see Appendix
B).

If entered, valid values are:-


(vii) 'T' = To Be Advised
(viii) 'V' = Various
(ix) 'N' = Not Applicable

If the value entered is not one of the above, display


the error E110 (see Appendix E) in the Error
Window (see Appendix B).
Loss Date This is narrative to describe the Date of Loss Optional Alphanumeric
Narrative Field (30 Chars)

David Willcocks 303 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
This field must not be completed if either Date of
Loss From Date or Date of Loss Qualifier is
entered.

Date Claim Either the date claim made or the first date of a Optional Date
Made From period of claim. Field (DD/MM/CCYY)

Date
This will be pre-populated with the value entered by
the technician on the Claim Details screen (or pre-
populated on the Claim Details screen, if entered by
the broker on ‘CLASS for Lloyds’)

Either the ‘Date of Loss’ or the ‘Date Claim Made’


must be entered. Either the date(s), or the qualifier
must be entered. Therefore, if the ‘Date of Loss
From Date’, the ‘Date of Loss Qualifier’ and the
‘Date Claim Made Qualifier’ have not been entered
– and this field (‘Date Claim Made From Date’) has
not been completed, display the error E106 (see
Appendix E) in the Error Window (see Appendix
B).

This field must not be completed if the ‘Date Claim


Made Qualifier’ has been entered. If it is, display
the error E111 (see Appendix E) in the Error
Window (see Appendix B).

Note:- Partial Dates may be entered in this field.


Therefore the following may be allowed and the
date elements validated accordingly:

1) Century and Year only


2) Century, Year and Month only
3) Full Date

Date Claim The last date of a period of claim. Optional Date


Made To Field (DD/MM/CCYY)

Date This field cannot be entered if the ‘Date Claim


Made From Date’ has not been entered. If it is,
display the error E112 (see Appendix E) in the
Error Window (see Appendix B).

If entered, this field must be greater than the ‘Date


Claim Made From Date’. If it is not, display the
error E113 (see Appendix E) in the Error Window
(see Appendix B).

Note:- Partial Dates may be entered in this field.

David Willcocks 304 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Therefore the following may be allowed and the
date elements validated accordingly:

1) Century and Year only


2) Century, Year and Month only
3) Full Date

Date Claim Qualifier that explains the absence of a ‘Date Claim Optional Alphanumeric
Made Made’. Field (1 Char)
Qualifier
Either the ‘Date of Loss’ or the ‘Date Claim Made’
must be entered. Either the date(s), or the qualifier
must be entered. Therefore, if the ‘Date of Loss
From Date’, the ‘Date of Loss Qualifier’ and the
‘Date Claim Made From Date’ have not been
entered – and this field (‘Date Claim Made
Qualifier’) has not been completed either, display
the error E106 (see Appendix E) in the Error
Window (see Appendix B).

If entered, valid values are:-


(x) 'T' = To Be Advised
(xi) 'V' = Various
(xii) 'N' = Not Applicable

If the value entered is not one of the above, display


the error E114 (see Appendix E) in the Error
Window (see Appendix B).
Catastroph The Catastrophe Code relating to the loss. Optional Alphanumeric
e Code Field (4 chars)
Initialisation of this field will be determined as
follows:- (note: this will be handled by the
appropriate CICS Transaction)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

David Willcocks 305 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

This field should be validated against the


Catastrophe Code table (name ?). If not present on
the table, display the error E070 (see Appendix E)
in the Error Window (see Appendix B).

PCS The PCS (Property Claims Service) Catastrophe Optional Alphanumeric


Catastroph Code relating to the loss. Field (4 chars)
e Code
Initialisation of this field will be determined as
follows:- (note: this will be handled by the
appropriate CICS Transaction)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

This field should be validated against the


Catastrophe Code table (name ?). If not present on
the table, display the error E071 (see Appendix E)
in the Error Window (see Appendix B).

Currency This is the Original (Estimate) Currency that applies Optional Alphanumeric
that applies to the SI Limits and Excess Limits (See below). Field (3 Chars)
to Policy
Limits This field will be pre-populated with the value
entered in the first occurrence of the Limit Currency
on the Policy/Risk Details Screen, either by the
broker or internal technician.

This must be a valid currency on the Currency


Table, TGLCURA. (All necessary data from this
table should be stored in the JAVA layer). If not
present on the Currency Table, display the error
E115 (see Appendix E) in the Error Window (see
Appendix B).

David Willcocks 306 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Any other more detailed validation will be carried
out by the appropriate CICS transaction.

Sum The Sum Insured Limit. Optional Numeric


Insured Field -(13)9.99
Limit This field will be pre-populated with the value
entered in the first occurrence of the Limit Currency
on the Policy/Risk Details Screen, either by the
broker or internal technician.

Format:- Z,ZZZ,ZZZ,ZZZ,ZZ9.99

Excess The Excess Limit. Optional Numeric


Limit Field -(13)9.99
This field will be pre-populated with the value
entered in the first occurrence of the Limit Currency
on the Policy/Risk Details Screen, either by the
broker or internal technician.

Format:- Z,ZZZ,ZZZ,ZZZ,ZZ9.99

Perils/ Any Perils or Conditions that may apply to the Optional Alphanumeric
Conditions policy. Field (70 chars)

This is a Free Text field.

This field will be pre-populated as detailed below:-


(note this is handled by the appropriate CICS
transactions)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Policy/Risk Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Location of The Location of the Loss. Optional Alphanumeric


Loss Field (50 chars)
This is a Free Text field.

David Willcocks 307 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

This field will be pre-populated as detailed below:-


(note this is handled by the appropriate CICS
transactions)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Voyage Voyage during which loss occurred. Optional Alphanumeric


Field (30 chars)
This is a Free Text field.

This field will be pre-populated as detailed below:-


(note this is handled by the appropriate CICS
transactions)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Name of Loss Name. Optional Alphanumeric


Loss Field (50 Chars)
This is a Free Text field.

This field will be pre-populated as detailed below:-

David Willcocks 308 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(note this is handled by the appropriate CICS
transactions)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Loss/Claim Description of loss. Mandatory Alphanumeric


Details (up Field (3 lines of 50
to 3 lines) This is a Free Text field. Chars)

This field will be pre-populated as detailed below:-


(note this is handled by the appropriate CICS
transactions)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
first 150 characters of the information supplied by
the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

SCM Name of Lawyer appointed to advise on the claim. Optional Alphanumeric


Lawyer Display (40 Chars)
Name For claim transactions that were not entered by the Only Field
broker on the ‘CLASS for Lloyds’ system, this field
will be pre-populated from that entered on the
Claim Details Screen. For ‘CLASS for Lloyds’

David Willcocks 309 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
transactions, the field will be populated by using the
Lawyer Code entered by the internal technician on
the Claim Details screen to access the Expert Table.
(This is because the name supplied by the broker
may not exist on the Expert Table)

If the user has entered a Lawyer Code on this screen


– this field will be populated with the Lawyer Name
from the Expert Table (accessed using the Lawyer
Code).

A drop-down list will be available for this field.


Details for this list will be obtained from the Expert
Table. The list should be in alphabetical order – If
the user enters a partial name, the list should start
from that point. (How are different types of expert
identified on this table?)

The user should be prevented from entering


anything that is not on the list.

If the user selects a name from the list, the


associated code should be used to populate the
Lawyer Code field.

This field will be populated using the details of the


Lawyer selected for SCM Advice on the ‘Expert
Fees Breakdown’ screen.

Note:- Only shown on enquiry version of the


screen.

SCM The Lawyer’s Reference. Optional Alphanumeric


Lawyer Display (16 Chars)
Reference This is a Free Text field. Only Field

This field will be pre-populated as detailed below:-


(note this is handled by the appropriate CICS
transactions)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally

David Willcocks 310 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Note:- the field will be populated using the Lawyer


Reference of the Lawyer selected for SCM Advice
on the ‘Expert Fees Breakdown’ screen.

Note:- Only shown on enquiry version of the


screen.

SCM The code associated with the Lawyer appointed to Optional Alphanumeric
Lawyer advise on the claim. Display (4 Chars)
Code Only Field
This field will be pre-populated from that entered
on the Claim Details Screen.

If the user has entered a Lawyer Name on this


screen – this field will be populated with the
Lawyer Code from the Expert Table (accessed using
the Lawyer Name).

The code entered should be validated against the


Expert Table (name ?). If not present on the table,
display the error E116 (see Appendix E) in the
Error Window (see Appendix B).

If the user enters a Lawyer Code, the associated


name should be used to populate the Lawyer Name
field.

This field will be populated using the details of the


Lawyer selected for SCM Advice on the ‘Expert
Fees Breakdown’ screen.

Note:- Only shown on enquiry version of the


screen.

SCM Name of Adjuster appointed to advise on the claim. Optional Alphanumeric


Adjuster Display (40 Chars)
Name For claim transactions that were not entered by the Only Field
broker on the ‘CLASS for Lloyds’ system, this field
will be pre-populated from that entered on the
Claim Details Screen. For ‘CLASS for Lloyds’
transactions, the field will be populated by using the

David Willcocks 311 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Adjuster Code entered by the internal technician on
the Claim Details screen to access the Expert Table.
(This is because the name supplied by the broker
may not exist on the Expert Table)

If the user has entered an Adjuster Code on this


screen – this field will be populated with the
Adjuster Name from the Expert Table (accessed
using the Adjuster Code).

A drop-down list will be available for this field.


Details for this list will be obtained from the Expert
Table. The list should be in alphabetical order – If
the user enters a partial name, the list should start
from that point. (How are different types of expert
identified on this table?)

The user should be prevented from entering


anything that is not on the list.

If the user selects a name from the list, the


associated code should be used to populate the
Adjuster Code field.

This field will be populated using the details of the


Adjuster selected for SCM Advice on the ‘Expert
Fees Breakdown’ screen.

Note:- Only shown on enquiry version of the


screen.

SCM The Adjuster’s Reference. Optional Alphanumeric


Adjuster Display (16 Chars)
Reference This is a Free Text field. Only Field

This field will be pre-populated as detailed below:-


(note this is handled by the appropriate CICS
transactions)

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a

David Willcocks 312 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Note:- the field will be populated using the Adjuster


Reference of the Adjuster selected for SCM Advice
on the ‘Expert Fees Breakdown’ screen.

Note:- Only shown on enquiry version of the


screen.

SCM The code associated with the Adjuster appointed to Optional Alphanumeric
Adjuster advise on the claim. Display (4 Chars)
Code Only Field
This field will be pre-populated from that entered
on the Claim Details Screen.

If the user has entered an Adjuster Name on this


screen – this field will be populated with the
Adjuster Code from the Expert Table (accessed
using the Adjuster Name).

The code entered should be validated against the


Expert Table (name ?). If not present on the table,
display the error E117 (see Appendix E) in the
Error Window (see Appendix B).

If the user enters an Adjuster Code, the associated


name should be used to populate the Adjuster Name
field.

This field will be populated using the details of the


Adjuster selected for SCM Advice on the ‘Expert
Fees Breakdown’ screen.

Note:- Only shown on enquiry version of the


screen.
Scheme Identifies whether settlement is processed under a Optional Alphanumeric
Code scheme. Used within accounting and settlement to Field (2 Chars)
control processing.

This field does not exist at CLASS Claim


Transaction level. It will be pre-populated as
described below:-
(note: this will be handled by the appropriate CICS
transaction)

David Willcocks 313 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(i) For the first breakdown on an internally created


initial advice, it will be initialised to spaces.
(ii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Must be a valid code (valid codes?). Only one code


currently used (Livestock Scheme). If not a valid
code, display the error E118 (see Appendix E) in
the Error Window (see Appendix B).

Trust Fund Identifies which US or Canadian Trust Fund is to be Optional Alphanumeric


Code used to pay the claim. Field (2 Chars)

This field is not entered by the broker on the


‘CLASS for Lloyds’ system.

It will be pre-populated as detailed below:-


(note:-

this will be handled by the appropriate CICS


transaction)

(i) For the first breakdown on an initial advice, it


will be pre-populated with the data entered by the
technician on the Policy/Risk Details screen.
(ii) For subsequent breakdowns on an initial advice
(or new breakdowns on a subsequent advice), it will
be pre-populated with the data entered for the
previous breakdown.
(iii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

A drop down list will be available. This will contain


values returned from LIDS for the OSND(s) entered
on the ‘Claim Creation’ screen. This list will be
filtered based on the value of FIL Code (if present).

i.e. If combinations returned from LIDS are:-


TF1 FIL1
TF2 FIL1
TF3 FIL1

David Willcocks 314 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
TF4 FIL2
TF5 FIL2
And the user has entered FIL2 in the ‘FIL Code 1’
field, then only TF4 and TF5 will appear in the
drop-down list.
The field is mandatory if the ‘Settlement Currency’
is US dollars or Canadian dollars, depending on
Year of account or date claim created (Detailed
rules to be provided ?)

Must be a valid value from the Trust Fund table


(name ?). If not, display the error E128 (see
Appendix E) in the Error Window (see Appendix
B).

The combination of FIL code and Trust Fund code


must be valid. This is determined by checking the
(name ?) Table. If the combination is not present on
this table, display the error E119 (see Appendix E)
in the Error Window (see Appendix B).

State Code Identifies the state or province of the claim. Optional Alphanumeric
Field (2 Chars)
This field is not entered by the broker on the
‘CLASS for Lloyds’ system.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For the first breakdown on an initial advice, it


will be pre-populated with the data entered by the
technician on the Policy/Risk Details screen.
(ii) For subsequent breakdowns on an initial advice
(or new breakdowns on a subsequent advice), it will
be pre-populated with the data entered for the
previous breakdown.
(iii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Mandatory for US or Canadian Trust Fund coded


claims. Therefore if ‘TF Code’ is present, this field
must be entered. If not, display the error E119 (see
Appendix E) in the Error Window (see Appendix
B).

This field must be a valid value from the

David Willcocks 315 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
State/Province Table (name ?). If not, display the
error E120 (see Appendix E) in the Error Window
(see Appendix B).

Country and State must be a valid combination.


(details to be provided ?). If not, display the error
E121 (see Appendix E) in the Error Window (see
Appendix B).

NAIC Code The National Association of Insurance Optional Alphanumeric


Commissioners (NAIC) Code. This identifies US Field (11 Chars)
cedants for regulatory reporting purposes.

This field is not entered by the broker on the


‘CLASS for Lloyds’ system.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For the first breakdown on an initial advice, it


will be pre-populated with the data entered by the
technician on the Policy/Risk Details screen.
(ii) For subsequent breakdowns on an initial advice
(or new breakdowns on a subsequent advice), it will
be pre-populated with the data entered for the
previous breakdown.
(iii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Mandatory if the US Trust Fund code is RI.


Therefore if user has entered a ‘TF Code’ of ‘RI’
and this field has been left blank, display the error
E122 (see Appendix E) in the Error Window (see
Appendix B).

Must be a valid NAIC code. Table maintained by


ins-sure with information supplied by NAIC. If the
entered code does not exist on the NAIC Code
Table (name ?), display the error E123 (see
Appendix E) in the Error Window (see Appendix
B).

NAIC Qualifier associated with the ‘National Association Optional Alphanumeric


Qualifier of Insurance Commissioners’ (NAIC) Code. This Field (1 Char)
indicates the type of NAIC code.

David Willcocks 316 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

This field is not entered by the broker on the


‘CLASS for Lloyds’ system.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For the first breakdown on an initial advice, it


will be pre-populated with the data entered by the
technician on the Policy/Risk Details screen.
(ii) For subsequent breakdowns on an initial advice
(or new breakdowns on a subsequent advice), it will
be pre-populated with the data entered for the
previous breakdown.
(iii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Mandatory if NAIC code provided. If NAIC Code


entered and this field has been left blank, display
the error E124 (see Appendix E) in the Error
Window (see Appendix B).

If entered, valid values are:-


(i) ‘G’ = Group NAIC Code
(ii) ‘P’ = Pool NAIC Code
(iii) ‘C’ = Company NAIC Code
(iv) ‘F’ = FEIN Code

If a code other than those listed above is entered,


display the error E125 (see Appendix E) in the
Error Window (see Appendix B).

War Indicates whether the claim includes elements of Tick-Box N/a


Indicator War losses.

This field will be pre-populated as detailed below:-


(note this is handled by the appropriate CICS
transactions).

(i) For initial advices loaded on the ‘CLASS for


Lloyds’ system it will be pre-populated with the
information supplied by the broker.
(ii) For the first breakdown on an internally created
initial advice, it will be pre-populated with the data
entered by the technician on the Claim Details
screen.

David Willcocks 317 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(iii) For subsequent breakdowns on an internally
created initial advice (or new breakdowns on a
subsequent advice), it will be pre-populated with the
data entered for the previous breakdown.
(iv) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

FIL Code 1 Identifies Foreign Insurance legislation applicable Optional Alphanumeric


to the claim. Field (4 Chars)

This field is not entered by the broker on the


‘CLASS for Lloyds’ system.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For the first breakdown on an initial advice, it


will be pre-populated with the data entered by the
technician on the Policy/Risk Details screen.
(ii) For subsequent breakdowns on an initial advice
(or new breakdowns on a subsequent advice), it will
be pre-populated with the data entered for the
previous breakdown.
(iii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Must be a valid value from the FIL Code table


(name ?). If not present on the FIL Code Table,
display the error E126 (see Appendix E) in the
Error Window (see Appendix B).

Must be a valid value from the Accounting Trust


Fund table (name ?). The combination of FIL code
and Trust Fund code must be valid. If not, display
the error E119 (see Appendix E) in the Error
Window (see Appendix B).

FIL Code 2 Identifies Foreign Insurance legislation applicable Optional Alphanumeric


to the claim (second of two codes). Field (4 Chars)

This field is not entered by the broker on the


‘CLASS for Lloyds’ system.

It will be pre-populated as detailed below:-

David Willcocks 318 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(note:- this will be handled by the appropriate CICS
transaction)

(i) For the first breakdown on an initial advice, it


will be pre-populated with the data entered by the
technician on the Policy/Risk Details screen.
(ii) For subsequent breakdowns on an initial advice
(or new breakdowns on a subsequent advice), it will
be pre-populated with the data entered for the
previous breakdown.
(iii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Must be a valid value from the FIL Code table


(name ?). If not present on the FIL Code Table,
display the error E127 (see Appendix E) in the
Error Window (see Appendix B).

Other TF Other Trust Fund Code. (Non-US Trust Fund Code) Optional Alphanumeric
Code Field (2Chars)
If a range of values for Non-US Trust Fund Code
was returned from the LIDS database from CICS
Transaction LY26 (via LY94) in Commarea C094
(see Appendix D), then these values should be
displayed in a ‘drop-down’ menu.

DTI Code Department of Trade and Industry code. Coding Mandatory Alphanumeric
used for reporting to responsible government Field (2 Chars)
department. Identifies a combination of
geographical location and business type. Still used
in some MRAD reports.

The DTI Code must be on the DTI Code Table


(name ?). If not, display the error E187 (see
Appendix E) in the error window (see Appendix
B).

USA/Canad The USA/Canada indicator. This tick-box is only Optional N/a


a Indicator available if the Settlement Currency is USD, United Tick-box
States Dollars (It may also be ticked for Settlement
Currency of CAD, Canadian Dollars, but this can be
system derived).

Loss Fund This tick-box indicates whether the current Tick-Box N/a
Entry breakdown is a Loss Fund Entry.
Indicator
Once ticked this field will be protected on all

David Willcocks 319 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
subsequent advices.

Loss Fund This tick-box indicates that any payment on the Tick-Box N/a
Advance current breakdown represents a Loss Fund Advance.
Indicator

Block This is the Block Indicator. This field is a Tick-Box. Optional N/a
Indicator Tick-Box

Service Service Type is used to show the Segmentation of Optional Alphanumeric


Type the claim at COR Level. It will enable XCS to route Field (1 Char)
(Update the COR to an appropriate Adjuster (i.e. basic skills
Version) routing). Validation will be switched on to force a
non blank value to be entered in this field from 1 st
Jan 2009 onwards.

This field is not entered by the broker on the


‘CLASS for Lloyds’ system.

It will be pre-populated as detailed below:-


(note:- this will be handled by the appropriate CICS
transaction)

(i) For the first breakdown on an initial advice, it


will be pre-populated with a space, except when the
claim is a Scheme Canada claim when it will be
pre-populated with ‘A'.
(ii) For subsequent breakdowns on an initial advice
(or new breakdowns on a subsequent advice), it will
be pre-populated with the value from the previous
breakdown’.
(iii) For subsequent advices, the field will be pre-
populated with the value held for this breakdown on
the previous transaction.

Must be a valid value selected from the drop down


list shown below.
C - Complex
S - Standard
P - Technical Processing
A- Technical Accounting
Space is allowed to be selected from the list

When an entry is selected, a single character will be


moved into the commarea to be passed to CICS
The associated CICS program will perform all of
the validation on this field

David Willcocks 320 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

Service A single character will be passed in the commarea Display Alphanumeric


Type for this field and this will be converted into a text Only Field (20 Chars)
(Enquiry value as shown in the list for the Update Version of
Version) the field above.
Enquiry Fields

A different view of the SCM Advice (Breakdown) Screen is displayed in enquiry mode. This view
contains a number of additional fields. Unfortunately, when this enhancement was made, this document
was not updated.

The following fields have been added to this enquiry view as part of the Syndicate Opt-Out
enhancement:-

The following two fields should be displayed towards the end of the ‘Financials’ section – below
the User Id field. The fields should be displayed in both the Update and Enquiry views

Claim Opt- This field indicates whether the claim Display Alphanum
Out Status as a whole is ‘Suspended’ or not. I.e. Only eric (7
one or more syndicates have opted Field chars)
out of settlement. If none of the
syndicates on the claim have opted
out of settlement, but some
syndicates on the policy have – as
status of ‘Partial’ will be displayed.
Claim Opt- If only one syndicate on the claim has Display Alphanum
Out Date opted out of settlement, this field Only eric (8
shows the date that this opt-out was Field chars)
effective from. If more than one
syndicate has opted out of
settlement, this field will show
‘various’.
The following two fields should be displayed for each line of market details. These fields will only
apply to the Enquiry View of the Screen. They should be displayed on each line of the market details,
between Syndicate Reference and Bureau Leader.

Synd. Opt- This shows the individual Opt-Out Display Alphanum


Out Status status of each syndicate on the Only eric (7
(n) market. This field will either be Field chars)
‘Suspend’ or blank.
Synd. Opt- This shows the date that each Display Alphanum
Out Date (n) syndicate opted-out of settlement. Only eric (8
Field Chars)

David Willcocks 321 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

D. Commands - (Main Screen)


VAT Rates This button is shown alongside the 100% VAT Command
Amount field. If a VAT Amount has been entered,
the ‘VAT Rates’ button should be pressed in order to
enter up to 6 VAT Rates (and their associated
amounts) that apply to the current breakdown. If a
previously entered VAT Amount is set to zero, the
associated VAT Rates/Amounts will be deleted.

Therefore, if this button is pressed and the 100%


VAT Amount is zero, display the error E174 (see
Appendix E) in the Error Window (see Appendix
B).

If the 100% VAT Rate is not equal to zero, display


the VAT Rates window. This is a new window, with
no Navigation Bar or Functions at the top of the
screen. It will simply overlay the SCM Advice
Screen and will then be closed down before the user
continues processing the current transaction. Note: a
new Session Record is not required for the ‘VAT
Rates’ screen, as the user is unable to navigate
anywhere from the screen – merely close it down
again.

For details of this screen, see Section 4.37.

Expert Fees This button is shown in the Financials area of the Command
Breakdown SCM Advice Screen – as shown in Section 4.17.1 If
a Fees PTT or Outstanding Amount has been
entered, the ‘Expert Fees Breakdown’ button should
be pressed in order to split the fees amounts across
up to 100 experts (Lawyers and/or Adjusters). The
button may be also be pressed on transactions that
do not include Fees PTT or Outstanding Amounts,
in order to specify experts and/or enquire upon the
previously settled fees amounts.

If the ‘Expert Fees Breakdown’ button is pressed


and the screen is in ‘Update’ mode (i.e. C043-
SCREEN-MODE = ‘U’) and C043-ORIG-CURR =
‘JPY’ and the amount entered in any of the
following fields includes decimal places:-
‘PTT Loss’
‘PTT Exp’
‘PTT Fee’

David Willcocks 322 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
‘PTT Total’
Then, issue the Error ‘E415’ (PAID THIS TIME
AMOUNTS MUST NOT CONTAIN DECIMAL
PLACES FOR ‘JPY’).

If the ‘Expert Fees Breakdown’ button is pressed,


display the ‘Expert Fees Breakdown’ screen. This is
a new screen, with no Navigation Bar or Functions
at the top of the screen.
Note: a new Session Record is not required for the
‘Expert Fees Breakdown’ screen, as the user is
unable to navigate anywhere from the screen –
merely return to the ‘SCM Advice (Breakdown)’
screen.

For details of this screen, see Section 4.41.

Save This key allows the user to save the details they Command
have entered on the screen without being navigated
onto a different screen. Note:- this button should be
disabled if the screen is being viewed in ‘Enquiry’
mode (i.e. C043-SCREEN-MODE = ‘E’)

(i) Call CICS transaction LY01 (see Appendix


C.1) to validate that any details entered on
the screen are valid – using Commarea
C044 (see Appendix D).

On return, check the C044-PROG-STATUS


And report any errors/warnings in the usual
Way.

(ii) If no errors returned from LY44, Call CICS


transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C045.
(see Appendix D).

On return, check the C045-PROG-STATUS


And report any errors/warnings in the usual
Way.

End Breakdown (iii) If C043-SCREEN-MODE = ‘U’(Update), Command


call CICS transaction LY01 (see Appendix

David Willcocks 323 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C.1) to validate that any details entered on
the screen are valid – using Commarea
C044 (see Appendix D).

On return, check the C044-PROG-STATUS


And report any errors/warnings in the usual
Way.

(iv) If C043-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY44, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C045. (see Appendix D).

On return, check the C045-PROG-STATUS


And report any errors/warnings in the usual
Way.

(v) If no errors returned from LY45 or C043-


SCREEN-MODE = ‘E’(Enquiry), call the
CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.
N.B. Set the C011-SCM-ADV-CODE to ‘E’
(End Breakdown)

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(vi) Navigate the user to whichever program is


identified in C011-NEXT-PROGRAM (see
Appendix N).

New Breakdown (i) If C043-SCREEN-MODE = ‘U’(Update), Command


call CICS transaction LY01 (see Appendix
C.1) to validate that any details entered on
the screen are valid – using Commarea
C044 (see Appendix D).

On return, check the C044-PROG-STATUS


and report any errors/warnings in the usual
way.

David Willcocks 324 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

(ii) If C043-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY44, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C045. (see Appendix D).

On return, check the C045-PROG-STATUS


and report any errors/warnings in the usual
way.

(iii) If no errors returned from LY45 or C043-


SCREEN-MODE = ‘E’(Enquiry), call
CICS transaction LY01 (see Appendix C.1)
to create a new breakdown and update the
Session Record with the details of the new
breakdown–using COMMAREA C047. (see
Appendix D).

On return, check the C010-PROG-


STATUS and report any errors/warnings in
the usual way.

(iv) If no errors returned from LY47, call the


CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.
N.B. Set C011-SCM-ADV-CODE to ‘N’.

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(v) If no errors returned from LY11, navigate


the user to the program indicated by C011-
NEXT-PROGRAM (see Appendix N)

Create R/I (i) If C043-SCREEN-MODE = ‘U’(Update), Command


Schedule call CICS transaction LY01 (see Appendix
C.1) to validate that any details entered on
the screen are valid – using Commarea
C044 (see Appendix D).

On return, check the C044-PROG-STATUS

David Willcocks 325 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
and report any errors/warnings in the usual
way.

(ii) If C043-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY44, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C045. (see Appendix D).

On return, check the C045-PROG-STATUS


and report any errors/warnings in the usual
way.

(iii) Navigate the user to ‘R/I Schedule’ screen


(see section 4.18)

Create Binder (i) If C043-SCREEN-MODE = ‘U’(Update), Command


Schedule call CICS transaction LY01 (see Appendix
C.1) to validate that any details entered on
the screen are valid – using Commarea
C044 (see Appendix D).

On return, check the C044-PROG-STATUS


and report any errors/warnings in the usual
way.

(ii) If C043-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY44, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C045. (see Appendix D).

On return, check the C045-PROG-STATUS


and report any errors/warnings in the usual
way.

(iii) Navigate the user to ‘Binder Schedule’


screen (see section 4.19)

Back to (i) If C043-SCREEN-MODE = ‘U’(Update),


Schedule call CICS transaction LY01 (see Appendix
C.1) to validate that any details entered on
the screen are valid – using Commarea
C044 (see Appendix D).

David Willcocks 326 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
On return, check the C044-PROG-STATUS
and report any errors/warnings in the usual
way.

(ii) If C043-SCREEN-MODE = ‘U’(Update)


and no errors returned from LY44, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details
entered on the screen – using
COMMAREA C045. (see Appendix D).

On return, check the C045-PROG-STATUS


and report any errors/warnings in the usual
way.

(vii) If no errors returned from LY45 or C043-


SCREEN-MODE = ‘E’(Enquiry), call the
CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix
D). This will invoke the ‘Navigation’
program, which decides on the next
program the user should be navigated to.
N.B. Set the C011-SCM-ADV-CODE to ‘B’
(Back to Schedule)

On return, check the Program Status in the


usual way, reporting errors if they exist in
the Error Screen (see Appendix B)

(iii) Navigate the user to whichever program is


identified in C011-NEXT-PROGRAM (see
Appendix N).

EURO Conv. If the details displayed are in EURO and were Command
Details originally in a redundant NCU currency which has
undergone conversion, an extra button will be
enabled on the screen – the ‘EURO Conv. Details’
button. If the user pushes this button, the ‘EURO
Conversion Details’ will be displayed. This is a new
window, with no Navigation Bar or Functions at the
top of the screen. It will simply overlay the SCM
Advice Screen and will then be closed down before
the user continues processing the current
transaction. Note: a new Session Record is not
required for the ‘EURO Conversion Details’ screen,
as the user is unable to navigate anywhere from the
screen – merely close it down again.

David Willcocks 327 May 2002


Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command

For details of this screen, see Section 4.31.

CCS Amounts If the settlement currency specified on the Financial Command


Details Control screen is a CCS currency and the
treasury rate has been returned from LIDS, an extra
button will be enabled on the screen – the ‘CCS
Amounts