PROBLEM: MT700 swift message REPAIR without capturing reason when field 58A is not maintained
(Doc ID 2548418.1)
Last updated on JUNE 21, 2021
Applies to:
Oracle FLEXCUBE Universal Banking - Version 12.3 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
MT700 Incoming SWIFT Message is in Repair without reason
EXPECTED BEHAVIOR
-----------------------
User should be able to view the repair reason to proceed further
ERROR
-----------------------
User-Defined Exception
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upload an incoming MT700 message with no maintenance for CIF for confirming Bank
2. Check if proper reason is captured as repair reason
BUSINESS IMPACT
-----------------------
Due to this issue, users cannot identify the reason for repair message to rectify for successful message processing
Changes
SWIFT 2018
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 |