During account class level modification for dormancy days in STDACCLS screen, system wrongly updating dormancy date for the accounts (under this account class), even if dormancy parameter is maintained as Manual.
(Doc ID 2570580.1)
Last updated on SEPTEMBER 02, 2019
Applies to:Oracle FLEXCUBE Universal Banking - Version 12.0.3 and later
Information in this document applies to any platform.
On : 12.0.3 version, Production Support-SET
Incorrect Dormancy Days on modification at account class level.
When account class level dormancy days are modified, system updates the dormancy date for all the accounts under the account class based on dormancy parameter. When dormancy days is changed, system is calculating incorrect date at account level.
For the reported issue, current application date was 02-July-2019 and dormancy date for CASA under one account class was marked as 03-Jul-2019 with last debit/credit date as 02-Jul-2018. Dormancy days in account class level is 365.
Now when the dormancy date is modified to account
For example, Last Debit 2018-07-02
Last Credit 2018-07-02
DR Activity 2018-07-02
CR Activity 2018-07-02
Expected Dormancy Day should be 1/7/2024.
Actual Dormancy Day calculated at the account level is 2/7/2025
As per the Dormancy days in account class level, system should calculate dormancy date for the account.
The issue can be reproduced at will with the following steps:
1. Modify dormancy days for any account class in in account class maintenance screen.
2. Save and authorize the modified account class maintenance changes.
3. Verify dormancy date of all accounts belonging to this account class.
The issue has the following business impact:
Due to this issue, system is not calculating/populating dormancy date of affected accounts.
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