OBTF|SWIFT_MSG_TYPE Not Updated For CUST_TRF_COV During Bill Liqd
(Doc ID 3071691.1)
Last updated on MARCH 10, 2025
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
---------------
SWIFT_MSG_TYPE not updated for CUST_TRF_COV during bill liqd
EXPECTED BEHAVIOR
-----------------------
SWIFT MESSAGE TYPE shall get updated as 202 for CUST_TRF_COV
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. A Bill liquidation is initiated
2. Settlement details for BILL LIQD is passed in a manner that OBPM creates a cover payment ( CUST_TRANSFER and CUST_TRF_COV)
3. OBPM sends the notification back for both messages ( CUST_TRANSFER; CUST_TRF_COV)
4. OBTF successfully parses the notification and the message browser is accordingly updated
5. We observe that SWIFT MESSAGE TYPE against CUST_TRF_COV is not getting captured. Same is getting captured as 103 against CUST_TRANSFER
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 |