Cutoff Scenario In OBDX/OBP Payment Type R (RTGS) is not considered For Dates
(Doc ID 2963457.1)
Last updated on SEPTEMBER 26, 2023
Applies to:
Oracle Banking Payments - Version 14.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Different behavior of DateDerivationService for RTGS and SWIFT transactions. Due to this, the date derived at OBDX is impacting the status of the payment.
When User initiates a Domestic Fund Transfer payment from OBDX after the Processing cutoff time set in OBP (PMDCTOFF), there is no popup info message shown to the user and the payment is landing directly into Processing Cutoff queue in OBP. And when the Processing cutoff job(PQDPRCUQ) is executed, the payment directly lands in Warehouse queue with activation date as next working date.
When User initiates a International payment from OBDX after the Processing cutoff time set in OBP (PMDCTOFF), a popup info message is shown to the user that the value date will be next working date and the payment is landing directly into Warehouse queue in OBP as the date derived from OBDX(DateDerivationService) is nextworking day.
Due to this different behavior, when user does an Inquiry of the payment, the status shown is different for these payments.
In this case, all transactions are booked from OBDX (channel) , and Bank's expectation is when Processing cutoff is crossed, the transaction should land in Processing Cutoff queue for the Backoffice user to have an option to release the payment on the same day before Network Cutoff is crossed. If not released transaction will move to warehouse queue once Processing Cutoff Job is executed and based on FV queue job will automatically get processed the next working day
Analysis:
In DateDerivationService, in the processing cutoff scenario handling, the Payment Type R (RTGS) is not considered in deriving the dates, whereas SWIFT, BOOK and other payment types are considered. Due to this, when RTGS payment is done after the processing cutoff , the dates are not deriving correctly.
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 |