Auto invoice error: Please supply both an invoicing rule and an accounting rule for this invoice
Hi friends , we are going to discuss about Auto invoice error of please supply both an invoicing rule and an accounting rule for this invoice. In this post , We will share the action step and the proposed solution to resolve this Auto invoice error of Please supply both an invoicing rule and an accounting rule for this invoice. This error comes in the AR Interface when we do import the sales order invoices into AR module. We will share complete step by step solution and will resolve this error in this further post.
Issue Cause of Auto invoice error of Please supply both an invoicing rule and an accounting rule for this invoice
The cause of the issue is the 'Accounting_rule_id' column in the AR interface which is populated.
Order Management passes an invoicing rule and an accounting rule for each
order transaction interfaced to Oracle Receivables, except for when the accounting rule is
Immediate, in which case Order Management does not pass any value (inserts null).
Issue Resolution of Auto invoice error of Please supply both an invoicing rule and an accounting rule for this invoice
We need to set two columns "NULL" in the ra_interface_lines_all tables to resolve this issue.
ACCOUNTING_RULE_ID=NULL
INVOICING_RULE_ID=NULL
Step by Step to to resolve the Auto Invoice Errors
Step 1:- For Example , Here below is the Stuck Transaction in the AR Interface with the Auto invoice error of please supply both an invoicing rule and an accounting rule for this invoice.
Auto invoice error: Please supply both an invoicing rule and an accounting rule for this invoice |
Step 2:-
To set the ACCOUNTING_RULE_ID=NULL & INVOICING_RULE_ID=NULL for this stuck AR Transaction. We need to click on that transaction and then go to the Help ==> Diagnostic ==> Examine.
Auto invoice error: Please supply both an invoicing rule and an accounting rule for this invoice |
Step 3:-
Here below , we need to keep this value null for both column ACCOUNTING_RULE_ID.
0 comments:
Post a Comment