OBPM|MT 103 To MX Pass Through Having Wrong 71F
(Doc ID 3037162.1)
Last updated on AUGUST 07, 2024
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 103 to MX Pass through having wrong value in field 71F.
EXPECTED BEHAVIOR
-----------------------
Field 71F should map correctly
STEPS
-----------------------
Please refer to the captioned SR for the below observations related to MT 103 to MX passthrough issues:
1. Field 71F is not correctly mapped to MX passthrough ( screen as well as message)--> Currently hard coded data "NOT PROVIDED" is going as name as well as address line 1
a) System shall pick up the latest occurrence for the BICFI passed in field 72 (/INS/)
b) System shall pick up the earlier occurrence for the BICFI passed which is before the instructed agent of the original message
2. Previous instructing agent 2 is not getting updated correctly in message as well as screen
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Wrong MX is getting generated
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 |