Enhance SEAT infrastructure to capture and test delivery

SAR-2007-10-03-0018

HOW TO GUIDE

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means, for any purpose,
without the express written permission of TEMENOS HEADQUARTERS SA.

COPYRIGHT 2007 - 2008 TEMENOS HEADQUARTERS SA. All rights reserved.

 USER GUIDE

Document History:

Author : Suresh SP Version : 1.1 Date : 01.12.07

Author : Suresh SP Version : 1.2 Date : 23.01.08

Comments:

Enhancement in seat infrastructure to capture and test the end result of delivery messages.

2 SEAT | Design And Development

 USER GUIDE

Table of Contents

Document History:.................................................................................................................. 2
Table of Contents.................................................................................................................... 3
1.1 Introduction....................................................................................................................... 4
1.2 OVERVIEW......................................................................................................................... 4
1.2.1 Functional overview...................................................................................................... 4
1.2.2 Technical overview....................................................................................................... 4
1.3 SETTING UP OF THE SYSTEM.........................................................................................5
1.3.1 HOW TO SET THE SEAT............................................................................................5
1.3.1.1 RECORD............................................................................................................... 5
1.3.1.2 TEST...................................................................................................................... 5
1.3.2 SETTING UP OF SEAT.SCRIPT.RESULT.FILES........................................................5
1.4 NEW CONCAT FILE CREATED........................................................................................6
1.4.1 SEAT.HOLD.REPORT.IDS.......................................................................................... 6
1.5 NEW TABLE CREATED.................................................................................................... 6
1.5.1 SEAT.SCRIPT.FORMAT.OUTPUT..............................................................................6
1.6 MODIFICATION IN SEAT.SCRIPT.RESULT.FILES..........................................................8
1.6.1 SEAT.SCRIPT.RESULT.FILES....................................................................................8
1.7 FLOW DIAGRAMS............................................................................................................. 9
1.7.1 FLOW CHART [RECORD OPTION].............................................................................9
1.7.1.1 SEAT.CREATE.CONCAT.IDS [ROUTINE FLOW].................................................9
1.7.1.2 SEAT.CREATE.FO.VAL.RECORD [ROUTINE FLOW].......................................10
1.7.2 FLOW CHART [TEST OPTION].................................................................................11
1.7.2.1 SEAT.UPDATE.FO.VAL.TEST [ROUTINE FLOW]..............................................11
1.8 SCREEN SHOTS FOR REFERENCE..............................................................................12

3 SEAT | Design And Development

 USER GUIDE

1.1 Introduction

 The objective of this development is to check the accuracy and

integrity of the end results of delivery messages.
 The output messages are captured after the delivery service
formats the message in unformatted stage.
 The services PRINT.OUT and SWIFT.OUT are started in auto
mode when the upload is initiated.
 The message outputs are read from the file
F.DE.O.MSG.ADVICE if it is a PRINT message and from
F.DE.O.MSG.SWIFT if it is a SWIFT message.
 The file SEAT.SCRIPT.FORMAT.OUTPUT is used to store the
expected and actual from the end result of delivery messages.
 The result is also updated in SEAT.SCRIPT.RESULT.FILES and
SEAT.RESULTS.
 For the inward delivery messages only the SEAT.RESULTS gets
updated.

1.2 OVERVIEW
1.2.1 Functional overview
 To capture the delivery message and check the end results of
delivery messages.

1.2.2 Technical overview

 The end result of delivery messages is captured and the
expected values are stored in
SEAT.SCRIPT.FORMAT.OUTPUT record during record option.
 While running in test option the end result of delivery message
are captured again and the actual values for the corresponding
position are populated in the SEAT.SCRIPT.FORMAT.OUTPUT
record.
 If there is any mismatch between the actual values and expected
values the ERROR field is populated in
SEAT.SCRIPT.FORMAT.OUTPUT,
SEAT.SCRIPT.RESULT.FILES and SEAT.RESULTS.

4 SEAT | Design And Development

 USER GUIDE

1.3 SETTING UP OF THE SYSTEM

1.3.1 HOW TO SET THE SEAT:

SEAT is turned on using the OP.CONSOLE field in SPF,

