DELIVERY

OBJECTIVES

 Understand the Delivery process

 Setup a message and message details and
status
 How to generate and format messages for
different carriers
 Adding and Directing to addresses
 Controlling and Repairing messages
 Adding Addresses for Multiple Carriers
 Directing Messages to addresses and
carriers
 Setting up of different layouts
 Soft Delivery
 Inward Processing
 Delivery - Enquiries
TABLES TO SETUP MESSAGE

 DE.MESSAGE
 DE.MAPPING
 DE.FORMAT.SWIFT
 DE.FORMAT.PRINT
 DE.TRANSLATION
 DE.PRODUCT
 DE.ADDRESS
 DE.CARRIER
 DE.INTERFACE
OVERVIEW

T
GLOBUS BANK D e
l
e e
Other bank
x
Funds
Transfer
l S
I W
I
F

v T
Customer
Customer names P
and addresses e r
i
r n
t
y
OUTWARD MESSAGE PROCESSING

Banking Application

Handoff

Mapping

Formatting

Carrier Control

SWIFT PRINT TELEX

DE.MESSAGE

Used to define the fields and their attributes, required for a

Message.
 DE.MESSAGE contd…

Contains fields to input the INWARD processing related routine and version
Field TRANSLATION if set to Y, allows us to define DE.PRODUCT in
Languages other than GB else, if NO only format allowed is GB (This is
especially for DE.FORMAT.PRINT)
Define field names for use in Mapping and Formatting
Define field characteristics
DE.MAPPING
Used to specify the position from which, values for the fields defined in
DE.MESSAGE, should be picked up from HANDOFF, to apply in the
message to be produced.
DE.MAPPING contd…

Contains field to input the routine name to fulfill user requirement, i.e., user
routine

 Defines location of data which will be used in messages e.g. 1.65

 Links field names from DE.MESSAGE to the Handoff File
 Field names can be used to format message types e.g. SWIFT
Formatting using DE.FORMAT.XXXX

 DE.FORMAT.XXXX where XXXX is the carrier e.g.

PRINT, SWIFT, TELEX

 Allow formatting of text and data

- sequence
- language ( Excluding Swift)
- position on page
 DE.FORMAT.PRINT
Used to define the Layout format, in which the message has to
be printed through PRINT carrier, with appropriate conversion
and calculation.
Key Fields in DE.FORMAT.PRINT
Field No & Name Description
2. FORM TYPE Defines form set up e.g. Advice
as defined in DE.FORM.TYPE
3.X LINE(S) Specifies actual or relative line on which
to print field e.g. 11 or +n
8.x FIELD/”TEXT” Name of field to be displayed or
text, which is input as “Text”
10.x MASK Controls formatting of data e.g.
DATE DDMMYY
11.x CALCULATION For calculations and totals on
relevant fields
12.x DEPENDENT.ON Sets conditions for output
DE.FORMAT.PRINT
Conditional Text

Shows specific text or data only when a condition

has been met
There is no limit to the number of conditions
DE.FORMAT.PRINT
Duplicate or Copy text

 Copy or duplicate advices are available within

T24

 Copies only relate to printed advices

 Duplicates are available when messages have

been re-submitted
DE.FORMAT.PRINT Conversions

 Linking data from the record to another Application

 Change the date into a different format

 Format the currency into the correct format with

the required decimal places
DE.FORMAT.PRINT Calculations

 Totals can be added to advices using

calculations

 Fields can also be added to the advice which

is
the totals of certain fields within the record
GENERATING A DELIVERY MESSAGE

Enter the details for the transaction

SAMPLE PRINT MESSAGE
WORKSHOP 1

 Input an Account Transfer using FT

 Make a note of all the Delivery Reference and
Transaction Numbers
 View the messages with the enquiry
- DE.MSG.SUM using Delivery Reference
DELIVERY REFERENCE NUMBER
STRUCTURE
 UNIQUE Header
 XYYYYMMDDNNNNNSSSSSNN
 X is “D” for Outward or “R” for Inward
 YYYYMMDD is the date
 NNNNN is the system user number of the inputter
 SSSSS is the time in seconds since midnight
 NN is the sequence number of transactions within a
second
HANDOFF FILE

Contains “raw” message data from transaction or

event if a message is produced

Can be viewed by enquiry DE.HANDOFF.DETS or a

