STDCUSAC | Unauthorized Account Updated As Authorized In STTB_ACCOUNT Table
(Doc ID 2943818.1)
Last updated on APRIL 24, 2023
Applies to:
Oracle FLEXCUBE Universal Banking - Version 14.6.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.6.0.0.0 version, Production Support-SET
ACTUAL BEHAVIOR
---------------
Unauthorized Account updated as Authorized in STTB_ACCOUNT table
EXPECTED BEHAVIOR
-----------------------
Only one Mod number has been selected and Authorized. Still Account is Unauthorized in sttm_cust_account, but Sttb_account already become authorized.
If STTB_ACCOUNT is already authorized updated means system allows to do transaction for Unauthorize account as well.
While Authorize system should validate to select all Mod number or Unauth status should be properly updated other tables as well.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Launch STDCUSAC Screen
2. Create account by input Mandatory fields and saved
3. Before First Auth user did modify one time account
4. Authorize STDCUSAC by selecting only one Mod number 1
5. STDCUSAC still under Unauthorize, but STTB_ACCOUNT table already updated account as authorized
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, system allows to do transaction for Unauthorize account as well which is not correct system behaviour.
Changes
Apply Patch 14.6.0.2.0
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 |