1.3.1.1 RECORD
While uploading the script with RECORD option and once a delivery message is formatted
the header fields, line and column details and expected values are populated in
SEAT.SCRIPT.FORMAT.OUTPUT record.
The FORMAT.OUTPUT field in SEAT.SCRIPT.RESULT.FILES record is updated with the
SEAT.SCRIPT.FORMAT.OUTPUT id.
Backups of SEAT.SCRIPT.RESULT.FILES record and SEAT.SCRIPT.FORMAT.OUTPUT
record should be taken after running with RECORD option.
During COB, the COB services has to be started before starting the formatting services

1.3.1.2 TEST
The backups of SEAT.SCRIPT.RESULT.FILES record and
SEAT.SCRIPT.FORMAT.OUTPUT record taken after running the RECORD option should be
included before running with TEST option.
While uploading the script with TEST option and once a delivery message is formatted the
actual values and the results are populated in SEAT.SCRIPT.FORMAT.OUTPUT record.
The results are also updated in SEAT.SCRIPT.RESULT.FILES record and SEAT.RESULTS
record accordingly.
For checking inward delivery messages get the value of OFS.SOURCE field from the
corresponding DE.MESSAGE record, then open the corresponding OFS.SOURCE record
and set the field MAINT.MSG.DETS to ‘Y’.

1.3.2 SETTING UP OF SEAT.SCRIPT.RESULT.FILES

 The COB.DATE field in SEAT.SCRIPT.RESULT.FILES record should be set

as PRINT.OUT or SWIFT.OUT, this field can be multivalued and both
PRINT.OUT and SWIFT.OUT can be mentioned.
 If the COB.DATE field is set as PRINT.OUT, then for this particular script only
the PRINT messages are checked.
 If the COB.DATE field is set as SWIFT.OUT, then for this particular script only
the SWIFT messages are checked.
 If the COB.DATE field is multivalued and both PRINT.OUT and SWIFT.OUT
is set, then for that particular script both print messages and swift messages
are checked.
 The COB.DATE field is a mandatory for this enhancement.

5 SEAT | Design And Development

 USER GUIDE

1.4 NEW CONCAT FILE CREATED

1.4.1 SEAT.HOLD.REPORT.IDS

 A new concat file has been created as a part of this enhancement.

 This concat file gets updated only if the COB.DATE field in
SEAT.SCRIPT.RESULT.FILES record contain either PRINT.OUT or
SWIFT.OUT or even both.
 The routine SEAT.CREATE.CONCAT.IDS updates this concat file while
running in RECORD option.
 The id of this concat file is the TRANSACTION REFERENCE.
 This concat file contains the script id and the corresponding
SEAT.SCRIPT.FORMAT.OUTPUT ids during online.
 This concat file contains the SEAT.RESULTS id and the corresponding
SEAT.SCRIPT.FORMAT.OUTPUT ids during COB.
 Example showing the content of SEAT.HOLD.REPORT.IDS record,
 SCRPT06150062842 - LD0033599977*320*50042*20001130 [FOR ONLINE]
 BNK/LD.END.OF.DAY*LD.END.OF.DAY.4*LD0033599977*20001204 -
LD0033599977*900*50042*20001204 [FOR COB]

1.5 NEW TABLE CREATED

1.5.1 SEAT.SCRIPT.FORMAT.OUTPUT

The table SEAT.SCRIPT.FORMAT.OUTPUT is created with the ID as follows,

TRANSACTION.REFERENCE*MESSAGE.TYPE*CUSTOMER*DATE. This id is formed from
the DE.O.HEADER record.
Example: LD0033599977*320*50042*20001130

Table Name SEAT.SCRIPT.FORMAT.OUTPUT

Description To check the expected and actual values generated for the
particular delivery messages.

Product SEAT

Classification INT

Field Name Type Description

1.1.1 GB DESCRIPTION A Description of the purpose of the script. This should cover

6 SEAT | Design And Development

 USER GUIDE

the every purpose for which this script is created. Is

updated from the SEAT.SCRIPTS for that particular script
id.

2 APPLICATION A The Application to which input is done. This value is also

obtained from SEAT.SCRIPTS for that particular script id.

3 REFERENCE A The Transaction id for that particular script. Obtained from

SEAT.SCRIPTS