database level through F.DE.O.HANDOFF and
Delivery Reference Number
VIEWING THE HANDOFF FILE
• Enquiry DE.HANDOFF.DETS
- Delivery Reference Number
HANDOFF MAPPING
Raw Application Data

DE.MAPPING
links the line number with
Handoff
field name
FILE FROM DE.MESSAGE
Record id example:
DATABASE FIELD DEFINITION
900.FT.1
e.g. 900

1.1
1.1
CUSTOMER CUSTOMER

1.4
1.4 ACCOUNT.NO ACCOUNT.NO

1.7
1.7 AMOUNT AMOUNT
WORKSHOP 2

 View the Handoff file for your message using Enquiry

DE.HANDOFF.DETS
 Your Delivery Reference Number with operand EQ
 NB : use ALLDATA to see the full record
 DIAGRAM TO SHOW HANDOFF
& MAPPING

Handoff data
MAPPING to
formatting

field names

DE.MESSAGE - contains
field names to be
included for each msg
type e.g. 900, 910
MESSAGE DETAILS & STATUS

 DE.O.HEADER
 QS – QUEUE STATUS
DE.O.HEADER
 Gives the Disposition status, and message related details
 Allows to Reroute, resubmit the message, change the priority,
DE.O.HEADER Contd…
 WORKSHOP 3

Modify the message type you have been assigned in

DE.FORMAT.PRINT adding the following –

 Add the FULL Customer Address from DE.ADDRESS Application

 Format the date field to reflect DD MM YY

 Commit and view the new layout using Report list with
REPORT.NAME LK …SAMPLE...
 What is DE.O.HEADER

• A new DE.O.HEADER record is created when message is

mapped

• Used to track the message through the Delivery process

• Contains information about processing and status of the

message

• Viewed using the Delivery Reference Number for

individual messages

• DE.O.HEADER L used to list all outward messages

Using DE.O.HEADER
WORKSHOP 4

• Find a previous message

• Resubmit the message using DE.O.HEADER

• View the message through enquiry DE.MSG.SUM

 WORKSHOP 5

• Using your earlier transaction, view the

DE.O.HEADER file to ascertain the message
type and format

• Add a new local reference for the FT Application

• Input a transaction and fill the local reference

• Add your field to the DE.MESSAGE record

• View the Handoff file generated to establish the

location of your local reference
 WORKSHOP 5 CONT.

• Amend DE.MAPPING to map the Handoff location to

the field name defined in DE.MESSAGE

• Add the field (as defined in DE.MESSAGE) to the

end of the message in DE.FORMAT.PRINT

• Input another transaction of the same type (or copy

the previous one) and view the resulting message
which should include your local ref.
DE.FORMAT.SWIFT
SWIFT- SOCIETY FOR WORLDWIDE INTERBANK FINANCIAL TRANSFER.
Used to define the various TAGS and the Fields to be attached under those tags, with
appropriate conversion / calculation whichever required.
DE.FORMAT.SWIFT

• Allows formatting of text, tags and data

• - sequence
• - position on page

• Worldwide message code for advices and instructions

• All SWIFT messages types are available

• Automatic update of any SWIFT changes

DE.FORMAT.SWIFT

• Using DE.FORMAT.SWIFT the data can be matched to the

• Field Tags

• Using all the formatting options available to meet the

• specifications from SWIFT

• Each Message type can have optional data and mandatory

• data
GENERATING A SWIFT MESSAGE
SAMPLE SWIFT MESSAGE
DE.TRANSLATION
Used to define various TAGS to be used in DFS and the conversion
equivalent for TABLE – Conversion type
DE.ADDRESS
GB0010001.C-100242.SWIFT.1
Company code . Customer or Account number Carrier . Version number
Used to specify the address, for both SWIFT and PRINT carriers
Adding Addresses in DE.ADDRESS

• New Customer record creates record in DE.ADDRESS

• “Delivery address” field value is taken from DE.BIC table

• Record no format is
- GB0010001.C-NNNNNN.PRINT.1

• SWIFT ID’s, Telex numbers and alternate Print addresses

may be entered with a key of format
- GB0010001.C-NNNNNN.XXXXX.n
XXXXXX is the carrier
n - is the address number
DE.BIC Table
Adding Addresses In DE.ADDRESS

Example DE.ADDRESS

GB0010001.C-100112.PRINT.2
GB0010001.C-100112.PRINT.3
GB0010001.C-100115.SWIFT.1
WORKSHOP 6

