Delivery messages

MT? like series of messages is generated by different applications and is handled by Delivery system. I think this is correct understanding.

How to know the format of the message type and the instance when particular message type is generated and how the delivery system will handle this message?

Is the format of each message type is fixed or is it configurable through any application?



For example, I want to know all the message types generated by Trade Finance product and the instances when message is generated and handed over to Delivery system, and how delivery system will handle this message? Are these messages are defined in any application or it is hard coded for Globus system? How to change the format of the message?





Also please post an example of how to use APPLICATION.HANDOFF routine.

What you are asking for is the complete life cycle of delivery system. I would suggest you to start with DE.MESSAGE and move on from there.

The main layout of swift messages is defined in DE.FORMAT.SWIFT for each message. you are setting what fields are going to be used. And the field settings and data mapping are mainly specified in DE.MESSAGE and DE.MAPPING.

for the Trade Finance (letter of credit, etc) there are very good details in standard temenos documentation. but I think there are several docs regarding this area.

Most of the messages are hardcoded inside T24. At the same time you can override them by creating your own messages. Look DE.MESSAGE, DE.MAPPING...

EB.PHANTOM

I don't think the delivery messages are hard-coded. Only the source raw data are hardcoded. The messages and their layout are user definable.

Generally Delivery we have Soft Delivery and Outward Delivery.

Soft Delievry >>>> This Delievry is used majorly for Trade Finance and certain Core messages. Soft Delivery can be defined easily through EB.ADVICE and EB.ACTIVITY.



Outward Delivery >>>> Outward Delivery is the common Delivery system handled for almost most of the T24 Applications. Ofcouse the Delivery message are defined by the user but we can hardcode it in the routine by calling Application Handoff. Outward Delivery flow would be DE.MESSAGE>DE.ADDRESS>DE.PRODUCT>DE.MAPPING>DE.FORMAT.PRINT (OR) DE.FORMAT.SWIFT



Delivery is a intresting module in T24. Try out your own message by calling core rouitine application Handoff you will learn more.

Hi,

Do you have any document on how to configure messages using EB.ADVICES?
If so please share with us in downloads section.

I have uploaded a document on configuring messages, mapping and formatting.
Please have a look


Keep posting and make this community active|Thanks

Hello to everybody. I have just registered in the forum today.

I am trying to process a swift message, specifically MT103 message.

What I have seen in the documentation is that these messages can be processed by the INWARD routine specified in DE.MESSAGE. For message with @ID = 103, this routine is DE.I.MT103. It is also specified a version and a OFS record, but I understand that this will be used after the message has already been inputted in DE.I.HEADER / DE.I.MSG.

My question refers to the previous step, that is, the way to convert the MT files into messages:

Is there a core process in T24 that gets the swift files from a given directory and converts them into messages (DE.I.HEADER, DE.I.MSG)? Or must I build a routine that does that?

I have seen that there is a process called SWIFT.IN, with a routine called DE.INWARD, but I don't know if this routine does what I need.

Thanks and regards to everybody.


Jose Antonio Ibañez

I am also stuck at a similar situation whery I want to read MT300 INWARD message from a UNIX folder and take it DE.I.HEADER. Can anybody help addressing how to get it done?. The TEMENOS document is not addressing in details..

I want to know the following

1. where to put the MT300 message received from the SWIFT (INWARD) and in which T24 TABLE we have to define the path of this folder so that the DELIVERY module can read it.

2. what services need to run?

3. what phantoms need to run?

Thanks

1. The paths are usually hard coded for delivery, in this case it should be ../bnk.interface/SWIFTIN
2. TSA.SERVICE --> SWIFT.IN
3. I think no more phnatoms are needed

Lars,

* I put the message thru FTP using binary mode in to ../bnk.interface/SWIFTIN folder (each message has file name in the format eg. 01148461.MSG)
* Then I started the SWIFT.IN tSS
* Then I started DE.I.SELECT.NEXT.MESSAGE

But I could not see any records in DE.I.HEADER or anything populated to CM.HEADER.QUEUE
Also SWIFTLOG is empty.

Your expertise is appreciated to sort out this issue.