R12: AP: Payment Clearing Event Fails with Error Message "The applied-to sources provided for this line are invalid or incomplete" (Doc ID 2975751.1)

Last updated on SEPTEMBER 27, 2023

Applies to:

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

Symptoms

Unable to account any Payment Cleared event from a payment, the accounting is failing with accounting errors:

Error Number: 0
Error Message: The applied-to sources provided for this line are invalid or incomplete. Either the transaction line may not be applied to a previous transaction, or your journal line definition is incorrectly defined to support business flow functionality.

Error Number: 0
Error Message: 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 Payables have been accounted: check_id: XXXXXXX.

The issue can be reproduced at will with the following steps:

Responsibility Payables Manager
Navigation: Menu > View > Requests > Submit a New Request... > Single Request
Select from List of Values (LOV) > Create Accounting program
Provide the End Date parameter > [B] Submit
See the output.

The FND Debug Log shows these error messages:

xla.plsql.xla_accounting_errors_pkg.modify_message 2 BEGIN of procedure modify_message
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_application_id = 200
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_appli_s_name = XLA
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_msg_name = XLA_AP_BFLOW_PE_NOT_FOUND
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_token_1 = APPLICATION_NAME
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_value_1 = Payables
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_token_2 = APPLIED_TO_ENTITY_ID
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_value_2 = &value_2
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_token_3 = APPLIED_TO_ENTITY_CODE
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_value_3 = AP_PAYMENTS
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_token_4 = APPLICATION_ID
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_value_4 = 200
[...]
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_event_id = &event_id
xla.plsql.xla_accounting_errors_pkg.modify_message 2 p_ledger_id = &ledger_id
[...]
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_BFLOW_PE_NOT_FOUND_DTL
xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_1 = APPLICATION_NAME
xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_1 = Payables
xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_2 = TRX_DATA
xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_2 = check_id: &check_id
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_NOT_FOUND_DTL
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: Payment Clearing Event Fails with Error Message "The applied-to sources provided for this line are invalid or incomplete" (Doc ID 2975751.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!