4 FIELD .DETAILS A The fields names from the ENQUIRIES that are displayed
in the report. The OFS.OUT.MSG has the values for this
application.

5 XX<LINE.AND.COLMN
A For print messages this field will contain the details of line
and column and in case of swift messages it will contain
the tag no.
If there is no need for this position to checked then this
field and the corresponding expected result fields can be
removed before running it in TEST mode

6 XX-ACTUAL.VALUE A The actual values for the corresponding line and column
or tag.no are stored here. These values are populated
during the upload, when SEAT is with ‘TEST’ option.

7 XX-EXPECTED.VALUE A The expected values for the corresponding line and

column or tag.no are stored here. These values are
populated during the upload, when the SEAT is with
‘RECORD’ option.

8 XX>RESULT A This field has the value as ‘ERROR’, when there is any
mismatch between the expected and actual values. If
there is no mismatch between the expected and actual
value this field will be null.

9 DEFAULT.VALUE A This field can have the value as ‘Y’ or null. When the
value is set to ‘Y’ the values of the field
EXPECTED.VALUE are copied to the values of
ACTUAL.VALUE.

10 OVERALL.RESULT A This field is populated with ‘ERROR’, when any of the

RESULTS field in the multi value set is populated with the
total number of times the error has occurred , If there is no
mismatch between the expected and actual then this field
is populated as ‘0’.

The Layout of SEAT.SCRIPT.FORMAT.OUTPUT is as under:

Table 1 – SEAT.SCRIPT.FORMAT.OUTPUT

7 SEAT | Design And Development

 USER GUIDE

1.6 MODIFICATION IN SEAT.SCRIPT.RESULT.FILES

1.6.1 SEAT.SCRIPT.RESULT.FILES
The table SEAT.SCRIPT.RESULT.FILES is modified to show the
SEAT.SCRIPT.FORMAT.OUTPUT file ID in the field ‘FORMAT.OUTPUT’ and
the status of the file SEAT.SCRIPT.FORMAT.OUPTUT in the field
‘FORMAT.RESULT’. The ID should be the same as SCRIPT.ID from
SEAT.SCRIPTS
(E.g. SCRPT03070715079-11)
Below are the field that is used for this enhancement.

15 XX- This field holds the SEAT.SCRIPT.FORMAT.OUTPUT ID

XX<FORMAT.OUTPUT E.g. MD0033522222*900*50044*20001130

If the status of the field ‘RESULT’ in format output file is set as

16
‘ERROR’, then the ‘FORMAT.RESULT’ field should also be
XX>XX>FORMAT.RESU
updated as
LT
‘ERROR’. Else this field will be null.

17 OVERALL.RESULT Stores the overall result. Contains overall error count.

Table 2 - SEAT.SCRIPT.RESULT.FILES

8 SEAT | Design And Development

 USER GUIDE

1.7 FLOW DIAGRAMS

1.7.1 FLOW CHART [RECORD OPTION]
1.7.1.1 SEAT.CREATE.CONCAT.IDS [ROUTINE FLOW]

SEAT.TEST

SEAT.TEST.RUN

SEAT.UPLOAD.SCRIPT

T.SEAT

CALL SEAT.CREATE.CONCAT.IDS

UPDATES THE CONCAT FILE SEAT.HOLD.REPORT.IDS

9 SEAT | Design And Development

 USER GUIDE

1.7.1.2 SEAT.CREATE.FO.VAL.RECORD [ROUTINE FLOW]

START THE SERVICE ‘SEAT.INJECTOR’ DURING ONLINE AND ‘COB’ W

START THE SERVICE PRINT.OUT AND SWIFT.OUT FOR FORMATTING TH

DE.OUTWARD

CALLS SEAT.CREATE.FO.VAL.RECORD WHEN OP.CONSOLE FIELD IN S

UPDATES THE LINE AND COLOMN, EXPECTED VALUE FIELDS

UPDATES
IN SEAT.SCRIPT.FORMAT.OUTPUT
THE FORMAT.OUTPUT FIELDRE
IN

10 SEAT | Design And Development

 USER GUIDE

1.7.2 FLOW CHART [TEST OPTION]

1.7.2.1 SEAT.UPDATE.FO.VAL.TEST [ROUTINE FLOW]

