Scribd
Upload
226 views24 pages

CLR & SHR - Master

The document discusses the process of inward delivery in the T24 banking system. When a message comes in through an interface like SWIFT, tSS generates a unique delivery ID and record. It identifies the carrier and stores the message in the unformatted queue. The formatting routine then extracts the carrier information, formats the message based on its type, and either calls the default funds transfer routine or places it in the appropriate application queue. The message is then processed by calling OFS.GLOBUS.MANAGER to update the relevant application.

Uploaded by

sangavi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
226 views24 pages

CLR & SHR - Master

The document discusses the process of inward delivery in the T24 banking system. When a message comes in through an interface like SWIFT, tSS generates a unique delivery ID and record. It identifies the carrier and stores the message in the unformatted queue. The formatting routine then extracts the carrier information, formats the message based on its type, and either calls the default funds transfer routine or places it in the appropriate application queue. The message is then processed by calling OFS.GLOBUS.MANAGER to update the relevant application.

Uploaded by

sangavi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 24

INWARD DELIVERY

Objectives

After completing this learning unit/course, you will be able to:

 Understand the routines involved in Inward delivery


 Understand the flow of inward delivery
 Explain how an inward message coming into T24 is processed

Slide 2
INWARD DELIVERY

INWARD DELIVERY

Slide 3
Inward Delivery - Overview

Interface tSS Raise Transactions through


Call DE.INWARD
OFS.GLOBUS.MANAGER

Start Inward Delivery Service FT LC SC .….


e.g. BNK/SWIFT.IN

Slide 4
DE.MESSAGE

 This table defines the contents of each basic Message Type.

 It lists the fields, describes them as single or multi value, and states
whether each field is mandatory or optional.

 The ID chosen for each Message Type should, where possible,


conform to a SWIFT message type, defined in the SWIFT manual

 SWIFT Range: 100 - 999 (ID in DE.MESSAGE)

 For eg: If you wanted to create a record to print a cheque, then its ID in
DE.MESSAGE should be outside the SWIFT ID range, i.e. outside the
range 100 - 999

Slide 5
DE.MESSAGE

Slide 6
tSS

What does tSS do ?

 Generate the unique delivery ID for the message (starting with R)


(e.g. R20070625-000270841801)

 Identify the Carrier

 Create a record in DE.I.HEADER, with the delivery ID as the record ID

 Store the ID in a common file called an ACTIVATION file


F.<Service ID>.LIST
(e.g. F.SWIFT.IN.LIST)

 Store the message in the Unformatted Queue (F.DE.I.MSG)

Slide 7
Internal working of tSS
Attach formatter to append
DECARRIER=SWIFT

SWIFT Start tSS process


message

OFS.BULK.MANAGER
TCServer receives a message

OFS.PROCESS.MANAGER

OFS.DE.REQUEST

OFS.DE.PROCESSING

ID written to -
F.SWIFT.IN.LIST
Msg written to - F.DE.I.MSG

Slide 8
Sample SWIFT message that tSS receives

DECARRIER=SWIFT,{1:F01BARCGB22XXXX.SN...ISN.}{2:I103DEM
OGBPXAXXXN}{3:{108:xxxxx}}{4:<Cr><Lf>:20:BARC3600184<Cr><
Lf>:23B:CRED<Cr><Lf>:32A:070824GBP1000,00<Cr><Lf>:33B:GB
P1000,00<Cr><Lf>:50K:RAM<Cr><Lf>MOGAPPAIR<Cr><Lf>:53B:/D
/23701<Cr><Lf>:59:SUJOY
GHOSH<Cr><Lf>:71A:SHA<Cr><Lf>:72:/REC/TO SUJOY
ACCOUNT<Cr><Lf>-}

Slide 9
Illustration - Inward SWIFT

Slide 10
Illustration - F.SWIFT.IN.LIST

Slide 11
Illustration - DE.I.HEADER

Slide 12
Illustration - Configure TSM

Slide 13
Illustration - Configure service SWIFT.IN

Slide 14
Illustration - Start the service

Slide 15
Illustration - TSA.STATUS

Slide 16
Illustration - Inward SWIFT

Slide 17
Illustration - Inward SWIFT

Slide 18
FT record created - Message received successfully

Slide 19
DE.INWARD - Working

Extract Carrier information from DE.I.HEADER record for the particular Delivery ID

Call the appropriate Formatting Routine - DE.I.FORMAT.<CARRIER>.MESSAGE


(e.g. DE.I.FORMAT.SWIFT.MESSAGE)

Read corresponding DE.MESSAGE record for the particular message type.


Is there an APPLICATION QUEUE specified?

NO YES

If Application Queue is ‘’ (NULL)


then the application is defaulted to Place the formatted messages in the following
FT (FUNDS.TRANSFER). The queue F.DE.I.MSG.<Application.Queue>
message is not stored in any (e.g. F.DE.I.MSG.LC
queue
Call the routine
<APPLICATION.QUEUE>.INWARD
Call the default routine specified in (e.g. LC.INWARD)
the field INWARD.OFS.ROUTINE
of DE.MESSAGE record Call the default routine specified in the field
INWARD.OFS.ROUTINE of DE.MESSAGE
record

Call OFS.GLOBUS.MANAGER to update the corresponding application

Slide 20
Quiz

Slide 21
Summary

 In this learning unit, you learnt about Inward Delivery in T24

 You will now be able to


 Understand the routines involved in Inward delivery
 Understand the flow of inward delivery
 Explain how an inward message coming into T24 is processed

Slide 22
Thank You
Authoring Contributions:
Sujoy Ghosh (First Edition, 2008) – Temenos India Private Ltd.

Thankful Acknowledgements:
Temenos Corporate Training Team

Slide 24

You might also like