My Oracle Support Banner

CL > Future Dated VAMI Reversal posts incorrect ESN in Master table (Doc ID 2461531.1)

Last updated on MARCH 12, 2021

Applies to:

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

Symptoms

Future Dated VAMI Reversal - Incorrect Latest ESN in account master

Latest ESN in account master goes incorrect when user reverses a future dated VAMB, when there is an event after VAMB.

Simulation Steps:
Step 1: Book a back dated loan with a manual payment scheduled for today. ---> Latest ESN is 3 (BOOK-INIT-DSBR)
Step 2: Book a Future dated VAMI ---> Latest ESN 4 (BOOK-INIT-DSBR-VAMB)
Step 3: Process manual payment scheduled for today from CLDPYMNT screen ---> Latest ESN is 5 (BOOK-INIT-DSBR-VAMB-MLIQ)
Step 4: Reverse the future dated VAMI booked in Step 2
Actual Result: Latest ESN is 3

Expected Result Latest ESN should be 6

As a result on this following two problems observed:
1. When user posts next event on this loan, that event gets stored with ESN 4
2. When user posts one more event, system throws unique constraint error.

The root cause for the issue is incorrect update of Latest ESN in master table while reversing future dated VAMI.

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.