MM \ Issue With Format Of Generated MT320
(Doc ID 2936366.1)
Last updated on MARCH 27, 2023
Applies to:
Oracle Banking Treasury Management - Version 14.7.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.6.2.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
MM \ issue with format of generated MT320
MM\There is an issue with format of generated MT320 – system is adding field 24D at the end of generated message.
Kindly provide the fix to remove the same.
EXPECTED BEHAVIOR
-----------------------
System shouldn't have field 24D at the end of generated message.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, issue with format of generated MT320.
Changes
Fix/solution :-
---------------
1. For "Dealing Method" field , Default value (PHON) has been removed from
the Screen(RAD) level and in the backend Unit also.
2. Code changes done to populate tag 24D if only user input the "Dealing
Method" filed with any value.
3. Code changes done to skip population of empty 15H block in MT320
Units Affected
-------------------
mmpks_mmdtronl_main.sql;
ldpks_tr_swift.sql;
MMDTRONL_RAD.xml;
Search String
-------------
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 |
Changes |
Cause |
Solution |
References |