MT300 Got NACK Due To Field 36 Exceeding Length – Error T33
(Doc ID 2900343.1)
Last updated on OCTOBER 10, 2022
Applies to:
Oracle FLEXCUBE Universal Banking - Version 14.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.1.0.0.0 version, Production Support-SET
MT300 got NACK due to field 36 exceeding length – Error T33
In prod one of the FX confirmation message got Nack'ed from SWIFT due to length limitation of field 36. While SWIFT allow only 12 digits in field 36 of MT300, FLEXCUBE sent with 13 digits.
User has manually edited to 12 digits and then resent the message which was successful.
ERROR
-----------------------
field 36 exceeding length – Error T33
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Book an FX contract and validate the outgoing MT300 message content.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, MT300 got NACK'ed.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |