app ar 11526 please complete the offset account assignments

Troubleshooting Autoinvoice Import

metalink ： 1089172.1

In this Document

Applies to: 

Oracle Receivables (AR): AutoInvoice Information Center > Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 > Note 1089172.1

This note was created to facilitate troubleshooting AutoInvoice Execution Report Error Messages. In such scenarios, the AutoInvoice process completes successfully. When the process completes, the AutoInvoice Execution Report can be reviewed to verify any validation errors experienced.  Such error messages are commonly found on the AutoInvoice Execution Report and require additional troubleshooting to resolve.  This note provides the common errors experienced, the cause, the actions required to resolve, and additional reference material to help explain such issues.   For general AutoInvoice Troubleshooting, please review Note 1075757.1 , Troubleshooting AutoInvoice for Oracle Receivables Release 12. For a comprehensive list of all AutoInvoice errors, please review Note 1138254.1 , Listing of AutoInvoice Error Messages and Troubleshooting Tips to Resolve each Error If the AutoInvoice Concurrent Request failed with an error status and no execution / validation report was generated then please review  Note 1082238.1 Troubleshooting AutoInvoice: Concurrent Request Failures (Request Status = Error) Also check out the new AutoInvoice Post-Process validation report tool Note 1523525.1 . This report will give you recommendations and action items to fix the validation errors raised by AutoInvoice.

Troubleshooting Steps

Autoinvoice execution report errors:  causes and actions, 1. customer, address, remit to address, and contact errors.

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 1.1 Invalid bill to customer ID (ORIG_SYSTEM_BILL_CUSTOMER_ID) Value passed as Null Value passed does not exist in HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID Transaction Source Setup Error (should have listed REF) Note 1097862.1 , AutoInvoice Error: Invalid bill to customer id (ORIG_SYSTEM_BILL_CUSTOMER_ID) 1.2 Invalid bill to customer reference (ORIG_SYSTEM_BILL_CUSTOMER_REF) Value passed as Null Value passed does not exist in HZ_CUST_ACCOUNTS.original_system_reference Transaction Source Setup Error (should have listed ID) Note 1097846.1 , AutoInvoice Error: Invalid bill to customer reference (ORIG_SYSTEM_BILL_CUSTOMER_REF) 1.3 The Bill To address ID must exist in Oracle Receivables, and it must be assigned to the Bill To customer ORIG_SYSTEM_BILL_ADDRESS_ID. Value passed as Null Value passed is not properly defined as a Bill To Site (inactive or invalid value) Transaction Source Setup Error (should have listed REF) Note 1097925.1 , AutoInvoice Error: The Bill To address id must exist in Oracle Receivables, and it must be assigned to the Bill To customer ORIG_SYSTEM_BILL_ADDRESS_ID 1.4 The Bill To address reference must exist in Oracle Receivables, and it must be assigned to the Bill To customer (ORIG_SYSTEM_BILL_ADDRESS_REF) Value passed as Null Value passed is not properly defined as a Bill To Site (inactive or invalid value) Transaction Source Setup Error (should have listed ID) Note 365287.1 , AutoInvoice Error: The Bill To Address Reference Must Exist In Receivables, And It Must Be Assigned To The Bill To Customer (ORIG_SYSTEM_BILL_ADDRESS_REF) 1.5 The bill to customer of your credit memo transaction must be the same or related to the one of the invoice it is crediting RMA was created and customer or customer address was changed Note 413607.1 , AutoInvoice Error: The Bill To Customer Of Your Credit Memo Transaction Must Be The Same Or Related To The One Of The Invoice It Is Crediting 1.6 Invalid ship to customer ID (ORIG_SYSTEM_SHIP_CUSTOMER_ID) Value passed as Null Value passed is not properly defined as a Ship To site use (inactive or invalid value) Transaction Source Setup Error (should have listed REF) Due to Bug 3424950 this error is not being displayed and instead the system is returning the error noted below for ORIG_SYSTEM_SHIP_ADDRESS_ID.  Steps to resolve have been included in that resolution article. 1.7 Invalid ship to customer reference (ORIG_SYSTEM_SHIP_CUSTOMER_REF) Value passed as Null Value passed is not properly defined as a Ship To site use (inactive or invalid value) Transaction Source Setup Error (should have listed ID) Note 219868.1 , AutoInvoice Error: The Supplied Ship To Address Reference Must Exist In Oracle Receivables And It Must Agree With The Supplied Ship To Customer(ORIG_SYSTEM_SHIP_ADDRESS_REF) 1.8 Invalid sold to customer id (ORIG_SYSTEM_SOLD_CUSTOMER_ID) Value passed as Null Value passed does not exist in HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID Transaction Source Setup Error (should have listed REF) Note 1161925.1 , AutoInvoice Error: Invalid sold to customer reference (ORIG_SYSTEM_SOLD_CUSTOMER_REF) 1.9 Invalid sold to customer reference (ORIG_SYSTEM_SOLD_CUSTOMER_REF) Value passed as Null Value passed does not exist in HZ_CUST_ACCOUNTS.original_system_reference Transaction Source Setup Error (should have listed ID) Note 1161925.1 , AutoInvoice Error: Invalid sold to customer reference (ORIG_SYSTEM_SOLD_CUSTOMER_REF) 1.10 The supplied ship to address ID must exist in Oracle Receivables, and it must agree with the supplied ship to customer (ORIG_SYSTEM_SHIP_ADDRESS_ID) or The supplied ship to address ID must exist in Oracle Receivables, and it must agree with the supplied ID Value passed as Null Value passed is not properly defined as a Ship To Site (inactive or invalid value) Transaction Source Setup Error (should have listed REF) Note 262735.1 , AutoInvoice Error: The supplied ship to address id must exist in Oracle Receivables, and it must agree with the supplied ship to customer (ORIG_SYSTEM_SHIP_ADDRESS_ID) 1.11 The supplied ship to address reference must exist in Oracle Receivables, and it must agree with the supplied ship to customer (ORIG_SYSTEM_SHIP_ADDRESS_REF) Value passed as Null Value passed is not properly defined as a Ship To Site (inactive or invalid value) Transaction Source Setup Error (should have listed ID) Note 219868.1 , AutoInvoice Error: The Supplied Ship To Address Reference Must Exist In Oracle Receivables And It Must Agree With The Supplied Ship To Customer (ORIG_SYSTEM_SHIP_ADDRESS_REF) 1.12 The Bill To contact ID must exist in Oracle Receivables, and it must be assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID) Contact is not valid for the site specified Contact has been end dated or disabled Note 747900.1 , AutoInvoice Error: The Bill To Contact Id Must Exist In Oracle Receivables, And It Must Be Assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID) 1.13 The Bill To contact ID must exist in Oracle Receivables, and it must be assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_REF) Contact is not valid for the site specified Contact has been end dated or disabled Note 747900.1 , AutoInvoice Error: The Bill To Contact Id Must Exist In Oracle Receivables, And It Must Be Assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID) 1.14 The supplied ship to contact ID must exist in Oracle Receivables, and it must agree with the supplied ship to customer (ORIG_SYSTEM_SHIP_CONTACT_ID) Contact is not valid for the site specified Contact has been end dated or disabled Note 747900.1 , AutoInvoice Error: The Bill To Contact Id Must Exist In Oracle Receivables, And It Must Be Assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID) 1.15 The Bill To contact ID must exist in Oracle Receivables, and it must be assigned to the Bill To customer (ORIG_SYSTEM_SHIP_CONTACT_REF) Contact is not valid for the site specified Contact has been end dated or disabled Note 747900.1 , AutoInvoice Error: The Bill To Contact Id Must Exist In Oracle Receivables, And It Must Be Assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID) 1.16 Balance forward billing is enabled for this customer at the account level, but is either disabled or not defined at site level or Balance forward billing is enabled for this customer but disabled at the account site level Incorrect Setup Step-by-Step instructions to fix are in Note 1053006.1 , Error "Balance forward billing is enabled for this customer but disabled at the account site level" is raised when creating transactions for Balance Forward enabled customers 1.17 11.5 Only AutoInvoice does not default the paying customer information, if the payment method associated with the Bill to customer is of type 'BR', Bills Receivable. Bug 3666519 Patch 3666519 (The fix is also included in 11i.AR.O / 11i.FP.G) Fixed files raaihd.lpc to 115.10.1158.3 raavpm.lpc 115.7.1159.4 1.18 Cannot get remit to address  A default remit to address is not setup.  Note 1101855.1 Troubleshooting Remit To Address in Oracle Receivables The following notes can be referenced for Customer, Address, and Contact related issues: Note 1097660.1 , Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions. Note 1069338.1 , How To Define Customers For AutoInvoice.

2. Accounting Errors

• Note 1080995.1 , Troubleshooting AutoAccounting in AutoInvoice
• Note 1069052.1 , Setting Up AutoAccounting Rules In Receivables.
• Note 1228525.1 How to Import and Troubleshoot Distributions in AutoInvoice Using RA_INTERFACE_DISTRIBUTIONS_ALL

3. Currency Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 3.1 The supplied amount must match unit selling price times the quantity when you do not use an AutoInvoice Clearing account. Currency Precision Note 1111566.1 , AutoInvoice Error: The supplied amount must match unit selling price times the quantity when you do not use an AutoInvoice Clearing account. 3.2 You cannot import transactions using a euro-derived currency after that currency's specified end date. Currency End Date Required Note 965810.1 , AutoInvoice Error: You Cannot Import Transactions Using a Euro-Derived Currency After That Currency's Specified End Date 3.3 Your Transaction currency must match one of the currencies which are associated with the payment method. Currency Mismatch Note 217545.1 , AutoInvoice Error: Your Transaction Currency Must Match One Of The Currencies Which Are Associated With The Payment Method

4. Transaction Type Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 4.1 Invalid transaction type name (CUST_TRX_TYPE_NAME) ((Nil)) Data/Transaction Source Setup Note 1112634.1 , AutoInvoice Error: Invalid Transaction Type Name (CUST_TRX_TYPE_NAME) 4.2 Invalid transaction type id (CUST_TRX_TYPE_ID) ((NULL)) Data/Transaction Source Setup Note 1116093.1 , AutoInvoice Error: Invalid Transaction Type id (CUST_TRX_TYPE_ID) The following note can be referenced for Tranaction Type related issues: Note 1067797.1 , Setting Up Transaction Types In Receivables

5. Transaction Flexfield Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 5.1 None of the transaction flexfield contexts you have provided for this request have enabled segments * Flexfield setup Responsibility: Receivables Manager Navigation: Setup > Financials > Descriptive > Segments Query for Application = Receivables, Title = Line Transaction Flexfield * In the Context field section, under Code, place the cursor on the record that matches the value returned by the select above * Click on Segments button * Ensure that at least one segment exists and is enabled Note 1077555.1 Troubleshooting Transaction Flexfields in AutoInvoice  (Step 1c) 5.2 All enabled segments of Transaction Flexfield must have a value. This error is raised when you do not provide the complete set of segments associated with the context you specified in the interface lines table. Review the interface table to identify with interface_line_id is raising such an error. Use the value in INTERFACE_LINE_CONTEXT to run a query in the form: Responsibility: Receivables Manger Navigation: Setup > Financials > Flexfields > Descriptive > Segments Query on Title = Line Transaction Flexfield Navigate to the Context Field Values of the form, and in the Context field, locate the record with the value that matches INTERFACE_LINE_CONTEXT above. Then click on Segments, paying attention to which segments are enabled, then make sure these same segments are provided in the Interface table. Note 1077555.1 Troubleshooting Transaction Flexfields in AutoInvoice (Step 1d)

6. Accounting Period Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 6.1 Please define all periods in which revenue is to be recognized or credited. Note that revenue cannot be recognized or credited in closed and close pending periods. Accounting Periods are not properly defined. Accounting Rule Definition Note 455691.1 , Error: Please Define All Periods In Which Revenue Is To Be Recognized Or Credited (AutoInvoice and Transaction Workbench) 6.2 Unable to derive a GL date for your transaction. Please ensure that your transaction is in a GL period which you have defined. Acounting Periods are not properly defined. Scheduled AutoInvoice Request. Note 1122898.1 , AutoInvoice Error: Unable To Derive A GL Date For Your Transaction. Please Ensure That Your Transaction Is In A GL Period Which You Have Defined

  The following note can be referenced for Date Derivation: Note 201241.1 , Troubleshooting AutoInvoice Date Derivation: GL Date, Invoice Date, Due Date, Ship Date, Billing Date, Rule Date

