Delivery Module

• Introduction
• Let T24 producing SWIFT messages without releasing them outside
• How to resubmit an advice
• How to check errors
• How to amend a SWIFT message after mapping but before releasing to SWIFT

Introduction

The DE- delivery module is able to reflect all financial transactions or financial events through delivery messages. A delivery message can be a SWIFT / SIC / SIT SECOM / SEPA / or any other carrier message, a printed advice, etc…

Each T24 application (FX, MM, SC, DX,…) has an access to the delivery layer and feeds a common file called HANDOFF. Some applications are providing more flexibility in linking messages to specific events: This relates more to recent modules (Swaps, Derivatives,…) and is known as “soft delivery” in T24 language.

Example of Soft Delivery Application:

   Delivery Business Model for DX module

Let T24 producing SWIFT messages without releasing them outside

In DE.DISP.CONTROL, create a record that contains the status “HOLD” in field 5. Record key is free.

Example:

   STATUS.KEY........ 50001
 1. 1 FIELD.NAME..... MESSAGE.TYPE
 2. 1 OPERAND........ EQUAL
 3. 1 CONDITION...... 360
 4. 1 FIELD.POS...... 1
 5 STATUS............ HOLD

How to resubmit an advice

1. The classic way: take the delivery ID in input with DE.O.HEADER and change field 32.1 MSG.DISPOSITION to put “RES” then authorise.

2. The alternative way: **Take the delivery ref. (ex. D20100111000125186200) from DE.O.HEADER

• Under Jbase prompt, enter:

ED F.DE.O.KEYLIST D20100111000125186200

• Insert the key on line one:

1>D20100111000125186200

• Save + quit (FI)

As long as MAPPING + FORMATTING phantoms are running, this will resubmit the advice to the formatting process.

Note that HANDOFF routines are not triggered with this resubmit. This simply allows to check DE.FORMAT.PRINT, DE.FORMAT.SWIFT or DE.TRANSLATION updates

How to check errors

DE.MM.DISPLAY will show various steps + processed / repaired messages. If you have used the F.DE.O.KEYLIST alternative way to resubmit an advice, it may remain in the error queue until you manually delete it from F.DE.O.REPAIR which contains all id’s in repair.

How to amend a SWIFT after mapping but before releasing to SWIFT network

Such an action should just NEVER be done in a production environment of course. Alterring a message should only be done in a the dedicated SWIFT application (such as STELINK, etc…) which records all changes to fix an NACK message. Now, if you need to amend a message for testing purpose:

Take the delivery ref. (ex. D20100111000125186200) from DE.O.HEADER

 SELECT F.DE.O.MSG.SWIFT LIKE "D20100111000125186200..." 
then
JED F.DE.O.MSG.SWIFT

then you can amend the message itself + save (FI).