Delivery Advices

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • retired . . . ¯\_(ツ)_/¯
More
14 years 6 months ago #7728 by jpb
Replied by jpb on topic Re: Delivery Advices
DE.MAPPING !

Please Log in or Create an account to join the conversation.

More
14 years 6 months ago #7781 by ridik
Replied by ridik on topic Re: Delivery Advices
Hi, jpb

I'm continuing working with DELIVERY module. I got 299 message to get delivered to Swift Alliance
from my application using the standard artefacts for "Free Format messages" defined in doc
Delivery - Message Creation, User Guide, as you suggested me before.

Now, I'm trying the inward messaging process. So far, everything seems to work fine. MT299 messages
delivered to F.ALLIANCE.MSG repository are load, formatted and finally registered in
application EB.FREE.MESSAGE. But, I was expecting all data from MT299 swift message to be match to the
corresponding field in EB.FREE.MESSAGE application, in the same way it does when doing outward delivery.

Example MT299 swift message:

{1:F01ASDFGBA12XXX}{2:O2990000100730DEUTDEFFXXXX}{3:}{4:

:20:RTC000000029

:21:NO REF.

:79:MT299 TEST MESSAGE

-}{5:{CHK:3ad4ef5480d6}}{S:{SPD:}{COP:P}}

an this is the corresponding entry registered on EB.FREE.MESSAGE application, after the message was processed:

livet24 Free Format Messages SEE

EB.MSG.KEY........ FM11-084-00029
3 CUSTOMER.NO....... 4649 DEUTSCHE BANK AG-FRANKFURT
4. 1 RECV.ADDR...... DEUTSCHE BANK AG
4. 2 RECV.ADDR...... TAUNUSANLAGE 12-21, 60262
4. 3 RECV.ADDR...... FRANKFURT AM MAIN, GERMANY
9 EB.ADVICE.NO...... EB-0299 MT 299 Free Format Message
17 DIRECTION......... INWARD
20 IN.DEL.REF........ R20110524001236004302
28 CURR.NO........... 1
29. 1 INPUTTER....... 121_SWIFTUSER_I_INAU_OFS_OFSONLINE
30. 1 DATE.TIME...... 24 MAY 11 16:41
30. 2 DATE.TIME...... 24 MAY 11 16:41
31 AUTHORISER........ 121_SWIFTUSER_OFS_OFSONLINE
32 CO.CODE........... DE-001-0001 livet24
33 DEPT.CODE......... 1


I was expecting to have the content of TAG20 captured on field OUR.REFERENCE or THEIR.REFERENCE,
TAG21 on field OUR.REFERENCE or THEIR.REFERENCE, and
TAG79 on field TEXT.


I have everything configured as it is recomended in the above mentioned documentation.

I want to be able to recover info from all of MT299 tag's. What I'm missing?

Best regards.

Please Log in or Create an account to join the conversation.

More
14 years 5 months ago #7851 by ridik
Replied by ridik on topic Re: Delivery Advices
I figured it out. I create my own inward routine and attached it to DE.MESSAGE record.

Best regards.

Please Log in or Create an account to join the conversation.

  • yasu
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
14 years 5 months ago #7910 by yasu
Replied by yasu on topic Re: Delivery Advices
Hi JPB ,

is it possible to add a Digital Signature while generating a Delivery Message. In DFP is their an option or is their any other way to achieve this.

Warmest Regards,
Yaser.

Please Log in or Create an account to join the conversation.

  • yasu
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
14 years 3 months ago #8753 by yasu
Replied by yasu on topic Re: Delivery Advices
Hi Jpb,

I have 3 DFP 1430.1.1.GB, 1430.2.1.GB, 1430.3.1.Gb
all 3 have different layouts and corresponding mapping records.
now wen i input an LC contract 3 delivery refs come up but in all the three of them i get the layout of 1430.1.1.Gb

Any idea how to handle this scenario.... also in EB.ADVICES i have specified the three mapping records 1430.LC.1, 1430.LC.2, 1430.LC.3

Your help is highly appriciated.

Thaks
Yassar.

Please Log in or Create an account to join the conversation.

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • retired . . . ¯\_(ツ)_/¯
More
14 years 3 months ago #8755 by jpb
Replied by jpb on topic Re: Delivery Advices
Hi yasu,

for your first question :
we use DFP only to generate "raw data", printing and layout is done by an external tool. I have no idea about adding a signature in DFP.

second :
we haven't installed LC. But i know that the User Guide for LC is one of the best documentations of delivery in hole T24. Came across in ModelBank some time back :)

Maybe it's something related to MSG.CLASS in EB.ADVICES (EB.MESSAGE.CLASS) and the definitions in LC.PARAMETERS for LC.CLASS.TYPE/EB.CLASS.NO ??

Kind regards
jpb

Please Log in or Create an account to join the conversation.

Time to create page: 0.035 seconds