My Oracle Support Banner

EOD abort on MARKEOFI when procesing transaction is posted with back dated transaction date which cause AC-FINBAL1 Error (Doc ID 3039042.1)

Last updated on AUGUST 02, 2024

Applies to:

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

Symptoms

On : 11.11.0.0.0 version, Production Support-SET

abort in EOD for the logical date Current date,in AP_UBS_MARK_EOFI_SHELL .
While analyzing the issue , we found that an entry in actb_daily_log with period_code ='JUN' and transaction date as 29/06/2024
but in the table gl_tmp_xf_stcap_txns , transaction date is correctly populated as 04/07/2024 for the account 988756713001.


Transaction posted in gl_tmp_xf_stcap_txns is populated with current date but while posting in actb_daily_log is populated with trn_dt as back value dated.


ERROR
-----------------------
Error is,
ORA-0000: normal, successful completion UBS batch execution failed for mark eofi AC-FINBL1
ORA-20000: ORA-0000: normal, successful completion UBS batch execution failed for mark eofi AC-FINBL1 Line: 75
ORA-06512: at "FCHOST.AP_UBS_MARK_EOFI_SHELL", line 55
ORA-06512: at "FCHOST.AP_UBS_MARK_EOFI_SHELL", line 55 Failed in ap_ubs_mark_eofi_shell




BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users facing issue in EOD for actb_daily_entries details processing 

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.