My Oracle Support Banner

R12: AP/XLA: The Following Error Messages “XLA-95103 Failure in xla_journal_entries_pkg.reverse_journal_entry” and “P_msg_name XLA_AP_INVALID_AMT_BASE” Shown in the FND Debug While Running the GDF Fix ap_func_curr_inv_with_base_amt_fix.sql (Doc ID 3037647.1)

Last updated on JULY 26, 2024

Applies to:

Oracle Subledger Accounting - Version 12.0.0 and later
Oracle Payables - Version 12.0.0 and later
Information in this document applies to any platform.

Symptoms

While applying ap_func_curr_inv_with_base_amt_fix.sql from document R12: Generic Data Fix (GDF) Patch to Correct Functional Currency Invoices for Which Base Amount is Populated (Doc ID 1272497.1), the following error messages appear in the FND Debug:

MODULE LOG_LEVEL MESSAGE_TEXT
xla.plsql.xla_datafixes_pub.reverse_journal_entries 1 Returned from  xla_journal_entries_pkg.reverse_journal_entry.
xla.plsql.xla_datafixes_pub.reverse_journal_entries 1 Failure in xla_journal_entries_pkg.reverse_journal_entry. Please verify log file.
fnd.plsql.APP_EXCEPTION.RAISE_EXCEPTION.dict_auto_log 4 "-: XLA-95103: An internal error occurred.  Please inform your system administrator or support representative that:
An internal error has occurred in the program xla.plsql.xla_datafixes_pub.reverse_journal_entries.  Failure in xla_journal_entries_pkg.reverse_journal_entry. Please verify log file.."
AP.PLSQL.AP_ACCTG_DATA_FIX_PKG.Undo_Accounting 2 l_Return_Status=U
AP.PLSQL.AP_ACCTG_DATA_FIX_PKG.Undo_Accounting 2 "Undo_Accounting : Error in xla_DataFixes_Pub.Reverse_Journal_entries:FND"
fnd.plsql.fnd_file.PUT_LINE 3 "sid:sid: Undo Accounting Unsuccessful for Invoice id &invoice_id event id &event_id<p>"
AP.PLSQL.AP_ACCTG_DATA_FIX_PKG.Undo_Accounting 2 "Undo Accounting Unsuccessful for Invoice id &invoice_id event id &event_id"
xla.plsql.xla_journal_entries_pkg.create_mrc_reversal_entry 2 BEGIN of procedure create_mrc_reversal_entry
xla.plsql.xla_journal_entries_pkg.create_mrc_reversal_entry 2 p_orig_event_id:&event_id
xla.plsql.xla_je_validation_pkg.balance_manual_entry 2 BEGIN of function balance_manual_entry
xla.plsql.xla_je_validation_pkg.initialize 2 BEGIN of procedure initialize
xla.plsql.xla_je_validation_pkg.initialize 3 g_use_ledger_security = N
xla.plsql.xla_je_validation_pkg.initialize 2 END of procedure initialize
xla.plsql.xla_je_validation_pkg.balance_manual_entry 1 Processing ae_header_id = &ae_header_id
xla.plsql.xla_je_validation_pkg.balance_manual_entry 1 starting g_err_count = 0
xla.plsql.xla_je_validation_pkg.balance_by_ledger 2 BEGIN of function balance_by_ledger - ledger_id = &ledger_id
xla.plsql.xla_je_validation_pkg.populate_ledger_info 2 BEGIN of function populate_ledger_info
xla.plsql.xla_je_validation_pkg.populate_ledger_info 2 END of function populate_ledger_info
xla.plsql.xla_je_validation_pkg.load_lines 2 BEGIN of procedure load_lines
xla.plsql.xla_je_validation_pkg.load_lines 1 # lines inserted = 10
xla.plsql.xla_je_validation_pkg.load_lines 2 End of procedure load_lines
xla.plsql.xla_je_validation_pkg.validation 2 BEGIN of procedure validation
xla.plsql.xla_je_validation_pkg.validation 5 before error count = 0
xla.plsql.xla_je_validation_pkg.validate_lines 2 BEGIN of function validate_lines
xla.plsql.xla_je_validation_pkg.validate_lines 3 BEGIN LOOP - invalid line
xla.plsql.xla_je_validation_pkg.validate_lines 5 LOOP - invalid line: ae_header_id = &ae_header_id, ae_line_num = 1
xla.plsql.xla_accounting_err_pkg.build_message 2 BEGIN of procedure BUILD_MESSAGE
xla.plsql.xla_accounting_err_pkg.build_message 2 p_appli_s_name = XLA
xla.plsql.xla_accounting_err_pkg.build_message 2 p_msg_name = XLA_AP_INVALID_AMT_BASE
xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_1 = LINE_NUM
xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_1 = 1
xla.plsql.xla_accounting_err_pkg.build_message 2 p_entity_id = &entity_id
xla.plsql.xla_accounting_err_pkg.build_message 2 p_event_id = &event_id
xla.plsql.xla_accounting_err_pkg.build_message 2 p_ledger_id = &ledger_id
xla.plsql.xla_accounting_err_pkg.build_message 2 p_ae_header_id = &ae_header_id
xla.plsql.xla_accounting_err_pkg.build_message 2 p_ae_line_num = 1
xla.plsql.xla_accounting_err_pkg.build_message 2 p_accounting_batch_id =
xla.plsql.xla_accounting_err_pkg.stack_error 2 BEGIN of procedure STACK_ERROR
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_appli_s_name = XLA
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_msg_name = XLA_AP_INVALID_AMT_BASE
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_entity_id = &entity_id
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_event_id = &event_id
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ledger_id = &ledger_id
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ae_header_id = &ae_header_id
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ae_line_num = 1
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_accounting_batch_id =
xla.plsql.xla_accounting_err_pkg.stack_error 1 l_msg_number = 95313
xla.plsql.xla_accounting_err_pkg.stack_error 2 END of procedure STACK_ERROR
xla.plsql.xla_accounting_err_pkg.build_message 2 END of procedure BUILD_MESSAGE

 Steps to reproduce the issue:

  1. Apply the action plan from document R12: Generic Data Fix (GDF) Patch to Correct Functional Currency Invoices for Which Base Amount is Populated (Doc ID 1272497.1)
  2. Before running the fix script, follow the point C) from document AP: How To Create and Capture an FND Debug Logfile (Doc ID 1320736.1) to enable the FND debug profiles
  3. Run fix script ap_func_curr_inv_with_base_amt_fix.sql
  4. Check the FND debug log.
  5. follow the point C) from document AP: How To Create and Capture an FND Debug Logfile (Doc ID 1320736.1) to disable the FND debug log profiles

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.