7. Sales Credit Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 7.1 Invalid salesrep id (SALESREP_ID) ((Nil)) Invalid Value Interfaced. Transaction Source Setup. Note 1112672.1 , AutoInvoice Error: Invalid Salesrep id (SALESREP_ID) 7.2 Invalid sales credit type name (SALES_CREDIT_TYPE_NAME) ((Nil)) Invalid Value Interfaced. Transaction Source Setup. Note 1112705.1 , AutoInvoice Error: Invalid Salesrep Number (SALESREP_NUMBER) 7.3 Invalid sales credit type id (SALES_CREDIT_TYPE_ID) ((Nil)) Invalid Value Interfaced. Transaction Source Setup. Note 1112672.1 , AutoInvoice Error: Invalid Salesrep id (SALESREP_ID) 7.4 Invalid primary salesrep number (PRIMARY_SALESREP_NUMBER) Transaction Source Setup Note 1112705.1 , AutoInvoice Error: Invalid Salesrep Number (SALESREP_NUMBER) 7.5 You must supply a value for the sales credit amount ((Nil)) Transaction Source Setup Note 1116984.1 , AutoInvoice Error: You Must Supply a Value For The Sales Credit Amount 7.6 You must supply sales credit assignments for this transaction because the system option Require Salesreps is set to Yes System Options Setup - Require Sales Person. Sales Credits are not provided in the interface. Note 1117036.1 , AutoInvoice Error: You Must Supply Sales Credit Assignments For This Transaction Because The System Option Require Salesreps Is Set To Yes 7.7 Please Enter Quota Sales Credit Percentages That Equal 100 Percent Sales Credit Percentage Note 1117668.1 , AutoInvoice Error: Please Enter Quota Sales Credit Percentages That Equal 100 Percent 7.8 Primary salesperson is invalid with current transaction date Salesrep is required but was not provided. Note 244957.1 AutoInvoice Error: Primary salesperson is invalid with current transaction date

The following note can be referenced for Sales Credit Related Issues: Note 1118944.1 , Troubleshooting AutoInvoice - Sales Credits

8. Credit Memo Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 8.1 Cannot apply the credit memo because the invoice is locked by another user. Please try again later. Data Related - Referenced Invoice. Note 1087146.1 , Cannot Apply The Credit Memo Because The Invoice Is Locked By Another User. Please Try Again Later. 8.2 You can not apply more than the original line amount OR The total amount of your credit memo cannot exceed the balance of the debit item it is crediting Invoice to be credited has existing applications (receipt, credit memo, etc). Note 1122945.1 , AutoInvoice Error: You Can Not Apply More Than The Original Line Amount 8.3 You cannot supply any account assignment for your credit memo transaction when the system option 'Use Invoice Accounting for Credit Memos' is Yes When AR: Use Invoice Accounting for Credit Memo is Yes, you should not pass distribution details. Note 1122964.1 , AutoInvoice Error: You Cannot Supply Any Account Assignment For Your Credit Memo Transaction When The System Option 'Use Invoice Accounting For Credit Memos' is Yes 8.4 The Open Receivable flag of your credit memo must match the flag of the transaction you are crediting Credit Memo/Invoice Transaction Type Open Receivables Flag Note 1122984.1 , AutoInvoice Error: The Open Receivable Flag Of Your Credit Memo Must Match The Flag Of The Transaction You Are Crediting 8.5 A credit memo is attempting to overapply a specific transaction line, but overapplication is not allowed. Credit Memo/Invoice Transaction Type Allow Overapplication Flag setting Note 1110573.1 , Troubleshooting Credit Memos in Receivables 8.6 You cannot apply a transaction with a negative amount to another transaction with a negative balance and vice versa Credit Memo/Invoice Transaction Type Allow Overapplication Flag setting Note 1174659.1 AutoInvoice Error: You cannot apply a transaction with a negative amount to another transaction with a negative balance and vice versa. 8.7 Please enter a unit selling price for this credit line that is less than the unit selling price for its target invoice line Data Related, UNIT_SELLING_PRICE Note 1145259.1 , AutoInvoice Error: Please enter a unit selling price for this credit line that is less than the unit selling price for its target invoice line 8.8 You cannot over apply this transaction. Setup Data Related Note 1147943.1 , AutoInvoice Error: You cannot over apply this transaction. 8.9 The valid values for credit method for accounting rule are PRORATE LIFO and UNIT Data Related Note 1149363.1 , AutoInvoice Error: The valid values for credit method for accounting rule are PRORATE, LIFO and UNIT. 8.10 Invoice Cannot Be Credited Due To Its Electronic Invoice Status Bug Note 884528.1 AutoInvoice Error: Invoice Cannot Be Credited Due To Its Electronic Invoice Status

