My Oracle Support Banner

CDDVAMND: System Erases Start Date When Its Different From The Populated Date (Doc ID 2879988.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

CDDVAMND: System erases Start date when its different from the populated date

When the start date in the CDDVAMND screen is updated to a different date from the actual date populated when the contract reference number is entered, after the save and authorize then system 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 start date is 21-DEC-2021, which is updated to 01-APR-2022, 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 (01-APR-2022 in this case).


Expected Behavior

System should accept the newly inputed start date or the Start date field should be read only.


Steps

1. Invoke the screen CDDVAMND
2. Input any existing contract and unlock it
3. Change tstart date and save and authorise it
4. Again check the newly changed start 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.