My Oracle Support Banner

R12: AP: Cash Ledger Prepayment Applied Event on Standard Invoice Failed Accounting "This line cannot be accounted until the accounting event for the application Payables" (Doc ID 2811901.1)

Last updated on JUNE 21, 2023

Applies to:

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

Symptoms

A standard invoice is not getting accounted after it was matched with a prepayment invoice and the accounting is failing with error message:


ERROR
-----------------------

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: xxxxx.

 

Note: The check_id is the payment for the Prepayment invoice applied to the Standard invoice.



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


1. Run the request name Create Accounting.
2. Review the output of Subledger Accounting Program Report.

 

 

The FND Log while running online create accounting from Invoice Workbench for standard invoice shows these error messages:

 

BEGIN of procedure modify_message
p_application_id = 200
p_appli_s_name = XLA
p_msg_name = XLA_AP_BFLOW_PE_NOT_FOUND
p_token_1 = APPLICATION_NAME
p_value_1 = Payables
p_token_2 = APPLIED_TO_ENTITY_ID
p_value_2 = p_entity_id
p_token_3 = APPLIED_TO_ENTITY_CODE
p_value_3 = AP_PAYMENTS
p_token_4 = APPLICATION_ID
p_value_4 = 200
p_event_id = p_event_id
p_ledger_id = p_ledger_id
BEGIN of procedure common_modify_message
BEGIN of procedure msg_bflow_pe_not_found
BEGIN of procedure get_transaction_details
p_application_id:200
p_entity_id:p_entity_id
BEGIN of procedure BUILD_MESSAGE
p_appli_s_name = XLA
p_msg_name = XLA_AP_BFLOW_PE_NOT_FOUND_DTL
p_token_1 = APPLICATION_NAME
p_value_1 = Payables
p_token_2 = TRX_DATA
p_value_2 = check_id: xxxxx
p_event_id = p_event_id
p_ledger_id = p_ledger_id
BEGIN of procedure STACK_ERROR
p_appli_s_name = XLA
p_msg_name = XLA_AP_BFLOW_PE_NOT_FOUND_DTL
p_event_id = p_event_id
p_ledger_id = p_ledger_id
END of procedure STACK_ERROR
END of procedure BUILD_MESSAGE
END of procedure msg_bflow_pe_not_found
END of procedure common_modify_message
END of procedure modify_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
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.