The Following Notes can be used for Credit Memo Related Issues: Note 1110573.1 , Troubleshooting Credit Memos in Receivables. Note 215373.1 , How to Setup and Create Credit Memos in Receivables

9. Grouping Rule Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 9.1 You can supply at most one Receivables account for a transaction (an invoice, a debit memo or a credit memo). Data Related - Transaction Flexfields Setup Related - Grouping Rules Note 1146563.1 , AutoInvoice Error: You can supply at most one Receivables account for a transaction (an invoice, a debit memo or a credit memo) 9.2 Extensions in the copy group do not have the same values for payment channel, instrument assignment. Bug Note 1176555.1 , Autoinvoice Error: Extensions in the copy group do not have the same values for payment channel, instrument assignment.

The Following Notes can be used for Credit Memo Related Issues: Note 1084554.1 , Troubleshooting Grouping Rules In AutoInvoice Note 1067993.1 , How To Use Grouping Rules With AutoInvoice

10. Receipt, Payment Method and Bank Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 10.1 A receipt method is required when a payment extension entity is passed Payment method associated with Automatic receipts or Credit Card payments incorrectly setup Note 1205775.1 AutoInvoice Error: A receipt method is required when a payment extension entity is passed 10.2 The supplied payment method must be defined and active for the bill-to customer or site Setup Note 1058782.1 AutoInvoice Error: The supplied payment method must be defined and active for the bill-to customer or site 10.3 When the receipt method is of type Automatic, you must either supply a valid bank account or ensure that a primary bank account for the currency code of the transaction has been set up for the Bill To Date attached to the receipt method falls after transaction date Note 1072672.1 AutoInvoice Error: When the receipt method is of type Automatic, you must either supply a valid bank account or ensure that a primary bank account for the currency code of the transaction has been set 10.4 The Supplied Cust Bank account (Customer_bank_account_id) Must Be Valid And Active AutoInvoice created the customer bank account with effective date as sysdate, and the invoice date is set to the sales-order date, which was before sysdate.  This is happening for non shippable lines. Note 438237.1 AutoInvoice Error : The Supplied Cust Bank account (Customer_bank_account_id) Must Be Valid And Active 10.5 Transaction extension does not exist. Setup , Note 1271912.1 Autoinvoice Error: Transaction Extension does not exist.

11. Payment Terms

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 11.1 Please set a default payment term for the customer, site, or transaction type. You will get the error if both of the following is true: You have not setup a default payment term You have not checked Override Terms Note 1171367.1 AutoInvoice Error: Please set a default payment term for the customer, site, or transaction type 11.2 You cannot supply payment terms for your credit memo transaction. Credit Memo was passed with payment terms Note 1174094.1  AutoInvoice Error: You cannot supply payment terms for your credit memo transaction 11.3 You Must Supply Payment Terms For Your Non-credit Transaction Setup/Data Note 1171284.1 AutoInvoice Error: You Must Supply Payment Terms For Your Non-credit Transaction

12. Invoice/Transaction Numbering

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 12.1 You must supply an invoice number when your batch source indicates manual invoice numbering; otherwise you must leave invoice number blank. Setup/Data Note 277086.1   You must supply an invoice number when your batch source indicates manual invoice numbering; otherwise you must leave invoice number blank 12.2 APP-11948 Duplicate invoice number () Setup/Data Note 130377.1 APP-11948 Duplicate invoice number ()

