My Oracle Support Banner

R12:AP: Invoice Failing With Hold 'Encumbrance Acctg Fail' Line Cannot Be Accounted Until the PO Accounting Event That It References Has Been Fully Accounted. (Doc ID 2802765.1)

Last updated on AUGUST 27, 2021

Applies to:

Oracle Payables - Version 12.1.3 and later
Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

In AP Accounting, following error appears:

This line cannot be accounted until the accounting event that it references has been fully accounted. Please ensure the accounting events for the transaction with the following identifiers for the application Purchasing have been accounted: po_header_id: xxxxx

 

FND Log is showing the following message:

xla.plsql.xla_accounting_errors_pkg.modify_message | BEGIN of procedure modify_message
xla.plsql.xla_accounting_errors_pkg.modify_message | p_application_id = 200
xla.plsql.xla_accounting_errors_pkg.modify_message | p_appli_s_name = XLA
xla.plsql.xla_accounting_errors_pkg.modify_message | p_msg_name = XLA_AP_BFLOW_PE_NOT_FOUND
xla.plsql.xla_accounting_errors_pkg.modify_message | p_token_1 = APPLICATION_NAME
xla.plsql.xla_accounting_errors_pkg.modify_message | p_value_1 = Purchasing
xla.plsql.xla_accounting_errors_pkg.modify_message | p_token_2 = APPLIED_TO_ENTITY_ID
xla.plsql.xla_accounting_errors_pkg.modify_message | p_value_2 = XXXXXXXX
xla.plsql.xla_accounting_errors_pkg.modify_message | p_token_3 = APPLIED_TO_ENTITY_CODE
xla.plsql.xla_accounting_errors_pkg.modify_message | p_value_3 = PURCHASE_ORDER
xla.plsql.xla_accounting_errors_pkg.modify_message | p_token_4 = APPLICATION_ID
xla.plsql.xla_accounting_errors_pkg.modify_message | p_value_4 = 201
xla.plsql.xla_accounting_errors_pkg.modify_message | p_event_id = XXXXXXXX
xla.plsql.xla_accounting_err_pkg.build_message | BEGIN of procedure BUILD_MESSAGE
xla.plsql.xla_accounting_err_pkg.build_message | p_appli_s_name = XLA
xla.plsql.xla_accounting_err_pkg.build_message | p_msg_name = XLA_AP_BFLOW_PE_NOT_FOUND_DTL
xla.plsql.xla_accounting_err_pkg.build_message | p_token_1 = APPLICATION_NAME
xla.plsql.xla_accounting_err_pkg.build_message | p_value_1 = Purchasing
xla.plsql.xla_accounting_err_pkg.build_message | p_token_2 = TRX_DATA
xla.plsql.xla_accounting_err_pkg.build_message | p_value_2 = po_header_id: XXXXXXXX
xla.plsql.xla_accounting_err_pkg.build_message | p_entity_id =
xla.plsql.xla_accounting_err_pkg.build_message | p_event_id = XXXXXXXX
xla.plsql.xla_accounting_err_pkg.build_message | p_ledger_id = 2
xla.plsql.xla_accounting_err_pkg.build_message | p_ae_header_id =
xla.plsql.xla_accounting_err_pkg.build_message | p_ae_line_num =
xla.plsql.xla_accounting_err_pkg.build_message | p_accounting_batch_id =
xla.plsql.xla_accounting_err_pkg.stack_error | BEGIN of procedure STACK_ERROR
xla.plsql.xla_accounting_err_pkg.stack_error | p_appli_s_name = XLA
xla.plsql.xla_accounting_err_pkg.stack_error | p_msg_name = XLA_AP_BFLOW_PE_NOT_FOUND_DTL
xla.plsql.xla_accounting_err_pkg.stack_error | p_entity_id =
xla.plsql.xla_accounting_err_pkg.stack_error | p_event_id = XXXXXXXX
xla.plsql.xla_accounting_err_pkg.stack_error | p_ledger_id = 2
xla.plsql.xla_accounting_err_pkg.stack_error | p_ae_header_id =
xla.plsql.xla_accounting_err_pkg.stack_error | p_ae_line_num =
xla.plsql.xla_accounting_err_pkg.stack_error | p_accounting_batch_id =
xla.plsql.xla_accounting_err_pkg.stack_error | l_msg_number = 0
xla.plsql.xla_accounting_err_pkg.stack_error | END of procedure STACK_ERROR
xla.plsql.xla_accounting_err_pkg.build_message | END of procedure BUILD_MESSAGE
xla.plsql.xla_accounting_errors_pkg.msg_bflow_pe_not_found | END of procedure msg_bflow_pe_not_found
xla.plsql.xla_accounting_errors_pkg.common_modify_message | END of procedure common_modify_message

 

xla.plsql.xla_je_validation_pkg.budgetary_control | BEGIN of procedure budgetary_control
psa.plsql.psafbcfb.psa_funds_checker_pkg.budgetary_control | BCTRL -> P_LEDGERID = 1
psa.plsql.psafbcfb.psa_funds_checker_pkg.budgetary_control | BCTRL -> MODE = P
psa.plsql.psafbcfb.psa_funds_checker_pkg.budgetary_control | BCTRL -> OVERRIDE = Y
psa.plsql.psafbcfb.psa_funds_checker_pkg.budgetary_control | BCTRL -> USER_ID =
psa.plsql.psafbcfb.psa_funds_checker_pkg.budgetary_control | BCTRL -> RESP_ID =
psa.plsql.psafbcfb.psa_funds_checker_pkg.check_for_xla_errors | Inside Program
psa.plsql.psafbcfb.psa_funds_checker_pkg.check_for_xla_errors | p_error_type=BFLOW
psa.plsql.psafbcfb.psa_funds_checker_pkg.check_for_xla_errors | Checking for BFLOW Errors
psa.plsql.psafbcfb.psa_funds_checker_pkg.budgetary_control | BCTRL -> Bflow failed
psa.plsql.psafbcfb.psa_funds_checker_pkg.budgetary_control | BCTRL -> ERROR: FATAL
xla.plsql.xla_je_validation_pkg.budgetary_control | ERROR: PSA_FUNDS_CHECKER_PKG.budgetary_control failed
fnd.plsql.APP_EXCEPTION.RAISE_EXCEPTION.dict_auto_log | "-: XLA-95103: An internal error occurred.  Please inform your system administrator or support representative that:

An internal error has occurred in the program xla_je_validation_pkg.budgetary_control.  PSA_FUNDS_CHECK_PKG.budgetary_control failed."
xla.plsql.xla_accounting_engine_pkg.PostAccountingEngine | "Error. = ORA-20001: -: XLA-95103: An internal error occurred.  Please inform your system administrator or support representative that:

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.