My Oracle Support Banner

Loan Got Liquidated even though Adhoc charge was pending for payment (Doc ID 2557684.1)

Last updated on SEPTEMBER 09, 2019

Applies to:

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

Symptoms

On : 12.2 version, Production Support-SET

ACTUAL BEHAVIOR
---------------
When there are two schedule due dates for an adhoc charge component one with 0 due and other with Non-Zero due, system picks the 0 due and omits the actual due to be paid while populating during Manual Payment

EXPECTED BEHAVIOR
-----------------------
System should fetch the non-zero due and populate the same during Manual Payment

STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Select an account where adhoc charge is booked and Reversed and on the same day another adhoc charge is booked
2. From the manual payment screen populate the dues
3. Verify the amount due of the adhoc charge components

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot pay the adhoc charge components thereby liquidating the account in spite of having balance

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
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.