TD - Did Not Automatically Close On Maturity Date- Sept 30, 2022 (#88857)
(Doc ID 2919921.1)
Last updated on JANUARY 19, 2023
Applies to:
Oracle FLEXCUBE Universal Banking - Version 12.1 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1 version, Production Support-SET
ACTUAL BEHAVIOR
---------------
Inquiry: TD - did not automatically close on Maturity Date- Sept 30, 2022
Requesting your assistance relative my inquiry, scenario details below:
td Account - original maturity date is Sept. 30, 2022, with "Auto-Roll Over" as the disposition on maturity date
Last Sept. 29, 2022(day before maturity date), branch made a maintenance via STDCUSTD to the account for the change on disposition - from "Auto-Roll Over" TO "Close on Maturity". Maintenance was successfully saved and authorized.
Come Sept. 30, 2022 - (Maturity Date) - account did not CLOSE, but system ROLLED-OVER the TD account for another term. Hence, the change on disposition made to the account did not affect despite the successful perform of maintenance.
Inquiry: What is the expected behavior of STDCUSTD for change of disposition for below scenarios?
1. Change disposition Auto Roll to Close on Maturity and vice-versa
2. What is the right timing for the maintenance? How many days prior to maturity day the maintenance is allowed for it to take effect on the current maturity date?
3. On the actual scenario stated above - is this the correct behavior of Flexcube- STDCUSTD.
EXPECTED BEHAVIOR
-----------------------
On Maturity date, the TD must have closed instead of rollover as Close on Maturity flag was selected.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Last Sept. 29, 2022(day before maturity date), branch made a maintenance via STDCUSTD to the account for the change on disposition - from "Auto-Roll Over" TO "Close on Maturity".
2. Sept. 30, 2022 - (Maturity Date) - account did not CLOSE, but system ROLLED-OVER the TD account for another term.
3. Hence, the change on disposition made to the account did not affect despite the successful perform of maintenance.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, though the Close on maturity flag was selected, the TD did not close instead rollover happened.
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 |