13. Tax Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 13.1 Invalid tax exempt flag (TAX_EXEMPT_FLAG) Setup / Data Note 1086586.1 AutoInvoice Error: Invalid tax exempt flag (TAX_EXEMPT_FLAG) 13.2 The system cannot calculate the taxable basis for the imported tax line because the tax rate is 0 but the tax amount  is not 0. Please change either the tax rate or the tax amount. AMOUNT interfaced is not equal to the AMOUNT of LINE * TAX_RATE Note 742419.1 AutoInvoice Error: The system cannot calculate the taxable basis for the imported tax line because the tax rate is 0 but the tax amount is not 0. Please change either the tax rate or the tax amount. 13.3 Adjusted document information is missing in our ZX repository Bug(s) Note 551361.1 AutoInvoice Error: Adjusted document information is missing in our ZX repository 13.4 This transaction business category code does not exist Bug(s) Note 973469.1 AutoInvoice Error: Transaction Business category code does not exist 13.5 The Tax Code does not allow override of the amount includes tax flag Setup / Data Note 402892.1 AutoInvoice Error: The Tax Code Does Not Allow Override Of The Amount Includes Tax Flag 13.6 Unable to find a default tax code for this transaction Occurs in 11i due to setup and defects Note 1086193.1 AutoInvoice Error: Unable to find a default tax code for this transaction 13.7 Error in ARP_PROCESS_TAX.populate_ar_tax_struct() Setup / Data Note 1115984.1 AutoInvoice Error: Error in ARP_PROCESS_TAX.populate_ar_tax_struct

14.Miscellaneous Data Validation Errors

Note: The following errors can be experienced when the AutoInvoice Import validation process determines the transaction records are not valid to create a complete transaction:

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 14.1 You cannot define rules when your Accounting Method is Cash Basis. Bug Note 369508.1 You cannot define rules when your Accounting Method is Cash Basis. 14.2 Please supply both an invoicing rule and an accounting rule for this invoice. Setup/Data Related Note 1116934.1 , How To Setup And Troubleshoot Invoicing Rules and Accounting Rules (under section 5.j) 14.3 Unable to get the product code for inventory_item_id Setup/Date Related Note 1217094.1 AutoInvoice Error: Unable to get the product code for inventory_item_id 14.4 You must supply the amount for this transaction ( Nil ) Setup/Date Related Note 370557.1 AutoInvoice Error: You Must Supply The Amount For This Transaction ( Nil ) 14.5 This inventory item has Invoice Enabled flag set to No Setup/Date Related Note 549203.1 Autoinvoice Error: This Inventory Item Has Invoice Enabled Flag Set To No 14.6 The supplied unit of measure and the primary unit of measure of your system item must share the same unit of measure class Setup/Date Related Note 1132807.1 Troubleshooting Unit of Measure Issues with AutoInvoice 14.7 Invalid ship via (SHIP_VIA) (SHIP_VIA) Setup/Date Related Note 274785.1 Autoinvoice Error: Invalid Ship Via (Ship_Via) (Ship_Via) 14.8 Invalid Warehouse ID (WAREHOUSE_ID) (xxx) Setup/Data Related Note 1089026.1 AutoInvoice Error: Invalid Warehouse ID (WAREHOUSE_ID) (xxx) 14.9 Consolidated billing is enabled for this customer or bill-to-site, therefore you cannot import bills. Balance Forward Billing was configured at the Customer level but not at the site level Note 1082767.1 Autoinvoice Error : Consolidated billing is enabled for this customer or bill-to-site, therefore you cannot import bills. 14.10 An invoice can only reference a commitment (xxxxx) Mandatory fields are not populated for the Commitment Transaction Type that was being passed Note 755834.1 AutoInvoice Error: An Invoice Can Only Reference A Commitment 14.11 A rule end date is required when using the Daily Revenue Rate rule. (DD-MON-YY) Bugs Note 563749.1 AutoInvoice Error: A rule end date is required when using the Daily Revenue Rate rule. (DD-MON-YY) 14.12 Please define the item validation organization in the Parameters window in Order Management Setup/Data Related Note 1163873. 1 Error: Please define the item validation organization in the Parameters window in Order Management 14.13 The document created must have a non-negative total amount because the creation sign for your transaction type is Positive Setup / Data Related Note 568095.1 AutoInvoice Error: The document created must have a non-negative total amount because the creation sign for your transaction type is Positive 14.14 You cannot supply system items for your debit memo transaction Bugs Note 1265765.1 AutoInvoice Error: You cannot supply system items for your debit memo transaction 14.15 Errors: 1) Bug Note 804334.1 , Autoinvoice Error: AutoInvoice Validation Report Shows an Error with Blank Text

