My Oracle Support Banner

On EOD Abort, EOD Is Restarting Again From First Sub Function In The SE Batch (Doc ID 2971894.1)

Last updated on SEPTEMBER 03, 2023

Applies to:

Oracle FLEXCUBE Universal Banking - Version 14.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Actual Behavior

Once an EOD is aborted in the SE securities (SEAUTDLY) batch, on resubmitting the batch, it restarts again from the 1st sub-function in the SE (SEAUTDLY) batch in all cases.
For example, if the IACR sub function fails sequence number 10, then on restart of EOD it starts from sub function 1 only, even though 1 to 9 sub functions are completed.


Expected Behavior

SE batch should again start with the incomplete sub functions


Steps

1. Run EOD for SE batch and make sure that EOD may abort with IACR sub function for any reason and which this is the last sub function for SE batch
2. Make the respective config to correct the error
3. Again run EOD
4. Check the SE batch is initiating from 1 or only the IACR is running.


Business Impact

SE batch takes time to complete and because of any abort, system doubles the time taken to run the SE batch.

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.