OBPM|Incorrect Behavior For Incoming MX Trransaction Post Network Cutoff
(Doc ID 3062698.1)
Last updated on DECEMBER 10, 2024
Applies to:
Oracle Banking Payments - 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
---------------
Observation :-
1.Source network preference for SWIFTMX, INCOMING for book date validation is NOT REQUIRED
2. Book an incoming MX txn which does not qualify for NSTP evaluation post network cutoff
a) Txn is booked in Network cutoff queue ( In the same scenario, MT txn is booked in warehouse queue)
b) System has derived all the dates as 11-July ( In the same scenario, MT txn has derived next working date)
c) Expectation is that MX behavior shall be similar to MT behavior ( Txn shall be booked in warehouse queue and dates shall be derived accordingly)
3. Book an incoming MX txn which qualifies for NSTP evaluation post network cutoff
a) Txn is booked in NSTP queue ( In the same scenario, MT txn is booked in warehouse queue)
EXPECTED BEHAVIOR
-----------------------
MX behavior shall be similar to MT behavior ( Txn shall be booked in warehouse queue and dates shall be derived accordingly)
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 |