OBPM|MT To Pass Through MX, 52D Field Behavior is Wrong
(Doc ID 3072467.1)
Last updated on FEBRUARY 18, 2025
Applies to:
Oracle Banking Payments - Version 14.7.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.7.0.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
MT to pass through MX, 52D diff behavior is wrong.
EXPECTED BEHAVIOR
-----------------------
Name of debtor agent shall get updated with details of F 52D even though / is not passed
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Initiate an incoming MT with F 52D without / which results in pass through RTGS
2. Pass though MX transaction is booked
3. Debtor agent ahs only BICFI tag ( sender of the original message) on the screen as well as in the message
4. Expectation is that name of debtor agent shall get updated with details of F 52D even though / is not passed
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 |
| References |