Dormancy Start Date Is Greater Than Account Closure Date
(Doc ID 2595275.1)
Last updated on OCTOBER 20, 2019
Applies to:
Oracle FLEXCUBE Universal Banking - Version 12.0.1 and laterInformation in this document applies to any platform.
Symptoms
On : 12.0.1 version, Production Support-SET
ACTUAL BEHAVIOR
---------------
For some closed accounts dormancy start date (at table: sttm_cust_account_dormancy) is greater than account closing date.
EXPECTED BEHAVIOR
-----------------------
The dormancy start date cannot be of a date after the account closure.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Pick any close account which is not dormant, check the expected dormancy date which is in future.
2. Run the EOD till the expected dormancy date, on this EOD System marks the closed account as dormant and sets the dormancy date in Sttm_Cust_Account_Dormancy.
BUSINESS IMPACT
-----------------------
Data Anomaly impacts bank reporting on dormant accounts.
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 |
| Cause |
| Solution |
| References |