My Oracle Support Banner

OBP Auto Job Execution To Be Based On Time Not Date&Time (Doc ID 2965907.1)

Last updated on AUGUST 07, 2023

Applies to:

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


We faced a scenario wherein the Processing cutoff job has not executed on the actual date. System has to consider the Execution Time instead of Date&Time to trigger the job.

Below is the scenario faced for Processing Cutoff Job (PQDPRCUQ):

Physical/Calendar Date : 17-JUN-2023
OBP Application Date : 17-JUN-2023
Next working date : 19-JUN-2023
Processing Cutoff Job time at PMDAJBPR maintained: 22:30

On 17-JUN-2023, when the Processing cutoff Job is executed at 22:30, the next execution Date for the job will be marked as 19-JUN-2023 22:30.
When the 17-JUN-2023 EOD is completed the OBP application Date will be changed to 19-JUN-2023 but the Physical/calendar date will be 18-JUN-2023.
In this case, on that 18-JUN-2023 22:30 - OBP application date and Processing cutoff execution date matches(both will be 19-JUN-2023) and system triggers the job and marks next execution date of the job as 20-JUN-2023 22:30.

On physical/calendar date 19-JUN-2023, OBP application date is also 19-JUN-2023, when user posts a transaction after the cutoff , it will land into
Processing Cutoff Queue and as on physical date 19-JUN-2023 22:30 , as the next excecution date for the Job is 20-JUN-2023, System will not trigger the job.
And the payment will stay in cutoff queue itself. Which will again be released on 20-JUN-2023 22:30 .

So, basically the customer has to wait for 2days to process the transaction.


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

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