My Oracle Support Banner

During EOC POSTEOPD Stages Tracked With Next_working Date In Eod_date Column (Doc ID 2753078.1)

Last updated on FEBRUARY 28, 2021

Applies to:

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

Symptoms

On : 12.0.3 version, Production Support-SET

ACTUAL BEHAVIOR
---------------
During EOC POSTEOPD stages tracked with next_working date in eod_date column

During EOC with complicated structure MARKEOPD and POSTEOPD_* stages tracked with next_working date in eod_date column because new day starts for the Branch.
Expected: eod_date equals to day of EOD for all EOD stages
Real: MARKEOPD and POSTEOPD_* tracked with next working day.
EOD spool End_of_Cycle_timings.sql attached for both days.

For examle, today is 11.08.2020. Last EOD was on 10.08.2020. EOD_DATE in all aetb* table should be 10.08.2020. But there are records with 11.08.2020 also.
Because of this EOD reports based on EOD date works not properly.

EOD spool End_of_Cycle_timings.sql attached for both days.

EXPECTED BEHAVIOR
-----------------------
<The EOD Date and Branch Date should be updated properly>

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. <Run EOD for Branch with Target Stage as Mark BOD>
2. <After Mark BOD is completed, complete the remaining stages>
3. <Complete EOD with Target Stage as POSTEOPD_3>

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot retrieve the records based on EOD Date

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


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