My Oracle Support Banner

Commitment Maturity Date Not In Synch With Collateral End Date (Doc ID 2942853.1)

Last updated on APRIL 19, 2023

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------

User amended the collateral “end Date” i.e to 21-JUL-2022; after EOD, I observed that the collateral maturity date was automatically changed to be in sync with the collateral End Date.

But when changed the collateral End Date, this time leaving it as blank; after a new EOD, commitment maturity did not change, which is wrong.


EXPECTED BEHAVIOR
-----------------------

The end date of a collateral must always be in synch with the correspondent commitment maturity date, and in case the collateral end date is null the commitment maturity date should get set to some far future date.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create collateral sand save without end date.
2. Amend the collateral, make end date i.e 21-jul-22.
3. Run EOD
4. Again amend end date of collateral as null.
5. Run EOD. Verify commitment details

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the commitment maturity date is not updating properly.

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


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