R12: AP/XLA: Error "There is no Applied To Amount for the subledger journal entry line." When Attempting To Account a Standard Invoice After Prepayment Application (Doc ID 3077830.1)

Last updated on MARCH 31, 2025

Applies to:

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

Symptoms

When attempting to run the Create Accounting concurrent program, the following error occurs for a standard invoice after the prepayment application:

Error Number: 0

Error Message: There is no Applied To Amount for the subledger journal entry line. Please inform your system administrator or support representative that the source assigned to the accounting attribute Applied To Amount does not have a value. Please assign a source containing a value to the accounting attribute Applied to Amount in the Accounting Attribute Assignments window.

The FND Debug Log while running online Create Accounting from Invoice Workbench for respective standard invoice shows these messages:

MODULE LOG_LEVEL MESSAGE_TEXT

xla.plsql.xla_events_pkg.event_exists    2    BEGIN of procedure event_exists
xla.plsql.xla_events_pkg.event_exists    2    source_application_id =
xla.plsql.xla_events_pkg.event_exists    2    application_id = 200
xla.plsql.xla_events_pkg.event_exists    2    legal_entity_id = &legal_entity_id
xla.plsql.xla_events_pkg.event_exists    2    ledger_id = &ledger_id
xla.plsql.xla_events_pkg.event_exists    2    entity_type_code = AP_INVOICES
xla.plsql.xla_events_pkg.event_exists    2    transaction_number = &invoice_num
xla.plsql.xla_events_pkg.event_exists    2    source_id_int_1 = &invoice_id
xla.plsql.xla_accounting_pkg.events_processor    1    event_id=&event_id event_date=&event_date status=U

xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.set_event_info    2    BEGIN of set_event_info
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.set_event_info    2    p_event_id = &event_id
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.GetTranslatedEventInfo    2    BEGIN of GetTranslatedEventInfo
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.GetTranslatedEventInfo    2    -> CALL xla_accounting_cache_pkg.get_event_info API
xla.plsql.xla_accounting_cache_pkg.get_event_info    2    BEGIN of procedure GET_EVENT_INFO
xla.plsql.xla_accounting_cache_pkg.get_event_info    2    p_ledger_id = &ledger_id
xla.plsql.xla_accounting_cache_pkg.get_event_info    2    p_event_class_code = PREPAYMENT APPLICATIONS
xla.plsql.xla_accounting_cache_pkg.get_event_info    2    p_event_type_code = PREPAYMENT APPLIED
xla.plsql.xla_accounting_cache_pkg.get_event_info    2    p_ledger_event_class_name = Prepayment Applications
xla.plsql.xla_accounting_cache_pkg.get_event_info    2    p_session_event_class_name = Prepayment Applications
xla.plsql.xla_accounting_cache_pkg.get_event_info    2    p_ledger_event_type_name = Prepayment Applied
xla.plsql.xla_accounting_cache_pkg.get_event_info    2    p_session_event_type_name = Prepayment Applied
xla.plsql.xla_accounting_cache_pkg.get_event_info    2    END of procedure GET_EVENT_INFO
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.GetTranslatedEventInfo    2    END of GetTranslatedEventInfo
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.set_event_info    1    -> Call Extract Source Values Disagnostics routine
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.insert_diag_event    2    BEGIN of insert_diag_event
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.insert_diag_event    1    SQL- Insert xla_diag_events the event_id =&event_id
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.insert_diag_event    1    Number of Diagnostic events inserted = 0
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.insert_diag_event    2    END of insert_diag_event
xla.plsql.XLA_AE_JOURNAL_ENTRY_PKG.set_event_info    2    END of set_event_info
xla.plsql.XLA_AE_LINES_PKG.SetExtractLine    2    BEGIN of SetExtractLine
xla.plsql.XLA_AE_LINES_PKG.SetExtractLine    3    Extract line number = &invoice_distribution_id
xla.plsql.XLA_AE_LINES_PKG.SetExtractLine    2    END of SetExtractLine
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 = 2
xla.plsql.xla_je_validation_pkg.validate_lines    3    END LOOP - invalid line
xla.plsql.xla_je_validation_pkg.update_error_status    2    BEGIN of procedure update_error_status
xla.plsql.xla_je_validation_pkg.update_error_status    3    # xla_ae_headers updated to C_AE_STATUS_INVALID = 8
xla.plsql.xla_je_validation_pkg.update_error_status    3    # xla_ae_headers updated to C_AE_STATUS_RELATED = 0
xla.plsql.xla_je_validation_pkg.update_error_status    3    # xla_events_gt updated = 8
xla.plsql.xla_je_validation_pkg.update_error_status    2    End of procedure update_error_status
xla.plsql.xla_accounting_err_pkg.insert_errors    2    BEGIN of procedure INSERT_ERRORS
xla.plsql.xla_accounting_err_pkg.insert_errors    1    Count of Error Messages in the stack = 4
xla.plsql.xla_accounting_err_pkg.reset    2    BEGIN of procedure RESET
xla.plsql.xla_accounting_err_pkg.reset    2    END of procedure RESET
xla.plsql.xla_accounting_err_pkg.insert_errors    2    END of procedure INSERT_ERRORS
xla.plsql.xla_accounting_pkg.accounting_program_events    2    p_errbuf = Accounting Program completed Normal with some events in error
xla.plsql.xla_accounting_pkg.accounting_program_events    2    p_retcode = 1

[...]
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_BFLOW_PE_NO_APPLIED_AMT
xla.plsql.xla_accounting_err_pkg.build_message 2 p_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 =
xla.plsql.xla_accounting_err_pkg.build_message 2 p_ae_line_num =
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_BFLOW_PE_NO_APPLIED_AMT
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_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 =
xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ae_line_num =
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 = 0
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

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

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

R12: AP/XLA: Error "There is no Applied To Amount for the subledger journal entry line." When Attempting To Account a Standard Invoice After Prepayment Application (Doc ID 3077830.1)

Applies to:

Symptoms

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!