INWARD MT103 WITH OWN BANK IN FIELD 57A
- Nash21979
- Topic Author
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
We have some issues with some inward Swifts that are sent to directly to our bank (RECEIVER: ABCDUS33) in favor of our Customers with our bank bic in field 57A ABCDUS33)
In such case T24 changes it from IT to OT03 as if we are going to execute an MT103 with firld 57A as ABCDUS33 (own bank).
Can you please advise if there is a simple way to make T24 ignore this tag when it''s equal to our own BIC.
One thought would be to act on DE.I.TAG57 routine, to make it return null when the BIC is equal to ours, but I dont know if it's an overkill.
Your input will be highly appreciated.
Regards,
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
Please Log in or Create an account to join the conversation.
- Nash21979
- Topic Author
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
Just said maybe it's a more straight way to do it.
Have done it this way and it is working. I get however the error : 'SUBROUTINE FOR TAG 57 NOT COMPILED' in the 'IN.PROCESS.ERR' field of the FT.
can you please advise how to remove this error.
thanks in advance!
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
Maybe just a question of re-login or restarting your services ???
Please Log in or Create an account to join the conversation.
- Nash21979
- Topic Author
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
On a slightly different note,
I got some Field.id & does not exist in format file#59X (Field 59F)
is there a workaround to make T24 behave as normal 59? In the DE.TAG.59 routine, I added a case '59F' with the same code as '59' but i still get this error.
Regards,
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
Check what is running that is connected to inward message handling.
Maybe also TCServer . . .
The missing field error must be solved in DE.FORMAT.SWIFT.
Please Log in or Create an account to join the conversation.
- Nash21979
- Topic Author
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
I added a DE.TRANSLATION for SW59X
and below is the 59 portion of my entry 103.1.1 in DE.FORMAT.SWIFT
Field Tag.37 59A
Field Name.37 BEN ACCOUNT
Conversion.37.1 ACC
Multiples.37 NO
Inward Routine.37 NO
Outward Routine.37 NO
Field Name.38 BEN CUSTOMER
Conversion.38.1 CUS
Multiples.38 NO
Inward Routine.38 NO
Outward Routine.38 NO
Best,
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
Please Log in or Create an account to join the conversation.
- Nash21979
- Topic Author
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
I have done it. it works fine for Inward, however for outward MT103, the Field 59 is duplicated.
My DE.FORMAT.SWIFT looks like this actually.
Field Tag.37 59A
Field Name.37 BEN ACCOUNT
Conversion.37.1 ACC
Multiples.37 NO
Inward Routine.37 NO
Outward Routine.37 NO
Field Name.38 BEN CUSTOMER
Conversion.38.1 CUS
Multiples.38 NO
Inward Routine.38 NO
Outward Routine.38 NO
Field Tag.39 59X
Field Name.39 BEN ACCOUNT
Conversion.39.1 ACC
Multiples.39 NO
Inward Routine.39 NO
Outward Routine.39 NO
Field Name.40 BEN CUSTOMER
Conversion.40.1 CUS
Multiples.40 NO
Inward Routine.40 NO
Outward Routine.40 NO
Any suggestion?
Regards,
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
We remove the unwanted field with an outward routine.
Please Log in or Create an account to join the conversation.
- Nash21979
- Topic Author
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
Can you please advise where this outward routine should be attached.
from the help text they say " However, so far it has not been found necessary to write a routine to convert a particular Field Tag. Therefore, at present, this field is not used.
Thanks
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
FIELD.TAG FIELD.NAME........ INWARD.ROUTINE OUTWARD.ROUTINE CONVERSION..............
59A BEN ACCOUNT NO Y ACC
@SUPPRESS.TAG59A
BEN CUSTOMER NO Y CUS
@SUPPRESS.TAG59A
59X BEN ACCOUNT NO NO ACC
BEN CUSTOMER NO NO CUS
SUBROUTINE SUPPRESS.TAG59A(FORMAT.SWIFT.REC, MESSAGE.REC, PASS.VALUE, SWIFT.FIELD.VALUE, ERR.MSG)
*-----------------------------------------------------------------------------
* Description:
* Routine attached to DE.FORMAT.SWIFT -> 103.1.1 to suppress one TAG59 in outgoing msg.
*
* Parameters:
* FORMAT.SWIFT.REC - DE.FORMAT.SWIFT record
* MESSAGE.REC - De message record
* PASS.VALUE - Tag value
* SWIFT.FIELD.VALUE - All Tags and its values formed from DE.FORMAT.SWIFT
* PASS.VALUE and SWIFT.FIELD.VALUE can be edited and passed back to the delivery process
*-----------------------------------------------------------------------------
$INSERT I_COMMON
$INSERT I_EQUATE
*-----------------------------------------------------------------------------
PASS.VALUE = ''
EQU CR TO CHARX(013)
EQU LF TO CHARX(010)
CRLF = CR:LF
TAG59 = CRLF:':59:'
FINDSTR TAG59 IN SWIFT.FIELD.VALUE SETTING POS1 THEN
DATA.WITHOUT.TAG59 = FIELD(SWIFT.FIELD.VALUE,TAG59,1)
SWIFT.FIELD.VALUE = DATA.WITHOUT.TAG59
END
*// Remove Empty CR:LF
CRLF.CNT = DCOUNT(SWIFT.FIELD.VALUE,CRLF)
LAST.VAL = FIELD(SWIFT.FIELD.VALUE,CRLF,CRLF.CNT)
PREV.CNT = CRLF.CNT-1
IF LAST.VAL EQ "" THEN
SWIFT.FIELD.VALUE = FIELD(SWIFT.FIELD.VALUE,CRLF,1,PREV.CNT)
END
RETURN
*-----------------------------------------------------------------------------
END
Please Log in or Create an account to join the conversation.
- Nash21979
- Topic Author
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
Please Log in or Create an account to join the conversation.
- Valleyman1
- Visitor
Please Log in or Create an account to join the conversation.
- armin
- Offline
- Elite Member
- “So long - and thanks for all the fish!”
- Posts: 300
- Thank you received: 57
Please Log in or Create an account to join the conversation.
- Nash21979
- Topic Author
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
Please Log in or Create an account to join the conversation.
- ppnartey
- Offline
- Junior Member
- Posts: 30
- Thank you received: 0
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
Please Log in or Create an account to join the conversation.
- mappiagyei
- Visitor
DE.FORMAT.SWIFT, INPUT
ID................ 103.1.1 CUSTOMER CREDIT TRANSFER
9.20 OUTWARD ROUTINE NO
10.20 HEADER NAME....
3.21 FIELD TAG...... 53A
4.21 FIELD NAME..... SENDER C/D
5.21. 1 CONVERSION.. @SUPRESS.TAG.53A
6.21 CALCULATION....
7.21 MULTIPLES...... NO
8.21 INWARD ROUTINE. NO
9.21 OUTWARD ROUTINE Y
10.21 HEADER NAME....
3.22 FIELD TAG......
4.22 FIELD NAME..... SENDER BANK ACC
5.22. 1 CONVERSION.. ACC
6.22 CALCULATION....
7.22 MULTIPLES...... NO
8.22 INWARD ROUTINE. NO
ACTION #13.21 ROUTINE NOT CATALOGEDþ
Please Log in or Create an account to join the conversation.
- Nash21979
- Topic Author
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
sometimes it's just a matter of 'Lag' before having it properly recognized.
try decataloging it and recatalog it. It often does the trick.
regards,
Please Log in or Create an account to join the conversation.