SEAT.TEST

SEAT.TEST.RUN

START THE SERVICE ‘SEAT.INJECTOR’ DURING ONLINE AND ‘COB’

START THE SERVICE (PRINT.OUT AND SWIFT.OUT) OR (SWIFT.IN) FOR FORMATTING THE DEL

DE.OUTWARD OR DE.INWARD

CALLS SEAT.UPDATE.FO.VAL.TEST WHEN OP.CONSOLE FIELD IN

DE.OUTWARD DE.INWAR

UPDATE
UPDATES
THE ACTUAL
THE FORMAT.RESULT
VALUE FIELD INFIELD
SEAT.SCRIPT.FORMAT.OUTPUT
IN SEAT.SCRIPT.FORMAT.OUTPUT
RECORDRECORD
UPDATES
FOR EACH
THE

11 SEAT | Design And Development

 USER GUIDE

1.8 SCREEN SHOTS FOR REFERENCE

SEAT.SCRIPT.FORMAT.OUTPUT updated when OP.CONSOLE field in SPF is set as

RECORD

Application field contain the

application name.

Reference field contains the

SCRIPT id.

Line and Column field contains

the line number and indent
details.

After uploading with record

option the only the expected
values are populated.

12 SEAT | Design And Development

 USER GUIDE

SEAT.SCRIPT.RESULT.FILES updated when OP.CONSOLE field in SPF is set as

RECORD

After uploading with

record option only the
FORMAT.OUTPUT field
is updated for the
corresponding
COB.DATE field.

13 SEAT | Design And Development

 USER GUIDE

SEAT.SCRIPT.FORMAT.OUTPUT updated when OP.CONSOLE field in SPF is set as

TEST.

Error field is
updated when
there is a
mismatch
between actual
value and
expected value.

Error field will

not be updated
when there is no
mismatch
between actual
value and
expected value.

Line and Column

field contains
the line number
and indent
details.

14 SEAT | Design And Development

 USER GUIDE

SEAT.SCRIPT.FORMAT.OUTPUT updated when OP.CONSOLE field in SPF is set as

TEST.

The overall
result field
indicating the
total number of
errors that has
occurred in this
record.

15 SEAT | Design And Development

 USER GUIDE

SEAT.SCRIPT.FORMAT.OUPUT updated when OP.CONSOLE field in SPF is set as

TEST and the delivery message is a SWIFT message.

For SWIFT
messages the
LINE AND
COLUMN field
will contain the
tag number.

SEAT.SCRIPT.RESULT.FILES updated when OP.CONSOLE field in SPF is set as TEST.

16 SEAT | Design And Development

 USER GUIDE

FORMAT.RESULT
field in
SEAT.SCRIPT.RESUL
T.FILES is updated as
‘ERROR’ if there is an
error in
SEAT.SCRIPT.FORM
AT.OUTPUT record
for the corresponding
FORMAT.OUTPUT
field.

SEAT.RESULTS updated when OP.CONSOLE field in SPF is set as TEST.

17 SEAT | Design And Development

 USER GUIDE

The result field in SEAT.RESULTS

record is updated as ‘0’ when
there is no error in corresponding
SEAT.SCRIPT.FORMAT.OUTPUT
record.

The result field in SEAT.RESULTS

record is updated as ‘1’ when
there is an error in corresponding
SEAT.SCRIPT.FORMAT.OUTPUT
record and for each error the
fields REASON, ACTUAL and
EXPECTED are multivalued and
populated according with relevant
details.

DE.I.HEADER record after sending an inward message and formatting the message by
running the service SWIFT.IN.

18 SEAT | Design And Development

 USER GUIDE

A FUNDS.TRANSFER record that gets created once the INWARD delivery message is
formatted.

19 SEAT | Design And Development

 USER GUIDE

OFS.REQUEST.DETAIL record that gets updated for the inward delivery message.

20 SEAT | Design And Development

 USER GUIDE

The above delivery message

contains error.

SEAT.RESULTS record that gets updated for the inward delivery messages.
The id of SEAT.RESULTS record is the same as OFS.REQUEST.DETAIL id.

The id of
SEAT.RESULTS
is the same as
ORD id.

21 SEAT | Design And Development