My Oracle Support Banner

TF|system Didnt Delete Records From Actb_recon_msater When User Detele Record From LCDTRONL Screen (Doc ID 2453736.1)

Last updated on FEBRUARY 20, 2019

Applies to:

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

1- user opened LCDAVMNT screen and aval LC contract and opened settlement
tab and changed account of AVAIL_SET_AMTEQ to be xxxSUND07 (Reconciled GL)
2- user deleted the transaction before authorization
3-user was trying to repeat the first step again the attached error has been
appeared (MAIN entry is already exist for recon No )
4- when we checked table actb_recon_master after deleting the transaction ,
we found that the record was not deleted from table

Root Cause :

Recon master entry was not getting deleted during undo of availment because
of which further availments were not getting saved

Fix :-
Fix provided to delete the recon master entry during undo of availment

Symptoms

SYSTEM FAILS TO DELETE RECORD FROM ACTB_RECON_MASTER DURING UNDO IN LCDAVAMNT 1- user opened LCDAVMNT screen and aval LC contract and opened settlement tab and changed account of AVAIL_SET_AMTEQ to be xxxSUND07 (Reconciled GL) 2- user deleted the transaction before authorization 3-user was trying to repeat the first step again the attached error has been appeared (MAIN entry is already exist for recon No ) 4- when we checked table actb_recon_master after deleting the transaction , we found that the record was not deleted from table

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.