My Oracle Support Banner

SET THE PROCESSING CUTOFF JOB (Doc ID 2862400.1)

Last updated on APRIL 17, 2022

Applies to:

Oracle Banking Payments - Version 14.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.5.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Changes REQUIRED TO SET THE PROCESSING CUTOFF JOB

Faster payments is a network configured as a RTGS payment in Flexcube. For
this network processing cutoff is maintained as 23 hours and 30 minutes.
When the processing cutoff job (PQDACQAU) was executing at 00:05, the
payments were moved to the next working day and into warehouse queue.
When the processing cutoff job (PQDACQAU) was moved to 23:57, the payments
between 23:57-00:00 are stuck in processing cut off queue which is incorrect.
We need the job to run after 00:00 (say 00:05) with an option not to carry
forward the payment but to force release the payment the next day of booking
date.

EXPECTED BEHAVIOR
-----------------------
Requirement Detail ---
Faster payments is a network configured as a RTGS payment in Flexcube.
Bank is expecting to receive faster payments 24x7.
Expectation is to process the payments received between 23.30 hours to
midnight on the next date.
The Processing cutoff for Faster Payment network code is maintained as 23
hours 30 minutes. So all the payments that are received from online banking
after the cutoff time are sent to Processing cutoff queue.
The requirement is to schedule the processing cutoff job (PQDACQAU) timings
to post midnight (say 00.05 hours).
After the job is executed, the action should be Force Release instead of
Carry forward. So that all the payments can be released post midnight and the
activation date can be re derived.

The change is required at 2 places-
PMQueueTxnService.class – The changes are required in method queueTxnHandler
to pass the queue action as “Force Release” when queue code is PRCU and
Channel is AUTOPROCESS.
PMQueueCutoffService.class – The changes are required in method
doActivationDateCheck to always approve the re-derivation of activation date
when queue is PQDACQAU and channel is AUTOPROCESS.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.