Cannot Delete Batch Due To The Batch Number Has Already Auth In Detb_jrnl_log In Previous Day.
(Doc ID 2636905.1)
Last updated on FEBRUARY 19, 2020
Applies to:Oracle FLEXCUBE Universal Banking - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
After EOD , DE uploaded entries should move from detb_jrnl_log to detb_jrnl_log_hist table, however, it does not.
System still keep the same batch number while it has already in authorized status. Hence when user upload with the same batch number recently and the batch number has already recorded in detb_jrnl_log from previous day then the system does not allow to delete the batch number even if it is in unauth status.
System throw error as batch has already authorized in Journal_log.
System should move the previous days data into history table and allow user to delete the unauthorized batch.
The issue has the following business impact:
Due to this issue, users cannot delete unauthorized DE batch.
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