My Oracle Support Banner

Dormant Account With Both Dormancy Param Can Not Eb Worked. (Doc ID 2575864.1)

Last updated on SEPTEMBER 03, 2019

Applies to:

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

Symptoms

On : 12.4.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
For products LGI and DGI at AVAL event for full and partial payment it is not possible to save event AVAL when DORMANT account. for both dormancy param B and non B ,same error code has been used which is wrong.

EXPECTED BEHAVIOR
-----------------------
At AVAL event for full and partial payment should be possible to save event AVAL when DORMANT account

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Account and account class the dormancy param is Both (any) which means we should allow the account to go through when transaction si done.
2, We have parameterized AC-VAC31 as an error.
3. The issue is in acpks misc.FN_VALIDATE_AC for both dormancy param B and non B we are using the same error code which is wrong.

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.