Input a new customer record and view the

DE.ADDRESS record created

Create a PRINT.2 address for the customer.

Create a SWIFT.1 address for the customer.

DE.PRODUCT
Used to setup Carrier for all / individual messages, and multiple delivery
recipients under customer wise product setup
Defining what message when in
DE.PRODUCT

• DE.PRODUCT records may be specified for

- a company
- a customer
- an account

• Each of the above may be specified for

- all message types
- specific message types
- all banking Applications
- a specific Application
Defining what message when in
DE.PRODUCT

Default company record must exist with the key of

“US010001.ALL.ALL”

This record normally specifies to send one copy

by print to print address 1
 DE.PRODUCT

Additional more specific records may be entered with keys as

follows -
US0010001.X-NNNNNN.ALL.ALL

‘A’ or ‘C’
Company depending on Message
Code whether Type
(Defaults Customer ‘ALL’ or Application
as or specific ‘ALL’ or
part of ID Account message specific
if not input) Application type Application
Plus Record
Number
DE.PRODUCT

DE.PRODUCT can be used to specify

– Message Status - Hold or Delete
– Priority - Urgent or Priority
– Carrier - e.g. PRINT.2, SWIFT.2
– Language - valid language code
– Format - format version to be used
– Copies - number of copies
WORKSHOP 7

• Set up a PRINT.3 address for your new customer

• Create a DE.PRODUCT so that all printed output

for FT 900 messages will be routed to your
Customer’s PRINT.3 address

• Create a new account for your Customer and do

a FT using this account

• View the message which should be sent to

PRINT.3
WORKSHOP 7 CONT.

• Set up new Customer with 2 Accounts

• Set up 2 additional addresses for this Customer. One

is their accountant and the other is the Tax Office

• Arrange for all Debit Advices on both accounts to be

sent to both the accountant and Tax Office

• On one account, Credit Advices should be sent to all 3

addresses, but on the other account, Credit advices
should only go to the Accountant
 Record ID for
DE.PRODUCT & FORMAT TYPE

• Can be used to identify not only which ADDRESS,

but also FORMAT is to be used. Multiple layouts of
the same message can be set up for different
groups or types of recipients.

• Field 5.x – FORMAT

• Specifies the code e.g. 1 which will relate to the

record in DE.FORMAT.XXXX. This will default to 1
DE.CARRIER
Used to define the Carrier attributes
DE.INTERFACE
DELIVERY FLOW

DE.MAPPING
DE.MESSAGE
DE.FORMAT.PRINT Message produced

DE.TRANSLATION DE.FORMAT.SWIFT

DE.CARRIER DE.PRODUCT
DE.O.HEADER
DE.INTERFACE DE.ADDRESS
CONTROLLING MESSAGES
DE.ALTERNATE
Used to reroute the message from one carrier to another.
CONTROLLING MESSAGES Contd…
DE.DISP.CONTROL
Used to control the Message Disposition based on the condition specified.
REPAIRING MESSAGES

 MAPPING ERRORS
Source : These error arise due to incorrect mapping, or
values missing in the positions, which are mandatory. This
Disposition is shown in field DISPOSITION of DE.O.HEADER.
Solution : The field which requires value is shown in
DE.O.HEADER, the respective field has to me mapped to the
appropriate position.

 FORMATTING ERRORS
Source : These error arise due to missing Address, formats
(DFP). This Disposition is shown in field MSG.DISPOSITION of
DE.O.HEADER.
Solution : The required address or DFP record has to be input
and RESUBMIT of message has to be done.
INWARD PROCESSING

• SETUP TABLES
• Processing messages from IN queue
• FLOW – Message transfer from OUT to IN
PROCESS FLOW

TC Server – Listeners
for Swift

T24 Host Server

Swift Alliance Interface F.ALLIANCE.IN

DE.ALLIANCE.OUT DE.ALLIANCE.IN

F.ALLIANCE.INPUT F.ALLIANCE.MSG

Swift Alliance Server

ENQUIRIES related to DELIVERY

 DE.O.HANDOFF.DETS
Input : Delivery.id
Output : Displays the entire handoff record pertaining
to the Delivery key given

 DE.MSG.SUM
Input : Delivery.id
Output : Displays the Message details, carrier, status,
To.address, if FORMATTED drills down to show the
formatted output.
Thank you