TD - Issue With EVENTS and sequence number When Back Dated TD Is Booked And Modified Before Authorize
(Doc ID 2480438.1)
Last updated on SEPTEMBER 10, 2020
Applies to:Oracle FLEXCUBE Universal Banking - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Issue with EVENTS and sequence number when back dated TD is booked and modified before authorize.
Steps to simulate:
Step 1- Booked BACK Dated TD, Saved the record (Say app_dt 28-may-2021 and TD booking date 1-Apr-2021)
Record in Unauth status and no record will be there in event will be fired for that account.
Step 2- Modified above TD and changed initial deposit amount, saved the record
Now AMND event will fire with event sequence number 1 for event date with 28-May-21
Step 3- Authorized TD record
Now DEBK event will fire with event sequence number 2 for event date with 1-Apr-2021
Note: Please simulate the issue with Tanking required = 'N' for STDCUSTD screen.
It is behaving as below, if tanking required= 'Y'.
1. Saved an account and then made modification.
2. No AMND event fired
3. Only after authorization of both the modifications, an event DEBK is fired.
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