Inconsistent Behaviour For The Fields ‘May Confirm’ And ‘Requested Confirmation Party’
(Doc ID 2598333.1)
Last updated on OCTOBER 11, 2019
Applies to:Oracle FLEXCUBE Universal Banking - Version 12.3 to 12.3 [Release 12]
Information in this document applies to any platform.
On : 12.3 version, Implementation Support
Inconsistent behavior for the fields ‘May Confirm’ and ‘Requested Confirmation Party’
Case 1: When the flag is ticked, there are no error messages and the amendment is successfully saved.
Case 2 : When the flag is unchecked, there is an error in validation even after providing value for 'Requested Confirmation Party’.
Error Node : ST-AMND-002!Field Requested Confirmation Party of Contract Details cannot be Modified
LCUPLD-601!Requested Confirmation Party should be provided when May confirm flag is selected or when operation code is open and confirm
LC-VALS-475!Failed while trying to confirm the amendment.
ST-SAVE-054!Failed to Save
The issue can be reproduced at will with the following steps:
1. Create a new LC contract using Flexcube front end screen LCDTRONL
2. Save and Authorize the same
3. Using Flexcube front end screen LCDAMEND, amend the contract
4. Uncheck beneficiary flag and provide values for may confirm and requested confirmation party
5. Save and authorize
The issue has the following business impact:
Due to this issue,user observed Inconsistent behavior for the fields ‘May Confirm’ and ‘Requested Confirmation Party’. System is not allowing to save the amendment for LC contract.
Changes provided in the unit to validate the value <
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