MT910 Generated With Wrong Option In Field 52
(Doc ID 2791413.1)
Last updated on JULY 15, 2021
Applies to:Oracle FLEXCUBE Universal Banking - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Production Support-SET
Field 52 of MT910 SWIFT message is getting generated with incorrect option.
When tried from both FTDTRONL screen as well as by uploading an incoming SWIFT MT103 message having field 52A, system seems to always generate field 52D in the outgoing MT910 message, even though it populated business identifier code in 52D
When business identifier is input in ordering institution, or when incoming 103 message is received with field 52A, the corresponding MT910 message should also contain the same business identifier code in 52A.
Currently, system puts the wrong option as 52D. Expectation is that option should be 52A.
The issue can be reproduced at will with the following steps:
1. Upload an incoming SWIFT MT103 message having field 52A.
2. Make sure that the FT product resolved by STP to book the contract has CREDIT ADVICE mapped to INIT event. Also make sure that the credit account being used has default MEDIA as SWIFT with a valid business identifier code.
3. Check the generated FT contract and its MT910 message.
4. System is copying the business identifier from incoming MT103 field 52A into 52D of the outgoing MT910 message.
The issue has the following business impact:
Due to this issue, users cannot use MT910 and MT900 messages to send real-time notifications to clients about the debits/credits happening on their accounts.
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