how to test delivery updates

8/7/2019 How to Test Delivery updates

1/21

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.

Enhance SEAT infrastructure to capture and test delivery

SAR-2007-10-03-0018

HOW TO GUIDE


2/21

SEAT | Design And Development2

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.


3/21


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] ................................ ................................ ..............111.7.2.1 SEAT.UPDATE.FO.VAL.TEST [ROUTINE FLOW] ................................ ............ 11

1.8 SCREEN SHOTS FOR REFERENCE ................................ ................................ ............ 12


4/21


USER GUIDE

1.1 Introduction

The objective of this development is to check the accuracy andintegrity of the end results of delivery messages.

The output messages are captured after the delivery serviceformats the message in unformatted stage.

The services PRINT.OUT and SWIFT.OUT are started in automode when the upload is initiated.

The message outputs are read from the fileF.DE.O.MSG.ADVICE if it is a PRINT message and fromF.DE.O.MSG.SWIFT if it is a SWIFT message.

The file SEAT.SCRIPT.FORMAT.OUTPUT is used to store theexpected 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 result s ofdelivery messages.

1.2.2 Technical overview

The end result of delivery messages is captured and theexpected values are stored inSEAT.SCRIPT.FORMAT.OUTPUT record during record option.

While running in test option the end result of delivery messageare captured again and the actual values for the correspondingposition are populated in the SEAT.SCRIPT.FORMAT.OUTPUTrecord.

If there is any mismatch between the actual values and expectedvalues the ERROR field is populated in

SEAT.SCRIPT.FORMAT.OUTPUT,SEAT.SCRIPT.RESULT.FILES and SEAT.RESULTS.


5/21


USER GUIDE

1.3 SETTING UP OF THE SYSTEM

1.3.1 HOW TO SETTHE 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 formattedthe header fields, line and column details and expected values are populated inSEAT.SCRIPT.FORMAT.OUTPUT record.

The FORMAT.OUTPUT field in SEAT.SCRIPT.RESULT.FILES record is updated with theSEAT.SCRIPT.FORMAT.OUTPUT id.

Backups of SEAT.SCRIPT.RESULT.FILES record and SEAT.SCRIPT.FORMAT.OUTPUTrecord 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 andSEAT.SCRIPT.FORMAT.OUTPUT record taken after running the RECORD option should beincluded before running with TEST option.

While uploading the script with TEST option and once a delivery message is formatted theactual 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.RESULTSrecord accordingly.

For checking inward delivery messages get the value of OFS.SOURCE field from thecorresponding DE.MESSAGE record, then open the corresponding OFS.SOURCE recordand set the f ield 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 setas PRINT.OUT or SWIFT.OUT, this field can be multivalued and bothPRINT.OUT and SWIFT.OUT can be mentioned.

If the COB.DATE field is set as PRINT.OUT, then for this particular script onlythe PRINT messages are checked.

If the COB.DATE field is set as SWIFT.OUT, then for this particular script onlythe SWIFT messages are checked.

If the COB.DATE field is multivalued and both PRINT.OUT and SWIFT.OUTis set, then for that particular script both print messages and swift messagesare checked.

The COB.DATE field is a mandatory for this enhancement.


6/21


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 inSEAT.SCRIPT.RESULT.FILES record contain either PRINT.OUT orSWIFT.OUT or even both.

The routine SEAT.CREATE.CONCAT.IDS updates this concat file whilerunning in RECORD option.

The id of this concat file is the TRANSACTION REFERENCE.

This concat file contains the script id and the correspondingSEAT.SCRIPT.FORMAT.OUTPUT ids during online.

This concat file contains the SEAT.RESULTS id and the correspondingSEAT.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*2000 1204 -LD0033599977*900*50042*20001204 [FOR COB]

1.5 NEW TABLE CREATED1.5.1 SEAT.SCRIPT.FORMAT.OUTPUT

The table SEAT.SCRIPT.FORMAT.OUTPUTis created with theID as follows,

TRANSACTION.REFERENCE*MESSAGE.TYPE*CUSTOMER*DATE. This id is formed fromthe 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 theparticular delivery messages.

