My Oracle Support Banner

TF: System Fire LIQD Event instead of LADV Event In Case Operation Advance for BC contract (Doc ID 2775688.1)

Last updated on MAY 12, 2021

Applies to:

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

Symptoms

On : 12.0.2 version, Production Support-SET

ACTUAL BEHAVIOR
---------------
TF: system fire LIQD event instead off LADV event in case operation advance
 
While create bills on product IAVC (avliazed bills)
Change the operation from acceptance to advance , system fire the event BADV (booking advance) and it's correct behavior
in case the user modify this contract for any modifications , system fire AMND event
try to liquidate the bill , System should fire LADV (liquidation advance)
But the issue is system fire LIQD event instead off LADV event
And the reason is AMND event fired after BADV
kind find the debug files for (BADV event - AMND event - LIQD event)
 

EXPECTED BEHAVIOR
-----------------------
System should for LADV event for advance liquidation

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create BC contract
2. Change the operation from acceptance to advance , system fire the event BADV
3. User modify this contract , system fire AMND event

4. Liquidate this bill. System fires LIQD event instead of LADV event


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot see LADV event fired which causes audit issue for customer having doing advance liquidation

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.