15. Globalization Issues (incl Latin Tax)

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 15.1 Please enter a numeric value for the total gross weight for this transaction. Please enter a numeric value for the total net weight. The value in Gross Weight was incorrectly set to be the same as Net Weight. Due to code bug documented in Bug 7656986 Please apply Patch 8871748:R12.JL.A 15.2 This Product Type Code is not associated with any Country Latin Tax Setup and/or Bugs Note 1160707.1 AutoInvoice Error: This Product Type Code is not associated with any Country 15.3 Please Enter A Fiscal Classification Code For Transaction Line and Please enter a Transaction Nature for transaction line Bug(s) Note 820473.1 AutoInvoice Error: Please Enter A Fiscal Classification Code For Transaction Line and Please enter a Transaction Nature for transaction line 15.3 Taiwan Globalizations / Localizations: All Government Uniform Invoice numbers were used for this transaction source. Please use a different transaction source for a new invoice number range Setup Note 1075056.1 AutoInvoice Error: All Government Uniform Invoice numbers were used for this transaction source. Please use a different transaction source for a new invoice number range

16. Other Errors

# Error String or Presentation Most Common Cause(s) Comprehensive List of Known Causes 16.1 in RAXTRX log file: REP-0004: Warning: Unable to open user preference file. in AutoInvoice Execution Report: No Data Found ***** ok no error Bug(s) Note 1106851.1 , AutoInvoice Error: REP-0004 Warning Unable to open user preference file 16.2 The Input Parameters which is normally shown at the top of the AutoInvoice Execution Report is missing. Bug(s) Note 807867.1 , AutoInvoice issue: Autoinvoice Execution Report Does Not Show Input Parameters Used by the Process 16.3 AutoInvoice Execution Report output shows the Selected count and Rejected count, however it shows ***** No Data Found ***** under Exceptions, no details are provided regarding the rejected rows. Setup Note 1339417.1 ,  Autoinvoice Issue: AutoInvoice Execution Report is Not Showing Validation Errors For Some Transactions

Still Have Questions?

• Test to see if the problem can be replicated in the AR transaction workbench
• Include the Autoinvoice Exception Report if any
• Include the Autoinvoice Concurrent Process log file (see Note 1079666.1 )
• Enable and include the FND debug log file generated by Autoinvoice (see Note 1079666.1 )
• Include Diagnostics:

Oracle Receivables AutoInvoice Interface Data Collection Test, this would show support what the interface data looks like. Oracle Receivables General Setup Test, this would show how the Line transaction Flexfield is defined.

•   Release 11.5: see Note 179661.1 , E-Business Suite Diagnostics 11i Test Catalog
•   Release 12.x: see Note 421245.1 , E-Business Suite Diagnostics References for R12
• 详解EBS接口开发之销售订单导入
• 自动行号功能实现不同方法研究

Oracle Apps Knowledge Sharing

Meant for sharing our knowledge related to Oracle E-Business Suite

• TECHNICAL TUTORIALS
• USEFUL LINKS
• ARTICLE INDEX
• VIDEO INDEX

Saturday, February 13, 2010

Autoinvoice error: please correct the revenue account assignment.

Iissue may be beacuse of follwing reasons 1) Autoaccouting setup 2) Memo line Setup 3) Item defination setup check 1: Go in Receivables Responsiblity Setup > Transactions > Sources Query the source that you are importing Go in the Other Information tab Check the setup for Memo Line Rule. check 2: Other way to do you can analayze the log and try to find the root cause. 1) Make sure you have done the proper setup for the source for your autoaccounting in AR Go to Setup->;Transactions->Autoaccounting Pay particular attention to the REVENUE sources and write them down. . 2) Go to each line that was rejected and manually walk through how each segment is built (fetch them from the proper sources as identified in step 1. Make sure that the accounts shown on the Autoinvoice Execution report (in the validation errors) are truly the correct accounts based on your setup. 3) Go into GL and verify that those accounts (the results of step 2) are valid, enabled, and that there are no problems with them (there probably are some recent changes that caused this) 4) If you still think they are valid after doing steps 1-3, go ahead and enter a new transaction and attempt to override the distributions to one of the invalid accounts and see if the form lets it pass. When the form rejects an account, it often puts the cursor on the bad segment -and that can be helpful in tracking down what is causing the rejections. Couple of other things you should also quick check: If it has transaction type, then you have to check the transaction type you are using and make sure that you have assigned a revenue account. If it has standard lines, then you have to check the standard lines you are using and make sure that you have assigned a sales account. Check it out in the Item defnition endable invoiceble flag, anmd check the how Sales account are linked with Revenue account. 1)Standard Lines - For an Inventory Item navigate to Menu: Setup>Transactions>Items>Inventory items, verify the ‘Sales Account’ is populated in the ‘Invoicing’ alternate region. For a Memo Line, navigate to Setup ->Transactions ->Memo Lines, and make sure that ‘Revenue Account’ is populated.

