0% found this document useful (0 votes)

571 views652 pages

XCS CLASS - Functional Specification - Process Description

This document outlines changes made to the Claims Applications Convergence Web GUI Functional Specification. It includes a change control log listing the release date, person who made the change, associated service incident or technical project number, description of changes made, and which screens were involved. The log contains over 20 entries documenting enhancements and fixes to various screens related to claims processing.

Uploaded by

Pradyut Tiwari

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

571 views652 pages

XCS CLASS - Functional Specification - Process Description

Uploaded by

Pradyut Tiwari

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

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

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

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

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

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’

(iii) On selection of the ‘Group Enquiry’

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

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

User should select one of these options:-

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

(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’

(iii) On selection of the ‘Group Enquiry’

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

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

User should select one of these options:-

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

(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’

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

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

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

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’

(iii) On selection of the ‘Group Enquiry’

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

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

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

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

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

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

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’

(iii) On selection of the ‘Group Enquiry’

(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

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

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

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

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

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’,

(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’

(iii) On selection of the ‘Group Enquiry’

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

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

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

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

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

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

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

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

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

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

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

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

(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

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

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

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

(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

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

(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

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’,

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

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’

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

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

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

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

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

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

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

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’

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

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-

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

(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

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

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

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

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

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

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

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

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’,

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

On return, check the C071-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’

(iii) On selection of the ‘Group Enquiry’

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

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

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

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

(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,

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

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

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

(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

(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

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’

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

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

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-

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

(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

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

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

(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

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

(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

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

User should select one of these options.

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

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

On return, check the C071-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’

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

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

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

(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,

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

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

(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

(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

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’

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

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)

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

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

(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

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

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

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

(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

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

(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

User should select one of these options.

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

David Willcocks 236 May 2002

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

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

On return, check the C071-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’

(iii) On selection of the ‘Group Enquiry’

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

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

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

(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

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,

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

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

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

(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

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’

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

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.

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

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

(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

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

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

(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

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

(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

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

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’,

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

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

(iii) On selection of the ‘Group Enquiry’

(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

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

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

(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

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,

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

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

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

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

(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

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’

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

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

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

(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

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)

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

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

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

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

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

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

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.

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

David Willcocks 312 May 2002

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

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

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

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

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

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

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.

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

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

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-

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’ button. If the user pushes this button, the
‘CCS Amounts’ 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 ‘CCS Amounts’ 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.32.

(i) Call CICS transaction LY01 (see Appendix

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

(iii) Rebuild the screen, based on the data

returned in the C043 Commarea.

David Willcocks 328 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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
‘Breakdown (SCM Advice)’ screen. Therefore:-

(i) 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)

(ii) Rebuild the screen, based on the data

returned in the C043 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

(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

David Willcocks 329 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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 330 May 2002

Xchanging Ins-sure Services Ltd
4.18. R/I Schedule Screen

4.18.1. Screen Layout

Below is a ‘mock-up’ of the ‘R/I Schedule’ Screen. Two screen images

are shown here, as the technician may need to scroll right in order to
view some fields.

David Willcocks 331 May 2002

Xchanging Ins-sure Services Ltd
4.18.2. 4.18.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
LY17 Validate Claim Transaction
LY19 Currency Validation
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
LY46 Check whether Curr/Trans. Validation
reqd.
LY47 Create New Breakdown
LY48 Build R/I Schedule Screen
LY49 R/I Schedule Screen Validation
LY50 R/I Schedule Screen D/B Update
LY51 Delete Breakdown
LY52 Check for next Currency
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
LZ07 Build LIDS Comparison Screen
LZ11 Create Re-Advice – Initial Validation

David Willcocks 332 May 2002

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

The fields and the navigation bar on this screen will be

derived as follows:-

Field Type Source

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 C048 (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: Each occurrence of C048-COR returned in the C048-BREAKDOWN-TABLE

(together with its associated C048-BREAKDOWN-NO) should be stored for use later.
These, along with the values in C048-KEY, will be used to update the Session Record if the
user ‘clicks’ on a ‘COR’. This will enable the correct details to be displayed on the ‘SCM
Advice’ screen.

XCR Field C048-XCR

(This field should be protected)
UCR Field C048-UCR
(This field should be protected)
TR Field C048-TR
(This field should be protected)
OSND Field C048-ORIG-REF
(This field should be protected)

Orig. Broker Field C048-ORIG-BKR

(This field should be protected)
Signed Tick-Box C048-SIGNED-IND
(This field should be protected)

David Willcocks 333 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source

Peer Review Field C048-PEER-REV-IND

(This field should be protected)
Orig.Curr Field C048-ORIG-CURR
(This field should be protected)
Read throug each occurrence in the C048-BREAKDOWN-TABLE, for
each occurrence with C048-COR > spaces, create a line on the screen.
COR (n) Field C048-COR (n)
(If C048-COR-ATTR (n) = ‘P’, this field
should be protected)
Reinsured (n) Field C048-REINSURED (n)
(If C048-REINS-ATTR (n) = ‘P’, this
field should be protected)
Broker Ref 1 Field C048-BKR-REF-1 (n)
(n) (If C048-BKR-REF-ATTR (n) = ‘P’, this
field should be protected)
Trust Fund Field C048-TF-CODE (n)
Code (n) (If C048-TF-CODE-ATTR (n) = ‘P’, this
field should be protected)
State Code (n) Field C048-STATE-CODE (n)
(If C048-STATE-CODE-ATTR (n) = ‘P’,
this field should be protected)
DOL From (n) Field C048-LOSS-DATE-FROM (n)
(If C048-DOL-ATTR (n) = ‘P’, this field
should be protected)
DOL To (n) Field C048-LOSS-DATE-TO (n)
(If C048-DOL-ATTR (n) = ‘P’, this field
should be protected)
DOL Qual (n) Field C048-LOSS-DATE-QUAL (n)
(If C048-DOL-ATTR (n) = ‘P’, this field
should be protected)
Catastrophe Field C048-CAT-CODE (n)
Code (n) (If C048-CAT-ATTR (n) = ‘P’, this field
should be protected)
PCS Field C048-PCS-CAT-CODE (n)
Catastrophe ( If C048-PCS-CAT-ATTR (n) = ‘P’, this
Code (n) field should be protected)
NAIC Code (n) Field C048-NAIC-CODE (n)
(If C048-NAIC-CODE-ATTR (n) = ‘P’,
this field should be protected)
NAIC Qualifier Field C048-NAIC-QUAL (n)
(n) (If C048-NAIC-QUAL-ATTR (n) = ‘P’,
this field should be protected)
Paid To Date Field C048-PTD-AMT (n)
Amount (n) (If C048-PTD-AMT-ATTR (n) = ‘P’, this
field should be protected)
Paid This Time Field C048-PTT-AMT (n)

David Willcocks 334 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Amount (n) (If C048-PTT-AMT-ATTR (n) = ‘P’, this
field should be protected)

Outstanding Field C048-OUTST-AMT (n)

Amount (n) (if C048-OUTST-AMT-ATTR (n) = ‘P’,
this field should be protected)
Outstanding Field C048-OUTST-QUAL (n)
Amount (If C048-OUTST-QUAL-ATTR (n) = ‘P’,
Qualifier (n) this field should be protected)
The following fields will not be supplied by the LY48 CICS Transaction but should be
calculated by the Java Layer. This is because they need to be updated as the Paid This
Time and Outstanding Amounts are updated by the technician.
Total Paid This Field Accumulation of all Paid This Time
Time amounts
(This field should be protected)
Total Field Accumulation of all Outstanding
Outstanding Amounts
Amount (This field should be protected)
C. Commands:-

The derivation for the commands is also returned in the C048

Commarea.
Delete Line (n) Option If C048-DELETE-ATTR (n) = ‘P’, this
Button button should be protected (or
preferably not displayed)
Delete Selected Comman If C048-DEL-BD-ATTR = ‘P’, this
Breakdowns d field should be protected (or
preferably not displayed)
New Comman If C048-NEW-BD-ATTR = ‘P’, this
Breakdown d button should be protected (or
preferably not displayed)
Next Currency Comman If C048-NEXT-CURR-ATTR = ‘P’,
d this button should be protected (or
preferably not displayed)
Finish Comman If C048-FINISH-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
PREV Comman If C048-PREV-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
NEXT Comman If C048-NEXT-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)

David Willcocks 335 May 2002

Xchanging Ins-sure Services Ltd
4.18.4. Process Description

This screen is the R/I Schedule Screen.

If a large number of breakdowns are required on a

particular claim where the vast majority of information
on each is the same, the user may opt to create a
schedule from the ‘SCM Advice’ screen. The user may
opt to create either a R/I Schedule or a Binder Schedule
depending on the type of business. Each line created by
the user on this schedule will result in a new
breakdown being created on the claim. The Claims
Office Reference will be assigned as each line is
created. If details other than those shown on the screen
need to be amended the user will be able to ‘click’ on
the Claims Office Reference to be taken to the SCM
Advice Screen. New breakdowns cannot be created if
any subsequent transactions exist on the claim.

The user will also have the ability to delete breakdowns

on this screen – but only on an unadvised claim
transaction where there are no subsequent transactions
and the breakdown in question did not exist on the
previous transaction.
In other words, they may remove breakdowns that they
have just added by mistake.

Fig 4.18.4.1. Field/Command Processing for ‘R/I Schedule’

Screen

Field / Attributes Data Type

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.

David Willcocks 336 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

(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

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)

David Willcocks 337 May 2002

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

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

(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

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

David Willcocks 338 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(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’,

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

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

David Willcocks 339 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
returned by previous transaction, LY71)

(iii) On selection of the ‘Group Enquiry’

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

David Willcocks 340 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

David Willcocks 341 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

David Willcocks 342 May 2002

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

If the user selects ‘Create Subsequent Advice

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,

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

David Willcocks 343 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

David Willcocks 344 May 2002

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

‘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

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

(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 C048 to obtain
the data and field protection for the
current screen.

On return check the Program Status and

David Willcocks 345 May 2002

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

(iii) Rebuild the current screen using the

data returned in the C048 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 346 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 C048-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 C049 (see
Appendix D).

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

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

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

(iii) If C048-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY50, 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 C048-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 347 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.3 Field Protection will be handled by the ‘Field Attributes’ returned in the C048 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

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’

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 currency Display Alphanumeric
that relates to the breakdown being viewed) 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 348 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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
Original This is the currency that relates to the breakdown Display Alphanumeric
Currency being maintained. Only Field (3 Chars)
COR (n) This is the Claims Office Reference. This field is Display Alphanumeric
system generated for each line created on the Only Field (14 Chars)
screen.

If the user ‘clicks’ on this field, they will be

navigated to the ‘SCM Advice’ Screen – see below
in the Commands Section.

Reinsure This is the name of the Reinsured. Mandatory Alphanumeric

d (n) Field (50 chars)
This is a free-text field subject only to ASCII
validation, described above.

Field derivation is as folows (handled by CICS

transaction):-
(i) 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.
(ii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

Broker The first of the two broker references. Mandatory Alphanumeric

Referenc Field (16 chars)
e 1 (n)
Trust Identifies which US or Canadian Trust Fund is to be Optional Alphanumeric
Fund used to pay the claim. Field (2 Chars)
Code (n)
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 subsequent breakdowns on an initial advice

David Willcocks 349 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(or new breakdowns on a subsequent advice), it will
be pre-populated with the data entered for the
previous breakdown.
(ii) 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.

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

State Identifies the state or province of the claim. Optional Alphanumeric

Code (n) 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 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.
(ii) 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 E129 (see
Appendix E) in the Error Window (see Appendix
B).

This field must be a valid value from the

State/Province Table (name ?). If not, display the
error E120 (see Appendix E) in the Error Window
(see Appendix B).

David Willcocks 350 May 2002

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

Date of Either the date of loss or the first date of a period of Optional Date
Loss loss. Field (DD/MM/CCYY)

From (n)
It will be pre-populated as detailed below:-
(note:- this will be handled by the appropriate CICS
transaction)

(i) For subsequent breakdowns on an initial advice

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

Date of The last date of a period of loss. Optional Date

Loss To Field (DD/MM/CCYY)

(n) It will be pre-populated as detailed below:-

(note:- this will be handled by the appropriate CICS
transaction)

(i) For subsequent breakdowns on an initial advice

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

Date of Qualifier that explains the absence of a Loss Date. Optional Alphanumeric
Loss Field (1 Char)
It will be pre-populated as detailed below:-

David Willcocks 351 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Qualifier (note:- this will be handled by the appropriate CICS
(n) transaction)

(i) For subsequent breakdowns on an initial advice

If entered, 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 E110 (see Appendix E) in the Error
Window (see Appendix B).

If entered, the Date of Loss From and To Dates

must not be entered. If they are, display the error
E107 (see Appendix E) in the Error Window (see
Appendix B).
Catastro The Catastrophe Code relating to the loss. Optional Alphanumeric
phe Code Field (4 Chars)
(n) Initialisation of this field will be determined as
follows:- (note: this will be handled by the
appropriate CICS Transaction)

(i) 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.
(ii) 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 E070 (see Appendix E)
in the Error Window (see Appendix B).

PCS The PCS (Property Claims Service) Catastrophe Optional Alphanumeric

Catastro Code relating to the loss. Field (4 Chars)

David Willcocks 352 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
phe Code Initialisation of this field will be determined as
(n) follows:- (note: this will be handled by the
appropriate CICS Transaction)

(i) For subsequent breakdowns on an internally

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

NAIC The ‘National Association of Insurance Optional Alphanumeric

Code (n) 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 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).

David Willcocks 353 May 2002

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

NAIC The qualifier associated with the ‘National Optional Alphanumeric

Qualifier Association of Insurance Commissioners’ (NAIC) Field (1 Char)
(n) Code. This indicates the type of NAIC code.

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 subsequent breakdowns on an initial advice

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

(v) ‘G’ = Group NAIC Code
(vi) ‘P’ = Pool NAIC Code
(vii) ‘C’ = Company NAIC Code
(viii) ‘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).

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 breakdown. It is a 100%
(n) amount.

It will be initialised as follows:-

(i) On initial advices, it will be initialsied to zero
(ii) On subsequent advices, it will be initialsed to
the Previously Settled amount for the current
breakdown plus the Paid This Time (if entered yet)
on the current breakdown.
(iii) For newly created breakdowns on initial or
subsequent advices, it will be set to zero.

David Willcocks 354 May 2002

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

Paid This The Paid This Time amount is the amount to be paid Optional Numeric
Time on this movement of the current Breakdown (COR). Field -(13)9.99
Amount
(n) It will be initialisesd to zeroes.
Outstandi This is the estimated outstanding amount still to be Optional Numeric
ng settled on the current breakdown. Field -(13)9.99
Amount
(n) It will be initialised to the value held for this
breakdown on the previous transaction within the
claim. If this is a first advice or a new breakdown
on a subsequent advice, this field will be initialised
to zero.

Total This is the qualifier associated with the Total Optional Alphanumeric
Outstand Outstanding Amount. Field (1 Char)
ing
Amount It will be pre-populated as detailed below:-
(note:- this will be handled by the appropriate CICS
Qualifier
transaction)

(i) 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 (which in turn was pre-
populated with the details entered on the Financial
Details Control Screen).
(ii) For subsequent advices, the field will pre-
populated with the value held for this breakdown on
the previous transaction.

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
(vii) ‘Z’ = Zero recommended reserve.

If the user enters a value other than the above,

David Willcocks 355 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
highlight the field and display the error ‘E088’ (see
Appendix E) in the Error Window (see Appendix
B).

Total This is the total of all Paid This Time amounts Display Numeric
Paid This across all breakdowns for the current Original Only Field -(13)9.99
Time Currency.

This is shown for display purposes only – in order

to assist the technician in ensuring that the Paid
This Time amounts total that specified on the
Financial Details Control Screen.
Total This is the total of all Outstanding amounts across Display Numeric
Outstand all breakdowns for the current Original Currency. Only Field -(13)9.99
ing
Amount This is shown for display purposes only – in order
to assist the technician in ensuring that the
Outstanding amounts total that specified on the
Financial Details Control Screen.

D. Commands - (Main Screen).

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C048-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
C049 (see Appendix D).

On return, check the C049-PROG-STATUS

and report any errors/warnings in the usual
way.

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

and no errors returned from LY49, Call
CICS transaction LY01 (see Appendix C.1)
to update the database with the details

David Willcocks 356 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
entered on the screen – using
COMMAREA C050. (see Appendix D).

On return, check the C050-PROG-STATUS

and report any errors/warnings in the usual
way.

Claims If the user wishes to add or amend fields other than Command
Office those that are shown on the R/I Schedule screen,
Reference they can ‘click’ on the Claims Office Reference.
This field is display only on the screen and cannot
be changed – however, it will provide a ‘link’ to the
‘SCM Advice’ screen. If the user ‘clicks’ on the
Claims Office Reference, the details on the screen
should be validated and stored and the user should
be navigated to the ‘SCM Advice’ screen.

(vi) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(vii) If C048-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
C049 (see Appendix D).

On return, check the C049-PROG-STATUS

and report any errors/warnings in the usual
way.

(viii) If C048-SCREEN-MODE = ‘U’ (Update)

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

On return, check the C050-PROG-STATUS

and report any errors/warnings in the usual
way.

(ix) Call CICS transaction LY01 (see Appendix

C.1) to update the Session Record with the
key values for the Claims Office Reference

David Willcocks 357 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
selected – using COMMAREA C010. (see
Appendix D). Pass the following values in
the C010 Commarea:-

C048-UCR-TR-SYS-REF
C048-CURR-NO
C048-SDN-NO
C048-STAT-SPLIT-NO (n)
C048-BREAKDOWN-NO (n)

(x) If no errors returned from LY10, call the

On return, check the Program Status in the

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

(xi) If no errors returned from LY11, navigate

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

New Pressing this button will cause the creation of a new Command
Breakdown breakdown (based on the previous breakdown), An
Claims Office Reference will be assigned by the
system.

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) Call CICS transaction LY01 (see Appendix

C.1) to validate that any details entered on
the screen are valid – using Commarea
C049 (see Appendix D).

On return, check the C049-PROG-STATUS

and report any errors/warnings in the usual
way.

(iii) If no errors returned from LY49, Call CICS

transaction LY01 (see Appendix C.1) to

David Willcocks 358 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
update the database with the details entered
on the screen – using COMMAREA C050.
(see Appendix D).

On return, check the C050-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) If no errors returned from LY50, call CICS

transaction LY01 (see Appendix C.1) to
create a new breakdown–using
COMMAREA C047. (see Appendix D).

On return, check the C047-PROG-

STATUS and report any errors/warnings in
the usual way.

(v) If no errors are returned from LY47, rebuild

the ‘R/I Schedule’ screen from scratch –
this will rebuild the table in the C048
Commarea (which is required to enable the
user to ‘click’ on the new breakdown and be
navigated to the ‘SCM Advice’ screen) and
rebuild the Navigation Bar at the left of the
screen, incorporating the new breakdown.

Delete If the user presses this button, a pop-up window Command

Selected will be displayed to them asking them to confirm
Breakdowns their deletion request. Assuming they do, the details
on the screen will be validated, the database
updated and the screen rebuilt with the selected
lines removed.

(i) If no lines have been selected for deletion,

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

(ii) Display the ‘Deletion Confirmation’ pop-up

window (see Appendix P). If the user
selects ‘YES’ in this window, continue with
the processing below. Otherwise, if the user
selects ‘NO’ the processing should be
halted and the Schedule screen redisplayed
unchanged.

(iii) Call CICS transaction LY01 (see Appendix

C.1) to validate that any details entered on
the screen are valid – using Commarea

David Willcocks 359 May 2002

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

On return, check the C049-PROG-STATUS

and report any errors/warnings in the usual
way.

(i) If no errors returned from LY49, Call CICS

transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen and delete the selected
breakdowns – using COMMAREA C050.
(see Appendix D).

On return, check the C050-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) If no errors returned from LY50, rebuild the

‘R/I Schedule’ screen from scratch – this
will rebuild the table in the C048
Commarea (which is required to enable the
user to ‘click’ on the new breakdown and be
navigated to the ‘SCM Advice’ screen) and
rebuild the Navigation Bar at the left of the
screen, incorporating the new breakdown.

Next If the user presses the ‘NEXT CURRENCY’ button, Command

Currency the details for the current currency will be validated.
The system will check that all amounts add up to
those specified on the Financial Details Control
Screen. Assuming all details are valid and that a
further currency was specified on the Claim
Creation Screen, the user will be navigated to the
Financial Details Control Screen for the next
currency. If no futher currencies exist, a suitable
error will be displayed – the user will be prompted
to press the ‘FINISH’ button instead.

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C048-SCREN-MODE = ‘U’, Call CICS

transaction LY01 (see Appendix C.1) to
validate that any details entered on the
screen are valid – using Commarea C049

David Willcocks 360 May 2002

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

On return, check the C049-PROG-STATUS

and report any errors/warnings in the usual
way.

(iii) If C048-SCREEN-MODE = ‘U’ and no

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

On return, check the C050-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) If C048-SCREEN-MODE = ‘U’ and no

errors returned from LY50, Call CICS
transaction LY01 (see Appendix C.1) to
perform Currency Validation – using
COMMAREA C019. (see Appendix D).

On return, check the C019-PROG-STATUS

and report any errors/warnings in the usual
way.

(v) If C048-SCREEN-MODE = ‘E’ or no

errors returned from LY19, Call CICS
transaction LY01 (see Appendix C.1) to
check that another currency exists – using
COMMAREA C052. (see Appendix D).

On return, check the C052-PROG-STATUS

and report any errors/warnings in the usual
way.

(vi) If no errors returned from LY52, navigate

the user to the Financial Details Control
Screen (see Section 4.15)

David Willcocks 361 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
encountered the user will be navigated to either the
Settlement or Non-Settlement Summary Screen,
depending on whether the current transaction
involves settlement or not. If the transaction
involves settlement, Take Down Numbers will be
assigned at this point (depending on the type of
claim) and displayed to the user on the Summary
Screen.

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C048-SCREEN-MODE = ‘U’, Call CICS

transaction LY01 (see Appendix C.1) to
validate that any details entered on the
screen are valid – using Commarea C049
(see Appendix D).

On return, check the C049-PROG-STATUS

and report any errors/warnings in the usual
way.

(iii) If C048-SCREEN-MODE = ‘U’ and no

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

On return, check the C050-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) If C048-SCREEN-MODE = ‘U’ and no

errors returned from LY50, Call CICS
transaction LY01 (see Appendix C.1) to
perform Currency Validation – using
COMMAREA C019. (see Appendix D).

On return, check the C019-PROG-STATUS

and report any errors/warnings in the usual
way.

(v) If C048-SCREEN-MODE = ‘U’ and no

errors returned from LY19, Call CICS

David Willcocks 362 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
transaction LY01 (see Appendix C.1) to
perform Transaction Validation – using
COMMAREA C017. (see Appendix D).

On return, check the C017-PROG-STATUS

and report any errors/warnings in the usual
way.

(vi) If C048-SCREEN-MODE = ‘E’ or no

errors returned from LY17, 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) If no errors returned from LY11, navigate

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

PREV The user will press this button to view the previous Command
page of breakdowns. (This will only be applicable
where more than 100 breakdowns exist for a
particular currency)

(i) If any breakdowns on the screen

have been selected for deletion,
display the error E182 (see Appendix
E) in the Error Window (see Appendix
B).

(ii) Call CICS transaction LY01 (see

Appendix C.1) to validate that any
details entered on the screen are valid –
using Commarea C049 (see Appendix
D).

On return, check the C049-PROG-

STATUS and report any
errors/warnings in the usual way.

(iii) If no errors returned from LY49, Call

CICS transaction LY01 (see Appendix

David Willcocks 363 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C.1) to update the database with the
details entered on the screen – using
COMMAREA C050. (see Appendix
D).

On return, check the C050-PROG-

STATUS and report any errors/warnings
in the usual way.

(iv) If no errors returned from LY50, call

CICS transaction LY01 (see Appendix
C.1) to read the previous page of
breakdowns – using COMMAREA
C048, setting C048-PREV-PRESSED
to ‘Y’ and passing the key for the first
line on the current screen in C048-
START-KEY (see Appendix D).

On return, check the C048-PROG-

STATUS and report any errors/warnings
in the usual way.

(v) If no errors are returned from LY48,

rebuild the ‘R/I Schedule’ screen as
detailed in Section 4.18.3.

NEXT The user will press this button to view the next page Command
of breakdowns. (This will only be applicable where
more than 100 breakdowns exist for a particular
currency)

(i) If any breakdowns on the screen

have been selected for deletion,
display the error E182 (see Appendix
E) in the Error Window (see Appendix
B).

(ii) Call CICS transaction LY01 (see

Appendix C.1) to validate that any
details entered on the screen are valid –
using Commarea C049 (see Appendix
D).

David Willcocks 364 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
On return, check the C049-PROG-
STATUS and report any
errors/warnings in the usual way.

(iii) If no errors returned from LY49, Call

CICS transaction LY01 (see Appendix
C.1) to update the database with the
details entered on the screen – using
COMMAREA C050. (see Appendix
D).

On return, check the C050-PROG-

STATUS and report any errors/warnings
in the usual way.

(iv) If no errors returned from LY50, call

CICS transaction LY01 (see Appendix
C.1) to read the next page of
breakdowns – using COMMAREA
C048, setting C048-NEXT-PRESSED
to ‘Y’ and passing the key for the last
line on the current screen in C048-
START-KEY (see Appendix D).

On return, check the C048-PROG-

STATUS and report any errors/warnings
in the usual way.

(v) If no errors are returned from LY48,

rebuild the ‘R/I Schedule’ screen as
detailed in Section 4.18.3.

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 ‘R/I
Scredule’ Screen. Therefore:-

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C048
(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

David Willcocks 365 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
returned in the C048 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

(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

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.19. Binder Schedule Screen

David Willcocks 366 May 2002

Xchanging Ins-sure Services Ltd
4.19.1. Screen Layout

Below is a ‘mock-up’ of the ‘Binder Schedule’ Screen. Two screen

images are shown here, because the technician may need to scroll to
the right to view some of the details on the screen.

4.19.2. CICS Transactions

David Willcocks 367 May 2002

Xchanging Ins-sure Services Ltd
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
LY17 Validate Claim Transaction
LY19 Currency Validation
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY46 Check whether Curr/Trans. Validation
reqd.
LY47 Create New Breakdown
LY52 Check for next Currency
LY53 Build Binder Schedule Screen
LY54 Binder Schedule Screen Validation
LY55 Binder Schedule D/B Update
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
LZ11 Create Re-Advice – Initial Validation

David Willcocks 368 May 2002

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

The fields and the navigation bar on this screen will be

derived as follows:-

Field Type Source

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 C053 (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: Each occurrence of C053-COR returned in the C053-BREAKDOWN-TABLE

(together with its associated C053-BREAKDOWN-NO) should be stored for use later.
These, along with the values in C053-KEY, will be used to update the Session Record if the
user ‘clicks’ on a ‘Claims Office Reference’. This will enable the correct details to be
displayed on the ‘SCM Advice’ screen.

XCR Field C053-UCR

UCR Field C053-UCR
(This field should be protected)
TR Field C053-TR
(This field should be protected)
OSND Field C053-ORIG-REF
(This field should be protected)

Orig. Broker Field C053-ORIG-BKR

(This field should be protected)
Signed Tick-Box C053-SIGNED-IND
(This field should be protected)
Peer Review Field C053-PEER-REV-IND

David Willcocks 369 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
(This field should be protected)
Orig.Curr Field C053-ORIG-CURR
(This field should be protected)
Read throug each occurrence in the C053-BREAKDOWN-TABLE, for
each occurrence with C053-COR > spaces, create a line on the screen.
COR (n) Field C053-COR (n)
(If C053-COR-ATTR (n) = ‘P’, this field
should be protected)
Insured (n) Field C053-INSURED (n)
(If C053-INSURED-ATTR (n) = ‘P’, this
field should be protected)
Broker Ref 1 Field C053-BKR-REF-1 (n)
(n) (If C053-BKR-REF-ATTR (n) = ‘P’, this
field should be protected)
Trust Fund Field C053-TF-CODE (n)
Code (n) (If C053-TF-CODE-ATTR (n) = ‘P’, this
field should be protected)
State Code (n) Field C053-STATE-CODE (n)
(If C053-STATE-CODE-ATTR (n) = ‘P’,
this field should be protected)
DOL From (n) Field C053-LOSS-DATE-FROM (n)
(If C053-DOL-ATTR (n) = ‘P’, this field
should be protected)
DOL To (n) Field C053-LOSS-DATE-TO (n)
(If C053-DOL-ATTR (n) = ‘P’, this field
should be protected)
DOL Qual (n) Field C053-LOSS-DATE-QUAL (n)
(If C053-DOL-ATTR (n) = ‘P’, this field
should be protected)
Catastrophe Field C053-CAT-CODE (n)
Code (n) (If C053-CAT-ATTR (n) = ‘P’, this field
should be protected)
PCS Field C053-PCS-CAT-CODE (n)
Catastrophe (if C053-PCS-CAT-ATTR (n) = ‘P’, this
Code (n) field should be protected)
Paid To Date Field C053-PTD-AMT (n)
Amount (n) (If C053-PTD-AMT-ATTR (n) = ‘P’, this
field should be protected)
Paid This Time Field C053-PTT-AMT (n)
Amount (n) (If C053-PTT-AMT-ATTR (n) = ‘P’, this
field should be protected)
Outstanding Field C053-OUTST-AMT (n)
Amount (n) (If C053-OUTST-AMT-ATTR (n) = ‘P’,
this field should be protected)
Outstanding Field C053-OUTST-QUAL (n)
Amount (If C053-OUTST-QUAL-ATTR (n) = ‘P’,
Qualifier (n) this field should be protected)

David Willcocks 370 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
The following fields will not be supplied by the LY53 CICS Transaction but should be
calculated by the Java Layer. This is because they need to be updated as the Paid This
Time and Outstanding Amounts are updated by the technician.
Total Paid This Accumulation of all Paid This Time
Time amounts
(This field should be protected)
Total Accumulation of all Outstanding
Outstanding Amounts
Amount (This field should be protected)
C. Commands:-

The derivation for the commands is also returned in the C053

Commarea.
Delete Line (n) Option If C053-DELETE-ATTR (n) = ‘P’, this
Button button should be protected (or
preferably not displayed)
Delete Selected Comman If C053-DEL-BD-ATTR = ‘P’, this
Breakdowns d field should be protected (or
preferably not displayed)
New Comman If C053-NEW-BD-ATTR = ‘P’, this
Breakdown d button should be protected (or
preferably not displayed)
Next Currency Comman If C053-NEXT-CURR-ATTR = ‘P’,
d this button should be protected (or
preferably not displayed)
Finish Comman If C053-FINISH-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
PREV Comman If C053-PREV-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
NEXT Comman If C053-NEXT-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)

4.19.4. Process Description

This screen is the Binder Schedule Screen.

If a large number of breakdowns are required on a

particular claim where the vast majority of information
on each is the same, the user may opt to create a
schedule from the ‘SCM Advice’ screen. The user may

David Willcocks 371 May 2002

Xchanging Ins-sure Services Ltd
opt to create either a R/I Schedule or a Binder Schedule
depending on the type of business. Each line created by
the user on this schedule will result in a new
breakdown being created on the claim. The Claims
Office Reference will be assigned as each line is
created. If details other than those shown on the screen
need to be amended the user will be able to ‘click’ on
the Claims Office Reference to be taken to the SCM
Advice Screen. New breakdowns cannot be created if
any subsequent transactions exist on the claim.

The user will also have the ability to delete breakdowns

Fig 4.19.4.1. Field/Command Processing for ‘Binder Schedule’

Screen

Field / Attributes Data Type

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

David Willcocks 372 May 2002

(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

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

David Willcocks 373 May 2002

(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

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

David Willcocks 374 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
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’,

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

On return, check the C071-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’

(iii) On selection of the ‘Group Enquiry’

(iv) On selection of ‘Add to Aggregate

David Willcocks 375 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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-

David Willcocks 376 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

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

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

David Willcocks 377 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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. 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

On return, check the C020-PROG-STATUS and

David Willcocks 378 May 2002

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

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

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

David Willcocks 379 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

David Willcocks 380 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

(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 C053 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 C053 Commarea.

‘Create Re-advice’ selected

This function will allow the user to create a re-

David Willcocks 381 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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 382 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 C053-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 C054 (see
Appendix D).

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

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

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

(iii) If C053-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY55, 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 C053-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 383 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.3 Field Protection will be handled by the ‘Field Attributes’ returned in the C053 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

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’

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

David Willcocks 384 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 currency that relates to the breakdown Display Alphanumeric
Currency being maintained. Only Field (3 Chars)
COR (n) This is the Claims Office Reference. This field is Display Alphanumeric
system generated for each line created on the Only Field (15 Chars)
screen.

If the user ‘clicks’ on this field, they will be

navigated to the ‘SCM Advice’ Screen – see below
in the Commands Section.

Insured This is the name of the Insured. Mandatory Alphanumeric

(n) Field (50 chars)
This is a free-text field subject only to ASCII
validation, described above.

Field derivation is as folows (handled by CICS

Broker The first of the two broker references. Mandatory Alphanumeric

Referenc Field (16 chars)
e 1 (n) This is a free-text field subject only to ASCII
validation, described above.

Field derivation is as folows (handled by CICS

David Willcocks 385 May 2002

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

Trust Identifies which US or Canadian Trust Fund is to be Optional Alphanumeric

Fund used to pay the claim. Field (2 chars)
Code (n)
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 subsequent breakdowns on an initial advice

A drop down list will be available. This will contain

values returned from LIDS for the OSND(s) entered
on the ‘Claim Creation’ screen.

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

State Identifies the state or province of the claim. Optional Alphanumeric

Code (n) 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 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.
(ii) For subsequent advices, the field will pre-

David Willcocks 386 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.

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 E129 (see
Appendix E) in the Error Window (see Appendix
B).

This field must be a valid value from the

State/Province Table (name ?). If not, display the
error E120 (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 loss. Field (DD/MM/CCYY)

From (n)
It will be pre-populated as detailed below:-
(note:- this will be handled by the appropriate CICS
transaction)

(i) For subsequent breakdowns on an initial advice

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

Date of The last date of a period of loss. Optional Date

Loss To Field (DD/MM/CCYY)

(n) It will be pre-populated as detailed below:-

(note:- this will be handled by the appropriate CICS
transaction)

(i) For subsequent breakdowns on an initial advice

David Willcocks 387 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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).

Date of Qualifier that explains the absence of a Loss Date. Optional Alphanumeric
Loss Field (1 Char)
Qualifier It will be pre-populated as detailed below:-
(n) (note:- this will be handled by the appropriate CICS
transaction)

(i) For subsequent breakdowns on an initial advice

If entered, 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 E110 (see Appendix E) in the Error
Window (see Appendix B).

If entered, the Date of Loss From and To Dates

must not be entered. If they are, display the error
E107 (see Appendix E) in the Error Window (see
Appendix B).
Catastro The Catastrophe Code relating to the loss. Optional Alphanumeric
phe Code Field (4 chars)
(n) Initialisation of this field will be determined as
follows:- (note: this will be handled by the
appropriate CICS Transaction)

(i) 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.

David Willcocks 388 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(ii) 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 E070 (see Appendix E)
in the Error Window (see Appendix B).

PCS The PCS (Property Claims Service) Catastrophe Optional Alphanumeric

Catastro Code relating to the loss. Field (4 chars)
phe Code
(n) Initialisation of this field will be determined as
follows:- (note: this will be handled by the
appropriate CICS Transaction)

(i) For subsequent breakdowns on an internally

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

It will be initialised as follows:-

Paid This The Paid This Time amount is the amount to be paid Optional Numeric
Time on this movement of the current Breakdown (COR). Field -(13)9.99
Amount
It will be initialisesd to zeroes.

David Willcocks 389 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(n)
Outstandi This is the estimated outstanding amount still to be Optional Numeric
ng settled on the current breakdown. Field -(13)9.99
Amount
(n) It will be initialised to the value held for this
breakdown on the previous transaction within the
claim. If this is a first advice or a new breakdown
on a subsequent advice, this field will be initialised
to zero.

(i) For subsequent breakdowns on an initial advice

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
(vii) ‘Z’ = Zero recommended reserve.

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

David Willcocks 390 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Total This is the total of all Paid This Time amounts Display Numeric
Paid This across all breakdowns for the current Original Only Field -(13)9.99
Time Currency.

This is shown for display purposes only – in order

D. Commands - (Main Screen).

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C053-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
C054 (see Appendix D).

On return, check the C054-PROG-STATUS

and report any errors/warnings in the usual
way.

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

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

On return, check the C055-PROG-STATUS

and report any errors/warnings in the usual

David Willcocks 391 May 2002

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

Claims If the user wishes to add or amend fields other than Command
Office those that are shown on the Binder Schedule screen,
Reference they can ‘click’ on the Claims Office Reference.
This field is display only on the screen and cannot
be changed – however, it will provide a ‘link’ to the
‘SCM Advice’ screen. If the user ‘clicks’ on the
Claims Office Reference, the details on the screen
should be validated and stored and the user should
be navigated to the ‘SCM Advice’ screen.

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C053-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
C054 (see Appendix D).

On return, check the C054-PROG-STATUS

and report any errors/warnings in the usual
way.

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

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

On return, check the C055-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) Call CICS transaction LY01 (see Appendix

C.1) to update the Session Record with the
key values for the Claims Office Reference
selected – using COMMAREA C010. (see
Appendix D). Pass the following values in
the C010 Commarea:-

C053-UCR-TR-SYS-REF

David Willcocks 392 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C053-CURR-NO
C053-SDN-NO
C053-STAT-SPLIT-NO (n)
C053-BREAKDOWN-NO (n)

(v) If no errors returned from LY10, call the

On return, check the Program Status in the

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

(vi) If no errors returned from LY11, navigate

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

New Pressing this button will cause the creation of a new Command
Breakdown breakdown (based on the previous breakdown), An
Claims Office Reference will be assigned by the
system.

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) Call CICS transaction LY01 (see Appendix

C.1) to validate that any details entered on
the screen are valid – using Commarea
C054 (see Appendix D).

On return, check the C054-PROG-STATUS

and report any errors/warnings in the usual
way.

(iii) If no errors returned from LY54, Call CICS

transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C055.
(see Appendix D).

On return, check the C055-PROG-STATUS

David Willcocks 393 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
and report any errors/warnings in the usual
way.

(iv) If no errors returned from LY55, call CICS

transaction LY01 (see Appendix C.1) to
create a new breakdown–using
COMMAREA C047. (see Appendix D).

On return, check the C047-PROG-

STATUS and report any errors/warnings in
the usual way.

(v) If no errors are returned from LY47, rebuild

the ‘Binder Schedule’ screen from scratch
– this will rebuild the table in the C053
Commarea (which is required to enable the
user to ‘click’ on the new breakdown and be
navigated to the ‘SCM Advice’ screen) and
rebuild the Navigation Bar at the left of the
screen, incorporating the new breakdown.

Delete If the user presses this button, a pop-up window Command

(iv) If no lines have been selected for deletion,

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

(v) Display the ‘Deletion Confirmation’ pop-up

(vi) Call CICS transaction LY01 (see Appendix

C.1) to validate that any details entered on
the screen are valid – using Commarea
C054 (see Appendix D).

On return, check the C054-PROG-STATUS

and report any errors/warnings in the usual
way.

David Willcocks 394 May 2002

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

(iii) If no errors returned from LY54, Call CICS

transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen and delete the selected
breakdowns – using COMMAREA C055.
(see Appendix D).

On return, check the C055-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) If no errors returned from LY55, rebuild the

‘Binder Schedule’ screen from scratch –
this will rebuild the table in the C053
Commarea (which is required to enable the
user to ‘click’ on the new breakdown and be
navigated to the ‘SCM Advice’ screen) and
rebuild the Navigation Bar at the left of the
screen, incorporating the new breakdown.

Next If the user presses the ‘NEXT CURRENCY’ button, Command

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C053-SCREN-MODE = ‘U’, Call CICS

transaction LY01 (see Appendix C.1) to
validate that any details entered on the
screen are valid – using Commarea C054
(see Appendix D).

On return, check the C054-PROG-STATUS

and report any errors/warnings in the usual
way.

David Willcocks 395 May 2002

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

(iii) If C053-SCREEN-MODE = ‘U’ and no

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

On return, check the C055-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) If C053-SCREEN-MODE = ‘U’ and no

errors returned from LY55, Call CICS
transaction LY01 (see Appendix C.1) to
perform Currency Validation – using
COMMAREA C019. (see Appendix D).

On return, check the C019-PROG-STATUS

and report any errors/warnings in the usual
way.

(v) If C053-SCREEN-MODE = ‘E’ or no

errors returned from LY19, Call CICS
transaction LY01 (see Appendix C.1) to
check that another currency exists – using
COMMAREA C052. (see Appendix D).

On return, check the C052-PROG-STATUS

and report any errors/warnings in the usual
way.

(vi) If no errors returned from LY52, navigate

the user to the Financial Details Control
Screen (see Section 4.15)

Finish If the user presses the ‘FINISH’ button, the details Command
for the current currency will be validated. The
system will check that all amounts add up to those
specified on the Financial Details Control Screen.
Assuming all details are valid, the Transaction level
validation will be performed. If no errors are
encountered the user will be navigated to either the
Settlement or Non-Settlement Summary Screen,
depending on whether the current transaction
involves settlement or not. If the transaction

David Willcocks 396 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
involves settlement, Take Down Numbers will be
assigned at this point (depending on the type of
claim) and displayed to the user on the Summary
Screen.

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C053-SCREEN-MODE = ‘U’, Call CICS

transaction LY01 (see Appendix C.1) to
validate that any details entered on the
screen are valid – using Commarea C054
(see Appendix D).

On return, check the C054-PROG-STATUS

and report any errors/warnings in the usual
way.

(iii) If C053-SCREEN-MODE = ‘U’ and no

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

On return, check the C055-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) If C053-SCREEN-MODE = ‘U’ and no

errors returned from LY55, Call CICS
transaction LY01 (see Appendix C.1) to
perform Currency Validation – using
COMMAREA C019. (see Appendix D).

On return, check the C019-PROG-STATUS

and report any errors/warnings in the usual
way.

(v) If C053-SCREEN-MODE = ‘U’ and no

errors returned from LY19, Call CICS
transaction LY01 (see Appendix C.1) to
perform Transaction Validation – using
COMMAREA C017. (see Appendix D).

David Willcocks 397 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
On return, check the C017-PROG-STATUS
and report any errors/warnings in the usual
way.

(vi) If C053-SCREEN-MODE = ‘E’ or no

On return, check the Program Status in the

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

(vii) If no errors returned from LY11, navigate

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

PREV The user will press this button to view the previous Command
page of breakdowns. (This will only be applicable
where more than 100 breakdowns exist for a
particular currency)

(i) If any breakdowns on the screen

have been selected for deletion,
display the error E182 (see Appendix
E) in the Error Window (see Appendix
B).

(ii) Call CICS transaction LY01 (see

Appendix C.1) to validate that any
details entered on the screen are valid –
using Commarea C054 (see Appendix
D).

On return, check the C054-PROG-

STATUS and report any
errors/warnings in the usual way.

(iii) If no errors returned from LY54, Call

CICS transaction LY01 (see Appendix
C.1) to update the database with the
details entered on the screen – using
COMMAREA C055. (see Appendix
D).

David Willcocks 398 May 2002

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

On return, check the C055-PROG-

STATUS and report any errors/warnings
in the usual way.

(iv) If no errors returned from LY55, call

CICS transaction LY01 (see Appendix
C.1) to read the previous page of
breakdowns – using COMMAREA
C053, setting C053-PREV-PRESSED
to ‘Y’ and passing the key for the first
line on the current screen in C053-
START-KEY (see Appendix D).

On return, check the C053-PROG-

STATUS and report any errors/warnings
in the usual way.

(v) If no errors are returned from LY53,

rebuild the ‘Binder Schedule’ screen as
detailed in Section 4.19.3.

NEXT The user will press this button to view the next page Command
of breakdowns. (This will only be applicable where
more than 100 breakdowns exist for a particular
currency)

(i) If any breakdowns on the screen

have been selected for deletion,
display the error E182 (see Appendix
E) in the Error Window (see Appendix
B).

(ii) Call CICS transaction LY01 (see

Appendix C.1) to validate that any
details entered on the screen are valid –
using Commarea C054 (see Appendix
D).

David Willcocks 399 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
On return, check the C054-PROG-
STATUS and report any
errors/warnings in the usual way.

(iii) If no errors returned from LY54, Call

CICS transaction LY01 (see Appendix
C.1) to update the database with the
details entered on the screen – using
COMMAREA C055. (see Appendix
D).

On return, check the C055-PROG-

STATUS and report any errors/warnings
in the usual way.

(iv) If no errors returned from LY55, call

CICS transaction LY01 (see Appendix
C.1) to read the next page of
breakdowns – using COMMAREA
C053, setting C053-NEXT-PRESSED
to ‘Y’ and passing the key for the last
line on the current screen in C053-
START-KEY (see Appendix D).

On return, check the C053-PROG-

STATUS and report any errors/warnings
in the usual way.

(v) If no errors are returned from LY53,

rebuild the ‘Binder Schedule’ screen as
detailed in Section 4.19.3.

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 ‘Binder
Schedule’ screen. Therefore:-

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C053
(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)

David Willcocks 400 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(ii) Rebuild the screen, based on the data
returned in the C053 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

(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

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.20. Subsequent Advice Schedule Screen

David Willcocks 401 May 2002

Xchanging Ins-sure Services Ltd
Change Control Log

Release Date Changed TP No. Description of Changes Made

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

4.20.1. Screen Layout

Below is the ‘Subsequent Advice Schedule’ Screen.

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

David Willcocks 402 May 2002

Xchanging Ins-sure Services Ltd
David Willcocks 403 May 2002
Xchanging Ins-sure Services Ltd
4.20.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
LY17 Validate Claim Transaction
LY19 Currency Validation
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY46 Check whether Curr/Trans. Validation
reqd.
LY47 Create New Breakdown
LY48 Build R/I Schedule Screen
LY52 Check for next Currency
LY56 Build Subsequent Advice Schedule
Screen
LY57 Subsequent Advice Schedule Screen
Validation
LY58 Subsequent Advice Schedule Screen
D/B Update
LY51 Delete Breakdown
LY52 Check for next Currency
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
LY11 Create Re-Advice – Initial Validation

David Willcocks 404 May 2002

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

The fields and the navigation bar on this screen will be

derived as follows:-

Field Type Source

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 C056 (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: Each occurrence of C056-COR returned in the C056-BREAKDOWN-TABLE

(together with its associated C056-BREAKDOWN-NO) should be stored for use later.
These, along with the values in C056-KEY, will be used to update the Session Record if the
user ‘clicks’ on a ‘Claims Office Reference’. This will enable the correct details to be
displayed on the ‘SCM Advice’ screen.

XCR Field C056-XCR

(This field should be protected)
UCR Field C056-UCR
(This field should be protected)
TR Field C056-TR
(This field should be protected)
OSND Field C056-ORIG-REF
(This field should be protected)

Orig. Current Field C056-ORIG-BKR

Broker (This field should be protected)
Signed Tick-Box C056-SIGNED-IND
(This field should be protected)

David Willcocks 405 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Peer Review Field C056-PEER-REV-IND
(This field should be protected)
Orig.Curr Field C056-ORIG-CURR
(This field should be protected)
Read throug each occurrence in the C056-BREAKDOWN-TABLE, for
each occurrence with C056-COR > spaces, create a line on the screen.
COR (n) Field C056-COR (n)
(If C056-COR-ATTR (n) = ‘P’, this field
should be protected)
Movement Field C056-MOVE-REF (n)
Reference (If C056-MOVE-REF-ATTR = ‘P’, this
field should be protected)
Name 1 (n) Field C056-NAME-1 (n)
(If C056-NAME-1-ATTR (n) = ‘P’, this
field should be protected)
Name 1 Field C056-NAME-1-QUAL (n)
Qualifier (n) (If C056-NAME-1-QL-ATTR (n) = ‘P’,
this field should be protected)
Name 2 (n) Field C056-NAME-2 (n)
(If C056-NAME-2-ATTR (n) = ‘P’, this
field should be protected)
Name 2 Field C056-NAME-2-QUAL (n)
Qualifier (n) (If C056-NAME-2-QL-ATTR (n) = ‘P’,
this field should be protected)
FIL Code Field C056-FIL-CODE (n)
(If C056-FIL-CODE-ATTR (n) = ‘P’, this
field should be protected)
Trust Fund Field C056-TF-CODE (n)
Code (n) (If C048-56-CODE-ATTR (n) = ‘P’, this
field should be protected)
State Code (n) Field C056-STATE-CODE (n)
(If C056-STATE-CODE-ATTR (n) = ‘P’,
this field should be protected)
DOL From (n) Field C056-LOSS-DATE-FROM (n)
(If C056-DOL-ATTR (n) = ‘P’, this field
should be protected)
DOL To (n) Field C056-LOSS-DATE-TO (n)
(If C056-DOL-ATTR (n) = ‘P’, this field
should be protected)
DOL Qual (n) Field C056-LOSS-DATE-QUAL (n)
(If C056-DOL-ATTR (n) = ‘P’, this field
should be protected)
Catastrophe Field C056-CAT-CODE (n)
Code (n) (If C056-CAT-ATTR (n) = ‘P’, this field
should be protected)
PCS Field C056-PCS-CAT-CODE (n)
Catastrophe ( If C056-PCS-CAT-ATTR (n) = ‘P’, this

David Willcocks 406 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Code (n) field should be protected)
NAIC Code (n) Field C056-NAIC-CODE (n)
(If C056-NAIC-CODE-ATTR (n) = ‘P’,
this field should be protected)
NAIC Qual (n) Field C056-NAIC-QUAL (n)
(If C056-NAIC-QUAL-ATTR (n) = ‘P’,
this field should be protected)
PTT Amt Total Field C056-PTT-AMT-TOTAL (n)
(n) (If C056-PTT-AMT-ATTR (n) = ‘P’, this
field should be protected)
Oustanding Field C056-OUTST-AMT (n)
Amt (n) (If C056-OUTST-AMT-ATTR (n) = ‘P’,
this field should be protected)
O/S Qualifier Field C056-OUTST-TOT-QL (n)
(If C056-OUTST-TOT-QL-ATTR (n) = ‘P’,
this field should be protected)
C. Commands:-

The derivation for the commands is also returned in the C048

Commarea.
Delete Line (n) Option If C056-DELETE-ATTR (n) = ‘P’, this
Button button should be protected (or
preferably not displayed)
Delete Selected Comman If C056-DEL-BD-ATTR = ‘P’, this
Breakdowns d field should be protected (or
preferably not displayed)
New Comman If C056-NEW-BD-ATTR = ‘P’, this
Breakdown d button should be protected (or
preferably not displayed)
Next Currency Comman If C056-NEXT-CURR-ATTR = ‘P’,
d this button should be protected (or
preferably not displayed)
Finish Comman If C056-FINISH-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
PREV Comman If C056-PREV-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
NEXT Comman If C056-NEXT-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)

4.20.4. Process Description

David Willcocks 407 May 2002

Xchanging Ins-sure Services Ltd
This screen is the Subsequent Advice Schedule Screen.

If a number of breakdowns were entered by the

technician, for a particular currency, on the first advice
of a claim then the user will be presented with the
‘Subsequent Advice Schedule’ Screen when they are
creating a subsequent advice. This screen will be
presented to the user after the financial details control
screen. It will allow them to select the breakdown or
breakdowns on which they wish to create a movement
for this transaction.

If the initial advice was created using either the ‘R/I

Schedule’ or the ‘Binder Schedule’, the user will be
presented with the appropriate schedule screen –
instead of this one. This screen is only used where more
than one breakdown exists on a claim that was not
created using either of these Scredule screens.

Breakdowns may be inserted on this screen but may

only be deleted (on unadvised claims) if the current
transaction is the latest on the claim and the
breakdown in question did not exist on the previous
transaction.
In other words, they may remove breakdowns that they
have just added by mistake. Each line created by the
user on this schedule will result in a new breakdown
being created on the claim. The Claims Office
Reference will be assigned as each line is created. If
details other than those shown on the screen need to be
amended the user will be able to ‘click’ on the Claims
Office Reference to be taken to the SCM Advice Screen.
New breakdowns cannot be created if any subsequent
transactions exist on the claim.

Fig 4.20.4.1. Field/Command Processing for ‘Subsequent Advice

Schedule’ Screen

Field / Attributes Data Type

On return from CICS, check the C004-PROG-

David Willcocks 408 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

(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

On return, check the Program Status in the

usual way, reporting errors if they exist in the

David Willcocks 409 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

(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

On return, check the Program Status in the

David Willcocks 410 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)

(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

User should select one of these options.

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

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

On return, check the C071-PROG-STATUS

and report any errors/warnings in the usual
way.

David Willcocks 411 May 2002

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

(ii) On selection of the ‘Maintain Group’

(iii) On selection of the ‘Group Enquiry’

(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

David Willcocks 412 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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)

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

On return, check the C088-PROG

-STATUS and report any errors in the
usual way.

David Willcocks 413 May 2002

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

(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

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

(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

David Willcocks 414 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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,

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

‘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

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

David Willcocks 416 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

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

David Willcocks 417 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(ii) If no errors returned from LZ06, call
LY01 using Commarea C056 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 C056 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 418 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 C056-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 C057 (see
Appendix D).

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

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

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

(iii) If C056-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY58, 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 C056-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 419 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.3 Field Protection will be handled by the ‘Field Attributes’ returned in the C056 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

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’

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

David Willcocks 420 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Orig. The Originating Current Broker (i.e. the broker who Display Alphanumeric
Current submitted this claim transaction). Only Field (4 chars)
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 currency that relates to the breakdown Display Alphanumeric
Currency being maintained. Only Field (3 Chars)
COR (n) This is the Claims Office Reference. This field is Display Alphanumeric
system generated for each line created on the Only Field (14 Chars)
screen.

If the user ‘clicks’ on this field, they will be

navigated to the ‘SCM Advice’ Screen – see below
in the Commands Section.

Moveme This is the latest Movement Reference for the Display Alphanumeric
nt current breakdown. This field is system generated Only Field (2 Chars)
Referenc and is shown for information purposes only.
e
Name 1 This field will either be set to the Insured or the Mandatory Alphanumeric
(n) Reinsured, depending on the type of claim. Field (50 chars)

If the associated qualifier is ‘I’, then this field

represents the Insured Name.
If the associated qualifier is ‘R’, then it is the
Reinsured Name.

It will be pre-populated as detailed below:-

(note:- this will be handled by the appropriate CICS
transaction)

(i) For subsequent breakdowns on an initial advice

When entered, it is free text field subject only to

ASCII validation as described above.

David Willcocks 421 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Name 1 This qualifier indentifies what has been entered in Mandatory Alphanumeric
Qualifier the Name 1 field. Field (1 Char)
(n)
Valid values are ‘I’ (Insured) or ‘R’ (Reinsured)

If a value other than these is entered, display the

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

Name 2 This field will either be set to the Cover Holder, the Optional Alphanumeric
(n) Original Insured or the Vessel, depending on the Field (50 chars)
type of claim.

If the associated qualifier is ‘C’, then this field

represents the Cover Holder Name.
If the associated qualifier is ‘O’, then it is the
Original Insured Name.
If the associated qualifier is ‘V’, then it is the
Vessel.

It will be pre-populated as detailed below:-

(note:- this will be handled by the appropriate CICS
transaction)

(i) For subsequent breakdowns on an initial advice

When entered, it is free text field subject only to

ASCII validation as described above.

Name 2 This qualifier indentifies what has been entered in Optional Alphanumeric
Qualifier the Name 2 field. Field (1 Char)
(n)
Valid values are ‘C’ (Cover Holder), ‘O’ (Original
Insured) or ‘V’ (Vessel)

If a value other than these is entered, display the

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

FIL Code This is the first FIL Code (The second is not shown Optional Alphanumeric
on this screen – the user will need to visit the SCM Field (4 Chars)
Advice Screen to update this).

David Willcocks 422 May 2002

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

Identifies Foreign Insurance legislation applicable

to the claim.

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

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

Trust Identifies which US or Canadian Trust Fund is to be Optional Alphanumeric

Fund used to pay the claim. Field (2 Chars)
Code (n)
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 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.
(ii) For subsequent advices, the field will pre-

David Willcocks 423 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.

A drop down list will be available. This will contain

values returned from LIDS for the OSND(s) entered
on the ‘Claim Creation’ screen.

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

State Identifies the state or province of the claim. Optional Alphanumeric

Code (n) 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 subsequent breakdowns on an initial advice

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 E129 (see
Appendix E) in the Error Window (see Appendix
B).

This field must be a valid value from the

State/Province Table (name ?). If not, display the
error E120 (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 loss. Field (DD/MM/CCYY)

David Willcocks 424 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
From (n) It will be pre-populated as detailed below:-
(note:- this will be handled by the appropriate CICS
transaction)

(i) For subsequent breakdowns on an initial advice

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

Date of The last date of a period of loss. Optional Date

Loss To Field (DD/MM/CCYY)

(n) It will be pre-populated as detailed below:-

(note:- this will be handled by the appropriate CICS
transaction)

(i) For subsequent breakdowns on an initial advice

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

(i) For subsequent breakdowns on an initial advice

David Willcocks 425 May 2002

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

If entered, the Date of Loss From and To Dates

(i) For subsequent breakdowns on an internally

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

Catastro Code relating to the loss. Field (4 Chars)
phe Code
(n) Initialisation of this field will be determined as
follows:- (note: this will be handled by the
appropriate CICS Transaction)

David Willcocks 426 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(i) 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.
(ii) 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).

NAIC The ‘National Association of Insurance Optional Alphanumeric

Code (n) 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 subsequent breakdowns on an initial advice

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 The qualifier associated with the ‘National Optional Alphanumeric

Qualifier Association of Insurance Commissioners’ (NAIC) Field (1 Char)
Code. This indicates the type of NAIC code.

David Willcocks 427 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(n)
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 subsequent breakdowns on an initial advice

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

(ix) ‘G’ = Group NAIC Code
(x) ‘P’ = Pool NAIC Code
(xi) ‘C’ = Company NAIC Code
(xii) ‘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).

PTT Amt This is the total Paid This time for the breakdown. Display Numeric
Total (n) Only Field -(13)9.99
It is displayed on this screen to enable the
technician to easily identify which, if any,
breakdown have the incorrect PTT amount, should
the breakdowns not total the PTT amount entered at
the Financial Details Control level.

Outstandi This is the total Outstanding for the breakdown. Display Numeric
ng Amt Only Field -(13)9.99
(n) It is displayed on this screen to enable the
technician to easily identify which, if any,
breakdown have the incorrect Outstanding amount,
should the breakdowns not total the Outstanding
amount entered at the Financial Details Control
level.

David Willcocks 428 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Format:- --,---,---,---,--9
O/S Qualifier associated with the Total Outstanding Display Alphanumeric
Qualifier Amount for the Breakdown Only Field (1 Char)

D. Commands - (Main Screen).

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C056-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
C057 (see Appendix D).

On return, check the C057-PROG-STATUS

and report any errors/warnings in the usual
way.

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

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

On return, check the C058-PROG-STATUS

and report any errors/warnings in the usual
way.

COR If the user wishes to add or amend fields other than

those that are shown on the Subsequesnt Advice
Schedule screen, they can ‘click’ on the Claims
Office Reference. This field is display only on the
screen and cannot be changed – however, it will
provide a ‘link’ to the ‘SCM Advice’ screen. If the
user ‘clicks’ on the Claims Office Reference, the
details on the screen should be validated and stored

David Willcocks 429 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
and the user should be navigated to the ‘SCM
Advice’ screen.

(vii) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(viii) If C056-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
C057 (see Appendix D).

On return, check the C057-PROG-STATUS

and report any errors/warnings in the usual
way.

(ix) If C056-SCREEN-MODE = ‘U’ (Update)

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

On return, check the C058-PROG-STATUS

and report any errors/warnings in the usual
way.

(x) If C056-SCREEN-MODE = ‘E’ (Enquiry)

or no errors returned from LY58, call CICS
transaction LY01 (see Appendix C.1) to
update the Session Record with the key
values for the Claims Office Reference
selected – using COMMAREA C010. (see
Appendix D). Pass the following values in
the C010 Commarea:-

C056-UCR-TR-SYS-REF
C056-CURR-NO
C056-SDN-NO
C056-STAT-SPLIT-NO (n)
C056-BREAKDOWN-NO (n)

(xi) If no errors returned from LY10, call the

CICS transaction LY01 (see Appendix C.1)
– using COMMAREA C011 (see Appendix

David Willcocks 430 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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 ‘Y’.

On return, check the Program Status in the

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

(xii) If no errors returned from LY11, navigate

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

Delete If the user presses this button, a pop-up window Command

(vii) If no lines have been selected for deletion,

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

(viii) Display the ‘Deletion Confirmation’ pop-up

(ix) Call CICS transaction LY01 (see Appendix

C.1) to validate that any details entered on
the screen are valid – using Commarea
C057 (see Appendix D).

On return, check the C057-PROG-STATUS

and report any errors/warnings in the usual
way.

(v) If no errors returned from LY57, Call CICS

transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen and delete the selected
breakdowns – using COMMAREA C058.
(see Appendix D).

David Willcocks 431 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
On return, check the C058-PROG-STATUS
and report any errors/warnings in the usual
way.

(vi) If no errors returned from LY58, rebuild the

‘Subsequent Advice Schedule’ screen from
scratch – this will rebuild the table in the
C056 Commarea (which is required to
enable the user to ‘click’ on the new
breakdown and be navigated to the ‘SCM
Advice’ screen) and rebuild the Navigation
Bar at the left of the screen, incorporating
the new breakdown.

New Pressing this button will cause the creation of a new

Breakdown breakdown (based on the previous breakdown), An
Claims Office Reference will be assigned by the
system.

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) Call CICS transaction LY01 (see Appendix

C.1) to validate that any details entered on
the screen are valid – using Commarea
C057 (see Appendix D).

On return, check the C057-PROG-STATUS

and report any errors/warnings in the usual
way.

(iii) If no errors returned from LY57, Call CICS

transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C058.
(see Appendix D).

On return, check the C058-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) If no errors returned from LY58, call CICS

transaction LY01 (see Appendix C.1) to
create a new breakdown–using
COMMAREA C047. (see Appendix D).

David Willcocks 432 May 2002

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

On return, check the C047-PROG-

STATUS and report any errors/warnings in
the usual way.

(v) If no errors are returned from LY47, rebuild

the ‘Subsequent Advice Schedule’ screen
from scratch – this will rebuild the table in
the C056 Commarea (which is required to
enable the user to ‘click’ on the new
breakdown and be navigated to the ‘SCM
Advice’ screen) and rebuild the Navigation
Bar at the left of the screen, incorporating
the new breakdown.

Next If the user presses the ‘NEXT CURRENCY’ button,

(i) If any breakdowns on the screen have

been selected for deletion, display the
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C056-SCREN-MODE = ‘U’, Call CICS

transaction LY01 (see Appendix C.1) to
validate that any details entered on the
screen are valid – using Commarea C057
(see Appendix D).

On return, check the C057-PROG-STATUS

and report any errors/warnings in the usual
way.

(iii) If C056-SCREEN-MODE = ‘U’ and no

errors returned from LY57, Call CICS
transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C058.

David Willcocks 433 May 2002

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

On return, check the C058-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) If C056-SCREEN-MODE = ‘U’ and no

errors returned from LY58, Call CICS
transaction LY01 (see Appendix C.1) to
perform Currency Validation – using
COMMAREA C019. (see Appendix D).

On return, check the C019-PROG-STATUS

and report any errors/warnings in the usual
way.

(v) If C056-SCREEN-MODE = ‘E’ or no

errors returned from LY19, Call CICS
transaction LY01 (see Appendix C.1) to
check that another currency exists – using
COMMAREA C052. (see Appendix D).

On return, check the C052-PROG-STATUS

and report any errors/warnings in the usual
way.

(vi) If no errors returned from LY52, navigate

the user to the Financial Details Control
Screen (see Section 4.15)

(i) If any breakdowns on the screen have

been selected for deletion, display the

David Willcocks 434 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
error E182 (see Appendix E) in the Error
Window (see Appendix B).

(ii) If C056-SCREEN-MODE = ‘U’, Call CICS

transaction LY01 (see Appendix C.1) to
validate that any details entered on the
screen are valid – using Commarea C057
(see Appendix D).

On return, check the C057-PROG-STATUS

and report any errors/warnings in the usual
way.

(iii) If C056-SCREEN-MODE = ‘U’ and no

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

On return, check the C058-PROG-STATUS

and report any errors/warnings in the usual
way.

(iv) If C046-SCREEN-MODE = ‘U’ and no

errors returned from LY58, Call CICS
transaction LY01 (see Appendix C.1) to
perform Currency Validation – using
COMMAREA C019. (see Appendix D).

On return, check the C019-PROG-STATUS

and report any errors/warnings in the usual
way.

(v) If C056-SCREEN-MODE = ‘U’ and no

errors returned from LY19, Call CICS
transaction LY01 (see Appendix C.1) to
perform Transaction Validation – using
COMMAREA C017. (see Appendix D).

On return, check the C017-PROG-STATUS

and report any errors/warnings in the usual
way.

(vi) If C056-SCREEN-MODE = ‘E’ or no

errors returned from LY17, call the CICS
transaction LY01 (see Appendix C.1) –

David Willcocks 435 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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) If no errors returned from LY11, navigate

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

PREV The user will press this button to view the previous Command
page of breakdowns. (This will only be applicable
where more than 100 breakdowns exist for a
particular currency)

(i) If any breakdowns on the screen

have been selected for deletion,
display the error E182 (see Appendix
E) in the Error Window (see Appendix
B).

(ii) Call CICS transaction LY01 (see

Appendix C.1) to validate that any
details entered on the screen are valid –
using Commarea C057 (see Appendix
D).

On return, check the C057-PROG-

STATUS and report any
errors/warnings in the usual way.

(iii) If no errors returned from LY57, Call

CICS transaction LY01 (see Appendix
C.1) to update the database with the
details entered on the screen – using
COMMAREA C058. (see Appendix
D).

On return, check the C058-PROG-

STATUS and report any errors/warnings
in the usual way.

(iv) If no errors returned from LY58, call

David Willcocks 436 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
CICS transaction LY01 (see Appendix
C.1) to read the previous page of
breakdowns – using COMMAREA
C056, setting C056-PREV-PRESSED
to ‘Y’ and passing the key for the first
line on the current screen in C056-
START-KEY (see Appendix D).

On return, check the C056-PROG-

STATUS and report any errors/warnings
in the usual way.

(v) If no errors are returned from LY56,

rebuild the ‘Subsequent Advice
Schedule’ screen as detailed in Section
4.20.3.

NEXT The user will press this button to view the next page Command
of breakdowns. (This will only be applicable where
more than 100 breakdowns exist for a particular
currency)

(i) If any breakdowns on the screen

have been selected for deletion,
display the error E182 (see Appendix
E) in the Error Window (see Appendix
B).

(ii) Call CICS transaction LY01 (see

Appendix C.1) to validate that any
details entered on the screen are valid –
using Commarea C057 (see Appendix
D).

On return, check the C057-PROG-

STATUS and report any
errors/warnings in the usual way.

(iii) If no errors returned from LY57, Call

CICS transaction LY01 (see Appendix
C.1) to update the database with the
details entered on the screen – using
COMMAREA C058. (see Appendix
D).

David Willcocks 437 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
On return, check the C058-PROG-
STATUS and report any errors/warnings
in the usual way.

(iv) If no errors returned from LY58, call

CICS transaction LY01 (see Appendix
C.1) to read the next page of
breakdowns – using COMMAREA
C056, setting C056-NEXT-PRESSED
to ‘Y’ and passing the key for the last
line on the current screen in C056-
START-KEY (see Appendix D).

On return, check the C056-PROG-

STATUS and report any errors/warnings
in the usual way.

(v) If no errors are returned from LY56,

rebuild the ‘Subsequent Advice
Schedule’ screen as detailed in Section
4.20.3.

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
‘Subsequent Advice Schedule Screen’ screen.
Therefore:-

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C056
(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 C056 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.

David Willcocks 438 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

(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

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 439 May 2002

Xchanging Ins-sure Services Ltd
4.21. Non-Settlement Summary Screen

4.21.1. Screen Layout

Below is the ‘Non-Settlement Summary’ Screen.

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

David Willcocks 440 May 2002

Xchanging Ins-sure Services Ltd
Tran Program Description
s. Name
Id.
LY16 Check Transaction Status
LY18 Delete Claim Transaction
LY20 Create Subsequent Advice
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY48 Build R/I Schedule Screen
LY59 Build Non-Settlement Summary Screen
LY61 Set Transaction/Collection status and
set up SCM Log Records
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
LZ11 Create Re-Advice – Initial Validation

4.21.3. Field/Command Derivation

The fields and the navigation bar on this screen will be

derived as follows:-

Field Type Source

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 441 May 2002

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

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C059 (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 C059-XCR

(This field should be protected)
UCR Field C059-UCR
(This field should be protected)
TR Field C059-TR
(This field should be protected)
Orig. Broker Field C059-ORIG-BKR
Current Bkr (This field should be protected)
Read throug each occurrence in the C059-CURRENCY-DETAILS table,
for each occurrence with C059-ORIG-CURR > spaces, create a set of
Currency/Breakdown line(s) on the screen.
Each occurrence in the C059-CURRENCY-DETAILS table will be
associated with a number of breakdowns in the C059-BREAKDOWN-
DETS table. (Note:- the Original Currency and the OSND should be
shown for the first breakdown within the currency only) A space line
should be left between the last breakdown for one currency and the
first for the next.

i.e. Orig. Curr 1 OSND 1 COR. 1 Movement AB

Outst. Amt.
COR 2 Movement AD
Outst Amt.
COR 3 Movement AC
Outst Amt.

Orig Curr 2 OSND 2 COR 4 Movement AD

Outst. Amt
COR 5 Movement AB
Outst. Amt.

Orig Curr 3 OSND 3 COR 6 Movement AD

Outst. Amt.

Orig Curr Field C059-ORIG-CURR

(This field should be protected)
OSND Field C059-ORIG-REF
(This field should be protected)
COR Field C059-COR
(This field should be protected)

David Willcocks 442 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Movement Ref. Field C059-MOVE-REF
(This field should be protected)
Outstanding Field C059-OUTST-AMT
Amount (This field should be protected)
C. Commands:-

The derivation for the commands is also returned in the C048

Commarea.
Release Comman If C059-RELEASE-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
Hold Comman If C059-HOLD-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
Delete Comman If C059-DELETE-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
Exit Comman If C059-EXIT-ATTR = ‘P’, this button
d should be protected (or preferably
not displayed)

4.21.4. Process Description

The Non-Settlement Summary screen is displayed to

the user after they have completed the entry of the
claim transaction. Full validation of the transaction will
have already been performed – the claim must be valid
for this screen to be displayed.

The screen will provide a brief summary of the Claims

Office References that have been updated on this
advice and will show the Movement References that
have been assigned to each of the breakdowns.

Only breakdowns (or Claims Office References) that

have had a new movement reference generated on this
claim transaction will be shown on this screen.

Once the user has reviewed the details on the screen,

they will have the option of either Releasing the claim
for advising, deleting the claim (this option will not be
available for claims created by the broker on the
‘CLASS for Lloyds’ system) or ‘Holding’ the claim (i.e.

David Willcocks 443 May 2002

Xchanging Ins-sure Services Ltd
saving the details, but not releasing the claim for
advising). All of these buttons will be protected if the
user is viewing the claim in enquiry mode – in which
case an additional ‘EXIT’ button will be available.

Fig 4.21.4.1. Field/Command Processing for ‘Non-Settlement

Summary’ Screen

Field / Attributes Data Type

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

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

David Willcocks 444 May 2002

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

Note: The following fields should be passed in

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

(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

David Willcocks 445 May 2002

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

Note: The following fields should be passed in

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

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’ –

David Willcocks 446 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

On return, check the C071-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’

(iii) On selection of the ‘Group Enquiry’

(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

David Willcocks 447 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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-

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

David Willcocks 448 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
-STATUS and report any errors in the
usual way.

(ii) If no errors returned from the first

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

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

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

David Willcocks 449 May 2002

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

(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. Set Diary Date
5. Create Bulk/CCS Correction
6. Set ‘File Last Seen’ Date
7. Reset Claim Transaction
8. Create Re-advice

User should select one of these options:-

‘Create Subsequent Advice’ selected

If the user selects ‘Create Subsequent Advice

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,

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.

David Willcocks 450 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
‘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).

‘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

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

David Willcocks 451 May 2002

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

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

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

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

David Willcocks 452 May 2002

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

(ii) If no errors returned from LZ06, call

LY01 using Commarea C059 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 C059 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).

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

(vi) 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 453 May 2002

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

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric

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’

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’
Orig. The Current Originating Broker (i.e. the broker who Display Alphanumeric
Broker submitted this claim transaction). Only Field (4 chars)
Current
Bkr
Original This is the currency that relates to the breakdown Display Alphanumeric
Currency being maintained. Only Field (3 Chars)
(n)
OSND Original Signing Number and date (for the currency Display Alphanumeric
(n) that relates to the breakdown being viewed) Only Field (15 Chars)
COR (n) This is the Claims Office Reference. Display Alphanumeric
Only Field (15 Chars)
Moveme This is a reference (unique within Claims Office Display Alphanumeric
nt Reference) which is assigned to breakdown if any Only Field (2 Chars)
Referenc details have been changed by the user on the current
e (n) advice. If no details have been changed this
reference will be the same as that for this

David Willcocks 454 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
breakdown on the previous transaction within the
claim.
Outstandi This is the total outstanding amount for a particular Display Numeric
ng breakdown on the claim. Only Field -(13)9.99
Amount

D. Commands - (Main Screen).

Release This will release the claim transaction for Command
advising on the SCM.

(i) Display the ‘File Seen Window’ (see

Appendix S.1). This allows the
technician to indicate that the Claim
File has been seen. If they click ‘YES’
in this window, ensure that the FILE-
SEEN-IND is set to ‘Y’ in the C061
Commarea (see below). If they click
‘NO’, it should be set to ‘N’.

(ii) Call CICS transaction LY01 (see Appendix

C.1) to set the transaction/collection status
of the claim to the appropriate value
(depending on whether the claim
transaction involves settlement or not) and
optionally set up SCM Log Records – using
COMMAREA C061.

On return, check the Program Status in the

usual way, reporting any errors on the Error
Screen (see Appendix B).

(iii) 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)

(iv) If no errors returned from LY11, navigate

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

David Willcocks 455 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
C011-NEXT-PROGRAM is set to ‘NONE’,
the current window should be closed.

Delete This will delete the current claim tranbsaction from Command
the system. this option is only allowed if
the current transaction is the last
transaction within a claim

An ‘Are you sure ?’ window should be

displayed to the user (see Appendix
T) and the delete action should only
be performed if the answer ‘Yes’ in
this window.

(i) Call CICS transaction LY01 (see

Appendix C.1) to delete current claim –
using COMMAREA C018. (see Appendix
D).

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

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). If
C011-NEXT-PROGRAM is set to ‘NONE’
the current window should be closed.

Hold This will save the claim transaction, but not release Command
it for advising on the SCM.

(iv) Call the CICS transaction LY01 (see

David Willcocks 456 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
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. (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.

Exit This function is only available if the claim Command

transaction is being viewed in enquiry mode.

It will simply exit the claim and return the user to

the screen from which the claim was initiated (i.e.
‘Find Claim’). Alternatively, if the user was viewing
the claim as part of the ‘History’ function, they will
be returned to either the transaction or movement
history screens.

(i) Call the CICS transaction LY01 (see

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). If
C011-NEXT-PROGRAM is set to ‘NONE’,
the current window should be closed.

Cancel When the technician presses the ‘Cancel’ button, the Command
screen will be rebuild from scratch. The technician
will remain in the ‘Non-Settlement Summary

David Willcocks 457 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Screen’ screen. Therefore:-

(iii) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C059
(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, based on the data

returned in the C059 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).

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

(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’, 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

David Willcocks 458 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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 459 May 2002

Xchanging Ins-sure Services Ltd
4.22. Settlement Summary Screen

4.22.1. Screen Layout

Below is a ‘mock-up’ of the ‘Settlement Summary’ Screen. The second

screen image illustrates the expandable area in which the technician is
able to view details of individual movements.

David Willcocks 460 May 2002

Xchanging Ins-sure Services Ltd
4.22.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

David Willcocks 461 May 2002

Xchanging Ins-sure Services Ltd
Tran Program Description
s. Name
Id.
LY48 Build R/I Schedule Screen
LY61 Set Transaction/Collection status and
set up SCM Log Records
LY62 Build Settlement Summary Screen
LY68 Create History Session Record
LY71 Set up Group Session Record
LY82 Treaty/LOC Take Down Number
processing
LY88 Build Narrative Details Screen
LY90 Bulk/CCS Correction Initial Validation
LY96 Set File Last Seen Date
LZ03 Obtain Breakdown for Collection
LZ11 Create Re-Advice – Initial Validation

4.22.3. Field/Command Derivation

The fields and the navigation bar on this screen will be

derived as follows:-

Field Type Source

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 462 May 2002

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

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C062 (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).

N.B. Ensure that the details returned are stored for later use – the key fields (CURR-NO,
SDN-NO and STAT-SPLIT-NO) will need to be passed to the ‘Treaty/LOC Take Down
Number Processing’ transaction and/or the ‘Obtain Breakdown for Collection’ transaction.

XCR Field C062-XCR

(This field should be protected)
UCR Field C062-UCR
(This field should be protected)
TR Field C062-TR
(This field should be protected)
Orig. Broker Field C062-ORIG-BKR
(This field should be protected)
Paid by Cheque Field C062-PAID-BY-CHEQUE
(This field should be protected)

David Willcocks 463 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Read throug each occurrence in the C062-CURRENCY-DETAILS table,
for each occurrence with C062-ORIG-CURR > spaces, create a set of
Currency/Collection line(s) on the screen.
Each occurrence in the C062-CURRENCY-DETAILS table will be
associated with a number of Collections in the C062-COLLECTION-
DETS table. (Note:- the Original Currency, Settlement Currency and the
OSND should be shown for the first collection within the currency only)
A space line should be left between the last collection for one currency
and the first for the next.

i.e. Orig. Curr 1 Sett. Curr 1 OSND 1 TDN1 PT T (Orig) Outst.

Amt.(Orig) PTT (Sett)
TDN2 PT T (Orig) Outst. Amt.
(Orig) PTT (Sett)
TDN3 PT T (Orig) Outst. Amt.
(Orig) PTT (Sett)

Orig. Curr 2 Sett. Curr 2 OSND 2 TDN4 PT T (Orig) Outst.

Amt.(Orig) PTT (Sett)

Orig. Curr 3 Sett. Curr 3 OSND 3 TDN5 PT T (Orig) Outst.

Amt.(Orig) PTT (Sett)
TDN6 PT T (Orig) Outst. Amt.
(Orig) PTT (Sett)

Each of these Collection Lines should be expandable. If the user

expands a particular line, call the CICS transaction LY01 (see Appendix C.1) –
using COMMAREA C102 (see Appendix D) . This transaction will return all breakdowns
for the selected collection (that have had a new movement reference assigned on the
current transaction).

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

The information returned by the LZ03 transaction should be displayed as follows:-

Orig. Curr 1 Sett. Curr 1 OSND 1 TDN1 PTT (Orig) Outst.

Amt.(Orig) PTT (Sett)
__ TDN2 PTT (Orig) Outst. Amt.
(Orig) PTT (Sett)
Breakdown details:- COR 1 Move Ref AD PTT (Orig) Outst.
Amt (Orig) PTT (Sett)
COR 2 Move Ref AB PTT (Orig) Outst.
Amt (Orig) PTT (Sett)
COR 3 Move Ref AC PTT (Orig) Outst.
Amt (Orig)_PTT (Sett)
TDN3 PTT (Orig) Outst. Amt.
(Orig) PTT (Sett)

David Willcocks 464 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Original Field C062-ORIG-CURR (n1)
Currency (This field should be protected)
Settlement Field C062-SETT-CURR (n1)
Currency (This field should be protected)
OSND Field C062-ORIG-REF (n1)
(This field should be protected)
Take Down Field C062-TDN-REF (n1, n2)
Number (If C062-TDN-ATTR (n1, n2) = ‘P’, this
field should be protected. Otherwise, it
should be unprotected)
Treasury Rate Field C062-TREASURY-RATE (n1, n2)
(If C062-TREASURY-ATTR (n1, n2) =
‘P’, this field should be protected.
Otherwise, it should be unprotected)
N.B. If C062-HIDE-RATE = ‘Y’, this
field should not be shown at all –
nor should any associated column
headings.
Paid This Time Field C062-PTT-AMT (n1, n2)
(Orig) (This field should be protected)
Outstanding Field C062-OUTST-AMT (n1, n2)
Amount (Orig) (This field should be protected)
Paid This Time Field C062-CLAIM-AMT-SETT (n1, n2)
(Sett) (This field should be protected)

The following fields are shown in the expandable area. The details are returned in the C102
Commarea. These details are provided by transaction LZ03 – which is called only if the
user expands a particular collection.

Claims Office Field C102-COR (n1)

Reference (This field should be protected)
Movement Field C102-MOVE-REF (n1)
Reference (This field should be protected)
Paid This Time Field C102-PTT-AMT-BD (n1)
(Breakdown) (This field should be protected)
Outstanding Field C102-OUTST-AMT-BD (n1)
Amount (This field should be protected)
(Breakdown)
Paid This Time Field C102-CLM-AMT-SETT-BD (n1)
in Settlement (This field should be protected)
Currency
(Breakdown)

David Willcocks 465 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
C. Commands:-

The derivation for the commands is also returned in the C048

Commarea.
Release Comman If C062-RELEASE-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
Hold Comman If C062-HOLD-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
Delete Comman If C062-DELETE-ATTR = ‘P’, this
d button should be protected (or
preferably not displayed)
Exit Comman If C062-EXIT-ATTR = ‘P’, this button
d should be protected (or preferably
not displayed)
CCVC Comman If C062-CCVC-ATTR = ‘P’, this button
d should be protected (or preferably
not displayed)

4.22.4. Process Description

The Settlement Summary screen is displayed to the

user after they have completed the entry of the claim
transaction. Full validation of the transaction will have
already been performed – the claim must be valid for
this screen to be displayed.

The screen will provide a brief summary of the

settlement that is taking place and display the Take
Down Numbers and Dates that have been assigned to
each ‘collection’ on the claim transaction. In addition,
the user is able to ‘expand’ each collection in order to
enquire on details of how each payment is split across
the Claims Office References. In the ‘expanded’ area
the user will be able to see the movement references
that have been assigned to each breakdown.

Only breakdowns (or Claims Office References) that

have had a new movement reference generated on this
claim transaction will be shown on this screen.

David Willcocks 466 May 2002

Xchanging Ins-sure Services Ltd
Once the user has reviewed the details on the screen,
they will have the option of either Releasing the claim
for advising on the USM and SCM, deleting the claim
(this option will not be available for claims created by
the broker on the ‘CLASS for Lloyds’ system) or
‘Holding’ the claim (i.e. saving the details, but not
releasing the claim for advising). All of these buttons
will be protected if the user is viewing the claim in
enquiry mode – in which case an additional ‘EXIT’
button will be available.

Fig 4.22.4.1. Field/Command Processing for ‘Settlement Summary’

Screen

Field / Attributes Data Type

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

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

Transaction options’ window, the user

David Willcocks 467 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

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

David Willcocks 468 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’, 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

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

David Willcocks 469 May 2002

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

User should select one of these options.

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

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

On return, check the C071-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’

(iii) On selection of the ‘Group Enquiry’

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

David Willcocks 470 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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-

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

David Willcocks 471 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

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

(i) call CICS transaction LY01 (see Appendix

David Willcocks 472 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

User should select one of these options:-

‘Create Subsequent Advice’ selected

If the user selects ‘Create Subsequent Advice

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,

On return, check the C020-PROG-STATUS and

David Willcocks 473 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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).

‘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

David Willcocks 474 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

(i) Call CICS transaction LY01 (see

Appendix C.1), passing the Commarea

David Willcocks 475 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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 C062 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 C062 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 476 May 2002

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

(ii) 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.

(vii) 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)

(iii) Fields (Main Screen)

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric

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’

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

David Willcocks 477 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
‘X / XXXX / XXXXXXXXXXXX’
Orig. The Originating Broker (i.e. the broker who Display Alphanumeric
Broker submitted this claim transaction). Only Field (4 chars)
Paid By This field indicates whether or not the current Display Alphanumeric
Cheque transaction has been paid by cheque. Only Field (1 Char)
Original This is the original (or estimate) currency that Display Alphanumeric
Currency relates to the breakdown being maintained. Only Field (3 Chars)
Settlemen This is the currency in which settlement is to be Alphanumeric
t Currency made. (3 Chars)
OSND Original Signing Number and date (for the currency Display Alphanumeric
that relates to the breakdown being viewed) Only Field (15 Chars)
Take This is a unique reference – comprising a sequence Optional Numeric
Down number and a date – that identifies a particular Field 9(13)
Number financial transaction.

For Treaty or Letter of Credit transactions, this field

will be unprotected and will allow the user to enter
the Taking Down Numbers that have been advised
by LIDS.

If entered, the baasic format should be:-

CCYYMMDDNNNNN

Where CCYYMMDD must be a valid date

NNNNN must be numeric

If the format is not as expected, display the error

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

Treasury This field will only be enabled for CCS Claim Mandatory Numeric
Rate Transactions for which the user has ticked the Field Z(6)9.9(5)
‘Previously Paid’ indicator on the Claim
Transaction Creation Screen.

If unprotected, the field is mandatory.

Paid This The amount (in original currency) that is to be paid Display Numeric
Time this time. Only Field -(13)9.99
(Orig)
Outstandi This is the total outstanding amount for a particular Display Numeric
ng breakdown on the claim. Only Field -(13)9.99
Amount
(Orig)
Paid This This is the amount to be paid this time, expressed in Display Numeric

David Willcocks 478 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Time the Settlement Currency Only Field -(13)9.99
(Sett)
COR This is the Claims Office Reference. Display Alphanumeric
Only Field (15 Chars)
Movement This is a reference (unique within Claims Office Display Alphanumeric
Reference Reference) which is assigned to breakdown if any Only Field (2 Chars)
details have been changed by the user on the current
advice. If no details have been changed this
reference will be the same as that for this
breakdown on the previous transaction within the
claim.
Paid This The amount (in original currency) that is to be paid Display Numeric
Time this time – for the current breakdown (Claims Only Field -(13)9.99
(Breakdow Office Reference).
n)
Outstandi This is the total outstanding amount for a particular Display Numeric
ng breakdown on the claim. Only Field -(13)9.99
Amount
(Breakdow
n)
Paid This This is the Paid This Time, expressed in the Display Numeric
Time in Settlement Currency, for a particular breakdown Only Field -(13)9.99
Settlemen (Claims Office Reference)
t Currency
(Breakdow
n)

D. Commands – (Main Screen).

Release This will release the claim transaction for Command
advising on the SCM.

(v) If any C062-TDN-ATTR fields = ‘U’ (i.e.

the current claim is Treaty or Letter of
Credit), call CICS transaction LY01 (see
Appendix C.1) to validate that any Take
Down Numbers entered are valid and, if
they are, update the database – using
COMMAREA C082.

On return, check the Program Status in the

usual way, reporting any errors on the Error
Screen (see Appendix B).

(vi) Display the ‘File Seen Window’ (see

Appendix S.1). This allows the

David Willcocks 479 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
technician to indicate that the Claim
File has been seen. If they click ‘YES’
in this window, ensure that the FILE-
SEEN-IND is set to ‘Y’ in the C061
Commarea (see below). If they click
‘NO’, it should be set to ‘N’.

(vii) Call CICS transaction LY01 (see Appendix

On return, check the Program Status in the

usual way, reporting any errors on the Error
Screen (see Appendix B).

(viii) Call the CICS transaction LY01 (see

On return, check the Program Status in the

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

(ix) If no errors returned from LY11, navigate

the user to the program indicated by C011-
NEXT-PROGRAM (see Appendix N) – if
not set to ‘NONE’.

(x) If C011-NEXT-PROGRAM is set to

‘NONE’, Call CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C004
(see Appendix D) to log-off the sub-session
and delete the Session Record.

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 are returned, the current

David Willcocks 480 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
window should be closed.

Delete This will delete the current claim tranbsaction from Command
the system. This option is only allowed if
the current transaction is the last
transaction within a claim

An ‘Are you sure ?’ window should be

displayed to the user (see Appendix
T) and the delete action should only
be performed if the answer ‘Yes’ in
this window.

(i) Call CICS transaction LY01 (see

Appendix C.1) to delete current claim –
using COMMAREA C018. (see Appendix
D).

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

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) – if
not set to ‘NONE’.

(iv) If C011-NEXT-PROGRAM is set to

‘NONE’, Call CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C004
(see Appendix D) to log-off the sub-session
and delete the Session Record.

David Willcocks 481 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)

If no errors are returned, the current

window should be closed.

Hold This will save the claim transaction, but not release Command
it for advising on the SCM.

(i) If C062-TDN-ATTR = ‘U’ (i.e. the current

claim is Treaty or Letter of Credit), call
CICS transaction LY01 (see Appendix C.1)
to validate that any Take Down Numbers
entered are valid and, if they are, update the
database – using COMMAREA C082.

On return, check the Program Status in the

usual way, reporting any errors on the Error
Screen (see Appendix B).

(ii) Call the CICS transaction LY01 (see

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) – if
not set to ‘NONE’

(iv) If C011-NEXT-PROGRAM is set to

‘NONE’, Call CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C004
(see Appendix D) to log-off the sub-session
and delete the Session Record.

On return, check the Program Status in the

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

David Willcocks 482 May 2002

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

If no errors are returned, the current

window should be closed.

Exit This function is only available if the claim Command

transaction is being viewed in enquiry mode.

It will simply exit the claim and return the user to

(iv) Call the CICS transaction LY01 (see

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
not set to ‘NONE’.

(vi) If C011-NEXT-PROGRAM is set to

‘NONE’, Call CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C004
(see Appendix D) to log-off the sub-session
and delete the Session Record.

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 are returned, the current

window should be closed.

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

any changes made since the last ‘Save’ will be
removed. Changes can only be made on this screen

David Willcocks 483 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
in the case of Treaty and Letter of Credit claims.The
technician will remain in the ‘Settlement Summary
Screen. Therefore:-

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C062
(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 C062 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

(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

David Willcocks 484 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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.

CCVC If the user selects the ‘CCVC’ option, the ‘Claims

Coverage Validation Check (CCVC)’ screen should
be displayed to them (see Section 4.42).

David Willcocks 485 May 2002

Xchanging Ins-sure Services Ltd
4.23. Bulk Component Selection Screen

Change Control Log

Release Date Changed SIRS Description of Changes Made

By No.

29/03/2004 DAS 36170 When using navigation bar to go from the bulk component
selection screen to the bulk component confirmation screen , if
a component has been de-selected and the user answers ‘no’
when asked if they want to de-select the component the bulk
component selection screen should be rebuilt using LY64.

4.23.1. Screen Layout

Below is a ‘mock-up’ of the ‘Bulk Component Selection’ Screen.

David Willcocks 486 May 2002

Xchanging Ins-sure Services Ltd
Below is an image illustrating the expanded area, displayed when the ‘more’ button is
clicked:-

4.23.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
LY09
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
David Willcocks 487 May 2002
Xchanging Ins-sure Services Ltd
Tran Program Description
s. Name
Id.
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY46 Check whether Currency/Transaction
Validn. reqd
LY64 Build Bulk Component Selection
Screen
LY65 Validate Bulk Collection
LY66 Create Bulk Component Session
Record
LY68 Create History Session Record
LY71 Set up Group Session Record
LY88 Build Narrative Details Screen
LY90 Bulk/CCS Correction Initial Validation
LY95 Delete Deselected Bulk Components
LY96 Set File Last Seen Date
LY98 Load Elligible Bulk Components
LY99 Store Selected/Deselected Components
LZ06 Reset Claim Transaction
LZ08 FIL Codes/Trust Fund Codes Validation
Module
LZ09 Obtain Additional Details for Bulk
Component

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

David Willcocks 488 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
See Appendix F for details of how to process the
information returned from this CICS transaction.

B. Fields:-

(i) call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA
C098 (see Appendix D) . This transaction will load all claims eligible to bulk
components on this bulk header onto a database table.

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

(ii) Call CICS transaction LY01 (see Appendix C.1) – using Commarea C064 (see
Appendix D). This transaction will read through the database table built by
LY98 (see above) and return the first page of details.

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

XCR Field C064-XCR

(This field should be protected)
UCR Field C064-UCR
(This field should be protected)
TR Field C064-TR
(This field should be protected)
OSND1 Field C064-ORIG-REF-1
(This field should be protected)
OSND2 Field C064-ORIG-REF-2
(This field should be protected)
OSND3 Field C064-ORIG-REF-3
(This field should be protected)
Orig. Current Field C064-ORIG-BKR
Broker (This field should be protected)
Peer Rev. Ind Field C064-PEER-REV-IND
(This field should be protected)
The following Fields should appear above the Bulk Component
list – but outside of the header area.
Target PTT Field C064-PTT-AMT-TARGET
Amount
Target Field C064-OUT-AMT-TARGET
Outstanding
Amount
Actual PTT Field C064-PTT-AMT-ACTUAL
Amount
Actual Field C064-OUT-AMT-ACTUAL

David Willcocks 489 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Outstanding
Amount

The details contained in the C064-COMPONENT-CLAIMS table

should be displayed in tabular format. C064-COMP-SYS-REF is
returned in the C064-COMPONENT-CLAIMS table, but is not
shown on the screen. This field is required for later use and the
value associated with each line on the screen should be stored.

Include Ind. Tick-Box Set to ‘TRUE’ if C064-INCLUDE-IND =

‘Y’
(If C064-INCLUDE-ATTR = ‘P’, this
field should be protected)
UCR Field C064-COMP-UCR
(This field should be protected)
COR Field C064-COR
(This field should be protected and
should appear underneath the UCR)
Name 1 Field C064-NAME-1
(This field should be protected)
Name 2 Field C064-NAME-2
(This field should be protected)
Date of Loss Field C064-LOSS-DATE-FROM
(This field should be protected)
Date Claim Field C064-CLAIM-DATE-FROM
Made (This field should be protected)

Broker Field C064-BKR-REF-1

Reference 1 (This field should be protected)
Processed Tick-Box C064-PROC-IND
Indicator (This field should be protected)

The following fields should be shown in an expanded area when the

user clicks a ‘More’ button that should be shown alongside each
Component UCR (to the right of the ‘Set Up and Released’ indicator).
The details will be displayed in a box that will be shown underneath the
Component UCR in question (Processing similar to that used in the
Settlement Summary screen). N.B. The details will be repeated for
every COR within the component claim

The details are obtained by calling LY01, passing Commarea C108 (See
Appendix D). N.B. The value of C064-COMP-SYS-REF for the
selected UCR should be passed in C108-COMP-SYS-REF.
COR C108-COR (n)

Original C108-ORIG-CURR (n)

David Willcocks 490 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Currency
Name 1 C108-NAME-1 (n)

DOL From C108-LOSS-DATE-FROM (n)

DOL To C108-LOSS-DATE-TO (n)

DCM From C108-CLAIM-DATE-FROM (n)

DCM To C108-CLAIM-DATE-TO (n)

State Code C108-STATE-CODE (n)

Cat Code C108-CAT-CODE (n)

PCS Cat Code C108-PCS-CAT-CODE (n)

NAIC Code C108-NAIC-CODE (n)

NAIC Qual C108-NAIC-QUAL (n)

PTT Amount C108-PTT-AMT (n)

Outstanding C108-OUTST-AMT (n)

Amount
C. Commands
< PREV Comman If C064-PREV-ATTR = ‘P’ (Protected),
d this command should be protected (or
preferably not shown at all).

NEXT > Comman If C064-NEXT-ATTR = ‘P’ (Protected),

d this command should be protected (or
preferably not shown at all).

4.23.4. Process Description

If the user specified that the current claim transaction

is a Bulk Settlement (i.e. one that links several UCR’s
together for settlement purposes), the Bulk Component
Selection screen will be presented to the user after they
have completed all Financial Details screens.

David Willcocks 491 May 2002

Xchanging Ins-sure Services Ltd
The selection screen will list all claims that are elligible
to be part of the collection. Elligible claims must satisfy
all of the following conditions:-

(i) They must have at least one of the

Original/Settlement Currency combinations
used on the header.
(ii) The OSND’s used for these currencies must
be the same on the header and the
component
(iii) The values of Trust Fund, FIL Code 1, FIL
Code 2 and DTI Code for the currencies
must be the same on the header and the
component.

Later validation will ensure that component claims

involve settlement only in those currencies specified on
the header.

The user will have the ability to identify (using a ‘Tick-

Box’) which of the claims listed should be included in
the Bulk Settlement. Only those identified in this way
can be selected (see below).

The component claims will have to be set up manually.

The user will do this by ‘clicking’ on the UCR in
question. This will take them into the most recent claim
transaction for that UCR – from where they must create
a ‘Subsequent Advice’ in the usual way. On release of
this subsequent advice, a cross-reference record will be
set up, linking the newly-created component claim with
the bulk header. This component processing will be
performed in a new window (or session) so that – on
release of the component transaction – the window will
be closed and the user will still be on the ‘Bulk
Component Selection’ screen.

As each component is processed, a tick will be put in

the box alongside the UCR in question. Once all UCR’s
that have been included in the Bulk Settlement are
flagged as processed, the user is able to press the
‘PROCEED’ button and conclude the Bulk.

David Willcocks 492 May 2002

Xchanging Ins-sure Services Ltd
If the Bulk Header was entered by the broker on the
‘CLASS for Lloyds’ system, the components will already
have been selected. In this case, the screen will simply
list the components that belong to this Bulk Header,
rather than all elligible claims. This will also apply to
Bulk Headers that are being viewed in enquiry mode.

Fig 4.23.4.1. Field/Command Processing for ‘Bulk Component

Selection’ Screen

Field / Attributes Data Type

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

(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

David Willcocks 493 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

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

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

David Willcocks 494 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

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

User should select one of these options.

David Willcocks 495 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

On return, check the C071-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) On selection of the ‘Maintain Group’

(iii) On selection of the ‘Group Enquiry’

(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

David Willcocks 496 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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-

User should select one of these options.

(i) Whichever option is selected, call CICS

David Willcocks 497 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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

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

(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

David Willcocks 498 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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. 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

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,

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

David Willcocks 499 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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
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

David Willcocks 500 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
‘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

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

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 501 May 2002

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

This function will reset the status of a previously

(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 C064 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 C064 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 502 May 2002

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

(i) If C064-SCREEN-MODE = ‘U’, call CICS transaction LY01 (see Appendix C.1) to save any
selections/deselections made on the current screen - using Commarea C099 (see Appendix
D).

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

(ii) If C064-SCREEN-MODE = ‘U’ (Update), call CICS transaction LY01 (see Appendix C.1) to
validate that all bulk component details are valid – using Commarea C065 (see Appendix D).
N.B. Ensure that C065-PROCESS-IND is set to ‘V’ (Validate)
On return, check the C065-PROG-STATUS. However, do not report any errors/warnings
returned.

If the C065-PROG-STATUS = 5, this means that one or more previouusly released bulk
components have been deselected. Display the ‘Delete Component Confirmation’ window (see
Appendix R).
(a) If the technician selects ‘NO’, rebuild the screen (by calling LY01 passing
Commarea C064) and redisplay the screen
(b) If the technician selects ‘YES’ in the ‘Delete Component Confirmation’ screen, call CICS
transaction LY01 (see Appendix C.1) to delete the deselected bulk component(s) – using
Commarea C095 (see Appendix D).
On return, check the C095-PROG-STATUS and report any errors/warnings in the usual
way.

(iii) If C064-SCREEN-MODE = ‘U’ (Update) and no errors returned from LY65, 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 C064-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 503 May 2002

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

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric

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’

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 The Original Signing Number and Date that applies Display Alphanumeric
to the first currency on the Bulk Header Claim Only Field (15 Chars)
transaction
OSND2 The Original Signing Number and Date that applies Display Alphanumeric
to the second currency on the Bulk Header Claim Only Field (15 Chars)
transaction
OSND3 The Original Signing Number and Date that applies Display Alphanumeric
to the second currency on the Bulk Header Claim Only Field (15 Chars)
transaction
Orig. The Broker Code that identifies the broking house Display Alphanumeric
Current that submitted that initiated the claim transaction. Only Field (4 Chars)
Broker
Peer Rev. Indicates whether or not peer review is required on Display Alphanumeric
Ind this claim transaction. Only (1 Char)
Field
Include This field allows the user to indicate which of the Optional N/A

David Willcocks 504 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Ind. listed claims should be included in the bulk Tick-Box
settlement.

If the user re-enters a partially completed Bulk

Header, this box will be ticked only for those
components that were actually processed the first
time round. If the user selected components but
failed to process them, then these will not be ticked
and the technician will need to reselect them.

If the user is enquiring on a completed Bulk Header

or a Bulk Header that was loaded by the broker on
the ‘CLASS for Lloyds’ system, this screen will list
only claims that have been included in the Bulk
Settlement – rather than all elligible claims. In this
case, all lines will be flagged as ‘included’.

If the user puts a tick in this box, the associated

UCR should be underlined and made available to
selected.

Componen The Unique Claim Reference of a particular Display Alphanumeric

t component of the Bulk Settlement. Only Field (17 Chars)
UCR (n)
If the associated ‘Include Ind.’ Has been ticked, the
user is able to click on this field in order to set up
the bulk component transaction (see below).

Name 1 The first ‘Name Field’ that applies to the component Display Alphanumeric
(n) claim. This can be set to either the Insured or Only Field (50 Chars)
Reinsured, depending on the type of claim.
Name 2 The first ‘Name Field’ that applies to the component Display Alphanumeric
(n) claim. This can be set to either the Cover Holder, Only Field (50 Chars)
Original Insured or Vessel, depending on the type of
claim.
Date of The date that the loss occurred or the first date of a Display Date
Loss (n) period of loss. Only Field (DD/MM/CCYY)

Date The date that the claim was made or the first date of Display Date
Claim a claim period Only Field (DD/MM/CCYY)

Made (n)
Broker The first of the two broker references that apply to Display Alphanumeric
Reference this claim. Only Field (12 Chars)
1 (n)
Processed This box will be ticked once the user has created the Display N/A
Indicator component claim transaction and released it for Only Tick-

David Willcocks 505 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(n) advising. Box

The Bulk Header will only be valid once all

components that the user has opted to include in the
bulk settlement have been processed in this way.

COR (n) This is the Claims Office Reference. This field is Display Alphanumeric
system generated for each line created on the Only Field (14 Chars)
screen.

If the user ‘clicks’ on this field, they will be

navigated to the ‘SCM Advice’ Screen – see below
in the Commands Section.

Original The Original Curreny currently held on CLASS for Display Alphanumeric
Currency the COR shown Only Field (3 Chars)
(n)
Name 1 The first ‘Name Field’ that applies to the component Display Alphanumeric
(n) claim. This can be set to either the Insured or Only Field (50 Chars)
Reinsured, depending on the type of claim.
DOL From Either the date of loss or the first date of a period of Display Date
(n) loss. Only Field (DD/MM/CCYY)

DOL To (n) The last date of a period of loss. Display Date

Only Field (DD/MM/CCYY)
DCM Either the date the claiom was made or the first date Display Date
From (n) of a claim period. Only Field (DD/MM/CCYY)

DCM To The last date of a claim period. Display Date

(n) Only Field (DD/MM/CCYY)

State Identifies the state or province of the claim. Display Alphanumeric

Code (n) Only Field (2 Chars)

Cat Code The Catastrophe Code relating to the loss. Display Alphanumeric
(n) Only Field (4 chars)

PCS Cat The Propert Caims Service (PCS) Catastrophe Code Display Alphanumeric
Code (n) relating to the loss. Only Field (4 chars)

NAIC The National Association of Insurance Display Alphanumeric

Code (n) Commissioners (NAIC) Code. This identifies US Only Field (11 Chars)
cedants for regulatory reporting purposes.

David Willcocks 506 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
NAIC Qual Qualifier associated with the ‘National Association Display Alphanumeric
(n) of Insurance Commissioners’ (NAIC) Code. This Only Field (1 Char)
indicates the type of NAIC code.

PTT The total amount to be paid (in the Original Display Numeric
Amount Currency above) on this Buk Settlement. I.e. across Only Field -(13)9.99
(n) all Bulk Components.

Format:- --,---,---,---,--9

Outstandi The amount still outstanding (in the Original Display Numeric
ng Currency above) on this particular Bulk Component Only Field -(13)9.99
Amount claim.
(n)
Format:- --,---,---,---,--9

D. Commands - (Main Screen).

Component If the technician ‘clicks’ on the Component Command
UCR UCR field, they will either be taken into the
‘Claim Creation’ screen for the most recent
transaction within the component UCR (for un-
processed components) or directly into the
component itself, if component claim
transaction has already been created (i.e. a
Cross-Reference record exists on TCLXRFA).

The Component UCR should only be

underlined and ‘available to be clicked on’ if
the user has ticked the associated ‘Included’
tick-box.

‘Clicking’ on the Component UCR should open

up a new ‘window’ – associated with its own
entry on the Session Table (i.e. a new Session
No.). Once the component has been processed
and released, 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
component claim - using Commarea C066
(see Appendix D).

N.B. Pass the value of C064-COMP-SYS-

David Willcocks 507 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
REF, associated with the selected line, in
the C066 Commarea – these values should
have been stored earlier.

On return, check the C066-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) If no errors have been found while creating

the new 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) and
setting C009-SESSION-NO to the new
Session Number (i.e. C066-COMP-
SESSION-NO).

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, Open new window and display

the Security Notes relating to the
component UCR in the ‘Security Notes’
screen (see Section 4.8). (a new
SESSION-NO is associated with this
window – this will have been
returned by previous transaction,
LY66)

(iii) If the PROG-STATUS returned from

LY09 was zero, open new window,
navigating user to ‘Claim Creation’
screen for component UCR (a new
SESSION-NO is associated with this
window – this will have been returned
by previous transaction, LY66)

< PREV If the user presses this button, any selections made Command
will be saved and the previous 100 elligible claims
will be displayed.

David Willcocks 508 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(i) If C064-SCREEN-MODE = ‘U’, call
call CICS transaction LY01 (see
Appendix C.1) to save any selections
made on the current screen - using
Commarea C099 (see Appendix D).

On return, check the C099-PROG

-STATUS and report any errors/
warnings in the usual way.

(ii) If C064-SCREEN-MODE = ‘E’ or

C064-SCREEN-MODE = ‘U’ and no
errors returned from LY99, call CICS
transaction LY01 (see Appendix C.1) to
read the previous page of eligible
claims – using COMMAREA C064,
setting C064-PREV-PRESSED to ‘Y’
and passing the key for the first line on
the current screen in C064-START-
KEY (see Appendix D).

On return, check the C064-PROG-

STATUS and report any errors/warnings
in the usual way.

(vi) If no errors are returned from LY64,

rebuild the ‘Bulk Component Selection
Screen’ as detailed in Section 4.23.3.

NEXT > If the user presses this button, any selections made Command
will be saved and the next 100 elligible claims will
be displayed.

(i) If C064-SCREEN-MODE = ‘U’, call

call CICS transaction LY01 (see
Appendix C.1) to save any selections
made on the current screen - using
Commarea C099 (see Appendix D).

On return, check the C099-PROG

-STATUS and report any errors/
warnings in the usual way.

(ii) If C064-SCREEN-MODE = ‘E’ or

C064-SCREEN-MODE = ‘U’ and no
errors returned from LY99, call CICS
transaction LY01 (see Appendix C.1) to
read the next page of eligible claims –

David Willcocks 509 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
using COMMAREA C064, setting
C064-NEXT-PRESSED to ‘Y’ and
passing the key for the last line on the
current screen in C064-START-KEY
(see Appendix D).

On return, check the C064-PROG-

STATUS and report any errors/warnings
in the usual way.

(iii) If no errors are returned from LY64,

rebuild the ‘Bulk Component Selection
Screen’ as detailed in Section 4.23.3.

Refresh Because Bulk Components are processed in a

separate window which ‘overlays’ the Bulk
Component Selection window. Once the technician
has released the bulk component and the window is
closed, the Bulk Component Selection screen is still
present in the background, with all details exactly as
before. This means that the bulk components that
have been processed will not be shown as such until
the screen is rebuilt. To do this the user should press
‘REFRESH’.

(i) If C064-SCREEN-MODE = ‘U’, call

CICS transaction LY01 (see Appendix
C.1) to save any selections/deselections
made on the current screen - using
Commarea C099 (see Appendix D).

On return, check the C099-PROG

-STATUS and report any errors/
warnings in the usual way.

(ii) If C064-SCREEN-MODE = ‘U’

(Update) and no errors have been
returned from LY99, call CICS
transaction LY01 (see Appendix C.1) to
validate that all bulk component details
are valid – using Commarea C065 (see
Appendix D). N.B. Ensure that C065-
PROCESS-IND is set to ‘R’ (Refresh)

On return, check the C065-PROG-

STATUS and if status is equal to 9,
report any errors/warnings in the usual
way.

David Willcocks 510 May 2002

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

(iii) If the C065-PROG-STATUS = 5, this

means that one or more previouusly
released bulk components have been
deselected. Display the ‘Delete
Component Confirmation’ window (see
Appendix R). If the technician
selects ‘NO’, continue with
processing in number (iv).

(iv) If C065-PROG-STATUS = 5 and

technician selected ‘YES’ in the ‘Delete
Component Confirmation’ screen, call
CICS transaction LY01 (see Appendix
C.1) to delete the deselected bulk
component(s) – using Commarea C095
(see Appendix D).

On return, check the C095-PROG

-STATUS and report any
errors/warnings in the usual way.

(v) If C064-SCREEN-MODE = ‘E’ or

C064-SCREEN-MODE = ‘U’ and no
errors returned from LY95, call the
CICS transaction LY01 (see Appendix
C.1) – using COMMAREA C064 (see
Appendix D) – in order to obtain the
necessary details from the database.

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
C064 Commarea (see Section
4.23.3.)

Proceed If the user presses ‘Proceed’, the details on the Command

screen are validated. If any bulk components - that
were previously set up, released and cross-
referenced to the header – are found to have been
subsequently deselected by the technician, a
confirmation window is displayed asking them
whether they wish to delete the deselected

David Willcocks 511 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
components or not. If so, the deselcted components
are deleted before the user is navigated to the next
screen. If not, the user is simply navigated onto the
next screen.

(i) If C064-SCREEN-MODE = ‘U’, call

CICS transaction LY01 (see Appendix
C.1) to save any selections/deselections
made on the current screen - using
Commarea C099 (see Appendix D).

On return, check the C099-PROG

-STATUS and report any errors/
warnings in the usual way.

(ii) If C064-SCREEN-MODE = ‘U’

(Update), call CICS transaction LY01
(see Appendix C.1) to validate that all
bulk component details are valid –
using Commarea C065 (see Appendix
D). N.B. Ensure that C065-
PROCESS-IND is set to ‘V’
(Validate)

On return, check the C065-PROG

-STATUS and if status is equal to 9,
report any errors/warnings in the usual
way.

(iii) If the C065-PROG-STATUS = 5, this

(iv) If C065-PROG-STATUS = 5 and

technician selected ‘YES’ in the ‘Delete
Component Confirmation’ screen, call
CICS transaction LY01 (see Appendix
C.1) to delete the deselected bulk
component(s) – using Commarea C095

David Willcocks 512 May 2002

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

On return, check the C095-PROG

-STATUS and report any
errors/warnings in the usual way. If no
errors returned, rebuild the screen
(by calling LY01 passing
Commarea C064) and redisplay the
screen.

(v) If C064-SCREEN-MODE = ‘E’ or

C064-SCREEN-MODE = ‘U’ and no
errors returned from LY95, 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)

(vi) If no errors returned from LY11,

navigate the user to the program
indicated by 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. I.e. claims selected for inclusion in the
bulk settlement, but not yet processed will be
removed. The technician will remain in the ‘Bulk
Component Selection’ screen. Therefore:-

(v) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C064
(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)

David Willcocks 513 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(vi) Rebuild the screen, based on the data
returned in the C064 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

(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

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 514 May 2002

Xchanging Ins-sure Services Ltd
David Willcocks 515 May 2002
Xchanging Ins-sure Services Ltd
4.24. Conclusion of Bulk Settlement Screen

4.24.1. Screen Layout

Below is a ‘mock-up’ of the ‘Conclusion of Bulk Settlement’ Screen.

4.24.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

David Willcocks 516 May 2002

Xchanging Ins-sure Services Ltd
Tran Program Description
s. Name
Id.
LY21 ROE Adjustment Initial Validation
LY22 Contra Correction Initial Validation
LY23 Add TDN’s Initial Validation
LY67 Build Conclusion of Bulk Screen
LY68 Create History Session Record
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.24.3. Field/Command Derivation

The fields and the navigation bar on this screen will be

derived as follows:-

Field Type Source

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 C067 (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 C067-XCR

(This field should be protected)
UCR Field C067-UCR

David Willcocks 517 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
(This field should be protected)
TR Field C067-TR
(This field should be protected)
Current Bkr Field C067-ORIG-BKR
Orig. Broker (This field should be protected)
Currency Details

When building the screen for the first time use the first occurrence in the Currency
Details table (i.e. n1 = 1). If the user presses the ‘NEXT CURRENCY’ button, the
occurrence should be incremented accordingly (i.e. n1 = 2, n1 = 3) – see later
processing – with ‘PREV CURRENCY’ obviously having the reverse effect.

Original Field C067-ORIG-CURR (n1)

Currency (This field should be protected)

OSND Field C067-ORIG-REF (n1)

(This field should be protected)

Each Occurrence in the C067-COMPONENT-CLAIMS table (with C067-COMP-

UCR > spaces) should be displayed on the screen in tabular format.

Note:- the UCR’s will not be in aphabetical order. The JAVA

Layer will need to sort the results. Note: only occurences
with C067-COMP-UCR > spaces should be included in sort.

Component Field C067-COMP-UCR (n1, n2)

UCR (This field should be protected)

Component TR Field C067-COMP-TR (n1, n2)

(This field should be protected)

Name 1 Field C067-NAME-1 (n1, n2)

(This field should be protected)

Name 2 Field C067-NAME-2 (n1, n2)

(This field should be protected)

Paid This Time Field C067-PTT-AMT (n1, n2)

(This field should be protected)

Outstanding Field C067-OUTST-AMT (n1, n2)

Amount (This field should be protected)

David Willcocks 518 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source

After the last Component Claim, the TOTAL line should be displayed. The Total Field
should be alligned underneath the associated component field.

Total Paid This Field C067-TOTAL-PTT (n1)

Time (This field should be protected)

4.24.4. Process Description

The ‘Conclusion of Bulk’ screen is displayed to the user

once they have selected and processed all the Bulk
Components associated with this Bulk Settlement and
the details have been validated. The screen will list all
the components by currency. The Bulk may involve
settlement in up to three currencies.
However,individual components may not include
settlement in all these currencies. The screen will
therefore be displayed for each currency and the user
will be able to page through the currencies by pressing
‘NEXT CURRENCY’ or ‘PREV CURRENCY’ as
appropriate. Below is an example illustrating how a
Bulk Settlement may be structured and how this will be
reflected on this screen.

Bulk Header GBP Paid This Time = 1,000

Outstanding = 2,000

USD Paid This Time = 2,000

Outstanding = 3,000

CAD Paid This Time= 500

Outstanding = 1,500

Component 1 GBP Paid This Time= 500

Outstanding = 1,000

USD Paid This Time= 1,000

Outstanding = 1,500

Component 2 USD Paid This Time= 1,000

Outstanding = 1,500

David Willcocks 519 May 2002

Xchanging Ins-sure Services Ltd
CAD Paid This Time= 300
Outstanding = 1,000

Component 3 GBP Paid This Time= 500

Outstanding = 1,000

CAD Paid This Time= 200

Outstanding = 500

Details shown on the screen will be:-

GBP OSND1

PTT Outst.
Component 1 500 1,000
Component 3 500 1,000

TOTAL 1,000

On Pressing ‘NEXT CURRENCY’:-

USD OSND2

PTT
Outst.
Component 1 1,000
1,500
Component 2 1,000
1,500

On pressing ‘NEXT CURRENCY’ again:-

David Willcocks 520 May 2002

Xchanging Ins-sure Services Ltd
CAD OSND3

PTT
Outst.
Component 2 300 1,000
Component 3 200 500

TOTAL 500

Note: the total line does not include the Outstanding Amount Total
because every Bulk Settlement does not necessarily include all the
components. Therefore, the outstanding amount for some components
may be missing – giving the technician misleading figures.

David Willcocks 521 May 2002

Xchanging Ins-sure Services Ltd
Fig 4.24.4.1. Field/Command Processing for ‘Conclusion of Bulk
Settlement’ Screen

Field / Attributes Data Type

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

(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

David Willcocks 522 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

(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:-

David Willcocks 523 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

User should select one of these options.

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

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

David Willcocks 524 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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’

(iii) On selection of the ‘Group Enquiry’

(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

David Willcocks 525 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 claim has
been added to. (see Appendix G)

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

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

David Willcocks 526 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(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

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

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

David Willcocks 527 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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

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,

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

David Willcocks 528 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
– 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).

‘Create Bulk/CCS Correction’ selected

This is a special correction facility for use only by

David Willcocks 529 May 2002

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

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

David Willcocks 530 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.

(iv) If no errors returned from LZ06, call

LY01 using Commarea C067 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.

(v) Rebuild the current screen using the

data returned in the C067 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 531 May 2002

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

(i) If C067-SCREEN-MODE = ‘U’ (Update), 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.

(ii) If no errors returned from LY46 or C067-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.

(iii) 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)

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric

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’

David Willcocks 532 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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’
Current The Broker Code that identifies the broking house Display Alphanumeric
Bkr that submitted that initiated the current claim Only Field (4 Chars)
Orig. transaction.
Broker
Original The Original (or Estimate) Currency that relates to Display Alphanumeric
Currency the details shown on the screen. Up to three Only Field (3 Chars)
currencies may exist on the bulk header – the user
may page through these by pressing the ‘Next
Currency’ or ‘Prev. Currency’ buttone (see below).
OSND The Original Signing Number and Date for the Display Alphanumeric
Original Currency that is being displayed. Only Field (15 Chars)
Componen The Unique Claim Reference or Xchanging Claim Display Alphanumeric
t UCR Reference (depending on whether the component Only Field (17 Chars)
claim was created by the broker on the ‘CLASS for
Lloyds’ system or whether it was created internally
by Xchanging technicians). This reference identifies
the component claim.
Componen The Transaction Reference. This reference identifies Display Alphanumeric
t TR the transaction on the component claim that belongs Only Field (17 Chars)
to this Buk Settlement.
Name 1 The first ‘Name Field’ that applies to the component Display Alphanumeric
claim. This can be set to either the Insured or Only Field (50 Chars)
Reinsured, depending on the type of claim.
Name 2 The first ‘Name Field’ that applies to the component Display Alphanumeric
claim. This can be set to either the Cover Holder, Only Field (50 Chars)
Original Insured or Vessel, depending on the type of
claim.
Paid This The amount to be paid (for the Original Currency Display Numeric
Time above) on this particular Bulk Component Only Field -(13)9.99
transaction.

Outstandi The amount still outstanding (in the Original Display Numeric
ng Currency above) on this particular Bulk Component Only Field -(13)9.99

David Willcocks 533 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Amount claim.
Total Paid The total amount to be paid (in the Original Display Numeric
This Time Currency above) on this Buk Settlement. I.e. across Only Field -(13)9.99
all Bulk Components.

D. Commands - (Main Screen).

Proceed (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).

Next Currency If the occurrence in the C067-CURRENCY- Command

DETAILS table that is currently shown on the
screen is equal to the C067-CURRENCY-COUNT
field returned in the C067 Commarea, then the last
currency is being dispayed. Display the error E130
(see Appendix E) in the Error Window (see
Appendix B).

If the occurrence being displayed is less than the

C067-CURRENCY-COUNT, increment the
occurrence by 1 and rebuild the screen using the
details held in the C067-CURRENCY-DETAILS
table for the next occurrence.
Prev. Currency If the occurrence in the C067-CURRENCY- Command
DETAILS table that is currently shown on the
screen is equal to 1, then the first currency is being
dispayed. Display the error E131 (see Appendix E)
in the Error Window (see Appendix B).

If the occurrence being displayed is greater than 1,

subtract 1 from the ccurrence and rebuild the screen
using the details held in the C067-CURRENCY-
DETAILS table for the previous occurrence.
Cancel If cancel pressed in this screen, rather than Proceed, Command
this implies that the technician is not happy with the
information displayed and wants to change the

David Willcocks 534 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
components of the bulk settlement. The technician
should therefore be returned to the ‘Bulk
Component Selection’ screen (see Section 4.23)

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

(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

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 535 May 2002

Xchanging Ins-sure Services Ltd
4.25. Transaction History Screen

4.25.1. Screen Layout

Below is a ‘mock-up’ of the ‘Transaction History Screen’ Screen.

4.25.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
LY69 Build Transaction History Screen
LY71 Set up Group Session Record

David Willcocks 536 May 2002

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

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

Field Type Source

A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C069 (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 C069-XCR

(This field should be protected)
UCR Field C069-UCR
(This field should be protected)
Current Bkr Field C069-ORIG-BKR
Orig. Broker (This field should be protected)
Peer Review Field C069-PEER-REV-IND
(This field should be protected)
Currency Details

Original Field C069-ORIG-CURR (n1)

Currency (This field should be protected)

OSND Field C069-ORIG-REF (n1)

(This field should be protected)

Each Occurrence in the C069-TRANSACTION-DETS table (with C069-TR >

spaces) should be displayed on the screen in tabular format.

C069-UCR-TR-SYS-REF is returned in the C069-TRANSACTION-

DETS table, but is not shown on the screen. This field is required
for later use and the value associated with each line on the
screen should be stored.

David Willcocks 537 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Sequence Field C069-SEQ-NO (n1, n2)
Number (n) (This field should be protected)

TR (n) Field C069-TR (n1, n2)

(This field should be protected)

Paid Amount Field C069-PTT-AMT (n1, n2)

(n) (This field should be protected)

Note:- If C069-CURR-PRESENT (n1, n2) = ‘N’,

this field should be set to spaces, rather than
zeroes – to signify that the currency was not
present on the claim at all at the time the
transaction was loaded.

Outstanding Field C069-OUTST-AMT (n1, n2)

Amount (n) (This field should be protected)

Note:- If C069-CURR-PRESENT (n1, n2) = ‘N’,

this field should be set to spaces, rather than
zeroes – to signify that the currency was not
present on the claim at all at the time the
transaction was loaded.

Outstanding Field C069-OUTST-QUAL (n1, n2)

Amount (This field should be protected)
Qualifier (n)
Transaction Field C069-TRANS-DATE (n1, n2)
Date (n) (This field should be protected)
Transaction Field C069-TRANS-STATUS (n1, n2)
Status (n) (This field should be protected)
Total Paid Field C069-TOTAL-PAID (n1)
Amount (This field should be protected)

B. COMMANDS
Transaction Comman The technician may select a particular
Reference d transaction for detailed enquiry by
‘clicking’ on the Transaction Reference.

This field should not be underlined and

‘available to be clicked on’ if C069-TR-
SELECT-ATTR = ‘P’.

PREV Comman This command should be protected if

d C069-PREV-ATTR = ‘P’, or preferably
not shown at all
NEXT Comman This command should be protected if

David Willcocks 538 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
d C069-NEXT-ATTR = ‘P’, or preferably
not shown at all.

4.25.4. Process Description

This screen can be invoked by the user when they are

viewing a claim transaction. It will be displayed when
the user ‘clicks’ on the ‘History’ option at the top of the
scree and they are currently viewing one of the
Transaction level Data-Entry screens. (If viewing a
Breakdown level screen, they will be shown the
‘movement Summary’).

This screen shows a list of all transaction on the current CLASS claim,
in reverse chronological order. It also displays the Paid Amount for
each transaction, together with the Outstanding Amount on the claim at
the time the transaction was raised. Because there may be up to three
currencies on a claim, the user will have the ability to page through the
currencies and view the Paid and Outstanding amounts in each
currency. On the rare occasions when there are more than 125
transactions on a particular claim, the user will be able to display
earlier transactions by pressing the ‘Prev’ button.

By ‘clicking’ on the Transaction Reference for a particular claim

transaction, the user will be able to view details of each of the
transactions on the screen.

This screen will be the route by which the user will create Contra
Corrections or Rate of Exchange Adjustments. They will select the
transaction against which they wish to raise the correction or
adjustment and use the ‘Functions’ option at the top of the screen once
the transaction has been selected.

David Willcocks 539 May 2002

Xchanging Ins-sure Services Ltd
Fig 4.25.4.1. Field/Command Processing for ‘Transaction History’
Screen

Field / Attributes Data Type

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

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

David Willcocks 540 May 2002

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

(ii) On selection of the ‘Maintain Group’

(iii) On selection of the ‘Group Enquiry’

C. Fields (Main Screen)

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric

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’

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’

Current The Broker Code that identifies the broking house Display Alphanumeric
Bkr that submitted that initiated the current claim Only Field (4 Chars)
Orig. transaction.
Broker
Peer This field indicates whether or not the current claim Display Alphanumeric
Review is subject to peer review or not Only Field (1 Char)
Original The Original (or Estimate) Currency that relates to Display Alphanumeric
Currency the details shown on the screen. Up to three Only Field (3 Chars)

David Willcocks 541 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
currencies may exist on the bulk header – the user
may page through these by pressing the ‘Next
Currency’ or ‘Prev. Currency’ buttone (see below).
OSND The Original Signing Number and Date for the Display Alphanumeric
Original Currency that is being displayed. Only Field (15 Chars)
Sequence This is a sequential numebr that identifies the Display Alphanumeric
Number position of a particular claim transaction in the Only Field (17 Chars)
lifecycle of the claim.
TR The Transaction Reference is unique within the Display Alphanumeric
claim. It is either the brokers reference for the claim Only Field (17 Chars)
transaction (if the transaction was created by
thebroker on the ‘CLASS for Lloyds’ system) or it
is an internally generated reference (for claims
created by Xchanging technicians).

It is a 17 character field which should be displayed

in the following format:-
‘X / XXXX / XXXXXXXXXXXX’

The user will ‘click’ on this field to select the

transaction and enquire on it in more detail (see
below).

Paid The amount to that was paid (for the Original Display Numeric
Amount Currency above) on this particular claim Only Field -(13)9.99
transaction.

Outstandi The amount outstanding (in the Original Currency Display Numeric
ng above) on the claim at the time this particular claim Only Field -(13)9.99
Amount transaction was raised.
Oustandin The Outstanding Amount Qualifier used for this Display Alphanumeric
g Amount Original Currency at the time this particular claim Only Field (1 Char)
Qualifier transaction was raised.
Transactio This is the date that the claim transaction was Display Date
n Date raised. This will be set to the date tha the claim Only Field (DD/MM/CCYY)
transaction was released for advising.
Transactio This is field indicates the current status of each Display Alphanumeric
n Status claim transaction. This will be set to the ‘short Only Field (8 Chars)
description’ of transaction status detailed in
Appendix K.1.

For ‘CLASS for Lloyds’, there are a number of

different transaction status’s that may apply. For
internally created claims, however, the main status’s
are :-
‘IN-PROG’ – The claim transaction is ‘in Progress’.
The transaction has been created, but has not yet

David Willcocks 542 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
been released for advising.
‘RELEASED’ – The claim transaction has been
released for advising
‘COMPLETE’ The claim transaction has been fully
advised on the USM and SCM.

Total This is the total amount paid (in the Original Display Numeric
Amount Currency, above) on the claim. It is an accumulation Only Field -(13)9.99
Paid of the Paid Amounts for each transaction

D. Commands - (Main Screen).

Transaction If the technician ‘clicks’ on the Transaction Command
reference Reference field, they will be taken into the
‘Claim Creation’ screen for selected
transaction.

The Transaction Reference that the user was in

when they initiated this History Enquiry will
not be underlined and ‘available to be clicked
on’. Otherwise the user would have two update
sessions on the same transaction running
simultaneously.

(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
= C069-UCR-TR-SYS-REF (n1, n2)
C010-CURR-NO = zero
C010-SDN-NO = zero
C010-STAT-SPLIT-NO = zero
C010-BREAKDOWN-NO = zero
C010-RETURN-SCREEN = ‘SCR025’
(Transaction History Screen)

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 by LY10, the user

should be navigated to the ‘Claim Creation’

David Willcocks 543 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
screen (see Section 4.9)

Next Currency If the occurrence in the C069-CURRENCY- Command

DETAILS table that is currently shown on the
screen is equal to the C069-CURRENCY-COUNT
field returned in the C069 Commarea, then the last
currency is being dispayed. Display the error E130
(see Appendix E) in the Error Window (see
Appendix B).

If the occurrence being displayed is less than the

C069-CURRENCY-COUNT, increment the
occurrence by 1 and rebuild the screen using the
details held in the C069-CURRENCY-DETAILS
table for the next occurrence.
Prev. Currency If the occurrence in the C069-CURRENCY- Command
DETAILS table that is currently shown on the
screen is equal to 1, then the first currency is being
dispayed. Display the error E131 (see Appendix E)
in the Error Window (see Appendix B).

If the occurrence being displayed is greater than 1,

subtract 1 from the ccurrence and rebuild the screen
using the details held in the C069-CURRENCY-
DETAILS table for the previous occurrence.
‘< PREV’ If the user presses this button, the previous (up to) Command
125 transactions will be displayed.

(i) call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA
C069 (see Appendix D), passing the
key of the last transaction on the screen
in C069-START-KEY (as the
transactions are displayed in reverse
chronological order) and setting C069-
PREV-PRESSED to ‘Y’. 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) If no errors returned from LY69, rebuil

the screen as described in Section
4.25.3.

David Willcocks 544 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
‘NEXT >’ If the user presses this button, the next 125 Command
transactions will be displayed.

(i) call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA
C069 (see Appendix D), passing the
key of the first movement on the screen
in C069-START-KEY (as the
movements are displayed in reverse
chronological order) and setting C069-
NEXT-PRESSED to ‘Y’. 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) If no errors returned from LY69, rebuil

the screen as described in Section
4.25.3.

Cancel If the technician presses the ‘Cancel’ button, the Command

Transaction History window should be closed,
leaving them in whichever screen they initiated the
History function from.

(i) If C011-NEXT-PROGRAM is set to

‘NONE’, Call CICS transaction LY01
(see Appendix C.1) – using
COMMAREA C004 (see Appendix D)
to log-off the sub-session and delete the
Session Record.

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 are returned, the current

window should be closed.

David Willcocks 545 May 2002

Xchanging Ins-sure Services Ltd
4.26. Movement History Screen

4.26.1. Screen Layout

Below is a ‘mock-up’ of the ‘Movement History Screen’ Screen.

4.26.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
LY70 Build Movement History Screen
LY71 Set up Group Session Record

David Willcocks 546 May 2002

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

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

Field Type Source

A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C070 (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 C070-XCR

(This field should be protected)
UCR Field C070-UCR
(This field should be protected)
OSND Field C070-ORIG-REF
(This field should be protected)
Current Bkr Field C070-ORIG-BKR
Orig. Broker (This field should be protected)
Signed Tick-Box Set to ‘TRUE’ if C070-SIGNED-IND
= ‘Y’
(This field should be protected)
Orig Currency Field C070-ORIG-CURR
(This field should be protected)
COR Field C070-COR
(This fied should be protected)
Peer Review Field C069-PEER-REV-IND
(This field should be protected)
Movement Details

All occurences returned in the C070-MOVEMENT-DETS table (where C070-MOVE-REF

> spaces) should be displayed in tabular format on the screen.

Note:- The System key fields identifying a particular movement are also returned in the
C070-MOVEMENT-DETS table. These should be stored for future use.

Movement Field C070-MOVE-REF

Reference (n) (This field should be protected)
Movement Field C070-MOVE-SEQ-NO
Sequence (This field should be protected)
Number (n)
Paid Amount Field C070-PTT-AMT

David Willcocks 547 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
(n) (This field should be protected)
Outstanding Field C070-OUTST-AMT
Amount (n) (This field should be protected)

Outstanding Field C070-OUTST-QUAL

Amount (This field should be protected)
Qualifier (n)
Transaction Field C070-TRANS-DATE
Date (n) (This field should be protected)
Take Down Field C070-TAKE-DOWN-NO
Number (n) (This field should be protected)
User Id. (n) Field C070-USER-ID
(This field should be protected)
Movement Field C070-MOVE-STATUS
Status (n) (This field should be protected)
Total Paid Field C070-TOTAL-PAID
(This field should be protected)

B. COMMANDS
Movement Comman The technician may select a particular
Reference d movement for detailed enquiry by
‘clicking’ on the Movement Reference.

This field should not be underlined and

‘available to be clicked on’ if C070-
MOVE-SELECT-ATTR = ‘P’.

< PREV Comman This command should be protected if

d C070-PREV-ATTR = ‘P’ (or preferably,
not shown at all)
NEXT > Comman This command should be protected if
d C070-NEXT-ATTR = ‘P’ (or preferably
not shown at all)

4.26.4. Process Description

This screen can be invoked by the user when they are

viewing a claim breakdown. It will be displayed when
the user ‘clicks’ on the ‘History’ option at the top of the
screen and they are currently viewing one of the
Breakdown level Data-Entry screens. (If viewing a

David Willcocks 548 May 2002

Xchanging Ins-sure Services Ltd
Transaction level screen, they will be shown the
‘Transaction Summary’).

This screen shows a list of all movements on the current breakdown (or
Claims Office Reference). It also displays the Paid Amount for each
movement, together with the Outstanding Amount on the breakdown at
the time the movement was raised. If more than 300 movements are
present, the user will be able to use ‘Previous’ and ‘Next’ buttons to
browse through the movements. Movements will be returned in reverse
chronological order.

By ‘clicking’ on the Movement Reference, the user will be able to view

details of the movement in question.

Fig 4.26.4.1. Field/Command Processing for ‘Movement History’

Screen

Field / Attributes Data Type

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

David Willcocks 549 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
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’

(iii) On selection of the ‘Group Enquiry’

C. Fields (Main Screen)

XCR The Xchanging Claim Reference. This is assigned Display Alphanumeric

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’

David Willcocks 550 May 2002

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

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 The Original Signing Number and Date associated Display Alphanumeric
with the claim breakdown for which the details are Only Field (15 Chars)
being displayed.
Current The Broker Code that identifies the broking house Display Alphanumeric
Bkr that submitted that initiated the current claim Only Field (4 Chars)
Orig. transaction.
Broker
Signed This Tick-Box indicates whether the current claim Display N/A
transaction has been signed or whether it has been Only Tick-
raised against an unclosed risk. Box
Orig The original (or Estimate) Currency that applies to Display Alphanumeric
Currency the claim breakdown. This is the currency in which Only Field (3 Chars)
the Paid and Outstanding amounts are expressed.
COR The Claims Office Reference that identifies this Display Alphanumeric
claim breakdown. Only Field (15 Chars)
Peer This field indicates whether or not the current claim Display Alphanumeric
Review is subject to peer review or not Only Field (1 Char)
Movement The reference associated with this particular Display Alphanumeric
Reference movement on the claim breakdown. This reference Only Field (6 Chars)
/Date is unique within Claims Office Reference.

The technician may select movements from the

screen by ‘clicking’ on this field. This will take
them to the ‘SCM Advice’ screen for the movement
in question (see below).

This field should be displayed in the following

format:-

XX / MMYY

Movement This is a sequential number that identifies the Display Numeric

Sequence position of a particular movement within the Only Field (3 digits)
Number lifecycle of the claim breakdown.
Paid The amount that was paid (in the Original Currency Display Numeric
Amount above) on this particular movement. Only Field -(13)9.99

Outstandi The amount outstanding (in the Original Currency Display Numeric
ng above) on the claim breakdown at the time this Only Field -(13)9.99
Amount particular movement was raised.

David Willcocks 551 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Outstandi The qualifier used on this claim breakdown at the Display Alphanumeric
ng time this particular movement was raised. Only Field (1 Char)
Amount
Qualifier
Transactio This is the date that the claim movement was Display Date
n Date processed. Only Field (DD/MM/CCYY)

Take The Taking Down Number and Date associated with Display Alphanumeric
Down this financial transaction. This field will only be Only Field (13 Chars)
Number present when the movement involved settlement.
User Id. The Examiner Id. of the system user who processed Display Alphanumeric
this movement. Only Field (3 Chars)
Movement This field indicates whether or not each movement Display Alphnumeric
Status has been advised to the Syndicates yet on the SCM. Only Field (9 Chars)
It will be set to either ‘ADVISED’ or
‘UNADVISED’.
Total Paid This is the total amount paid (in the Original Display Numeric
Currency, above) on the current breakdown (i.e. Only Field -(13)9.99
Claims Office Reference). It is an accumulation of
the Paid Amounts for each of the movements.

D. Commands - (Main Screen).

Movement If the technician ‘clicks’ on the Movement Command
Reference Reference field, they will be taken into the ‘SCM
(Select) Advice’ screen (or potentially the ‘Loss Reserves’
screen, depending on the type of claim) for the
selected movement.

The Movement that the user was in when they

initiated this History Enquiry will not be underlined
and ‘available to be clicked on’. Otherwise the user
would have two update sessions on the same
transaction running simultaneously.

(ii) 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
= C070-UCR-TR-SYS-REF (n)
C010-CURR-NO
= C070-CURR-NO (n)
C010-SDN-NO

David Willcocks 552 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
= C070-SDN-NO
C010-STAT-SPLIT-NO
= C070-STAT-SPLIT-NO
C010-BREAKDOWN-NO
= C070-BREAKDOWN-NO
C010-RETURN-SCREEN = ‘SCR026’
(Movement History Screen)

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 by LY10, 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)

(iii) If no errors returned from LY11, navigate

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

‘< PREV’ If the user presses this button, the previous (up to) Command
300 movements will be displayed.

(iii) call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA
C070 (see Appendix D), passing the
key of the last movement on the screen
in C070-START-KEY (as the
movements are displayed in reverse
chronological order) and setting C070-
PREV-PRESSED to ‘Y’. 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) If no errors returned from LY70, rebuil

the screen as described in Section

David Willcocks 553 May 2002

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

‘NEXT >’ If the user presses this button, the next 300 Command
movements will be displayed.

(iii) call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA
C070 (see Appendix D), passing the
key of the first movement on the screen
in C070-START-KEY (as the
movements are displayed in reverse
chronological order) and setting C070-
NEXT-PRESSED to ‘Y’. 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) If no errors returned from LY70, rebuil

the screen as described in Section
4.26.3.

Cancel If the technician presses the ‘Cancel’ button, the Command

Movement History window should be closed,
leaving them in whichever screen they initiated the
History function from.

David Willcocks 554 May 2002

Xchanging Ins-sure Services Ltd
4.27. Maintain Group Screen

4.27.1. Screen Layout

Below is a ‘mock-up’ of the ‘Maintain Group’ Screen.

4.27.2. CICS Transaction

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LY04 Log-off
LY71 Set up Group Session Record
LY72 Obtain Group Contents
LY73 Validate Group Details
LY74 Update Group Details

David Willcocks 555 May 2002

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

(i) All fields will be initialised to spaces on first entry to

this screen. On first entry only the ‘Agg Ref/Non-
Agg Ref’ field will be Unprotected. The ‘Add
OSND/UCR’ and ‘Update Group’ buttons should be
protected on first entry to the screen.

(ii) After the user has entered a Group Reference, the

fields will be derived as follows (Note:- All commands
will now be ‘Unprotected’):-

Field Type Source

A. Fields:-

A.1. When the screen is first built the Group Reference

field should be pre-populated with the data returned in the
C071 Commarea from the program that sets up the Group
Session Record – as follows:-

Agg Ref/Non- Field C071-GROUP-REF

Agg Ref (This field should be unprotected).

A.2. When the user presses ‘Find group’ button (see

Command section of Process Description), the fields
returned in the C072 Commarea will be mapped to the
screen as follows:-

Agg Ref/Non- Field C072-GROUP-REF

Agg Ref (When rebuilding the screen after
details returned from LY72, this
field should be protected).
Group Type Field C072-GROUP-TYPE
(This field should be protected)

Read through each non-space occurrence in the C072-GROUP-

CONTENTS table, and display the contents in tabular form:-

UCR/OSND (n) Field C072-UCR-OSND (n)

David Willcocks 556 May 2002

Xchanging Ins-sure Services Ltd
4.27.4. Process Description

This screen allows the user to maintain groups. On first

entry to the screen, the Group Reference field will be
unprotected. The user may enter a Group Reference for
maintenance purposes. The system will then obtain the
details for the group and display them on the screen.

If the group is an Aggregate group, the Group Type will

be set to ‘Aggregate’ and a list of the Original Signing
Numbers and Dates that belong to the group will be
displayed. If the group is a Non-Aggregate Group, the
Group Type will be set to ‘Non-Aggregate’ and a list of
the Unique Claim References that belong to the group
will be displayed.

The user will then be able to select items for deletion

from the group by ‘clicking’ on the ‘option Button’
alongside the item that they wish to delete. If the user
wishes to add an item to the group, they can press the
‘Add OSND/UCR’ button. This will cause a new
Unprotected field to be displayed at the bottom of the
list – enabling the user to key in a new OSND or UCR
(depending on the type of group). Once they have
inserted/deleted all the items they wish, the user can
press the ‘Update Group’ button to implement the
changes on the database.

If the user wishes to maintain a new group, they should

press the ‘CLEAR’ button – this will clear the screen
ready for a new Group Reference to be entered.

If the user presses ‘Cancel’ during the maintenance of a

group, any changes made to the group they are
maintaining (since they last pressed ‘Update Group’)
will be removed.

To exit the Group function, the user should simply close

the window.

David Willcocks 557 May 2002

Xchanging Ins-sure Services Ltd
Fig 4.27.4.1. Field/Command Processing for ‘Maintain Group’
Screen

Field / Attributes Data Type

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)
C. Fields (Main Screen)

If the user entered an Aggregate Group Reference,

then this field will contain Original Signing
Numbers and Date(s) (OSND).

If the user entered a Non-Aggregate Group

Reference, then this field will contain Unique Claim
Reference(s) (UCR).

All pre-existing items that belong to the group will

be protected.

David Willcocks 558 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
If the user opts to add items to the group then, for
new items, this field will be blank and unprotected.

D. Commands - (Main Screen).

Find Group This button will use the Group Reference on the Command
screen and obtain the details for that group. These
details are then displayed on the screen for the user
to add or remove items as required.

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C072
(see Appendix D). This will obtain the
details associated with the Group reference
entered by the technician on the screen.

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 by LY72, build the

screen as described in part (ii) of the
Field/Command derivation section (section
4.27.3)

Add If the user presses this button a new Unprotected Command

OSND/UCR field will be displayed at the bottom of the list –
enabling the user to key in a new OSND or UCR
(depending on the type of group).

Note:- If there are already 1200 OSND’s or UCR’s

on the screen, issue the error ‘E377’ in the Error
Screen (See Appendix B).
Update Group If the user presses this button, the details on the Command
screen will be validated and, assuming that all
details entered are valid, the group will be updated
according to the users instructions. I.e. any new
items will be added to the group and any items
flagged for deletion will be removed.

(i) Display the ‘Confirmation Window’ (see

Appendix Q). If the user presses ‘YES’ in
this window, continue with the processing
as detailed below. Otherwise, if they press
‘NO’, redisplay the Maintain Group screen
unchanged.

(ii) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C073

David Willcocks 559 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(see Appendix D). This will validate that
the details on the screen are not in error (i.e.
any new UCR’s or OSND’s are valid).

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 by LY73, call the CICS

transaction LY01 (see Appendix C.1) –
using COMMAREA C074 (see Appendix
D). This will update the group with the new
details – inserting any new items and
removing any that the user has flagged for
deletion.

On return, check the Program Status in the

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

(iv) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C072
(see Appendix D). This will re-obtain the
details associated with the Group reference
entered by the technician on the screen.

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 by LY72, build the

screen as described in part (ii) of the
Field/Command derivation section (section
4.27.3). Rebuilding the screen in his way
will ensure that any deleted lines are
removed.

Clear If the user presses this button, all details will be Command
removed from the screen. The Group Reference
field will be blanked out and unprotected again – as
it was when the user first entered the screen. This
will enable the user to key in a new Group
Reference and begin the process again. The ‘Add
OSND/UCR’ and ‘Update Group’ buttons should be
protected again.

Cancel If the technician presses the ‘Cancel’ button, the Command

Maintain Group window should be closed, leaving

David Willcocks 560 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
them in whichever screen they initiated the
Grouping function from.

(i) Call CICS transaction LY01 (see

Appendix C.1) – using COMMAREA
C004 (see Appendix D) to log-off the
sub-session and delete the Session
Record.

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 are returned, the current

browser session should be closed.

David Willcocks 561 May 2002

Xchanging Ins-sure Services Ltd
4.28. Group Enquiry Screen

4.28.1. Screen Layout

Below is a ‘mock-up’ of the ‘Group Enquiry’ Screen. Note, this screen

also acts as the ‘Add to Non-Aggregate Group’ screen. If the user has
selected ‘Add to Non-Aggregate group’ from the ‘Grouping menu and
enters a non-Aggregate group for enquiry – the ‘Add to Group’ button
will be enabled.

4.28.2. CICS Transaction

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LY04 Log-off
LY71 Set up Group Session Record
LY75 Build Group Enquiry Screen
LY76 Add UCR to Non-Aggregate Group
David Willcocks 562 May 2002
Xchanging Ins-sure Services Ltd
4.28.3. Field/Command Derivation

(i) All fields will be initialised to spaces on first entry to

this screen. On first entry only the ‘Agg Ref/Non-
Agg Ref’ field will be Unprotected. The only
Commands that should initially be available are
‘Cancel and ‘Find Claim’

(ii) After the user has entered a Group Reference, the

fields will be derived as follows:-

Field Type Source

A. Fields:-

A.1. When the screen is first built the Group Reference

field should be pre-populated with the data returned in the
C071 Commarea from the program that sets up the Group
Session Record – as follows:-

Agg Ref/Non- Field C071-GROUP-REF

Agg Ref (This field should be unprotected).

A.2. When the user presses ‘Find group’ button (see

Command section of Process Description), the fields
returned in the C075 Commarea will be mapped to the
screen as follows:-

Agg Ref/Non- Field C075-GROUP-REF

Agg Ref (This field should be unprotected).
Group Type Field C075-GROUP-TYPE
(This field should be protected)
Currency Details

When building the screen for the first time after user has pressed ‘Find Group’, use
the first occurrence in the Currency Details table (i.e. n1 = 1). If the user presses
the ‘NEXT CURRENCY’ button, the occurrence should be incremented accordingly
(i.e. n1 = 2, n1 = 3, etc.) – see later processing – with ‘PREV CURRENCY’
obviously having the reverse effect.

Original Field C075-ORIG-CURR (n1)

Currency (This field should be protected)
Total Paid Field C075-PAID-AMT-TOTAL (n1)

David Willcocks 563 May 2002

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

A.1. When the screen is first built the Group Reference

field should be pre-populated with the data returned in the
C071 Commarea from the program that sets up the Group
Session Record – as follows:-

Agg Ref/Non- Field C071-GROUP-REF

Agg Ref (This field should be unprotected).
Amount (This field should be protected)
Total Field C075-OUTST-AMT-TOTAL (n1)
Outstanding (This field should be protected)
Amount

Each Occurrence in the C069-GROUP-DETAILS table (with C075-UCR > spaces)

should be displayed on the screen in tabular format. (Varying n2 from 1 to 1200)

UCR (n1, n2) Field C075-UCR (n1, n2)

Paid Amount Field C075-PAID-AMT (n1, n2)
(n1, n2)
Outstanding Field C075-OUTST-AMT (n1, n2)
Amount (n1,
n2)

B. Commands

All Commands will now be unprotected with the exception of the ‘Add to Group’
button. The ‘Add to Group’ key will only be enabled in certain circumsatnces (see
below).

Add to Group Comman If C075-ADD-ATTR = ‘P’, this key

d should be protected or, preferably,
not displayed.

David Willcocks 564 May 2002

Xchanging Ins-sure Services Ltd
4.28.4. Process Description

This screen allows the user to enquire on Aggregate

and Non-Aggregate Groups. On first entry to the
screen, the Group Reference field will be unprotected.
The user may enter a Group Reference for enquiry
purposes. The system will then obtain the details for
the group and display them on the screen.

A list of the Unique Claim References that belong to the

group is displayed. For each UCR, the Total Paid and
Outstanding amounts will be displayed. These will be
accumulated and the total Paid and Outstanding
amounts for the group (by Currency) will be shown at
the bottom of the screen.

If the group is an Aggregate group, the Group Type will

be set to ‘Aggregate’ and the ‘Add to Group’ button will
not be available. If the group is a Non-Aggregate
Group, the Group Type will be set to ‘Non-Aggregate’
and, if the user originally selected the ‘Add to Non-
Aggregate Group’ option from the Grouping menu
(available only when in the Data Entry screens), the
‘Add to Group’ button will be enabled.

Because the UCR’s that belong to the group could

involve payment and/or outstanding amounts in a
number of currencies, the screen will show the details
for one currency at a time. The user can press ‘Next
Currency’ and ‘Prev. Currency’ to view details of all the
currencies that are involved in this group.

If the user presses the ‘Add to Group’ button, the UCR

that the user was processing, prior to initiating the
Group function, will be added to the group. This is only
available for Non-Aggregate Groups. On adding it to the
group, the details will be rebuilt and the revised totals
displayed. These totals will not include partially
complete claims – so if the user was in the process of
creating an initial advice – the details will not be
reflected on this screen until the claim has been
released.

To exit the Group function, the user should simply close

the window.

David Willcocks 565 May 2002

Xchanging Ins-sure Services Ltd
David Willcocks 566 May 2002
Xchanging Ins-sure Services Ltd
Fig 4.28.4.1. Field/Command Processing for ‘Group Enquiry’ Screen

Field / Attributes Data Type

On return from CICS, check the C004-PROG-

STATUS field:-

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

commarea in the Error Screen (see
Appendix B)

(iv) 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)
C. Fields (Main Screen)

Agg. Ref/ This is the reference that identifies the group that Mandatory Alphanumeric
Non-Agg. the user wishes to maintain. The type of group is Field (10 Chars)
Ref. held on the database.
Group This field tells the user what type of group they Display Alphanumeric
Type have selected – i.e. ‘Aggregate’ Group or ‘Non- Only Field (7 Chars)
Aggregate’ Group.
Original This is the Original (or Estimate) Currency that the Display Alphanumeric
Currency paid and outstanding amounts shown on the current Only Field (3 Chars)
screen are expressed in.
UCR This is the Unique Claim Reference or Xchanging Display Alphanumeric
Claim Reference that identifies the CLASS Claim. Only Field (17 Chars)
This field should be displayed in the following
format:-
‘X / XXXX / XXXXXXXXXXXX’
Paid This is the amount paid in total (in the Original Display Numeric
Amount Currency, above) on the claim listed Only Field -(13)9.99
Outstandi This is the amount that was quoted as Outstanding Display Numeric
ng (in the Original Currency, above) on the last Only Field -(13)9.99
Amount (released) transaction on the claim.
Total Paid This is the total amount paid, in the Original Display Numeric

David Willcocks 567 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Amount Currency (above), across all claims in the group. Only Field -(13)9.99
Total This is the total amount outstanding, in the Original Display Numeric
Outstandi Currency (above), across all claims in the group. Only Field -(13)9.99
ng
Amount

D. Commands - (Main Screen).

(vi) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C075
(see Appendix D). This will obtain the
details associated with the Group reference
entered by the technician on the screen.

On return, check the Program Status in the

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

(vii) If no errors returned by LY75, build the

screen as described in part (ii) of the
Field/Command derivation section (section
4.28.3)

Add to Group If the user presses this button, the UCR that the user Command
was processing, prior to initiating the Group
function, will be added to the group. This is only
available for Non-Aggregate Groups. On adding it
to the group, the details will be rebuilt and the
revised totals displayed.

Note:- If there are already 1200 UCR’s on the

screen, issue the error ‘E377’ in the Error Screen
(See Appendix B).

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C076
(see Appendix D). This will add the UCR,
that the user was processing prior to
initiating the group function, to the current
group.

On return, check the Program Status in the

Usual way, reporting errors if they exist in

David Willcocks 568 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
The Error Screen (see Appendix B).

(ii) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C075
(see Appendix D). This will obtain the
details associated with the Group reference
entered by the technician on the screen. The
Group Reference hasn’t changed – but the
details have.

On return, check the Program Status in the

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

Next Currency If the occurrence in the C075-CURRENCY- Command

DETAILS table that is currently shown on the
screen is equal to the C075-CURRENCY-COUNT
field returned in the C075 Commarea, then the last
currency is being dispayed. Display the error E133
(see Appendix E) in the Error Window (see
Appendix B).

If the occurrence being displayed is less than the

C075-CURRENCY-COUNT, increment the
occurrence by 1 and rebuild the screen using the
details held in the C075-CURRENCY-DETAILS
table for the next occurrence.
Prev. Currency If the occurrence in the C075-CURRENCY- Command
DETAILS table that is currently shown on the
screen is equal to 1, then the first currency is being
dispayed. Display the error E134 (see Appendix E)
in the Error Window (see Appendix B).

If the occurrence being displayed is greater than 1,

subtract 1 from the ccurrence and rebuild the screen
using the details held in the C075-CURRENCY-
DETAILS table for the previous occurrence.
Cancel If the technician presses the ‘Cancel’ button, the Command
Group Enquiry window should be closed, leaving
them in whichever screen they initiated the
Grouping function from.

(i) Call CICS transaction LY01 (see

Appendix C.1) – using COMMAREA
C004 (see Appendix D) to log-off the
sub-session and delete the Session

David Willcocks 569 May 2002

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

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 are returned, the current

browser session should be closed.

David Willcocks 570 May 2002

Xchanging Ins-sure Services Ltd
4.29. Rate of Exchange Adjustment window

4.29.1. Screen Layout

Below is the ‘Rate of Exchange Adjustment’ window.

4.29.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
LY77 Build Rate of Exchange Adjustment
Window
LY78 Create Rate of Exchange Adjustment

David Willcocks 571 May 2002

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

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

Field Type Source

A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C077 (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).

Original Field C077-ORIG-CURR (n)

Currency (n) (This field should be protected)
Paid Amount Field C077-PAID-AMT (n)
(n) (This field should be protected)
Settlement Field C077-SETT-CURR (n)
Currency (n) (This field should be protected)
Original Field C077-ORIG-RATE-EXCH (n)
Exchange Rate (This field should be protected)
(n)
Original Field C077-ORIG-SETT-AMT (n)
Settlement (This field should be protected)
Amount (n)
Revised Field C077-REV-RATE-EXCH (n)
Exchange Rate (If C077-REV-ROE-ATTR = ‘P’, this
(n) field should be protected.
Otherwise, it should be
unprotected)
Revised Field C077-REV-SETT-AMT (n)
Settlement (If C077-REV-AMT-ATTR = ‘P’, this
Amount (n) field should be protected.
Otherwise, it should be
unprotected)

4.29.4. Process Description

In order to bring up this window, the technician must be enquiring on

the claim that they wish to adjust. When the technician is enquiring on
a claim, the ‘Rate of Exchange Adjustment’ option will appear in the
David Willcocks 572 May 2002
Xchanging Ins-sure Services Ltd
‘Functions’ menu at the top of the screen. Providing the claim that the
user is enquiring on is suitable to be adjusted, this window is
displayed.

The ‘Rate of Exchange Adjustment’ window lists up to three currencies

(depending on how many are present on the claim). For each currency,
the original details are displayed. The user is then able to enter a
revised exchange rate and settlement amount for any currencies that
involved settlement on the original transaction. The revised Rate of
Exchange and Settlement Amount will be protected for any currencies
that were originally for advising purposes only.

Fig 4.29.4.1. Field/Command Processing for ‘Rate of Exchange

Adjustment’ Window

Field / Attributes Data Type

Description
Command
A. Fields (Main Screen)

Original The Original (or Estimate) currency in which the Display Alphanumeric
Currency Paid Amount is expressed. Only Field (3 Chars)
(n)
Paid The 100% Paid Amount on the claim transaction to Display Numeric
Amount be adjusted. Only Field -(13)9.99
(n)
Format:- --,---,---,---,--9

Settlemen The Settlement Currency in which the claim was Display Numeric
t settled. Only Field -(13)9.99
Currency
(n)
Original The Original Exchange Rate that was applied to the Display Numeric
Exchange 100% Paid Amount to arrive at the 100% Settlement Only Field Z(4)9.9(7)
Rate (n) Amount.

Format:- ZZ,ZZ9.9999999

Original The 100% Settlement Amount on the claim Display Numeric

Settlemen transaction to be adjusted. Only Field -(13)9.99
t Amount
(n) Format:- --,---,---,---,--9

Revised The new Exchange Rate to be applied to the 100% Optional Numeric
Exchange Paid Amount. Field Z(4)9.9(7)
Rate (n)
At least one Rivised Exchange Rate must be

David Willcocks 573 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
entered. If none have been entered, display the error
E139 (see Appendix E) in the Error Window (see
Appendix B).

If entered and it is the same as the Original

Exchange Rate, display the error E140 (see
Appendix E) in the Error Window (see Appendix
B).

Format:- ZZ,ZZ9.9999999

Revised The Revised 100% Settlement Amount. Optional Numeric

Settlemen Field -(13)9.99
t Amount This amount is entered for control purposes.
(n)
It must be entered if a Revised Exchange Rate has
been entered. If not, display the error E136 (see
Appendix E) in the Error Window (see Appendix
B).

It must not be entered if the associated Revised

Exchange Rate has been left blank. If it is, display
the error E137 (see Appendix E) in the Error
Window (see Appendix B).

It is validated as being equal to the 100% Paid

Amount divided by the Revised Exchange Rate
(within a tolerance – see Appendix J). If not within
the tolerance, display the error E135 (see Appendix
E) in the Error Window (see Appendix B) and
highlight the amount in red.

Format:- --,---,---,---,--9

D. Commands - (Main Screen).

OK When the user presses the ‘OK’ button, the system Command
will create the ‘Rate of Exchange Adjustment’
transaction and then navigate the user to the
‘Settlement Summary’ so that they can review the
details and release it for advising.

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C078
(see Appendix D). This will create the Rate
of Exchange Adjustment transaction based
on the details of the transaction to be
adjusted – and the outstanding position on

David Willcocks 574 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
the most recent 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) Navigate the user to the Settlement

Summary (Section 4.22)

Cancel When the user presses the ‘Cancel’ button, the Command
window should be closed, leaving the user in the
screen they were in prior to initiating the Movement
History screen.

(ii) If C011-NEXT-PROGRAM is set to

‘NONE’, Call CICS transaction LY01
(see Appendix C.1) – using
COMMAREA C004 (see Appendix D)
to log-off the sub-session and delete the
Session Record.

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 are returned, the current

window should be closed.

David Willcocks 575 May 2002

Xchanging Ins-sure Services Ltd
4.30. Contra Correction window

4.30.1. Screen Layout

Below is an illustration of what the ‘Contra Correction’

window should look like.

Contra Correction

Reduce Outstanding Amount to Zero ? 

Are you sure you want to release this

Contra Correction ?

Release Cancel

4.30.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LY79 Create Contra Correction

4.30.3. Field/Command Derivation

The ‘Reduce Outstanding Amount to Zero ?’ tick-box should be

initialised to ‘FALSE’ (i.e. no tick).

4.30.4. Process Description

In order to bring up this window, the technician must be enquiring on

the claim that they wish to contra. When the technician is enquiring on
a claim, the ‘Contra Correction’ option will appear in the ‘Functions’
menu at the top of the screen. Providing the claim that the user is
enquiring on is suitable to be corrected, this window is displayed.

David Willcocks 576 May 2002

Xchanging Ins-sure Services Ltd
The user is able to opt to reduce the Outstanding Amount to zero. This
is used where the contra is being raised in order to reduce the Incurred
Amount to zero. This is necessary if the technician wishes to change
any of the key fields on the claim. Allowing the user the option of
reducing the outstanding amount to zero at this point will enable the
incurred to be reduced to zero – thus removing the need for the
technician to raise a separate transaction to do this.

If this option is not ticked the Outstanding Amount on the most recent
transaction will be adjusted by the amount being Contra’d.

Fig 4.30.4.1. Field/Command Processing for ‘Contra Correction’

Window

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

Reduce This field allows the technician to optionally reduce Optional N/A
Outstandi the outstanding amount on the claim to zero at the Tick-Box
ng same time as refunding the earlier transaction.

This field is optional and is initialised to ‘False’ (i.e.

no tick).

B. Commands - (Main Screen).

OK When the user presses the ‘OK’ button, the system Command
will create the ‘Contra Correction’ transaction and
then navigate the user to the ‘Settlement Summary’
so that they can review the details and release it for
advising.

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C079
(see Appendix D). This will create the
Contra Correction transaction based on the
details of the transaction to be corrected –
reducing the outstanding position (as
quoted on the most recent transaction) by
the refunded amount – unless the user has
ticked the ‘Reduce Outstanding to Zero’
box.

On return, check the Program Status in the

Usual way, reporting errors if they exist in

David Willcocks 577 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
The Error Screen (see Appendix B).

(ii) Navigate the user to the Settlement

Summary screen (Section 4.22)

Cancel When the user presses the ‘Cancel’ button, the Command
window should be closed.

David Willcocks 578 May 2002

Xchanging Ins-sure Services Ltd
4.31. EURO Conversion Details Screen

4.31.1. Screen Layout

Below is a ‘mock-up’ of the ‘EURO Conversion Details’

Screen.

4.31.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LY80 Build EURO Conversion Details Screen

David Willcocks 579 May 2002

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

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

Field Type Source

A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C080 (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:- All fields on this screen should be protected.

Original NCU Field C080-ORIG-NCU-CURR

Currency
Original NCU Field C080-ORIG-CURR-NAME
Currency Name
PTD Loss in Field C080-PTD-LOSS-NCU
NCU (prior to
conversion)
PTD Expense in Field C080-PTD-EXP-NCU
NCU (prior to
conversion)
PTD Fees in Field C080-PTD-FEE-NCU
NCU (prior to
conversion)
PTD VAT in Field C080-PTD-VAT-NCU
NCU
(prior to
conversion)
PTD Total in Field C080-PTD-TOTAL-NCU
NCU
(Prior to
conversion)
Incurred in Field C080-INCURRED-NCU
NCU (prior to
conversion)
Highest Field C080-HIGH-EST-NCU
Estimate in
NCU (prior to
conversion)

David Willcocks 580 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Rate of Field C080-RATE-EXCH
Exchange
between NCU
and EURO
PTD Loss in Field C080-PTD-LOSS-EAC
EURO (as at
conversion)
PTD Expense in Field C080-PTD-EXP-EAC
EURO (as at
conversion)
PTD Fees in Field C080-PTD-FEE-EAC
EURO (as at
conversion)
PTD VAT in Field C080-PTD-VAT-EAC
EURO (as at
conversion)
PTD Total in Field C080-PTD-TOTAL-EAC
EURO (as at
conversion)
Incurred in Field C080-INCURRED-EAC
EURO (as at
conversion)
Highest Field C080-HIGH-EST-EAC
Estimate in
EURO (as at
conversion)
Current Field C080-MOVE-REF
Movement
PTD Loss in Field C080-PTD-LOSS-EPC
EURO (post-
conversion)
PTD Expense in Field C080-PTD-EXP-EPC
EURO (post-
conversion)
PTD Fees in Field C080-PTD-FEE-EPC
EURO (post-
conversion)
PTD VAT in Field C080-PTD-VAT-EPC
EURO (post-
conversion)
PTD Total in Field C080-PTD-TOTAL-EPC
EURO (post-
conversion)

David Willcocks 581 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Incurred in Field C080-INCURRED-EPC
EURO (post-
conversion)
Highest Field C080-HIGH-EST-EPC
Estimate in
EURO (post-
conversion)
PTD Loss in Field C080-PTD-LOSS-ETOT
EURO (total
combined)
PTD Expense in Field C080-PTD-EXP-ETOT
EURO (total
combined)
PTD Fees in Field C080-PTD-FEE-ETOT
EURO (total
combined)
PTD VAT in Field C080-PTD-VAT-ETOT
EURO (total
combined)
PTD Total in Field C080-PTD-TOTAL-ETOT
EURO (total
combined)
Incurred in Field C080-INCURRED-ETOT
EURO (total
combined)
Highest Field C080-HIGH-EST-ETOT
Estimate in
EURO (total
combined)

4.31.4. Process Description

The ‘EURO Conversion Details’ screen is only available for

breakdowns that were originally expressed in a redundant NCU
Currency and have been converted to EURO. It is a display only
window that is presented to the user when they press the ‘EURO Conv.
Details’ button in the ‘SCM Advice’ screen. This is a separate window
that ‘overlays’ the ‘SCM Advice’ screen and will simply be closed
down (by pressing the ‘Close’ button) once the user has finished
enquiring on the conversion details. (Hence it has no navigation bar to
the left of the screen or functions at the top)

David Willcocks 582 May 2002

Xchanging Ins-sure Services Ltd
After conversion the Previously Paid amounts reflect only the amount
paid since in conversion in EURO. As a result, this screen is required
in order to allow the technician to enquire on the total amount settled
on this claim both prior to and after conversion.

Fig 4.31.4.1. Field/Command Processing for ‘EURO Conversion

Details’ Screen

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

Original The Original NCU Currency that applied to this Display Alphanumeric
NCU claim prior to the introduction of the EURO Only Field (3 Chars)
Currency
Original The full name of the original NCU currency that Display Alphanumeric
NCU applied to this claim prior to the introduction of the Only Field (20 Chars)
Currency EURO.
Name
PTD Loss This is the amount paid (in relation to the Loss Display Numeric
in NCU itself) in the original NCU currency on this claim Only Field -(13)9.99
(prior to breakdown - up to EURO conversion.
conversion
)
PTD This is the amount paid (in relation to Expenses) in Display Numeric
Expense the original NCU currency on this claim breakdown Only Field -(13)9.99
in NCU - up to EURO conversion.
(prior to
conversion
)
PTD Fees This is the amount paid (in relation to Fees) in the Display Numeric
in NCU original NCU currency on this claim breakdown - Only Field -(13)9.99
(prior to up to EURO conversion.
conversion
)
PTD VAT This is the amount paid (in relation to VAT) in the Display Numeric
in NCU original NCU currency on this claim breakdown - Only Field -(13)9.99
(prior to up to EURO conversion.
conversion
)
PTD Total This is the total amount paid in the original NCU Display Numeric
in NCU currency on this claim breakdown - up to EURO Only Field -(13)9.99
(Prior to conversion.
conversion

David Willcocks 583 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
)
Incurred This is the Incurred amount (i.e. Paid To Date + Display Numeric
in NCU Outstanding) in the original NCU currency on this Only Field -(13)9.99
(prior to claim breakdown – immediately prior to EURO
conversion Conversion.
)
Highest This is the Highest Estimate on this claim Display Numeric
Estimate breakdown – up to EURO Conversion – expressed Only Field -(13)9.99
in NCU in the original NCU currency.
(prior to
conversion
)
Rate of The fixed Rate of Exchange between the redundant Display Numeric
Exchange NCU currency and the EURO. Only Field Z(4)9.9(7)
between
NCU and
EURO
PTD Loss This is the amount paid (in relation to the Loss Display Numeric
in EURO itself) on this claim breakdown - up until EURO Only Field -(13)9.99
(as at conversion – converted into EURO.
conversion
)
PTD This is the amount paid (in relation to Expenses) on Display Numeric
Expense this claim breakdown - up until EURO conversion – Only Field -(13)9.99
in EURO converted into EURO.
(as at
conversion
)
PTD Fees This is the amount paid (in relation to Fees) on this Display Numeric
in EURO claim breakdown - up until EURO conversion – Only Field -(13)9.99
(as at converted into EURO.
conversion
)
PTD VAT This is the amount paid (in relation to VAT) on this Display Numeric
in EURO claim breakdown - up until EURO conversion – Only Field -(13)9.99
(as at converted into EURO.
conversion
)
PTD Total This is the total amount paid on this claim Display Numeric
in EURO breakdown - up until EURO conversion – converted Only Field -(13)9.99
(as at into EURO.
conversion
)

David Willcocks 584 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Incurred This is the Incurred amount (i.e. Paid To Date + Display Numeric
in EURO Outstanding) on this claim breakdown – Only Field -(13)9.99
(as at immediately prior to EURO Conversion – converted
conversion into EURO.
)
Highest This is the Highest Estimate on this claim Display Numeric
Estimate breakdown – up until EURO Conversion – Only Field -(13)9.99
in EURO converted into EURO.
(as at
conversion
)
Current The movement reference assigned to the current Display Alphanumeric
Movement transaction on this particular breakdown. Only Field (2 Chars)
PTD Loss This is the amount paid on this claim breakdown (in Display Numeric
in EURO relation to the Loss itself) in EURO since the Only Field -(13)9.99
(post- EURO Conversion took place (up to and including
conversion the transaction the user is currently processing).
)
PTD This is the amount paid on this claim breakdown (in Display Numeric
Expense relation to Expenses) in EURO since the EURO Only Field -(13)9.99
in EURO Conversion took place (up to and including the
(post- transaction the user is currently processing).
conversion
)
PTD Fees This is the amount paid on this claim breakdown (in Display Numeric
in EURO relation to Fees) in EURO since the EURO Only Field -(13)9.99
(post- Conversion took place (up to and including the
conversion transaction the user is currently processing).
)
PTD VAT This is the amount paid on this claim breakdown (in Display Numeric
in EURO relation to VAT) in EURO since the EURO Only Field -(13)9.99
(post- Conversion took place (up to and including the
conversion transaction the user is currently processing).
)
PTD Total This is the total amount paid on this claim Display Numeric
in EURO breakdown in EURO since the EURO Conversion Only Field -(13)9.99
(post- took place (up to and including the transaction the
conversion user is currently processing).
)
Incurred This is the Incurred amount (i.e. Paid To Date + Display Numeric
in EURO Outstanding) for this claim breakdown on the Only Field -(13)9.99
(post- current transaction – expressed in EURO. This does
conversion not include any amounts paid prior to conversion.

David Willcocks 585 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
)
Highest This is the Highest Estimate on this claim Display Numeric
Estimate breakdown – since conversion and up to and Only Field -(13)9.99
in EURO including the transaction the user is currently
(post- processing – expressed in EURO.
conversion
)
PTD Loss This is the total amount paid on this claim Display Numeric
in EURO breakdown (in relation to the loss itself) both prior Only Field -(13)9.99
(total to EURO Conversion and post EURO Conversion –
combined) expressed in EURO.
PTD This is the total amount paid on this claim Display Numeric
Expense breakdown (in relation to expenses) both prior to Only Field -(13)9.99
in EURO EURO Conversion and post EURO Conversion –
(total expressed in EURO
combined)
PTD Fees This is the total amount paid on this claim Display Numeric
in EURO breakdown (in relation to fees) both prior to EURO Only Field -(13)9.99
(total Conversion and post EURO Conversion – expressed
combined) in EURO
PTD VAT This is the total amount paid on this claim Display Numeric
in EURO breakdown (in relation to VAT) both prior to EURO Only Field -(13)9.99
(total Conversion and post EURO Conversion – expressed
combined) in EURO
PTD Total This is the total amount paid on this claim Display Numeric
in EURO breakdown both prior to EURO Conversion and Only Field -(13)9.99
(total post EURO Conversion – expressed in EURO
combined)
Incurred This is the Incurred Amount, as quoted on the Display Numeric
in EURO current transaction, plus the total Paid to date Only Field -(13)9.99
(total amount (expressed in EURO) prior to EURO
combined) Conversion.
Highest This is either the highest estimate (expressed in Display Numeric
Estimate EURO) prior to EURO Conversion or the highest Only Field -(13)9.99
in EURO estimate post EURO Conversion – whichever is the
(total greater.
combined)

B. Commands - (Main Screen).

Close If the user presses this button the ‘EURO Command

Conversion Details’ window should be closed –

David Willcocks 586 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
returning the user to the ‘SCM Advice’ screen.

David Willcocks 587 May 2002

Xchanging Ins-sure Services Ltd
4.32. CCS Amounts Screen

4.32.1. Screen Layout

Below is a ‘mock-up’ of the ‘CCS Amounts’ Screen.

4.32.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LY81 Build CCS Amounts Screen

David Willcocks 588 May 2002

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

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

Field Type Source

A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C081 (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:- All fields on this screen should be protected.

Original Field C081-ORIG-CURR

Currency
CCS Field C081-CCS-CURR
Settlement
Currency
Outstanding Field C081-OUTST-RATE-EXCH
Rate of
Exchange
100% Order Field C081-PTD-AMT-ORIG
Amount (PTD)
100% Field C081-PTD-CCS-AMT
Settlement
Amount in GBP
(PTD)
100% Order Field C081-PTT-AMT-ORIG
Amount (PTT)
Settlement Field C081-RATE-EXCH
Rate
(Orig:GBP)
Settlement Field C081-SETT-CURR
Currency
Treasury Rate Field C081-TREASURY-RATE
(Sett:GBP)
100% Field C081-CCS-SETT-AMT
Settlement
Amount in GBP
(PTT)

David Willcocks 589 May 2002

Xchanging Ins-sure Services Ltd
4.32.4. Process Description

Certain currencies fall into the CCS category – i.e. they

are elligible for conversion by the ‘Currency Conversion
Service’ so that some syndicates are able to settle
claims in GBP rather than the settlement currency
specified on the claim. In order for the technicians to be
able to view the Settlement Amount in GBP for these
claims, this window can be accessed from the ‘SCM
Advice’ screen. It is a display only window that is presented to the
user when they press the ‘CCS Amounts’ button in the ‘SCM Advice’
screen. It is a separate window that ‘overlays’ the ‘SCM Advice’ screen
and will simply be closed down (by pressing the ‘Close’ button) once
the user has finished enquiring on the CCS Amounts. (Hence it has no
navigation bar to the left of the screen or functions at the top)

Fig 4.32.4.1. Field/Command Processing for ‘CCS Amounts’ Screen

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

Original The Original (or Estimate) currency for the current Display Alphanumeric
Currency claim breakdown. Only Field (3 Chars)
CCS The Settlement currency for the current claim Display Alphanumeric
Settlemen breakdown. This is currently GBP. Only Field (3 Chars)
t Currency
100% The Settled to Date amount in the settlement Display Numeric
Order currency that applies to this claim Only Field -(13)9.99
Amount
(PTD)
100% The Settled to Date amount, expressed in the CCS Display Numeric
Settlemen Currency (i.e. GBP) Only Field -(13)9.99
t Amount
in GBP
(PTD)
100% The 100% Settlement amount in the Settlement Display Numeric
Order currency that applies to this claim. Only Field -(13)9.99
Amount
(PTT)
Settlemen The Rate of Exchange between the Original (or Display Numeric
t Rate Estimate) currency and the CCS Currency (i.e. Only Field Z(4)9.9(7)
(Orig:GBP GBP)
)

David Willcocks 590 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Settlemen The Settlement currency for the current claim Display Alphanumeric
t Currency breakdown. This will be one of the settlement Only Field (3 chars)
currencies that is elligible for conversion by the
Currency Conversion Service (CCS)..
Treasury The Rate of Exchange between the Settlement Display Numeric
Rate Currency and the CCS Currency (i.e. GBP) Only Field Z(4)9.9(7)
(Sett:GBP)
100% The 100% Settlement Amount, expressed in the Display Numeric
Settlemen CCS Currency (i.e. GBP) Only Field -(13)9.99
t Amount
in GBP
(PTT)

B. Commands - (Main Screen).

Close If the user presses this button the ‘CCS Amounts’ Command
window should be closed – returning the user to the
‘SCM Advice’ screen.

4.33.

David Willcocks 591 May 2002

Xchanging Ins-sure Services Ltd
4.34. ‘Copy from UCR’ Screen

4.34.1. Screen Layout

Below is a ‘mock-up’ of the pop-up window that will be

displayed when the user selects the ‘Copy from UCR’
function.

Copy Facility

Please enter claim from which details are to be

copied

UCR or XCR :

TR :

OK CANCEL

4.34.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LY12 Build Screen Navigation Bar
LY13 Build Claim Creation Screen
LY84 Copy from another UCR

4.34.3. Field/Command Derivation

All fields should be initialised to spaces

4.34.4. Process Description

When the user is creating a new claim (i.e. the first transaction on a
claim), they have the option of selecting a pre-existing claim from

David Willcocks 592 May 2002

Xchanging Ins-sure Services Ltd
which to copy the basic claim details. They will do this by clicking on
the ‘Functions’ option at the top of the screen. A sub-menu will then be
presented to them – from this they should select the ‘Copy from UCR’
option.

The user should enter the Unique Claims Reference (or Xchanging
Claims reference) that identifies the claim from which the details
should be copied. They may then (optionally) select the Transaction
Reference that identifies a particular transaction on this claim –
oitherwise, the details will be copied from the most transaction on the
claim.

On pressing the ‘OK’ button, the details will be copied to the claim.

Fig 4.33.4.1. Field/Command Processing for ‘Copy from UCR’

Window

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

UCR/XCR The Unique Claim Reference for claims entered by Mandatory Alphanumeric
the broker on the ‘CLASS for Lloyds’ system or Field (6-17 Chars)
Xchanging Claim Reference for claim entered by
internal technicians.
TR Transaction Reference which identifies a particular Optional Alphanumeric
claim transaction. Field (6-17 Chars)

B. Commands - (Main Screen).

OK When the user presses this button, the details on the Command N/a
screen are validated and, assuming the UCR/XCR
and TR are valid, certain details are copied from the
specified claim transaction.

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA
C084 (see Appendix D). This will copy
the details from the specified
transaction and set up the skeleton
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 593 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
(ii) Close the ‘Copy from UCR’ window
and return control to the ‘Claim
Transaction Creation’ screen. N.B. The
Claim Transaction Creation Screen
should be rebuilt by calling the CICS
transaction LY01 (see Appendix C.1) –
using COMMAREA C013 (see
Appendix D) and the Navigation Bar
should be rebuilt by calling the CICS
transaction LY01 – using Commarea
C012 (also see Appendix D).

Cancel When the user presses the ‘Cancel’ button, the Command N/a
window should be closed.

David Willcocks 594 May 2002

Xchanging Ins-sure Services Ltd
4.35. ‘Set Diary Date’ Screen

4.35.1. Screen Layout

Below is a ‘mock-up’ of the pop-up window that will be

displayed when the user selects the ‘Set Diary Date’
function.

Set Diary Date

Please enter or amend diary date for this claim

Diary Date:

OK Cancel

4.35.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LY85 Obtain existing Diary Date
LY86 Update Diary Date

4.35.3. Field/Command Derivation

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

Field Type Source

A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C085 (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).

David Willcocks 595 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Diary Date Field C085-DIARY-DATE

4.35.4. Process Description

The user has the option of setting a diary date for a particular claim.
When the user logs on, all claims with a diary date up to and including
the current date (that have not been flagged as displayed on a previous
day) will be listed on the ‘Home Page’. The claims will be displayed
only to the user who set the diary date.

Fig 4.34.4.1. Field/Command Processing for ‘Set Diary Date’

Window

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

Diary Date This is the date on which the user wishes to be Mandatory Date
remined to review the claim that they are currently Field (DD/MM/CCYY)
viewing.

Date entered must be a future date.

B. Commands - (Main Screen).

OK When the user presses this button, the details on the Command N/a
screen are validated and, assuming the date is valid
(see above), the diary date will be updated.

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA C086
(see Appendix D). This will update the
diary date for the current claim and user.

On return, check the Program Status in

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

(ii) Close the ‘Set Diary Date’ window.

Cancel When the user presses the ‘Cancel’ button, the Command N/a
window should be closed.

David Willcocks 596 May 2002

Xchanging Ins-sure Services Ltd
4.36. Narrative Screen

4.36.1. Screen Layout

Below is a ‘mock-up’ of the Narrative Screen.

4.36.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LY88 Build Narrative Details Screen
LY89 Update Narrative Details

David Willcocks 597 May 2002

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

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

Field Type Source

A. Fields:-

The fields to be displayed on this screen, together with screen/field potection, was
returned in the C088 Commarea by the LY88 transaction called prior to navigation
to this screen. LY88 may have been called twice, depending on whether more
narrative existed on the database than could be contained in one Commarea. If this
was the case – up to 600 lines may have been returned from LY88 (300 for each
call).

Text Type Field C088-TEXT-TYPE

This field should be protected.

Explanatory Field Up to 3 50 character lines should be
Text shown in this field. These are held in
C088-TEXT-NARR (n) (where n varies
from 1 to 3).

This field should be protected.

Narrative Field All occurences of C088-TEXT-LINE
Details (n) should be shown in this field (up
to n = C088-LINE-COUNT. If LY88
was called twice, will be up to C088-
LINE-COUNT (from first call) +
C088-LINE-COUNT (from second
call).

If the C088-SCREEN-MODE = ‘E’

(Enquiry), then this field should be
protected.

If C088-SCREEN-MODE = ‘U’,l then

the field should be unprotected. The
maximum number of lines that can
be entered is held in C088-MAX-NO-
LINES and the length of the lines
that can be entered is held in C088-
LINE-LENGTH. I.e. although C088-
TEXT-LINE is 75 characters long,
the particular type of text that they
are updating may only have 50

David Willcocks 598 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Character lines – we therefore need
to ensure that any characters
greater than C088-LINE-LENGTH
are protected (or that the size of the
field shown on the screen is
governed by the values of C088-
LINE-LENGTH and C088-MAX-NO-
LINES).

Note:- If C088-PROTECT-LINES is
set to ‘Y’, this means that any non-
space lines should be protected. I.e.
all occurences less than or equal to
C088-LINE-COUNT should be
protected – occurences greater than
C088-LINE-COUNT and less than or
equal to C088-MAX-NO-LINES
should be unprotected. (Note:- if
LY88 was called twice then the Line
Count would be C088-LINE-COUNT
from first call + C088-LINE-COUNT
from second call)

N.B. The maximum number of lines

may be over 600 – so this field
should have a scroll bar associated
with it.

4.36.4. Process Description

From the narrative sub-menu at the top of the data

entry screens, the user may select from a number of
different narrative types. The types of narrative
available are as follows:-

(i) Security Notes

(ii) Claim Notes
(iii) Loss Details
(iv) Policy Details
(v) Settlement Narrative
(vi) EURO Conversion Narrative (FME)
(vii) Broker Additional Details
(viii) Broker Aggregate Details
(ix) Slip Lead Comments

David Willcocks 599 May 2002

Xchanging Ins-sure Services Ltd
(x) Lead Comments
(xi) Lead Additional Details

Some of these types of narrative can only be entered on

the ‘CLASS for Lloyds’ system by either the broker or
the lead syndicate – namely, numbers (vii) and above.
These will be shown for display purposes only and
cannot be updated from within the Web GUI system.
The remaining narrative types may be available at both
Transaction or Breakdown level within the claim, in
which case the text appropriate to the screen the
technician was processing at the time they selected the
narrative option will be displayed for enquiry and/or
update. If the user is enquiring on narrative at the
breakdown level and additional narrative for this text
type is also present at the transaction level – a warning
will be displayed at the bottom of the screen. Should
the user wish to view the transaction level narrative,
they should select the narrative option from a
transaction level screen (i.e. claim transaction creation,
policy/risk details, etc.).

David Willcocks 600 May 2002

Xchanging Ins-sure Services Ltd
Fig 4.35.4.1. Field/Command Processing for ‘Narrative’ Screen

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

Text Type The Type of Text that the user selected from the Display Alphanumeric
narrative sub-menu. I.e. one of the following Only Field (50 Chars)

(i) Security Notes

Explanato This is a description of the contents of the text that Display Alphanumeric
ry Text is being displayed, plus notes on how the technician Only Field (3 x 50 chars)
should complete the text (if in update mode).

Text The lines of narrative. The numebr of lines present Mandatory Alphanumeric
Line(s) will depend on the type of narrative displayed. Field (n x l chars)
n=C088-MAX-NO-LINES
l =C088-LINE-LENGTH

B. Commands - (Main Screen).

OK If the user presses the OK button, any changes made

to the narrative on the screen will be saved (if the
user is in Update Mode) and the Narrative window
will be closed.

(i) If C088-SCREEN-MODE = ‘U’ (Update),

Call the CICS transaction LY01 (see
Appendix C.1) – using COMMAREA C089
(see Appendix D), passing the first 300
lines on the screen. This will update the
narrative details on the dabase with the first
300 lines entered on the screen. Set the
C089-CALL-NUMBER field to 1.

On return, check the Program Status in

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

David Willcocks 601 May 2002

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

(ii) If C088-SCREEN-MODE = ‘U’ (Update),

no errors returned from first LY89 call and
more than 300 lines of Narrative are present
on the screen, Call the CICS transaction
LY01 (see Appendix C.1) – using
COMMAREA C089 (see Appendix D) for a
second time, passing lines 301 to 600 on the
screen (if present). This will update the
narrative details on the dabase with the
second 300 lines entered on the screen. Set
the C089-CALL-NUMBER field to 2.

On return, check the Program Status in

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

(iii) Close the ‘Narrative Screen’ window.

Save If the user presses ‘Save’, any changes made to the

narrative on the screen will be saved – but the
window will not yet be closed.

(i) If C088-SCREEN-MODE = ‘U’

(Update), Call the CICS transaction
LY01 (see Appendix C.1) – using
COMMAREA C089 (see Appendix D),
passing the first 300 lines on the screen.
This will update the narrative details on
the dabase with the first 300 lines
entered on the screen. Set the C089-
CALL-NUMBER field to 1.

On return, check the Program Status in

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

(ii) If C088-SCREEN-MODE = ‘U’

(Update), no errors returned from first
LY89 call and more than 300 lines of
Narrative are present on the screen,
Call the CICS transaction LY01 (see
Appendix C.1) – using COMMAREA
C089 (see Appendix D) for a second

David Willcocks 602 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
time, passing lines 301 to 600 on the
screen (if present). This will update the
narrative details on the dabase with the
second 300 lines entered on the screen.
Set the C089-CALL-NUMBER field to
2.

On return, check the Program Status in

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

Cancel If the user presses this button the ‘Narrative Screen’ Command
window should be closed – returning the user to the
screen they were processing prior to selecting the
narrative option.

David Willcocks 603 May 2002

Xchanging Ins-sure Services Ltd
4.37. Bulk/CCS Correction window

4.37.1. Screen Layout

Below is an illustration of what the ‘Bulk/CCS

Correction’ window should look like.

Contra Correction

Please enter treasury rate(s):-

Orig.Curr. Sett.Curr. Treasury Rate
(Sett:GBP)

Reduce Outstanding Amount to Zero ? 

Are you sure you want to release this

Bulk/CCS Correction ?

Release Cancel

4.37.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LY91 Build Bulk/CCS Correction window
LY92 Create Bulk/CCS Correction

David Willcocks 604 May 2002

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

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

Field Type Source

A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C091 (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).

Original Field C091-ORIG-CURR (n)

Currency (n) (This Field should be protected)

Settlement Field C091-SETT-CURR (n)

Currency (n) (This Field should be protected)
Treasury Rate (n) Field Initialise to spaces
(If C091-TREASURY-ATTR = ‘P’, this
field should be protected)

Reduce Tick-Box The ‘Reduce Outstanding Amount to Zero ?’

Outstanding tick-box should be initialised to
Amount to Zero ? ‘FALSE’ (i.e. no tick).

4.37.4. Process Description

In order to bring up this window, the technician must be enquiring on

the claim that they wish to contra. When the technician is enquiring on
a claim, the ‘Bulk/CCS Correction’ option will appear in the
‘Functions’ menu at the top of the screen. Providing the claim that the
user is enquiring on is suitable to be corrected and the technician has
the necessary authority, this window is displayed.

This correction facility is for use on Bulk Components, converted

bulks and pre-redenomination transactions. The technician ias able to
specify the treasury rates that should be applied to the correction. The
GBP Equivalent Amount will be calculated and the USM suppresses
for Bulk/CCS Corrections.

David Willcocks 605 May 2002

Xchanging Ins-sure Services Ltd
The user is also able to opt to reduce the Outstanding Amount to zero.
This is used where the contra is being raised in order to reduce the
Incurred Amount to zero. This is necessary if the technician wishes to
change any of the key fields on the claim. Allowing the user the option
of reducing the outstanding amount to zero at this point will enable the
incurred to be reduced to zero – thus removing the need for the
technician to raise a separate transaction to do this.

If this option is not ticked the Outstanding Amount on the most recent
transaction will be adjusted by the amount being Contra’d.

Fig 4.36.4.1. Field/Command Processing for ‘Bulk/CCS Correction’

Window

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

Original The Original Currencies that apply to this claim. Display Alphanumeric
Currency There may be up to three. However, for Converted Only Field (3 Chars)
(n) Bulks, there will only ever be one currency.
Settlemen The Settlement Currency that applies to the Dispay Alphanumeric
t Currency transaction to be corrected. Only Field (3 Chars)
(n)
Treasury This is the treasury rate of exchange between the Mandatory Numeric
Rate (n) Original Currency and GBP. Field Z(4)9.9(7)
Reduce This field allows the technician to optionally reduce Optional N/A
Outstandi the outstanding amount on the claim to zero at the Tick-Box
ng same time as refunding the earlier transaction.

This field is optional and is initialised to ‘False’ (i.e.

no tick).

B. Commands - (Main Screen).

OK When the user presses the ‘OK’ button, the system Command
will create the ‘Bulk/CCS Correction’ transaction
and then navigate the user to the ‘Settlement
Summary’ so that they can review the details and
release it for advising.

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA
C092 (see Appendix D). This will
create the Bulk/CCS Correction

David Willcocks 606 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
transaction based on the details of the
transaction to be corrected and the
treasury rate entered – reducing the
outstanding position (as quoted on the
most recent transaction) by the
refunded amount – unless the user has
ticked the ‘Reduce Outstanding to Zero’
box.

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 Settlement

Summary Screen (Section 4.22).

Cancel When the user presses the ‘Cancel’ button, the Command
window should be closed.

David Willcocks 607 May 2002

Xchanging Ins-sure Services Ltd
4.38. VAT Rates window

4.38.1. Screen Layout

Below is an illustration of what the ‘VAT Rates’ window

should look like.

VAT Rates

Bureau Proportion of
100% VAT Amount:

Please enter up to six VAT Rates/Amounts:-

VAT Rate VAT Amount

V
V

OK Cancel

4.38.2. CICS Transactions

No CICS transactions are called by this function.

4.38.3. Field/Command Derivation

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

Field Type Source

A. Fields:-

Fields shown on this screen will have been entered on the SCM Advice Screen or
supplied by the CICS transaction that builds the SCM Advice Screen (LY43).

David Willcocks 608 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Bureau Field Amount displayed/entered on the SCM
Proportion of Advice Screen in the ‘100% VAT
the 100% VAT Amount’ field multiplied by C043-
Amount BUREAU-LINE and divided by 100.
(This field should be protected)
VAT Rate (n) Field Set to C043-VAT-RATE (n)
(If C043-VAT-RATE-ATTR (n) = ‘P’,
this field should be protected)
VAT Amount (n) Field C043-VAT-AMT (n)
(If C043-VAT-ATTR (n) = ‘P’, this
field should be protected)

4.38.4. Process Description

This screen is available to the technician only if a non-zero 100% VAT

Amount has been entered on the SCM Advice (Breakdown) Screen. It
enables the user to enter up to 6 VAT Rates that apply to this claim
breakdown and the VAT Amounts associated with each VAT Rate.
These amounts must be entered if a 100% VAT Amount has been
supplied.

When the technician presses ‘OK’ on this screen, the system will
validate that the amounts are correct and that they total the Bureau
proportion of the 100% VAT Amount (which will be shown at the top
of the screen).

Fig 4.37.4.1. Field/Command Processing for ‘VAT Rate’

Window

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

Bureau This is the Bureau Proportion of the 100% VAT Display Numeric
Proportion Amount (in Settlement Currency), entered on the Only Field -(13)9.99
of the SCM Advice (Breakdown) Screen. It is shown here
100% VAT for display purposes only, to enable the user to to
see when the VAT Amounts they are entering for
Amount
each VAT Rate add up to the appropriate amount.

VAT Rate This field cannot be entered by the user – they must Optional Numeric
select the VAT Rate from a drop down list that is Field Z(2)9.9(7)
built from the VAT Rate Reference Table (name?).

David Willcocks 609 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
VAT This field is the part of the Bureau Proportion of the Optional Numeric
Amount 100% VAT Amount to which this VAT Rate applies. Field -(13)9.99

If the VAT Rate has been entered, but this field is

left blank, display the error E175 (see Appendix E)
in the Error Window (see Appendix B).

If the VAT Rate has not been entered and this field
has, display the error E176 (see Appendix E) in the
Error Window (see Appendix B).

If the Bureau Proportion of the 100% VAT Amount

is positive, this field must not be greater than the
Bureau proportion of the 100% VAT Amount. If it
is, display the error E177 (see Appendix E) in the
Error Window (see Appendix B).

If the Bureau Proportion of the 100% VAT Amount

is negative, this field must not be less than the
Bureau Proportion of the 100% VAT Amount. If it
is, display the error E178 (see Appendix E) in the
Error Window (see Appendix B).

Format:- --,---,---,---,--9

B. Commands - (Main Screen).

OK When the user presses the ‘OK’ button, validate that Command
the amounts entered total the Bureau Proportion of
the 100% VAT Amount at the top of the screen. If
the amounts do not add up to the Bureau Proportion
of the 100% VAT Amount, display the error E179
(see Appendix E) in the Error Window (see
Appendix B).

If the details are correct – store the details on the

screen (as they will need to be passed to the CICS
transactions that validate the SCM Advice Screen
(LY44) and perform the associated database updates
(LY45).

Close the window and return the user the ‘SCM

Advice’ Screen.

Cancel When the user presses the ‘Cancel’ button, the Command
window should be closed.

David Willcocks 610 May 2002

Xchanging Ins-sure Services Ltd
4.39. LIDS Comparison Screen

4.39.1. Screen Layout

Below is a ‘mock-up’ of the ‘CCS Amounts’ Screen.

4.39.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

David Willcocks 611 May 2002

Xchanging Ins-sure Services Ltd
Tran Program Description
s. Name
Id.
LZ07 Build LIDS Comparison Screen

David Willcocks 612 May 2002

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

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

Field Type Source

A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C107 (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:- All fields on this screen should be protected.

Original Field C107-ORIG-REF-1

Reference 1
Original Field C107-ORIG-REF-2
Reference 2
Original Field C107-ORIG-REF-3
Reference 3
CLASS Risk Field C107-RISK-CODE-C
Code
This field should be protected.

If C107-RISK-CODE-DIFF = ‘Y’, the

field should be highlighted.
CLASS Year of Field C107-YEAR-OF-ACC-C
Account
This field should be protected.

If C107-YEAR-OF-ACC-DIFF = ‘Y’,
the field should be highlighted.
LIDS Risk Code Field C107-RISK-CODE-L

This field should be protected

LIDS Year of Field C107-YEAR-OF-ACC-L
Account
This field should be protected

Read through the details in the C107-CLASS-DETAILS table and

display details in a Scrolling area on the screen, up to and
including occurrence equal to C107-CLASS-COUNT.

CLASS Claims Field C107-COR-C

David Willcocks 613 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Office
Reference (n) This field should be protected
CLASS FIL Field C107-FIL-CODE-1-C
Code 1 (n)
This field should be protected.

If C107-FIL-CODE-1-DIFF = ‘Y’, the

field should be highlighted.
CLASS FIL Field C107-FIL-CODE-2-C
Code 2 (n)
This field should be protected.

If C107-FIL-CODE-2-DIFF = ‘Y’, the

field should be highlighted.
CLASS DTI Field C107-DTI-CODE-C
Code (n)
This field should be protected.

If C107-DTI-CODE-DIFF = ‘Y’, the

field should be highlighted.
CLASS TF Code Field C107-TF-CODE-C
(n)
This field should be protected.

If C107-TF-CODE-DIFF = ‘Y’, the

field should be highlighted.
CLASS Other Field C107-OTHER-TF-C
TF Code (n)
This field should be protected.

If C107-OTHER-TF-DIFF = ‘Y’, the

field should be highlighted.
CLASS Original Field C107-ORIG-CURR-C
Currency (n)
This field should be protected.

If C107-ORIG-CURR-DIFF = ‘Y’, the

field should be highlighted.
CLASS Country Field C107-CNTRY-CODE-C
of Origin (n)
This field should be protected.

If C107-CNTRY-CODE-DIFF = ‘Y’,
the field should be highlighted.

David Willcocks 614 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source

Read through the details in the C107-LIDS-DETAILS table and

display details in a Scrolling area on the screen, up to and
including occurrence equal to C107-LIDS-COUNT.

LIDS FIL Code Field C107-FIL-CODE-1-L

1 (n)
This field should be protected
LIDS FIL Code Field C107-FIL-CODE-2-L
2 (n)
This field should be protected
LIDS DTI Code Field C107-DTI-CODE-L
(n)
This field should be protected
LIDS TF Code Field C107-TF-CODE-L
(n)
This field should be protected
LIDS Other TF Field C107-OTHER-TF-L
Code (n)
This field should be protected
LIDS Original Field C107-ORIG-CURR-L
Currency (n)
This field should be protected
LIDS Country Field C107-CNTRY-CODE-L
of Origin (n)
This field should be protected

4.39.4. Process Description

It is possible that, since the current claim was first creayted, the data
held on the LIDS database has been corrected. If this is the case, this
screen will be displayed to the user to highlight any differences
between the data on CLASS and the data held on LIDS.

It is a separate window that ‘overlays’ the ‘SCM Advice’ screen and

will simply be closed down (by pressing the ‘Close’ button) once the
user has finished enquiring on the CCS Amounts. (Hence it has no
navigation bar to the left of the screen or functions at the top)

Fig 4.38.4.1. Field/Command Processing for ‘LIDS Comparison’

Screen

David Willcocks 615 May 2002

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

A. Fields (Main Screen)

Original The Original Signing Reference (OSND) associated Display Alphanumeric

Reference with the first Original Currency on the claim. only Field (15 Chars)
1
This field should be displayed according to
standards. I.e. SSSSS*DD/MM/YY
Original The Original Signing Reference (OSND) associated Display Alphanumeric
Reference with the second Original Currency on the claim. Only Field (15 Chars)
2
This field should be displayed according to
standards. I.e. SSSSS*DD/MM/YY
Original The Original Signing Reference (OSND) associated Display Alphanumeric
Reference with the third Original Currency on the claim. Only Field (15 Chars)
3
This field should be displayed according to
standards. I.e. SSSSS*DD/MM/YY
CLASS The Risk Code currently held on the CLASS Display Alphanumeric
Risk Code database for this claim Only Field (2 Chars)
CLASS The Year of Account currently held on the CLASS Display Alphanumeric
Year of database for this claim Only Field (4 Chars)
Account
LIDS Risk The Risk Code currently held on LIDS for the Display Alphanumeric
Code OSND(s) the claim is being made against Only Field (2 Chars)
LIDS Year The Year of Account currently held on LIDS for the Display Alphanumeric
of Account OSND(s) the claim is being made against Only Field (4 Chars)
CLASS The Claims Office Reference. This uniquely Display Alphanumeric
Claims identifies each line of details displayed in the Only Field (12 Chars)
Office ‘CLASS’ Section of the screen
Reference
(n)
CLASS The FIL Code 1 currently held on CLASS for the Display Alphanumric
FIL Code COR shown Only Field (4 Chars)
1 (n)
CLASS The FIL Code 2 currently held on CLASS for the Display Alphanumeric
FIL Code COR shown Only Field (4 Chars)
2 (n)
CLASS The DTI Code currently held on CLASS for the Display Alphanumeric
DTI Code COR shown Only Field (2 Chars)
(n)
CLASS TF The Trust Fund Code currently held on CLASS for Display Alphanumeric
Code (n) the COR Shown Only Field (2 Chars)

David Willcocks 616 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
CLASS The Non-US Trust Fund Code currently held on Display Alphanumeric
Other TF CLASS for the COR shown Only Field (2 Chars)
Code (n)
CLASS The Original Curreny currently held on CLASS for Display Alphanumeric
Original the COR shown Only Field (3 Chars)
Currency
(n)
CLASS The Country of Origin currently held on CLASS for Display Alphanumeric
Country of the COR shown. Only Field (2 Chars)
Origin (n)
LIDS FIL The FIL 1 Code(s) currently held on LIDS for the Display Alphanumric
Code 1 (n) OSND(s) against which the claim is being made Only Field (4 Chars)
LIDS FIL The FIL 2 Code(s) currently held on LIDS for the Display Alphanumeric
Code 2 (n) OSND(s) against which the claim is being made Only Field (4 Chars)
LIDS DTI The DTI Code(s) currently held on LIDS for the Display Alphanumeric
Code (n) OSND(s) against which the claim is being made Only Field (2 Chars)
LIDS TF The Trust Fund Code(s) currently held on LIDS for Display Alphanumeric
Code (n) the oSND(s) against which the claim is being made. Only Field (2 Chars)
LIDS The Non-US Trust Fund Code(s) currently held on Display Alphanumeric
Other TF LIDS for the OSND(s) against which the claim is Only Field (2 Chars)
Code (n) being made.
LIDS The Original Currency(s) currently held on LIDS Display Alphanumeric
Original for the OSND(s) against which the claim is being Only Field (3 Chars)
Currency made.
(n)
LIDS The Country Code(s) currently held on LIDS for the Display Alphanumeric
Country of OSND(s) against which the claim is being made. Only Field (2 Chars)
Origin (n)

B. Commands - (Main Screen).

OK Close the ‘LIDS Comparison’ window and return Command

control to the Claim Transaction Creation screen –
continue with either ‘SAVE’ or ‘CONTINUE’
proocessing, as defined by Section 4.9.4.

Cancel If the user presses this button the ‘LIDS Command

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

David Willcocks 617 May 2002

Xchanging Ins-sure Services Ltd
4.40. Re-Advice Creation

4.40.1. Screen Layout

Below is an illustration of what the ‘Create Re-Advice’

window should look like.

Create Re-Advice

Please enter Current Narrative:-

OK Cancel

N.B. Please note that in reality, this will be an HTML screen similar to
that for Contra Corrections, etc.

4.40.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LZ12 LC0586R0 Build Re-Advice Screen
LZ13 LC0587R0 Re-Advice Screen Validation
LZ14 LC0588R0 Create Re-Advice

David Willcocks 618 May 2002

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

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

Field Type Source

A. Fields:-

call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C111 (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).

Current Field C111-CURR-NARR-1

Narrative 1
If C111-CURR-NARR-ATTR1 = ‘P’, this
fied should be protected.
Narrative Code Field C111-NARR-CODE-1
1
If C111-NARR-CODE-ATTR1 = ‘P’, this
field should be protected.
Current Field C111-CURR-NARR-2A
Narrative 2
(Part 1) If C111-CURR-NARR-ATTR2A = ‘P’,
this field should be protected
Narrative Code Field C111-NARR-CODE-2
2
If C111-NARR-CODE-ATTR2 = ‘P’,
this field should be protected.
Current Field C111-CURR-NARR-2B
Narrative 2
(Part 2) If C111-CURR-NARR-ATTR2B = ‘P’,
this field should be protected.

4.40.4. Process Description

In order to bring up this window, the technician must be enquiring on

the claim that they wish to rea-advise. When the technician is
enquiring on a claim, the ‘Create Re-Advice’ option will appear in the
‘Functions’ menu at the top of the screen. Providing the claim that the
user is enquiring on is suitable to be readvised, this window is
displayed.

On pressing ‘OK’, a new movement will be created with all details as

per the previous transaction – except for the current narrative, which

David Willcocks 619 May 2002

Xchanging Ins-sure Services Ltd
the user is able to enter on the ‘Create Re-Advice’ screen – and the
user will be routed to the Non-Settlement Summary screen in order to
review and release the newly created claim transaction.

Fig 4.39.4.1. Field/Command Processing for ‘Create Re-Advice’

Window

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

Current Narrative that applies to the claim movement. Optional Alphanumeric

Narrative Field (50 Chars)
1 This is a free format narrative field in which the
technician may key details relating to the claim
movement.

Narrative A code that identifies a standard piece of narrative. Optional Alphanumeric

Code 1 Field (3 Chars)
A drop-down list will be associated with this code,
which will be built from the data on the
VGLCNDA1. When the user selects from this list,
the associated text should be shown immediately in
the “Current Narrative 2 (Part 1)” field.

Current Narrative that applies to the claim transaction. Optional Alphanumeric

Narrative Field (25 Chars)
2 (part 1) If Narrative Code 1 has been entered - when the
user tabs out of the Narrative Code 1 field, read the
Narrative Description Table (VGLCNDA1), which
should be held in the JAVA Layer, and pre-populate
this field with the associated Narrative Text (first 25
chars).

Narrative A second code that identifies an additional standard Optional Alphanumeric

Code 2 piece of narrative. Field (3 Chars)

A drop-down list will be associated with this code,

which will be built from the data on the
VGLCNDA1. When the user selects from this list,
the associated text should be shown immediately in
the “Current Narrative 2 (Part 2)” field.

N.B. On CCS Claims, this field will be protected –

as “Current Narrative 2 (Part 2)” contains the CCS
Rate of Exchange.

David Willcocks 620 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Current Additional Narrative that applies to the claim Optional Alphanumeric
Narrative transaction. Field (25 Chars)
2 (part 2)
If Narrative Code 1 has been entered - when the
user tabs out of the Narrative Code 1 field, read the
Narrative Description Table (VGLCNDA1), which
should be held in the JAVA Layer, and pre-populate
this field with the associated Narrative Text (first 25
chars).

N.B. On CCS Claims, this field will be protected –

as “Current Narrative 2 (Part 2)” contains the CCS
Rate of Exchange.

B. Commands - (Main Screen).

OK When the user presses the ‘OK’ button, the system Command
will create the Re-Advice and then navigate the user
to the ‘Non-Settlement Summary’ so that they can
review the details and release it for advising.

(i) Call the CICS transaction LY01 (see

Appendix C.1) – using COMMAREA
C112 (see Appendix D). This will
validate the details entered on the
screen.

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
C113 (see Appendix D). This will
create the readvice based on the details
of the most recent transaction on the
claim – setting the Current Narrative
appropriately.

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 the Non-Settlement

Summary screen (Section 4.21)

David Willcocks 621 May 2002

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

Cancel When the user presses the ‘Cancel’ button, the Command
window should be closed.

David Willcocks 622 May 2002

Xchanging Ins-sure Services Ltd
4.41. ‘Expert Fees Breakdown’ Screen

4.41.1. Screen Layout

Below is an illustration of what the ‘Expert Fees

Breakdown’ screen should look like.

Fig 4.41.1.1. ‘Expert Fees Breakdown’ screen – Update mode

David Willcocks 623 May 2002

Xchanging Ins-sure Services Ltd
Fig 4.41.1.2. ‘Expert Fees Breakdown’ screen – Enquiry mode

David Willcocks 624 May 2002

Xchanging Ins-sure Services Ltd
NOTE:- Where multiple experts exist, the area of the screen below the ‘totals’ section
should scroll – as illustrated in the following example:-

N.B. This example is of the Update version of the screen – but the same
should also apply to the enquiry version.

4.41.2. CICS Transactions

No CICS transactions are called by this function.

4.41.3. Field/Command Derivation

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

Field Type Source

A. Fields:-

Fields shown on this screen will have been entered on the SCM Advice Screen or
supplied by the CICS transaction that builds the SCM Advice Screen (LY43).

David Willcocks 625 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Orig Ccy Field C043-ORIG-CURR
This field should be protected.
PTT Exp Total Field C043-PTT-EXP
This field should be protected
PTT Fee Total Field C043-PTT-FEE
This field should be protected
O/S Exp Total Field C043-OUTST-EXP
This field should be protected
O/S Fee Total Field C043-OUTST-FEE
This field should be protected
Read through all occurences in the C043-EXPERT-DETAILS table. Display the
details in tabular format on the screen.

Note:- If no expert details are returned (i.e. C043-EXPERT-COUNT = Zero), set up

the first occurrence as follows (N.B. All Fields, except the ‘PTD Exp’ and ‘PTD
Fee’ fields, should be unprotected) :-
Expert Code (1) = Spaces
Expert Type (1) = Spaces
Expert Ref (1) = Spaces
Advise on SCM (1) = ‘un-ticked’
Expert Org Name (1) = Spaces
Expert Name (1) = Spaces
PTD Exp (1) = Zero
PTD Fee (1) = Zero
PTT Exp (1) = Zero
PTT Fee (1) = Zero
O/S Exp (1) = Zero
O/S Fee (1) = Zero
‘Delete Expert ?’ (1) = ‘un-ticked’

Expert Code (n) Field C043-EXPERT-CODE

(If C043-EX-CODE-ATTR (n) = ‘P’, this
field should be protected)

David Willcocks 626 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Expert Type (n) Field If C043-EXPERT-TYPE = ‘A’
This field should be set to ‘Adjuster’.
If C043-EXPERT-TYPE = ‘L’
This field should be set to ‘Lawyer’.
If C043-EXPERT-TYPE = Spaces
This field should be set to Spaces.

(If C043-EX-TYPE-ATTR (n) = ‘P’, this field

should be protected)
Expert Ref (n) Field C043-EXPERT-REF
(If C043-EX-REF-ATTR (n) = ‘P’, this field
should be protected)
Advise on SCM (n) Field C043-EXPERT-SCM
(If C043-EX-SCM-ATTR (n) = ‘P’, this field
should be protected)
Expert Org Name Field C043-EXPERT-NAME
(n) (If C043-EX-NAME-ATTR (n) = ‘P’, this
field should be protected)
Expert Name (n) Field C043-EXPERT-CNTCT
(If C043-EX-CNTCT-ATTR (n) = ‘P, this
field should be protected)
PTD Exp (n) Field C043-EXPERT-PTD-EXP
(If C043-EX-PTD-EXP-ATTR (n) = ‘P’, this
field should be protected)
PTD Fee (n) Field C043-EXPERT-PTD-FEE
(If C043-EX-PTD-FEE-ATTR (n) = ‘P’, this
field should be protected)
PTT Exp (n) Field C043-EXPERT-PTT-EXP
(If C043-EX-PTT-EXP-ATTR (n) = ‘P’, this
field should be protected)
PTT Fee (n) Field C043-EXPERT-PTT-FEE
(If C043-EX-PTT-FEE-ATTR (n) = ‘P’, this
field should be protected)
O/S Exp (n) Field C043-EXPERT-OS-EXP
(If C043-EX-OS-EXP-ATTR (n) = ‘P’, this
field should be protected)

David Willcocks 627 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
O/S Fee (n) Field C043-EXPERT-OS-FEE
(If C043-EX-OS-FEE-ATTR (n) = ‘P’, this
field should be proteted)
Delete Expert ? (n) Field Initialise to ‘Un-ticked’.

If C043-EX-DEL-ATTR (n) = ‘P’ this field

should be protected
B. Commands
New Expert Command If C043-EXP-SCREEN-ATTR = ‘U’
(Update),
The Update version of the screen
should be
shown (as in 4.41.1.1), on which this
button is
always available
Otherwise
The enquiry version of the screen
should be
shown (as in 4.41.1.2), on which this
button is
not available.
(See note below)
Delete Selected Command If C043-EXP-SCREEN-ATTR = ‘U’
(Update),
The Update version of the screen
should be
shown (as in 4.41.1.1), on which this
button is
always available
Otherwise
The enquiry version of the screen
should be
shown (as in 4.41.1.2), on which this
button is
not available.
(See note below)

Note:- If C043-EXP-SCREEN-ATTR is set to ‘E’ (Enquiry), then the

Enquiry Version of the screen (as shown in Figure 4.41.1.2 – above)
should be shown. All fields are protected and the ‘New Expert’ and
‘Delete Selected’ commands are not shown.

Note:- Any new experts entered should have their fields initialised
and protected as follows:-

Field Initial value / protection

David Willcocks 628 May 2002

Xchanging Ins-sure Services Ltd
Expert Code Spaces (Unprotected)
Expert Type Spaces (Unprotected)
Expert Ref Spaces (Unprotected)
Advise on SCM Un-ticked (Unprotected)
Expert Org Name Spaces (Unprotected)
Expert Name Spaces (Unprotected)
PTD Exp Zeroes
(If C043-EXP-PTD-ATTR = ‘P’, this
field should be protected. Otherwise, it
should be unprotected)
PTD Fee Zeroes
(If C043-FEE-PTD-ATTR = ‘P’, this field
should be protected. Otherwise, it should
be unprotected)
PTT Exp Zeroes
(If C043-PTT-EXP-ATTR = ‘P’, this field
should be protected. Otherwise, it should
be unprotected)
PTT Fee Zeroes
(If C043-PTT-FEE-ATTR = ‘P’, this field
should be protected. Otherwise, it should
be unprotected)
O/S Exp Zeroes (Unprotected)
O/S Fee Zeroes (Unprotected)
Delete Expert ? Un-ticked (Unprotected)

4.41.4. Process Description

This screen is available to the technician only if the ‘Expert Fees

Breakdown’ button is enabled on the ‘SCM Advice (Breakdown)’
Screen (as indicated by the C043-FEES-BDOWN-ATTR field).

There are two versions of the screen – as shown in Section 4.41.1.; an

update version and an enquiry version. The version shown is dictated
by the value of C043-EXP-SCREEN-ATTR

The screen enables the user to split the Fees Amounts, entered on the
‘SCM Advice (Breakdown)’ screen, across up to 100 experts (Lawyers
or Adjusters).

David Willcocks 629 May 2002

Xchanging Ins-sure Services Ltd
When the technician presses ‘OK’ on this screen, the system will
validate that the amounts are correct and that they add up to the
amounts entered on the ‘SCM Advice (Breakdown)’ screen (which will
be shown at the top of the screen, to make this process easier). Note:-
no validation will be performed when in the Enquiry version of the
screen.

Fig 4.37.4.1. Field/Command Processing for ‘Expert Fees

Breakdown’ screen

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

‘Free Format’ 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 fail. Valid ASCII Characters are as
follows:-
space, 0-9, A-Z, a-z, ',', '.', '-', '(', ')', '/', '=', ''', '*','+', ':', '?', '!','"', '%','&', ';','<', '>'.

Orig Ccy This is the Original Currency for the current COR – Display- Alphanumeric
i.e. the currency in which all financial amounts Only Field (3 Chars)
shown or enterable on this screen are expressed.

PTT Exp Total This is the total Expense Amount for the current Display- Numeric
breakdown. It is set to the value entered in the “PTT Only Field -(13)9.99
Exp” field on the SCM Advice Screen (from where (Display with
this screen is invoked). commas)

The total of all ‘PTT Exp’, for all experts on this

screen, must equal this value.

PTT Fee Total This is the total Fees Amount for the current Display- Numeric
breakdown. It is set to the value entered in the “PTT Only Field -(13)9.99
Fee” field on the SCM Advice Screen (from where (Display with
this screen is invoked). Commas)

The total of all ‘PTT Fee’, for all experts on this

screen, must equal this value.

David Willcocks 630 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
O/S Exp Total This is the total amount, relating to Expenses, that is Display- Numeric
outstanding for the current breakdown. It is set to Only Field -(13)9.99
the value entered in the “O/S Exp” field on the (Display with
SCM Advice Screen (from where this screen is Commas)
invoked).

The total of all ‘O/S Exp’, for all experts on this

screen, must equal this value.

O/S Fee Total This is the total amount, relating to Fees, that is Display- Numeric
outstanding for the current breakdown. It is set to Only Field -(13)9.99
the value entered in the “O/S Fee” field on the SCM (Display with
Advice Screen (from where this screen is invoked). Commas)

The total of all ‘O/S Fee’, for all experts on this

screen, must equal this value.

Expert Type The type of expert – i.e. ‘Lawyer’ or ‘Adjuster’. Mandatory Alphanumeric
(8 Chars)
This field will be associated with a drop-down list,
containing two possible values (‘Lawyer’ and
‘Adjuster’)
Note:- this should be configurable, in case other
expert types are added in future.
If the user enters an Expert Type and an Expert
Code has also been entered, the associated name
should be used to populate the Expert Name field
(obtained using the Expert Type and Expert Code).
Otherwise
If the user enters an Expert Type and an Expert
Name has also been entered, the associated code
should be used to populate the Expert Code field
(obtained using the Expert Type and Expert Name).
Field will be ‘greyed-out’ and protected, if the
expert existed on the previous movement. Note:-
This will be dictated by the value of the associated
attribute field, passed from the mainframe.

David Willcocks 631 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Advise on This tick-box will indicate that the current Adjuster Conditional Tick-Box
SCM or Lawyer should be advised on the SCM. Only one
of each may be advised.
If any Lawyers are entered (that exist on the Expert
reference table – i.e. are still valid), one (and only
one) must be selected.
If any Adjusters are entered (that exist on the Expert
reference table – i.e. are still valid), one (and only
one) must be selected.

Expert Code The code associated with the Lawyer or Adjuster Conditional Alphanumeric
appointed to advise on the claim. (4 Chars)

If the user has entered an Expert Name for this

occurence – this field will be populated with the
Expert Code from the Expert Table (accessed using
the Expert Type and Expert Name).

If the user enters an Expert Code, the associated

name should be used to populate the Expert Name
field (obtained using the Expert Type and Expert
Code).
Field will be ‘greyed-out’ and protected, if the
expert existed on the previous movement. Note:-
This will be dictated by the value of the associated
attribute field, passed from the mainframe.
Expert Ref The experts reference. This is a free-format field. Optional Free Format
(16 Chars)

David Willcocks 632 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Expert Org Name of the Expert Organisation appointed to Conditional Free Format
Name advise on the claim. (40 Chars)
If the user has entered an Expert Code for this
occurence – this field will be populated with the
Expert Name from the Expert Table (accessed using
the Expert Type and Expert 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. The list should be filtered based on
the Expert Type entered (i.e. if ‘Adjuster’ is selected,
the drop-down list should only show Adjusters)
If the user selects a name from the list, the
associated code should be used to populate the
Expert Code field (obtained using the Expert Type
and Expert Org Name).
Field will be ‘greyed-out’ and protected, if the
expert existed on the previous movement. Note:-
This will be dictated by the value of the associated
attribute field, passed from the mainframe.
Expert Name Name of the individual within the Expert Optional Free Format
Organisation appointed to advise on this claim. (40 Chars)
This is an optional free-format text field and may be
changed from one movement to the next, if
required.

David Willcocks 633 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
PTD Exp The part of the Paid To Date amount that relates to Optional Numeric
‘Expenses’. This is the sum of all previously settled -(13)9.99
‘Expense’ amounts and the Paid This Time
‘Expense’ amount on the current transaction - for
the expert in question. It is a 100% amount.
It will be initialised to the value held on the
previous transaction for this breakdown and expert -
or Zero for initial advices, or for new experts.
Note:- On the first movement following
implementation of this screen, the PTD amounts
will be enterable (if any Fees/Expert Amounts are
present on any previous movements). The user will
be prompted to split any previously entered fees
and/or expense amounts across the experts
involved.
(Display with Commas when user tabs out of field
& on first display of both update and enquiry
versions of screen)
PTD Fee The part of the Paid To Date amount that relates to Optional Numeric
‘Fees’. This is the sum of all previously settled -(13)9.99
‘Fees’ amounts and the Paid This Time ‘Fees’
amount on the current transaction - for the expert in
question. It is a 100% amount.
It will be initialised to the value held on the
previous transaction for this breakdown and expert -
or Zero for initial advices, or for new experts.
Note:- On the first movement following
implementation of this screen, the PTD amounts
will be enterable (if any Fees/Expert Amounts are
present on any previous movements). The user will
be prompted to split any previously entered fees
and/or expense amounts across the experts
involved.
(Display with Commas when user tabs out of field
& on first display of both update and enquiry
versions of screen)

David Willcocks 634 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
PTT Exp This is the amount (in Original Currency) to be Optional Numeric
settled for a particular expert in relation to -(13)9.99
expenses. It is a 100% amount. (If Orig Ccy
not = ‘JPY’ or
It will be initialised to zero on first entry to the ‘ITL’)
screen on new movements or for new experts.
OR
-(13)9
This field will be protected on advice-only
transactions. (if Orig Ccy =
‘JPY’ or ‘ITL’)
(Display with Commas when user tabs out of field
& on first display of both update and enquiry
versions of screen).

PTT Fee This is the amount (in Original Currency) to be Optional Numeric
settled for a particular expert in relation to Fees. It -(13)9.99
is a 100% amount. (If Orig Ccy
not = ‘JPY’ or
It will be initialised to zero on first entry to the ‘ITL’)
screen on new movements or for new experts.
OR
This field will be protected on advice-only -(13)9
transactions. (if Orig Ccy =
(Display with Commas when user tabs out of field ‘JPY’ or ‘ITL’)
& on first display of both update and enquiry
versions of screen)
O/S Exp This is the amount (in Original Currency), relating Optional Numeric
to expenses, that is outstanding for the current -(13)9.99
expert. It is a 100% amount.
(No decimal
This will be initialised to the value held on the places)
previous transaction for the current breakdown or
zero for first advices.
(Display with Commas when user tabs out of field
& on first display of both update and enquiry
versions of screen)

David Willcocks 635 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
O/S Fee This is the amount (in Original Currency), relating Optional Numeric
to fees, that is outstanding for the current expert. It -(13)9.99
is a 100% amount.
(No decimal
This will be initialised to the value held on the places)
previous transaction for the current breakdown or
zero for first advices.
(Display with Commas when user tabs out of field
& on first display of both update and enquiry
versions of screen)

Delete Expert? This tick-box will alow the user to remove details Optional Tick-Box
for any experts that may have been added
erroneously.

This can only be done if the expert was not present

on the previous movement.

B. Commands - (Main Screen).

OK When the user presses the ‘OK’ button, perform the Command
associated GUI-level validation, outlined in Section
4.41.5 (below).

If the details are correct – store the details on the

screen (as they will need to be passed to the CICS
transactions that validate the SCM Advice Screen
(LY44) and perform the associated database updates
(LY45).

Close the window and return the user the ‘SCM

Advice’ Screen.

Note:- This button is not available on the enquiry

version of the screen

Cancel When the user presses the ‘Cancel’ button, the Command
claims adjuster should be returned to the SCM
Advice (Breakdown) screen – no validation will be
performed and no changes will be saved.

David Willcocks 636 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
NEW When the user presses the ‘NEW EXPERT’ button, Command
EXPERT a new set of fields for a new expert should be added
to the bottom of those currently displayed. All fields
for the new expert should be initialised to spaces or
zeroes, as applicable.

Maximum Number of Experts allowed will be set

to 100.

Note:- This button is not available on the enquiry

version of the screen

DELETE This will remove all fields for any experts for which
SELECTED the user has ticked the ‘Delete Expert ?’ box.

When the user presses the ‘DELETE SELECTED’

button, perform the associated GUI-level validation,
outlined in Section 4.41.5 (below).

If no error encountered, a warning should be

displayed – as follows:-

Are you sure you want to

remove the selected experts ?

CANCEL OK

If the user .clicks ‘CANCEL’, no expert rows

should be removed.

If the user clicks ‘OK’, the fields for the selected

experts should be removed and the screen
redisplayed with the remaining experts ‘shuffled up’
appropriately.

Note:- This button is not available on the enquiry

version of the screen

David Willcocks 637 May 2002

Xchanging Ins-sure Services Ltd
4.41.5. GUI-Level Validation

The following validation should be performed by the user interface

when the user presses the command indicated.

Errors should be displayed in the standard error screen format.

Note Error Message text is obtained from the Error Table, passed from
the mainframe.

Error/Warning E/ Code Comman

Message Output
Situation W d
‘OK’ has been pushed, and E E674 PLEASE DELETE SELECTED ‘OK’
one or more experts are EXPERTS BEFORE
flagged for deletion. PROCEEDING
The ‘PTD Exp’ is E E689 PTD EXPENSE AMTS FOR ‘OK’
unprotected and the sum of EXPERTS NOT = TOTAL PTD
the ‘PTD Exp’ Amounts, for EXPENSE AMT
all experts, is not equal to the
EXPERT AMT =
‘PTD Exp Total’ Amount
Z,ZZZ,ZZZ,ZZZ,ZZ9.99,
(displayed at the top of the TOTAL AMT =
screen). Z,ZZZ,ZZZ,ZZZ,ZZ9.99

(Note:- only unprotected on

first movement following
implementation)
The ‘PTD Fee’ is E E690 PTD FEE AMTS FOR EXPERTS ‘OK’
unprotected and the sum of NOT = TOTAL PTD FEE AMT
the ‘PTD Fee’ Amounts, for
all experts, is not equal to EXPERT AMT =
the ‘PTD Fee Total’ Amount Z,ZZZ,ZZZ,ZZZ,ZZ9.99,
(displayed at the top of the TOTAL AMT =
screen) Z,ZZZ,ZZZ,ZZZ,ZZ9.99

(Note:- only unprotected on

first movement following
implementation)
The sum of the ‘PTT Exp’ E E675 PTT EXPENSE AMTS FOR ‘OK’
Amounts, for all experts, is EXPERTS NOT = TOTAL PTT
not equal to the ‘PTT Exp
Total’ Amount (displayed at
EXPENSE AMT
the top of the screen)
EXPERT AMT =
Z,ZZZ,ZZZ,ZZZ,ZZ9.99,
TOTAL AMT =
Z,ZZZ,ZZZ,ZZZ,ZZ9.99

David Willcocks 638 May 2002

Xchanging Ins-sure Services Ltd
Error/Warning E/ Code Comman
Message Output
Situation W d
The sum of the ‘PTT Fee’ E E676 PTT FEE AMTS FOR ‘OK’
Amounts, for all experts, is EXPERTS NOT = TOTAL PTT
not equal to the ‘PTT Fee
Total’ Amount (displayed at
FEE AMT
the top of the screen)
EXPERT AMT =
Z,ZZZ,ZZZ,ZZZ,ZZ9.99,
TOTAL AMT =
Z,ZZZ,ZZZ,ZZZ,ZZ9.99
The sum of the ‘O/S Exp’ E E677 O/S EXPENSE AMTS FOR ‘OK’
Amounts, for all experts, is EXPERTS NOT = TOTAL O/S
not equal to the ‘O/S Exp
Total’ Amount (displayed at
EXPENSE AMT
the top of the screen)
EXPERT AMT =
Z,ZZZ,ZZZ,ZZZ,ZZ9.99,
TOTAL AMT =
Z,ZZZ,ZZZ,ZZZ,ZZ9.99
The sum of the ‘O/S Fee’ E E678 O/S FEE AMTS FOR ‘OK’
Amounts, for all experts, is EXPERTS NOT = TOTAL O/S
not equal to the ‘O/S
FeeTotal’ Amount (displayed
FEE AMT
at the top of the screen)
EXPERT AMT =
Z,ZZZ,ZZZ,ZZZ,ZZ9.99,
TOTAL AMT =
Z,ZZZ,ZZZ,ZZZ,ZZ9.99
The ‘DELETE SELECTED’ E E679 PLEASE SELECT AT LEAST ONE ‘DELETE
button is pressed, and no EXPERT FOR DELETION SELECTED
experts have been flagged
for deletion ’
For a particular expert, the E E680 THE EXPERT NAME OR CODE ‘OK’
Expert Name/Code are MUST BE ENTERED and
spaces
‘NEW
EXPERT’
For a particular expert, the E E681 EXPERT TYPE MUST BE ‘OK’
Expert Type is spaces ENTERED and
EXPERT CODE = XXXX
‘NEW
EXPERT’
At least one VALID expert E E682 PLEASE SELECT AN ADJUSTER ‘OK’
has an Expert Type of TO BE ADVISED ON THE SCM
‘Adjuster’ – but none of the
experts flagged as
‘Adjusters’ have the ‘Advise
on SCM’ indicator ticked.

David Willcocks 639 May 2002

Xchanging Ins-sure Services Ltd
Error/Warning E/ Code Comman
Message Output
Situation W d
At least one VALID expert E E683 PLEASE SELECT A LAWYER TO ‘OK’
has an Expert Type of BE ADVISED ON THE SCM
‘Lawyer’ – but none of the
experts flagged as ‘Lawyers’
have the ‘Advise on SCM’
indicator ticked.
One or more Expert E E688 DUPLICATE EXPERT CODE HAS ‘OK’
Code/Expert Type BEEN SPECIFIED and
combinations are duplicated
EXPERT CODE = XXXX
‘NEW
EXPERT’
User attempts to add E E689 EXPERT LIMIT EXCEEDED – ‘NEW
another Expert, when there LIMIT IS 100 EXPERT’
are already 100 for the
current COR.
If the user ticks the ‘Advise E E690 LAWYER TO BE ADVISED ON ‘OK’
on SCM’ indicator for a SCM IS NO LONGER VALID
Lawyer that is no longer
valid, issue an error. PLEASE SELECT ANOTHER
LAWYER
i.e. If ‘Advise on SCM’ ticked
and associated Expert Type
is ‘Lawyer’ and associated
Expert Code is not present
on VGLFEEA1 (with and
Expert Type of ‘L’), issue
error

If the user ticks the ‘Advise E E691 ADJUSTER TO BE ADVISED ON ‘OK’

on SCM’ indicator for a SCM IS NO LONGER VALID
Adjuster that is no longer
valid, issue an error. PLEASE SELECT ANOTHER
ADJUSTER
i.e. If ‘Advise on SCM’ ticked
and associated Expert Type
is ‘Adjuster’ and associated
Expert Code is not present
on VGLFEEA1 (with and
Expert Type of ‘A’), issue
error

David Willcocks 640 May 2002

Xchanging Ins-sure Services Ltd
Error/Warning E/ Code Comman
Message Output
Situation W d
C043-ORIG-CURR = ‘JPY’ E E415 PAID THIS TIME AMOUNTS Validated
and the amount entered in MUST NOT CONTAIN DECIMAL by GUI
any of the following fields PLACES FOR ‘JPY’
includes decimal places:- when user
‘PTT Exp’ clicks ‘OK’
‘PTT Fee’ button
OR When
the user
clicks
‘NEW
EXPERT’
button.

David Willcocks 641 May 2002

Xchanging Ins-sure Services Ltd
4.42. ‘Claims Coverage Validation Check (CCVC)’ Screen

4.42.1. Screen Layout

Below is an illustration of what the CCVC screen should

look like.

Fig 4.42.1.1. ‘CCVC Screen’

David Willcocks 642 May 2002

Xchanging Ins-sure Services Ltd
4.42.2. CICS Transactions

The following CICS transactions are called by this

program (via GUI/CICS Interface Program).

Tran Program Description

s. Name
Id.
LZ24 LC0565R0 Build CCVC Screen
LZ25 LC0566R0 CCVC Screen Validation
LZ26 LC0567R0 CCVC Screen D/B Updates

4.42.3. Field/Command Derivation

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

Field Type Source

A. Fields:-

Call the CICS transaction LY01 (see Appendix C.1) – using COMMAREA C122 (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)

UCR Field C122-UCR

(This field should be protected)
XCR Field C122-XCR
(This field should be protected)
TR Field C122-TR
(This field should be protected)
OSND1 Field C122-ORIG-REF-1
(This field should be protected)
OSND2 Field C122-ORIG-REF-2
(This field should be protected)
OSND3 Field C122-ORIG-REF-3
(This field should be protected)
Peer Review Field C122-PEER-REV-IND
(This field should be protected)
Curr Bkr Field C122-ORIG-BKR
(This field should be protected)

David Willcocks 643 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Payee Bkr Field C122-PAYEE-BKR
(This field should be protected)
Paid By Cheque Field C122-PAID-BY-CHEQUE
(This field should be protected)
Broker Field C122-BKR-PRES-DATE
Presentation Date (If C122-BKR-DATE-ATTR = ‘P’, this field
should be protected)
Leader Field C122-LDR-PRES-DATE
Presentation Date (If C122-LDR-DATE-ATTR = ‘P’, this field
should be protected)
Is the Lloyd’s Radio C122-LLOYDS-LEAD-IND
Lead The Overall Buttons (If C122-SY-LEAD-ATTR = ‘P’, this field
Lead? should be protected)
Is the claim part Radio C122-BORD-IND
of a Bordereaux, a Buttons (If C122-BORD-ATTR = ‘P’, this field
recovery or a should be protected)
Coverage/Defence
Fee Settlement or
has the issue of
Coverage not yet
been determined
on this claim?
Is the Date of Loss Radio C122-DOL-IN-POL-Q
/ Date Claim Made Buttons (If C122-DOL-IN-POL-ATTR = ‘P’, this
within Policy/Cert field should be protected)
Period?
Is the claim within Radio C122-CLAIM-IN-POL-Q
available Buttons (If C122-CLM-IN-POL-ATTR = ‘P’, this
Policy/Cert Limits? field should be protected)
Is the Identity of Radio C122-CORRECT-IDENT-Q
the Buttons (If C122-CORRECT-ID-ATTR = ‘P’, this
Coverholder/Insur field should be protected)
ed/Reinsured/Ced
ant correct?
Has the correct Radio C122-DEDUCT-EXCESS-Q
Deductible/Excess Buttons (If C122-DEDUCT-EX-ATTR = ‘P’, this
been applied? field should be protected)
Does the type of Radio C122-COVERAGE-Q
coverage match Buttons (If C122-COVERAGE-ATTR = ‘P’, this
the claim? field should be protected)

David Willcocks 644 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
Cause Code? Radio C122-CAUSE-CODE-Q
Buttons (If C122-CAUSE-CODE-ATTR = ‘P’, this
field should be protected)
Has the Leader Radio C122-LEAD-AGREEMENT-Q
clearly provided Buttons (If C122-LEAD-AGREE-ATTR = ‘P’, this
agreement to field should be protected)
settle?
If this is a Special Radio C122-MKT-AGREEMENT-Q
Category claim, Buttons (If C122-MKT-AGREE-ATTR = ‘P’, this
have all the field should be protected)
agreement parties
clearly indicated
their agreement to
settle?
Policy Tick-Box C122-POLICY-DOC-IND
(If C122-POLICY-DOC-ATTR = ‘P’, this
field should be protected)
Slip Tick-Box C122-SLIP-DOC-IND
(If C122-SLIP-DOC-ATTR = ‘P’, this field
should be protected)
Cover Notes Tick-Box C122-COVER-DOC-IND
(If C122-COVER-DOC-ATTR = ‘P’, this
field should be protected)
Preliminary Loss Tick-Box C122-LOSS-DETS-DOC-IND
Details (If C122-LOSS-DETS-ATTR = ‘P’, this
field should be protected)
Other Tick-Box C122-OTHER-DOC-IND
(If C122-OTHER-DOC-ATTR = ‘P’, this
field should be protected)
B. Commands
OK Command If C122-SCREEN-MODE = ‘U’,
This button should be available
Otherwise,
This button should not be shown
CANCEL Command This button should be shown under all
circustances

David Willcocks 645 May 2002

Xchanging Ins-sure Services Ltd
Field Type Source
CLEAR FORM Command If C122-SCREEN-MODE = ‘U’,
This button should be available
Otherwise,
This button should not be shown

4.42.4. Process Description

This screen is available to the technician only if the ‘CCVC’ button is

enabled on the ‘Settlement Summary’ Screen.

The XCS business process dictates that, for every claim movement that
involves settlement, the Claims Coverage Validation Check (CCVC)
questionnaire must be completed.

This involves the technician answering various questions about the

nature and coverage of the claim – thus ensuring that the adjuster has
considered everything in processing the entry, and has recorded this for
audit purposes.

Fig 4.37.4.1. Field/Command Processing for ‘CCVC’ screen

Field / Attributes Data Type

Description
Command

A. Fields (Main Screen)

UCR Broker’s UCR. Read Only Alphanumeric

19 Characters
Alphanumeric - 19 Characters

i.e. 17 characters – separated with slashes as shown

below
X/XXXX/ XXXXXXXXXXXX
XCR XCR, for claims created on XCS CLASS. Read Only Alphanumeric
19 Characters
Alphanumeric - 19 Characters

i.e. 17 characters – separated with slashes as shown

below
X/XXXX/ XXXXXXXXXXXX

David Willcocks 646 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
TR XTR (or Brokers TR, for coupled CLASS @ Read Only Alphanumeric
Lloyd’s claims). 19 Characters
Alphanumeric - 19 Characters

i.e. 17 characters – separated with slashes as shown

below
X/XXXX/ XXXXXXXXXXXX
OSND1 Original Signing Number and Date for the first Read-Only Alpahanumeric
currency on the claim (15 chars)
N.B. For Lloyds, this is 13 numeric
OSND2 Original Signing Number and Date for the second Read-Only Alphanumeric
currency on the claim (15 chars)
N.B. For Lloyds, this is 13 numeric
OSND3 Original Signing Number and Date for the third Read-Only Alphanumeric
currency on the claim (15 chars)
N.B. For Lloyds, this is 13 numeric
Peer Review Peer Review Code for the current claim transaction Read-Only Alphanumeric
(1 Char)
Curr Bkr Current Broker Code Read-Only Alphanumeric
(4 chars)
Payee Bkr Payee Broker Code Read-Only Alphanumeric
(4 chars)
Paid By Indicates whether the current settlement transaction Read-Only Alphanumeric
Cheque is to be paid by check or not. (1 Char)
Broker The date the information the user is reviewing was Conditional 3 Numeric
Presentation presented to the broker. If direct business, this is not Fields:-
Date required – Otherwise, it is mandatory. DD/MM/CCYY

Leader The date of the last leader’s ‘ scratch’. Conditional 3 Numeric

Presentation If XCS are the delegated lead, this is not required – Fields:-
Date Otherwise, it is mandatory. DD/MM/CCYY

Is the Lloyd’s This allows XCS to determine whether or not there Mandatory Radio Buttons
Lead The are any significant time differences between
Overall Lead? presentation to the companies market and
presentation to the Lloyd’s market.

David Willcocks 647 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Is the claim A bordereaux is a collection of claims, presented on Mandatory Radio Buttons
part of a a regular basis (usually monthly), on an aggregate
Bordereaux, a basis by a coverholder or broker.
recovery or a
Coverage/Defe If the user answers ‘Yes’ to this question – the
nce Fee answer to subsequent 5 questions will
Settlement or automatically be set to ‘N/A’.
has the issue
of Coverage
not yet been
determined on
this claim?
Is the Date of Provides assurance to auditors that the adjuster has Mandatory Radio Buttons
Loss / Date checked that the DOL / DCM is within Policy
Claim Made Period.
within
Policy/Cert If the claim is part of a Bordereaux, then this
Period? should be set to ‘N/A’ automatically
Is the claim Provides assurance to auditors that adjuster has Mandatory Radio Buttons
within checked that the claim is within the Policy period.
available
Policy/Cert If the claim is part of a Bordereaux, then this
Limits? should be set to ‘N/A’ automatically
Is the Identity Provides assurance to auditors that the adjuster has Mandatory Radio Buttons
of the checked the Coverholder / Reinsured / Cedant.
Coverholder/I
nsured/Reinsu If the claim is part of a Bordereaux, then this
red/Cedant should be set to ‘N/A’ automatically
correct?
Has the correct Provides assurance to auditors that user has checked Mandatory Radio Buttons
Deductible/Ex the Deductible/Excess.
cess been
applied? If the claim is part of a Bordereaux, then this
should be set to ‘N/A’ automatically
Does the type Allows the user to indicate whether they have Mandatory Radio Buttons
of coverage checked that the coverage and claim type are
match the compatible.
claim?
If the claim is part of a Bordereaux, then this
should be set to ‘N/A’ automatically
Cause Code? Allows the user to indicate whether a Cause Code Mandatory Radio Buttons
has been entered on this claim
Has the Leader Allows the user to indicate whether lead has agreed Mandatory Radio Buttons
clearly to settle.
provided
agreement to
settle?

David Willcocks 648 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
If this is a Special Category claims include all liability claims Mandatory Radio Buttons
Special (including those on a Binder or Reinsurance),
Category Contract Frustration and Political Risks.
claim, have all
the agreement
parties clearly
indicated their
agreement to
settle?
Policy Ticked if the XCS adjuster processing the claim has Optional Tick-Box
seen this document.
Slip As above Optional Tick-Box
Cover Notes As above Optional Tick-Box
Preliminary As above Optional Tick-Box
Loss Details
Other As above Optional Tick-Box

B. Commands - (Main Screen).

David Willcocks 649 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
OK Note:- This button is only available when C122- Command
SCREEN-MODE = ‘U’ (Update).

When the user presses the ‘OK’ button, perform the

associated GUI-level validation, outlined in Section
4.42.5 (below).

If the details are valid:-

(i) Call CICS transaction LY01 (see Appendix

C.1) to validate that any details entered on
the screen are valid – using Commarea C123
(see Appendix D).

On return, check the C123-PROG-STATUS

and report any errors/warnings in the usual
way.

(ii) If no errors returned from LZ25, Call CICS

transaction LY01 (see Appendix C.1) to
update the database with the details entered
on the screen – using COMMAREA C124.
(see Appendix D).

On return, check the C124-PROG-STATUS

and report any errors/warnings in the usual
way.

(iii) If no errors returned from LZ26, return the

user the ‘Settlement Summary’ Screen.

Cancel Note:- This button is available whether C122- Command

SCREEN-MODE = ‘U’ (Update) or ‘E’ (Enquiry).

When the user presses the ‘Cancel’ button, the

claims adjuster should be returned to the
‘Settlement Summary’ screen – no validation will
be performed and no changes will be saved.

David Willcocks 650 May 2002

Xchanging Ins-sure Services Ltd
Field / Attributes Data Type
Description
Command
Reset Form Note:- This button is only available when C122-
SCREEN-MODE = ‘U’ (Update).

This will initialise all fields on the screen to the

values shown on first entry (i.e. returned by the
mainframe).

When the user presses the ‘Reset Form’ button, a

warning should be displayed – as follows:-

Are you sure you want to reset

the questionnaire ?

CANCEL OK

If the user .clicks ‘CANCEL’, no no fields should

be initialised.

If the user clicks ‘OK’, all fields should be

initialised to the values shown on first entry (i.e.
returned by the mainframe).

4.42.5. GUI-Level Validation

The following validation should be performed by the user interface

when the user presses the command indicated.

Errors should be displayed in the standard error screen format.

Note Error Message text is obtained from the Error Table, passed from
the mainframe.

Error/Warning E/ Code Comman

Message Output
Situation W d
If entered, the Broker E E693 BROKER PRESENTATION ‘OK’
Presentation Date is an DATE MUST BE A VALID
invalid date format DATE

David Willcocks 651 May 2002

Xchanging Ins-sure Services Ltd
Error/Warning E/ Code Comman
Message Output
Situation W d
If entered, the Leader E E695 LEADER PRESENTATION ‘OK’
Presentation Date is an DATE MUST BE A VALID
invalid date format DATE
The adjuster has not E E697 PLEASE PROVIDE ANSWERS ‘OK’
selected an answer to one TO ALL MANDATORY
or more questions (i.e. QUESTIONS
questions with Radio
Button answers)

Note SCR040 Scheme Canada

SCR041 Settlement Search Screen
SCR042 Settlement Search Results Screen
SCR043 Settlement Details Screen
SCR044 Expert Fees Breakdown Screen
SCR045 Advanced Search Results Screen

have all been used – DBP

David Willcocks 652 May 2002

Xchanging Ins-sure Services Ltd

Xcs Class KT Session
No ratings yet
Xcs Class KT Session
28 pages
TUEF Guide CIBIL
No ratings yet
TUEF Guide CIBIL
104 pages
Insurance Brokering System Requirements
75% (8)
Insurance Brokering System Requirements
44 pages
Genesis Data Item Dcs Handling of Data Items Acord Data Output
No ratings yet
Genesis Data Item Dcs Handling of Data Items Acord Data Output
25 pages
BROKER System Package Maintenance Guide
No ratings yet
BROKER System Package Maintenance Guide
19 pages
Insurance - 8 21 2025
No ratings yet
Insurance - 8 21 2025
2,976 pages
Maximo Change Management Guide
No ratings yet
Maximo Change Management Guide
5 pages
Domain Knowledge
No ratings yet
Domain Knowledge
27 pages
PC Assignment-4 Answers
No ratings yet
PC Assignment-4 Answers
6 pages
SAP Tcodes
No ratings yet
SAP Tcodes
47 pages
Module Changes and Testing Feedback
No ratings yet
Module Changes and Testing Feedback
6 pages
Digital Evaluation Analysis Report-1
No ratings yet
Digital Evaluation Analysis Report-1
10 pages
Web Services in Insurance Efficiency
No ratings yet
Web Services in Insurance Efficiency
26 pages
Cub It User Guide
No ratings yet
Cub It User Guide
217 pages
Monrec 80 Application User Guide Cisco
No ratings yet
Monrec 80 Application User Guide Cisco
160 pages
RDZ Search Options
No ratings yet
RDZ Search Options
74 pages
Insurance Suite Guide
100% (1)
Insurance Suite Guide
20 pages
SBI Core Banking User Guide
No ratings yet
SBI Core Banking User Guide
16 pages
Tcs Bancs For Health and Personal Accident Insurance
0% (1)
Tcs Bancs For Health and Personal Accident Insurance
4 pages
1ACC QRG+Job+Management+-+Job+Statuses
No ratings yet
1ACC QRG+Job+Management+-+Job+Statuses
1 page
Unicenter Jobtrac Management
No ratings yet
Unicenter Jobtrac Management
316 pages
SCU0 Customizing Comparison Tool Saphelp Nw74
No ratings yet
SCU0 Customizing Comparison Tool Saphelp Nw74
9 pages
03-Management of Change - Change Request Co-Ordinator
No ratings yet
03-Management of Change - Change Request Co-Ordinator
9 pages
Cash Journal Issue and Support Tools Guide
No ratings yet
Cash Journal Issue and Support Tools Guide
4 pages
Logan IT INc Insurance Services
No ratings yet
Logan IT INc Insurance Services
12 pages
Ho To Create Monitor Entries From A Transformation Routine PDF
No ratings yet
Ho To Create Monitor Entries From A Transformation Routine PDF
7 pages
ReleaseNotes PDF
No ratings yet
ReleaseNotes PDF
65 pages
Integration Manager User Guide 1 10
No ratings yet
Integration Manager User Guide 1 10
10 pages
Integration Manager User Guide PDF
No ratings yet
Integration Manager User Guide PDF
74 pages
Integration Manager-User Guide
No ratings yet
Integration Manager-User Guide
74 pages
Max Coder Application Overview
No ratings yet
Max Coder Application Overview
81 pages
CICS External Interface
No ratings yet
CICS External Interface
371 pages
Wxcce B Reporting User Guide
No ratings yet
Wxcce B Reporting User Guide
354 pages
Universal Interface - Quick User Guide
No ratings yet
Universal Interface - Quick User Guide
46 pages
Sap For Ins Claims Manage
No ratings yet
Sap For Ins Claims Manage
3 pages
TXP-TW Interface Specifications Guide
No ratings yet
TXP-TW Interface Specifications Guide
6 pages
Unit Test Script for Application Extensions
No ratings yet
Unit Test Script for Application Extensions
28 pages
Managing Policy Change Transactions
No ratings yet
Managing Policy Change Transactions
5 pages
Insurance API Integration Guide
No ratings yet
Insurance API Integration Guide
23 pages
CICS Problem Determination Guide
No ratings yet
CICS Problem Determination Guide
387 pages
CR - Hide JS Reason & Type Fields - Version 1.00 - 20250225
No ratings yet
CR - Hide JS Reason & Type Fields - Version 1.00 - 20250225
10 pages
BW ASGroupWebInterfaceAdminGuidePart2 R230
No ratings yet
BW ASGroupWebInterfaceAdminGuidePart2 R230
519 pages
Insurance Domain Knowledge For Software Professionals
No ratings yet
Insurance Domain Knowledge For Software Professionals
15 pages
KPI Implementation-A Simplified Guide Book
No ratings yet
KPI Implementation-A Simplified Guide Book
20 pages
SBWP - Business Workplace
No ratings yet
SBWP - Business Workplace
11 pages
ALL - CR - 4834 - CORE - CWISS-RAMS Coinsurer FAC Placement Integration V - 3.0
No ratings yet
ALL - CR - 4834 - CORE - CWISS-RAMS Coinsurer FAC Placement Integration V - 3.0
12 pages
Oracle Cloud Update 19D Overview Guide
No ratings yet
Oracle Cloud Update 19D Overview Guide
19 pages
Updated Set of Instructions For HO - SO - BO
No ratings yet
Updated Set of Instructions For HO - SO - BO
26 pages
Guide For Change Creation v.0.0
No ratings yet
Guide For Change Creation v.0.0
21 pages
TYBCA Project Documentation
100% (1)
TYBCA Project Documentation
25 pages
Group Health & Life Insurance Manual
No ratings yet
Group Health & Life Insurance Manual
49 pages
Sectional Title Product Update Request
No ratings yet
Sectional Title Product Update Request
2 pages
Xero Fast Track Answers
0% (4)
Xero Fast Track Answers
14 pages
BMQ Release Updates and Enhancements
No ratings yet
BMQ Release Updates and Enhancements
186 pages
(CL) (04-2019) - Notice of Replacement A&S - OG 2024-08-22 20 - 56 - 52
No ratings yet
(CL) (04-2019) - Notice of Replacement A&S - OG 2024-08-22 20 - 56 - 52
4 pages
Maximo 7.6 Feature Functionality Update
No ratings yet
Maximo 7.6 Feature Functionality Update
36 pages
T e 1729007036 Bobby and The Robin Story Powerpoint - Ver - 1
No ratings yet
T e 1729007036 Bobby and The Robin Story Powerpoint - Ver - 1
16 pages
06 - LLMIT CH 6 Feb 08 PDF
No ratings yet
06 - LLMIT CH 6 Feb 08 PDF
10 pages
A Tale of Two Feathers: KS1 Story
No ratings yet
A Tale of Two Feathers: KS1 Story
16 pages
02 - LLMIT CH 2 Feb 08
No ratings yet
02 - LLMIT CH 2 Feb 08
24 pages
05 - LLMIT CH 5 Feb 08 PDF
No ratings yet
05 - LLMIT CH 5 Feb 08 PDF
22 pages
Tech Impact on Banking Employee Performance
No ratings yet
Tech Impact on Banking Employee Performance
14 pages
Legal Principles of Insurance Contracts
No ratings yet
Legal Principles of Insurance Contracts
20 pages
01 - LLMIT CH 1 Feb 08
No ratings yet
01 - LLMIT CH 1 Feb 08
18 pages
Xero Degrees Café: Unique Dining Experience
No ratings yet
Xero Degrees Café: Unique Dining Experience
25 pages
Togaf 9 Foundation: Target Audience
No ratings yet
Togaf 9 Foundation: Target Audience
2 pages
lm1 Questions 1 2 and 6 - Amended 15.9.16
No ratings yet
lm1 Questions 1 2 and 6 - Amended 15.9.16
1 page
Seriously Cinderella Is So Annoying PDF
100% (2)
Seriously Cinderella Is So Annoying PDF
22 pages
London Matters: The Competitive Position of The London Insurance Market
No ratings yet
London Matters: The Competitive Position of The London Insurance Market
9 pages
London Market Insurance Essentials: Objective
No ratings yet
London Market Insurance Essentials: Objective
3 pages
Insurance Tackling Financial Crime
No ratings yet
Insurance Tackling Financial Crime
8 pages
Us Cons How Robotics and Cognitive Automation Will Transform The Insurance Industry
No ratings yet
Us Cons How Robotics and Cognitive Automation Will Transform The Insurance Industry
12 pages
The Great Amherst Mystery by Walter Hubbell PDF
100% (1)
The Great Amherst Mystery by Walter Hubbell PDF
228 pages
UK Insurance & Savings Market Overview
No ratings yet
UK Insurance & Savings Market Overview
36 pages
New Revenue Streams for MNOs: 5-Step Model
No ratings yet
New Revenue Streams for MNOs: 5-Step Model
10 pages
Tech Nation
No ratings yet
Tech Nation
29 pages
DS Qlik Sense Enterprise en
No ratings yet
DS Qlik Sense Enterprise en
6 pages
Understanding Algorithms and Complexity
No ratings yet
Understanding Algorithms and Complexity
19 pages
207 (A7) - A7f 9 92a02a - Front Hinged Side Door Glass
No ratings yet
207 (A7) - A7f 9 92a02a - Front Hinged Side Door Glass
3 pages
ACS800 Parameter Copy Guide
No ratings yet
ACS800 Parameter Copy Guide
3 pages
PITCHMASTIC
No ratings yet
PITCHMASTIC
8 pages
Spare Parts Manual
100% (1)
Spare Parts Manual
733 pages
Coca-Cola Rural Ad Campaign Analysis
No ratings yet
Coca-Cola Rural Ad Campaign Analysis
9 pages
Fly Ash Purchase Terms & Conditions
No ratings yet
Fly Ash Purchase Terms & Conditions
1 page
SL150 Tape Library Features & Monitoring
No ratings yet
SL150 Tape Library Features & Monitoring
14 pages
New Community Health Strategy
No ratings yet
New Community Health Strategy
31 pages
Journeys DDA PR Book
No ratings yet
Journeys DDA PR Book
43 pages
Flooring Solutions for Professionals
No ratings yet
Flooring Solutions for Professionals
1 page
Katie Bank - Google Search
No ratings yet
Katie Bank - Google Search
1 page
Extension Activity Design
100% (2)
Extension Activity Design
4 pages
PRS Exam Guide: Physics Concepts
No ratings yet
PRS Exam Guide: Physics Concepts
46 pages
Design Review Process
No ratings yet
Design Review Process
2 pages
Fast Switching Diodes 1N4148 & 1N4448
No ratings yet
Fast Switching Diodes 1N4148 & 1N4448
5 pages
Lab Report Cover Sheet Template
No ratings yet
Lab Report Cover Sheet Template
1 page
Mechanical Engineering Problem Set
100% (1)
Mechanical Engineering Problem Set
6 pages
13th International Conference of Laboratory Animal Scientists' Association - LASACON2025-1
No ratings yet
13th International Conference of Laboratory Animal Scientists' Association - LASACON2025-1
8 pages
AEFI Reporting Concise Guide Small DigitalOnly 100725
No ratings yet
AEFI Reporting Concise Guide Small DigitalOnly 100725
56 pages
Consulting's Future: Accenture's Path
No ratings yet
Consulting's Future: Accenture's Path
19 pages
Micro Matters Macro View
No ratings yet
Micro Matters Macro View
136 pages
Past Simple Verb Exercises for Students
No ratings yet
Past Simple Verb Exercises for Students
10 pages
Cars24 Proprietary Report
No ratings yet
Cars24 Proprietary Report
6 pages
The S-LANSS Pain Score: Scoring A Score of 12 or More Suggests Pain of Predominantly Neuropathic Origin
No ratings yet
The S-LANSS Pain Score: Scoring A Score of 12 or More Suggests Pain of Predominantly Neuropathic Origin
1 page
Fun ITF
No ratings yet
Fun ITF
5 pages
Textile Specialties Formulation List - ZDHC MRSL V 1.1 Dec 2015 (June 2018)
83% (6)
Textile Specialties Formulation List - ZDHC MRSL V 1.1 Dec 2015 (June 2018)
27 pages
2.5MB RAM Upgrade for 1040ST
No ratings yet
2.5MB RAM Upgrade for 1040ST
6 pages
Cost of Capital
No ratings yet
Cost of Capital
37 pages
Watcher (Comics)
No ratings yet
Watcher (Comics)
5 pages