Hi,
The processing will vary between the different T24 releases, and also
different messages will translate into different applications in T24,
e.g. MT1xx into FUNDS.TRANSFER, MT5xx into SC.PRE.DIARY, so you would
need to provide more information to get a precise answer. But let's
consider a simple example - MT103 funds transfer, above R06.
There are two main processes in the incoming SWIFT: receiving the
message from the interface, and formatting it into an OFS string.
I am assuming that you will have the standard T24 delivery setup, so
that DE.INTERFACE (ALLIANCE), DE.CARRIER (SWIFT), DE.MESSAGE (103),
DE.MAPPING (103...), DE.FORMAT.SWIFT (103..), etc. are already
parameterised.
First you need to attach an inward OFS routine to DE.MESSAGE, record
103, field INWARD.OFS.RTN - and there is a standard routine tempate
for that in GLOBUS.BP, called DE.I.MT103 (you will find routines for
different messages as well). You can amend the routine to fit your
needs, or leave as it is. Then you also fill OFS.SOURCE and FT VERSION
to use for the MT103 input. And that's pretty much it - assuming that
you want to process the messages in the simplest way.
For the two processes mentioned earlier:
1) TSA.SERVICE >
DE.CC.GENERIC.IN - will transfer the incoming
messages from the DE.I.MSG.ALLIANCE file (this is where your SWIFT
interface should write the messages) to SWIFT unformatted queue (as
far as I recall, with R07 you can use OFS call with
DE.CARRIER=SWIFT,msg syntax)
2) TSA.SERVICE >
SWIFT.IN - will pick the unformatted messages,
translate them into OFS (using the DE.I.MT103 routine) and create a
record in T24.
Regards,
Lukasz
On 23 Paź, 06:22, "Harish Venugopal" <
venugopal.har...@gmail.com>
wrote: