Adhoc International Transaction : First match Swift code Is Picked Up While Verify The Incomplete Swift Code
(Doc ID 2918717.1)
Last updated on JANUARY 04, 2023
Applies to:
Oracle Banking Digital Experience - Version 18.1.0.0.0 to 18.1.0.0.0 [Release 18]Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
-----------------------
Adhoc International Transaction : First match Swift code is picked up while verify the incomplete swift code.
So even if a customer enters CTBA and click on verify button, system fills the value to the first match "CTBAAU2SXXX" which is not the correct swift code.
Since OBDX fills the first matched Swift code, the transaction is posted successfully.
EXPECTED BEHAVIOR
--------------------------
The system should stop the filling of closest match of Swift code and only keep exact match .
STEPS
--------
The issue can be reproduced at will with the following steps:
1. Login into OBDx
2. Navigate to International payment
3. Enter swift code and validate
BUSINESS IMPACT
----------------------
The issue has the following business impact:
Due to this issue, matched Swift code is picked which is wrong.
Changes
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 |