My Oracle Support Banner

Application processing using workflow on booking second application on the same liability or customer id the liability outstanding becomes zero (Doc ID 2710970.1)

Last updated on SEPTEMBER 20, 2020

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
On performing the new application of same existing client, if there is the outstanding in existing liability than after completion of new application, liability outstanding will become zero.

EXPECTED BEHAVIOR
-----------------------
The Liability Should be Added/Updated with Utilization as the Incremental Value and not the value as per new Facility Utilization

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Book a Application using Origination(ORDMUSAE)
2. on Booking Second Application on the Same Client the Utilization at the liability amount becomes 0 instead of updating the Liability as per Previous Utilization


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users can see Liability Balance Imbalance.

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.