My Oracle Support Banner

CDDVAMND: Amend Date For Past Dated Amendments Is Not Allowing (Doc ID 2879990.1)

Last updated on JUNE 29, 2022

Applies to:

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

Symptoms

Actual Behavior  

When the amendment date in the CDDVAMND screen is updated to a back value date from the actual date populated, system after the save and authorize automatically updates it back to the previous date that was available before changing the date.

For e.g., when the contract is entered and system populated amendment date is 21-DEC-2021, which is updated to 10-NOV-2021, after the save and authorize, the date resets back to 21-DEC-2021. This is an incorrect behavior and system should allow to save the date as provided by the user (10-NOV-2021 in this case).


Expected Behavior

System should accept the newly inputted back dated amendment date.


Steps

1. Invoke the screen CDDVAMND
2. Input any existing contract and unlock it
3. Change the amendment date and save it
4. Again check the newly changed amendment date is existing or not.



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
References


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