OBTF :Field 33A And 71D Not Captured In MT752
(Doc ID 3052614.1)
Last updated on OCTOBER 24, 2024
Applies to:
Oracle Banking Trade Finance - 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
---------------
Field 33A and 71D not captured in MT752
While generating MT752 (DISCREPANCY_AUT), system not capturing all the FFTs added as part of Save. Fields 33A and 71D are not present after the authorization message generation. Please check the same and provide the fix.
EXPECTED BEHAVIOR
-----------------------
Field 33A and 71D must be captured in MT752
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Go to BCDTRONL and open existing IMCU contract in initial stage in which discrepancy is not resolved.
Unlock the contract Move the stage to Final and Go to Discrepancy tab, Resolve the discrepancy.
Visit Advices/FFT tab and update FFT's for MT752 as shown in the screenshot excel
Click on Save.
Go to Message Preview and check MT752 (not all fields shown here)
Authorize the contract.
Check MT752 in ADIS event->All Messages (33A and 71D are not captured
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, fields not populated in MT752
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 |