Do you think this Article is useful?

0 Responses to “Autoinvoice error: Please correct the revenue account assignment”

Post a comment, stay connected.

Popular Posts

• Query to fetch Purchase Receipt and its related Purchase order, Vendor details in Oracle Apps R12 (RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES)
• Query to Fetch Employee Details in Oracle Apps R12 (PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_JOBS, PER_ALL_POSITIONS, PER_PHONES)
• Query to get basic AP Invoice and Payment information from Oracle Apps R12
• Query to get active Customer and their Profile Details (HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUSTOMER_PROFILES, HZ_CUST_PROFILE_AMTS)
• WSH_DELIVERY_DETAILS.RELEASED_STATUS ( Pick Release Status)
• How to find Order types in R12 (Script for Order types)
• How to get Oracle Application User Password from database - oracle.apps.fnd.security.WebSessionManagerProc.decrypt
• Query fetching the customer information based on order number ( R12 - Order to Cash Cycle )
• Query To Fetch Customer Account/Site Contact Details in R12
• Query to find Supplier and their Bank Details in R12

Blog Archive

shareoracleapps.com

Site Stats (Last 30 Days)

Steps to be considered when we get ‘Please Correct Revenue Account Assignment’ in AR Autoinvoice import program?

Introduction :

This is used to fix the invalid revenue account for AR invoice

Auto accounting is used to determine the accounts when the distribution table is not populated. When Auto Invoice gives this error, it generally gives the account with the missing segment(s).

Menu: Setup>Transactions>Auto accounting Query the account mentioned in the above error and note the setup for that missing segment.

If it is based on:

Transaction Type – Menu: Setup>Transaction>Transaction Types, and verify that all accounts are populated.

Salesperson – Menu: Setup>Transactions>Salespersons, and verify that all accounts are populated.

Standard Lines – For an Inventory Item navigate to Menu: Setup>Transactions>Items>Inventory items, and verify that the ‘Sales Account’ is populated in the ‘Invoicing’ alternate region. For a Memo Line, navigate to Setup =>Transactions =>Memo Lines, and make sure that ‘Revenue Account’ is populated.

Taxes – Menu: Setup>Tax>Codes and verify that account is populated in ‘Tax’ column under the ‘Accounting’ alternate region. Additionally the following can be checked: Setup of Cross Validation Rules. Run Cross validation Listing Report in GL to identify the cross validation rule stopping the import of this line.

Know more about post.

[email protected]

Start typing and press Enter to search

ERPstuff - Oracle EBS Community

You love we care since 2006 by Malik Sikandar Hayat.

Skip to content

• Home Forums Oracle Applications (EBS) R12 & 11i Financials (GL, AP, AR, FA & CM)

APP-AR-11526: ORA-01400

Post by admin » Thu Oct 03, 2013 1:19 am

Return to “Financials (GL, AP, AR, FA & CM)”

• Home Forums
• All times are UTC

Powered by phpBB ® Forum Software © phpBB Limited

Privacy | Terms

Receivables - EBS (MOSC)

Discussions

APP-AR-11526: ORA-28113: policy predicate has error

After upgrade form 11i to R12.2.6 AR invoice import program in error

Current system time is 05-SEP-2017 21:56:39

insert into RA_INTERFACE_ERRORS (INTERFACE_LINE_ID,MESSAGE_TEXT,INVALI

APP-AR-11526: 12715851/ar/lib/raavpm.lpc 536

Error calling raavpm()

Error calling raapic()

raarrt2()+ Current system time is 05-SEP-2017 21:56:39

issued rollback in raarrt2 Current system time is 05-SEP-2017 21:56:39

• EBS_AR_Receivables

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Instructions for posting

1. Select a discussion category from the picklist.

2. Enter a title that clearly identifies the subject of your question.

3. In the body, insert detailed information, including Oracle product and version.

Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).

Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .

New to My Oracle Support Community? Visit our Welcome Center