Product SEAT

Classification INT

Field Name Type Description


7/21


8/21


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 fieldFORMAT.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-XXXX>FORMAT.RESULT

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

ERROR, then the FORMAT.RESULT field should also be updated as

ERROR. Else this field will be null.

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

Table 2 - SEAT.SCRIPT.RESULT.FILES


9/21


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 CONCATFILE

SEAT.HOLD.REPORT.IDS


10/21


USER GUIDE

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

STARTTHE SERVICE PRINT.OUTAND SWIFT.OUT FOR

FORMATTING THE DELIVERYMESSAGES

DE.OUTWARD

CALLS SEAT.CREATE.FO.VAL.RECORDWHEN OP.CONSOLE FIELD IN SPF IS

SET AS RECORD

UPDATES THE LINE ANDCOLOMN, EXPECTED VALUE

FIELDS INSEAT.SCRIPT.FORMAT.OUTPUT

RECORD

UPDATES THEFORMAT.OUTPUT FIELD IN

SEAT.SCRIPT.RESULT.FILESRECORD

STARTTHE SERVICE SEAT.INJECTOR DURING ONLINE

AND COB WHILE RUNNING COB .


11/21


USER GUIDE

1.7.2 FLOW CHART [TEST OPTION]

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

STARTTHE SERVICE (PRINT.OUTAND SWIFT.OUT) OR (SWIFT.IN)

FOR FORMATTING THE DELIVERYMESSAGES BOTH OUTWARD OR

INWARD

DE.OUTWARD ORDE.INWARD

CALLS SEAT.UPDATE.FO.VAL.TEST WHENOP.CONSOLE FIELD IN SPF IS SET AS TEST

UPDATE THE ACTUAL

VALUE FIELD INSEAT.SCRIPT.FORMAT.

OUTPUT RECORD

UPDATES THE

FORMAT.RESULT FIELD INSEAT.SCRIPT.FORMAT.OUTPUT

RECORD FOR EACHCORRESPONDING

FORMAT.OUTPUT FIELD

UPDATES THE

SEAT.RESULTSRECORD

SEAT.TEST

SEAT.TEST.RUN

STARTTHE SERVICE SEAT.INJECTOR DURING

ONLINE AND COB WHILE RUNNING COB .

DE.OUTWARD DE.INWARD


12/21


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

Reference field contains theSCRIPT id.

Line and Column field containsthe line number and indentdetails.

After uploading with record optionthe only the expected values are

populated.


13/21


14/21


USER GUIDE

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

Error field isupdated when

there is amismatchbetween actualvalue and

expected value.

Error field willnot be updatedwhen there is no

mismatchbetween actualvalue andexpected value.

Line andColumn fieldcontains the linenumber and

indent details.


15/21


USER GUIDE

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

The overallresult field

indicating thetotal number oferrors that hasoccurred in

this record.


16/21


USER GUIDE

SEAT.SCRIPT.FORMAT.OUPUT updated whenOP.CONSOLE field in SPF is set asTEST and the delivery message is a SWIFTmessage.

For SWIFTmessages theLINE ANDCOLUMN fieldwill contain the

tag number.


17/21


USER GUIDE

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

FORMAT.RESULTfield in

SEAT.SCRIPT.RESULT.FILES is updated asERROR if there is anerror inSEAT.SCRIPT.FORMAT.OUTPUT recordfor the correspondingFORMAT.OUTPUT

field.


18/21


USER GUIDE

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

The result field in SEAT.RESULTSrecord is updated as 0 when

there is no error in correspondingSEAT.SCRIPT.FORMAT.OUTPUTrecord.

The result field in SEAT.RESULTSrecord is updated as 1 whenthere is an error in correspondingSEAT.SCRIPT.FORMAT.OUTPUTrecord and for each error thefields REASON, ACTUAL andEXPECTED are multivalued andpopulated according with relevantdetails.


19/21


USER GUIDE

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


20/21


USER GUIDE

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


21/21

USER GUIDE

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

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 above delivery messagecontains error.

The id ofSEAT.RESULTS

is the same asORD id.

how to test delivery updates

Documents