Auto Invoice Errors

Document 1075757.
1 3/17/16, 7:05 PM
Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 (Doc ID

1075757.1)
Modified: Nov 12, 2013 Type: TROUBLESHOOTING
In this Document
Purpose
Troubleshooting Steps
1. How Does AutoInvoice Work?
2. Alternatives to AutoInvoice
3. Using Diagnostics to Check Setup
4. Identifying What Went Wrong

a. Import Failed: ERROR
b. Import Completed: Exception Report ERROR
c. Import Completed: Nothing Imported
d. Transaction Imported: Record is Incorrect
e. Master Program Failed: ERROR
f. Import Never Completes
5. Validating the Data Being Imported (Custom Interface vs. Seeded Integration)
a. Custom Integration or Data Migration Issues
b. Integration with Oracle Applications that Feed AutoInvoice
6. Troubleshooting Specific Steps in AutoInvoice
a. Accounting (AutoAccounting)
b. Credit Memos
c. Customer, Addresses and Customer Contact
d. Currency and Exchange Rates
e. Dates: Transaction Date, GL Date
f. Flexfields: Transaction, Global, Descriptive
g. Freight
h. Grouping Rules
i. Inventory Transactions (Warehouse, Items, etc)
j. Line Ordering
k. Numbering: Document Sequencing and Transaction Numbering
l. Payment Terms
https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=15bmmwf0pl_419&id=1075757.1 Page 1 of 25
Document 1075757.1 3/17/16, 7:05 PM
m. Purge
n. Invoicing and Accounting Rules
o. Revenue Recognition
p. Receipt Method
q. Remit To Addresses
r. Sales Representatives, Sales Credits and Territories
s. Taxes
t. Transaction Sources
u. Transaction Types
v. Unit of Measure
w. Commitments
7. Environment Issues: Performance, Hardware, Database, Memory or other peripheral issues
8. Fixing Data Issues
9. Capturing Debug Logs and Trace Files
10. Additional Diagnostics
11. Still Have Questions?
12. Logging a Service Request
References
APPLIES TO:
Oracle Receivables - Version 11.5.10.0 and later

Oracle Contracts - Version 11.5.10 and later
Oracle Order Management - Version 11.5.10.0 and later
Oracle Project Billing - Version 11.5.10.0 and later
Oracle E-Business Tax - Version 12.0 and later
Information in this document applies to any platform.
Executable:RAXMTR - Autoinvoice Master Program
Executable:RAXTRX - Autoinvoice Import Program
Executable:RAXDEL - Autoinvoice Purge Program
PURPOSE
Oracle Receivables (AR): AutoInvoice Information Center > Generic Setup and Troubleshooting Resources >
Note 1075757.1
This note is intended to walk you through a set of sequential steps that will facilitate troubleshooting AutoInvoice issues in
Releases 11.5 through 12.1.
TIP:
There are many notes in the Knowledge base written to help you troubleshoot AutoInvoice. However, since this feature
Document 1075757.1 3/17/16, 7:05 PM
is large and is impacted by many components, it may get confusing to navigate through the notes to find your solution.
We highly recommend using the following notes:
Note 1523525.1, AutoInvoice Post-Processor Validation Report: Overview and Installation Instructions
Note 1483249.1, AutoInvoice: Debugging Flow Advisor, it is designed to help you narrow in and identify the note
that may assist in resolving your issue.
TROUBLESHOOTING STEPS
1. How Does AutoInvoice Work?
How is it submitted? AutoInvoice is run using the Concurrent Request submission process.
Scheduling: Through the Concurrent Request form, AutoInvoice can be scheduled to run on a periodic basis.
Parameters: When scheduling or submitting AutoInvoice, parameters allow you to control what data sources
are used when importing records and what dates default on transactions. Additional controls are available on the
transaction source that you specify on the records being imported.
AutoInvoice Master Program (RAXMTR): Upon submission the master program is called. This program
coordinates the activities being done such as gathering statistics, marking records for processing (setting request
IDs on blocks of records, parallel processing). The master program also spawns and manages child requests for
importing and purging of data.
AutoInvoice Import Program (RAXTRX): The key step in AutoInvoice is the import program. Upon
submission this request is spawned by the Master Program. It converts the data in the interface table into invoices
and also produces the execution and validation reports.
AutoInvoice Report: This is produced by the import stage, and actually contains output from 2 reports:
AutoInvoice Execution Report: Provides a summary of the records from each of the Interface tables
indicating a count for selected, processed and rejected. This section also provides a breakdown of the types
of transactions created.
AutoInvoice Validation Report: If there were errors during Import, this section provides detailed
messages describing the errors encountered. This section should assist users in correcting the interface data
so they can be re-processed successfully.
Note: Many existing notes discussing topics regarding the output of the AutoInvoice Import, refer to the
Execution and Validation Report interchangeably, because they are contained in the same output file.
AutoInvoice Purge (RAXDEL): This is conditionally run after import (based upon your AR system options
settings).
Run as standalone? AutoInvoice Import can be run as a standalone request (not spawned by the Master Program)
by adding AutoInvoice Import to the request group associated with your responsibility. This is normally only done as a
troubleshooting step when the Master Program is failing. Note that no statistics are gathered in this scenario, thus you
may encounter performance issues in some scenarios.
Document 1075757.1 3/17/16, 7:05 PM
Invoke Programatically? <<Note 1127399.1>> Provides some sample code that can be modified to invoke
autoinvoice from a custom procedure. This is provided to assist customers in building integration however support for
this type of cusotomization is limited.
2. Alternatives to AutoInvoice
AutoInvoice is one of several utilities provided to import transactions. Other options include:
Oracle EDI Gateway

Oracle Receivables API's
XML Invoices (Part of Bill Presentment Architecture)
Despite the availability of alternatives, AutoInvoice is by far the most popular and heavily used integration point for
Receivables (AR) transactions. This is especially true where batch processing is desired. Most integration with Oracle AR
and other Oracle modules occurs through AutoInvoice.
3. Using Diagnostics to Check Setup
An easy step when troubleshooting AutoInvoice is to execute the AutoInvoice Setup Diagnostic test. This diagnostic can be
run by following the simple instructions in Note 1079666.1. The output of this diagnostic will help you work through many
configuration issues and avoid encountering the corresponding problems.
A sample output is shown below. Note the warning next to several of the lines.
Document 1075757.1 3/17/16, 7:05 PM
Selecting the link will take you to the corresponding setup check where you can review the warnings. In the example
below we can see that our current settings could negatively impact our system performance. Taking proactive steps here
to eliminate or address these issues can often resolve the issue we are encountering.
Document 1075757.1 3/17/16, 7:05 PM
4. Identifying What Went Wrong
If you are setting up a new interface to AR, we strongly encourage you to begin with a thorough review of the steps in:
Note 1067402.1 AutoInvoice Setup for Release 12: A Case Study Using a Simple Script
Also, if you are getting error messages and are not quite sure where to start, you can also review
Note 1138254.1 Listing of AutoInvoice Execution Report Error Messages and Troubleshooting Tips to Resolve each Error
Common Causes when AutoInvoice doesn't Import or Imports Incorrectly

There are five scenarios that typically occur when AutoInvoice fails to import a record from the interface table or Imports it
Document 1075757.1 3/17/16, 7:05 PM
incorrectly.
a. Import Failed: ERROR
When AutoInvoice fails with an ERROR status, it is important to review the concurrent log files: AutoInvoice
Master and AutoInvoice Import, for any error messages. Your primary goal when the request returns an
ERROR status is to identify the error stack so that you can search for and find the solution document (for
known issues)
There are three primary types of diagnostics that you can leverage to find an error:
AutoInvoice Debug Logs

FND Debug Logs
Trace Files
Note 1079666.1 "How to Capture a Debug Log or Trace File for AutoInvoice in 11i and R12" explains how
and when to capture each of these Debug records, what they look like in the log file and shows some
examples on how you can interpret them.
In most cases when reviewing these logs it is possible to find an error written by the code to the log file.
Once you have the error in hand, search for your error in Document 1082238.1 "Troubleshooting
AutoInvoice: Concurrent Request Failures (Request Status = Error)"
If you do not find your specific issue documented in this note then conduct a keyword search on your error
message to see if the issue is known and if a solution is available.
Tip: Always do a keyword search in My Oracle Support after finding an error message. It is the fastest
way to identify root cause and a solution for your issue.
raagtf()+ Current system time is 26-MAR-2010 17:07:57

None of the transaction flexfield contexts you have provided for this request have
enabled segments
Error calling raagtf()
Error calling raamil()
Error calling raapft()
In the example above, begin by searching on the error phrase from the log file "None of the transaction
flexfield contexts you have provided for this request have enabled segments"
If you are unable to find the solution using that phrase or if you receive too many choices in the search
results, add one or more of the additional messages such as "Error calling raagtf()" to your search phrase.
Document 1075757.1 3/17/16, 7:05 PM
In the unlikely event that none of these steps returns a known issue it may be helpful to review Note
100435.1 "What Do Each of the Subprograms in AutoInvoice Do ". Searching within this document for the
first program name "raagtf" can help you to understand what the program was doing when it failed. In this
example, the program is designed to "Get Transaction Flexfield Information". You can use this along with
section 6 in this note to find detailed troubleshooting documents for each main section of AutoInvoice. In
the scenario above this would take you to the section on Transaction Flexfields and guide you through
additional troubleshooting steps.
b. Import Completed: Exception Report ERROR
Exceptions are the most straightforward scenario to handle. In most cases the exception message is clear
enough so that you realize what you must fix.
For example, if the report output shows this:
The supplied ship-to address ID must exist in Oracle Receivables, and it must agree with the supp
Then there is a problem with the customer ship-to address Id provided, and you can investigate that further.
The best option to resolve these errors is a search on the exact error phrase. This should return a
consolidation note detailing known setup and bugs that can trigger the error. We suggest that you exclude
the token values (fields that reflect your environment such as ID's or names) to improve your search results.
Another option is to search Section 6 of this document. This section speaks to known setup and other issues
for each sub-feature invoked by AutoInvoice.
In some cases the exception report will show a vague error such as the one below:
ERROR
Unexpected Error Populate Error - 1071886
When this occurs you will need to treat the situation as if AutoInvoice failed (see section 2a above) and use
the AutoInvoice Debug Log and FND Debug log to find the cause. In Release 12 this vague exception can
occur when E-Business Tax fails but AutoInvoice is able to work past the issue without failing.
Note 1089172.1, Troubleshooting Autoinvoice Import - Execution Report Errors (Request Status =
Completed) explains the most common exceptions, and provides recommendations for each issue.
c. Import Completed: Nothing Imported
Document 1075757.1 3/17/16, 7:05 PM
While uncommon, it is possible that records will not be picked up when you submit the AutoInvoice program.
This is almost always the result of invalid parameters being passed to the concurrent request. Check to
make sure that the source you are submitting exactly matches the data in the interface table. If this occurs
and you are setting up AutoInvoice for a new data source either as part of a migration or as part of an
integration, refer to Note 1067402.1 AutoInvoice Setup for Release 12: A Case Study Using a Simple Script
This is often reported as "Records are Stuck in the RA_INTERFACE_LINES_ALL interface table" Which is
additionally discussed in the following notes:
Note 1146573.1 Troubleshooting Items that won't import or that are "Stuck" in the interface table
Note 1094863.1 Troubleshooting AutoInvoice: Master Program (RAXMTR) Errors And 'No Data Found' Issues
d. Transaction Imported: Record is Incorrect
There are two primary scenarios that are encountered here: Either the record imported incorrectly due to
AutoInvoice setup (grouping rules are wrong, the Transaction Flexfield is not set up properly, GL date
derivation is wrong, etc.) or it imported incorrectly due to a more generic system setup. In a few cases the
import can fail due to a defect (bug).
To establish which case you are facing we again must try to narrow the scope to identify the most likely root
cause. Use the appropriate section in section 5 of this document to review the setup from the perspective of
the system feeding autoinvoice and then, if unresolved, section 6 to focus on specific causes for the
symptoms reported..
e. Master Program Failed: ERROR
Document 1075757.1 3/17/16, 7:05 PM
The AutoInvoice Master program has a very simple role which is to manage the worker programs, memory
allocation and gather statistics.
The most common presentation with the Master Program occurs when no records are found to be
processed. In this case the master program completes but no data is imported.
Note 1094863.1 Troubleshooting AutoInvoice: Master Program Errors or Shows 'No Data Found' has been
created to document the steps you can use to diagnose and fix issues that present with the Master Program.
f. Import Never Completes
In some situations, the AutoInvoice process never completes, this could be a performance issue, please
check Note 1083467.1, How to Setup AutoInvoice for Optimal performance.
It is also possible that there is data corruption in your interface or core AR tables, please check Note
1294898.1, Troubleshooting AutoInvoice: Process Stops Working, No Errors in Log File
5. Validating the Data Being Imported (Custom Interface vs. Seeded Integration)
a. Custom Integration or Data Migration Issues
While the Receivables Reference Guide provides a good outline of field validation used by AutoInvoice, just
getting a file to import can be difficult. To simplify the implementation, case study Note 1067402.1 was
created. This document, along with several supporting "child" notes, provides a comprehensive overview of
how to implement AutoInvoice to support data sourced in a legacy application. If this is the first time you
are attempting to run AutoInvoice for a new source we strongly encourage you to use this case study to
validate your setup.
b. Integration with Oracle Applications that Feed AutoInvoice
In most cases, problems with Oracle Applications that interface with Receivables through AutoInvoice occur
in the utility that inserts data into the tables. If your data is sourced in an Oracle Application, we encourage
you to review the note on the specific module listed below. These notes outline some of the more common
issues that have been reported with the integration.
Troubleshooting AutoInvoice Integration with Oracle Project Billing

Troubleshooting AutoInvoice Integration with Oracle Order Management
Document 1075757.1 3/17/16, 7:05 PM
If your problem is not resolved then please proceed to section 6 below 'Troubleshooting Specific Steps in
AutoInvoice' where we break AutoInvoice into components and walk you through the steps required to debug
the unique area where your exception is occurring.
6. Troubleshooting Specific Steps in AutoInvoice
Note 100435.1 provides a list of AutoInvoice progams and a short description of what it handles.
Check it out!
Troubleshooting has never been easier, with this tool Note 1523525.1 AutoInvoice Post-Process Validation
Report: Overview and Installation Instructions
a. Accounting (AutoAccounting)
AutoAccounting is used by Receivables to assign preliminary accounting to an invoice or credit memo and the
corresponding tax and freight lines. As with other areas of AutoInvoice, when AutoAccounting fails it can
occur as a handled error in the debug log. An example of this might be:
APP-11526: 0 arcerr()- Current system time is 21-MAY-2001 13:54:11arcsai() Not all

AutoAccounting types are definedError calling arcdsu_do_setup()
Again, if you encounter any log error you should begin by performing a My Oracle Support search on the
primary portion of the error message. In the example above, start with "arcsai() Not all AutoAccounting types
are defined" and then expand to add additional error components if the results from your search are too
large.
Alternately, AutoAccounting can fail to generate an account segment (say the company segment) and then
generate an error in the exception report such as the one shown below:
Please Correct Revenue (or Receivable or Freight or Tax) Account Assignment
To troubleshoot these errors the following note has been created. In this note you will step through the basic
troubleshooting required to debug common exceptions with AutoInvoice accounting.
Note 1080995.1 Troubleshooting AutoAccounting in AutoInvoice

Note 1228525.1 How to Import and Troubleshoot Distributions in AutoInvoice Using
RA_INTERFACE_DISTRIBUTIONS_ALL
b. Credit Memos
As part of the AutoInvoice process, you can interface Applied or On-Account Credit Memos. You may
encounter various errors such as:
The Open Receivable flag of your credit memo must match the flag of the transaction you are credi
Document 1075757.1 3/17/16, 7:05 PM
An invoice can only reference a commitment
Invalid reference line attribute value
To troubleshoot these and other errors regarding Credit Memos in AutoInvoice or in the Transaction form, the
following note was created.
Note 1110573.1, Troubleshooting Credit Memos in Receivables
c. Customer, Addresses and Customer Contact
Customer validation errors typically are caused by incomplete setup and take the form of messages similar to
these:
Invalid bill to customer id (ORIG_SYSTEM_BILL_CUSTOMER_ID)The Bill To address id must exist in Or
The exact string will differ based upon the column from RA_INTERFACE_LINES_ALL that is invalid.
To troubleshoot these errors the following note has been created. In this note you will step through the basic
troubleshooting required to debug common exceptions with Customer fields in AutoInvoice.
Note 1097660.1 Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions
d. Currency and Exchange Rates
(Work in Process - check back soon)
e. Dates: Transaction Date, GL Date
Date errors will most often present with the following message in the AutoInvoice execution report:
Error: Unable to derive a GL date for your transaction. Please ensure that your transaction is i
If you find that AutoInvoice is using the wrong date or that it is rejecting the transaction with the above
message, we encourage you the following to troubleshoot the issue:
Note 201241.1 Troubleshooting AutoInvoice Date Derivation and How AutoInvoice Derives Dates
f. Flexfields: Transaction, Global, Descriptive
Transaction Flexfields are very important in your AutoInvoice setup as they control how AutoInvoice uniquely
identifies a discrete transaction and the lines that should exist within that transaction. Link-To transaction
flexfields also allow you to create a credit memo against an existing invoice.
Note 1077555.1 Troubleshooting Transaction Flexfields in AutoInvoice provides a step-by-step flow for you to
use when diagnosing issues related to Transaction Flexfield setup.
Common error presentations discussed in this note include:

APP-11914 Duplicate Transaction Flexfield
AutoInvoice terminated abnormally
Document 1075757.1 3/17/16, 7:05 PM
All enabled segments of Transaction Flexfield must have a value
APP-00778 invalid context field value (OE) passed to flexfield routine FDFDFA
None of the transaction flexfield contexts you have provided for this request
have enabled segments
Data in ATTRIBUTE1-15 fields are not transferred into core AR table fields.
Value set validation is not done against segments of the Transaction Flexfield
Attributes from Order Entry are truncated when transferred into AR tables
g. Freight
Receivables allows you to associate Freight to your transactions. You have the option of recognizing revenue
and calculating taxes on freight, or simple freight wherein you charge a fee.
For more information on what to check when you encounter issues with freight, please review:
Note 1096942.1, How to Setup and Troubleshoot Freight in AutoInvoice and the Transactions Form
h. Grouping Rules
AutoInvoice uses grouping rules to group invoices, credit memos and debit memos. Grouping rules contain
various transaction attributes (columns in RA_INTERFACE_LINES_ALL table) that must be identical across
several interface records if the intention was for it to create one transaction.
If AutoInvoice is generating one invoice for multiple orders, then you may not have correctly defined the
attributes that are being used to group invoice lines.
The Grouping Rule that is used by AutoInvoice is attached in your Batch source :
Navigation: Setup > Transactions > Sources
in the AutoInvoice tab
Grouping Rule Setup can be checked at:

Navigation: Setup > Transactions > AutoInvoice > Grouping Rules
Common Error:
Invoice lines with the same invoice number have been separated by the grouping process, causing duplicate
invoice numbers.
For Troubleshooting information see Note 1084554.1 Troubleshooting Grouping Rules in AutoInvoice
For additional information see Note 1067993.1 How To Use Grouping Rules With AutoInvoice
Document 1075757.1 3/17/16, 7:05 PM
i. Inventory Transactions (Warehouse, Items, etc)
The message Invalid Warehouse ID (WAREHOUSE_ID) (xxx) is normally displayed whenever an invoice line is
processed by AutoInvoice but the warehouse is invalid.
To troubleshoot this issue, refer to:
Note 1089026.1 AutoInvoice Error: Invalid Warehouse Id (WAREHOUSE_ID) (xxx), where a comprehensive
listing of causes/fixes has been compiled.
j. Line Ordering
AutoInvoice uses Line Ordering Rules to order transaction lines when grouping the transactions it creates into
invoices, debit memos, and credit memos. You can assign a line ordering rule to each grouping rule. You also
assign transaction attributes to your line ordering rules.
AutoInvoice uses these attributes to order invoice lines. You can assign a priority to these attributes for each
of your invoice line ordering rules. You can also specify an ascending or descending order for each
transaction attribute assigned to a rule.
For Troubleshooting information see Note 1086155.1 - Troubleshooting Line Ordering in AutoInvoice
For Additional Information see Note 1067965.1 - How to Manage Line Ordering When Using AutoInvoice to
Import.
k. Numbering: Document Sequencing and Transaction Numbering
For your transaction numbers, if you use Document Sequencing and/or you have the system set up to 'Copy
Document Number to Transaction Number', refer to the notes below:
Note 1086565.1 How To Setup Document Sequences In Receivables.

Note 1087122.1 Troubleshooting Document Sequences in Receivables
For invoice number ordering, review:

Note 1071559.6 AutoInvoice Issue: Invoice Numbering During Import of Invoices is Not in Logical/Expected
Order
For Batch Numbering: Refer to:
Note 1088132.1 Troubleshooting Transaction Batch Sources For AutoInvoice
l. Payment Terms
Most problems encountered with Payment Terms arise due to missing or invalid terms on a transaction that is
being imported. A Term ID or Term Name is required for all invoices imported via AutoInvoice.
To learn more about the payment term validation used when importing records please refer to:
Note 1083494.1 Troubleshooting Payment Terms in AutoInvoice where you can follow step-by-step
instructions to troubleshoot and resolve most issues with Payment Terms.
m. Purge
Document 1075757.1 3/17/16, 7:05 PM
AutoInvoice purge provides a method of clearing out records from the Interface tables that have been
processed successfully.
To learn more about AutoInvoice Purge, please refer to:
Note 1127413.1, Understanding and Troubleshooting AutoInvoice Purge.
n. Invoicing and Accounting Rules
Invoicing and Accounting rules allow you to control the schedule for recognizing Receivable and Revenue on
a transaction. You may encounter issues such as:
Please supply both an invoicing rule and an accounting rule for this invoice
Please define all periods in which revenue is to be recognized or credited. Note that revenue can
To learn more about Invoicing and Accounting Rules, please refer to:
Note 1116934.1, How To Setup And Troubleshoot Invoicing Rules and Accounting Rules
o. Revenue Recognition
Revenue Recognition allows you to spread out the accounting for the revenue associated to your transaction
across multiple periods. This feature is used in conjunction with Invoicing Rules and Accounting Rules above.
You may encounter errors such as the following:

arp_auto_rule.create_other_plug()- 09-JUL-03 09:03:01
EXCEPTION: arp_auto_rule.create_assignments()
ORA-06512: at "APPS.ARP_AUTO_RULE", line 479
To learn more about Revenue Recognition, please refer to
Note 1121944.1, Understanding and Troubleshooting Revenue Recognition.
p. Receipt Method
Receipt Method errors typically present as one of the following the AutoInvoice execution report:
R12:
1) 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 customer
Document 1075757.1 3/17/16, 7:05 PM
11.5
1) The supplied payment method must be defined and active for the bill-to customer or site
2) When the payment 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 customer
These errors are typically resolved by validating that the non-Manual receipt methods are able to derive a
valid bank account.
To investigate this further and to read about some known bugs with the derivation of Receipt Methods and
Bank Accounts, refer to Note 1098583.1 Troubleshooting AutoInvoice Receipt Method and Payment Method
Errors and Issues
q. Remit To Addresses
Common Error:
Cannot get remit to address
A "Default Value" should be assigned for the Country and State with a blank zip code range.
Adding this "default value" will eliminate the user from having to enter every possible Country and State
combination that may be used. Also, by using this "default value" items will pass validation without running
into an error because the remit-to address is not defined.
For more on remit-to address setup and troubleshooting please see Note 1101855.1 Troubleshooting
Receivables Remit To Address Errors
r. Sales Representatives, Sales Credits and Territories
Common Error:
Invalid Salesrep Number
Log File shows:

AR_RAXTRX_SALESREP_INACTIVE.
This is a known issue, please refer Note 1112705.1 : AutoInvoice Error: Invalid Salesrep Number
(SALESREP_NUMBER)
For a compilation of other troubleshooting tips, please refer to Note 1118944.1, Troubleshooting AutoInvoice
- Sales Credits, explains troubleshooting common issues experienced when interfacing sales credit records.
s. Taxes
For R12 refer to Note 745968.1 Troubleshooting AutoInvoice Tax Issues with R12 E-Business Tax (EBTax)
For 11i refer to Note 1086146.1 Troubleshooting AutoInvoice Tax Issues with R11.5 (11i) Receivables Tax
Engine
t. Transaction Sources
Document 1075757.1 3/17/16, 7:05 PM
Whenever a new Transaction Source is created, it's common to experience various issues related to the setup
of the source, and the data that is being imported. The Transaction Source Setup plays a key function as to
how AutoInvoice validates the data to be imported. The following is a list of some of the functionality that is
controlled by the Transaction Source setup:
Transaction Numbering - Automatic or Manual

GL Date Derivation
Grouping Rules
Customer Information - Values Passed (ID, Value, Segment)
Bill To and Ship To
Address
Contact
Payment Method
Accounting Information - Values Passed (ID, Value, Segment)
Invoicing Rule
Payment Terms
Sales Credit Validation
Invalid Lines
GL Date in a Closed Period
For more details on Troubleshooting AutoInvoice Transaction Sources, review Note 1088132.1, Setups to
Consider When Implementing New Interface Source Requirements
u. Transaction Types
Transaction Types are used to classify transactions, and have several attributes that help to manage how
transactions are processed within the applications. Utilizing these attributes allows you to manage
transactions based on a business operation's requirements. The following reflects some of the attributes that
can be used when defining a Transaction Type:
Class: Invoice, Credit Memo, Debit Memo, etc.

Creation Sign: Negative, Positive, Any
Post To GL
Open Receivable
Allow Over Application
Accounting Distribution:
Receivable
Revenue
Unbilled Receivable
Tax Account
Freight
Clearing Account
Unearned Revenue Account
Payment Terms
For more details on Troubleshooting AutoInvoice Transaction Types, review
Note 1090878.1, Troubleshooting - Transaction Types In Oracle Receivables.
Also you can refer to
Note 1067797.1, Setting Up Transaction Types In Oracle Receivables.
Document 1075757.1 3/17/16, 7:05 PM
v. Unit of Measure
Unit of Measure is required only when inventory items are passed as part of the interface. When passed, the
Unit of Measure is validated to ensure that it exists in the UOM base tables and, if associated to an inventory
item, that the UOM is consistent with the UOM Class from the inventory item and organization combination.
For more on troubleshooting Unit of Measure issues with AutoInvoice, please see
Note 1132807.1 Troubleshooting Unit of Measure Issues with AutoInvoice
w. Commitments
Note 120410.1 Transactions Workbench: Overview of Commitments (Deposits and Guarantees)
7. Environment Issues: Performance, Hardware, Database, Memory or other peripheral issues
AutoInvoice Performance Setup and Troubleshooting is outlined in detail in the following documents:
Note 1089196.1 Troubleshooting AutoInvoice Performance Issues

Note 1083467.1 Setup AutoInvoice for Optimal Performance
8. Fixing Data Issues
As mentioned in the section above on "How AutoInvoice Works", the AutoInvoice import program generates an output
validation report when it completes. This report will list out each record that was rejected during import and will then
provide an error code detailing why the record was rejected. In the example below, the error points to an invalid
transaction type.
This record can be corrected using the Receivables Interface Lines Form
Responsibility: Receivables Manager
Navigation: Control > AutoInvoice > Interface Lines
Query the record or records that were rejected using the "Errors Exist" checkbox as your query parameter
Document 1075757.1 3/17/16, 7:05 PM
To correct the error, navigate back to the lines form and position your cursor on the Line type field, Click on the folder
menu and click on Show field. Doing this will allow you to expose more fields from the table in the form.
Document 1075757.1 3/17/16, 7:05 PM
To fix this particular error, we want to modify the Transaction Type Id, so locate that field name in the list of values and
click on it.
Document 1075757.1 3/17/16, 7:05 PM
The Transaction Type Id field will now be displayed to the right of Line type and you can enter the correct ID, and save
your changes.
Document 1075757.1 3/17/16, 7:05 PM
If there were multiple errors on a line, you would follow the same process to make corrections to other fields. Once all
corrections are complete you can run AutoInvoice again.
Some other similar errors due to invalid ID values would be:
For more details on execution report Error Messages and how to correct them, refer to Note 1089172.1 Troubleshooting
AutoInvoice - Execution Report Errors (Request Status = Complete)
For more details on correcting errors when AutoInvoice fails with an error status on the concurrent request, refer to Note
1082238.1 Troubleshooting AutoInvoice: Concurrent Request Failures (Request Status = Error)
9. Capturing Debug Logs and Trace Files
There are three primary types of diagnostics:
AutoInvoice Debug Logs

FND Debug Logs
Trace Files
Note 1079666.1 How to Capture a Debug Log or Trace File for AutoInvoice in 11i and R12 explains how and when to
Document 1075757.1 3/17/16, 7:05 PM
capture each of these Debug records, what they look like in the log file and shows some examples on how you can
interpret them.
10. Additional Diagnostics
AutoInvoice has numerous diagnostic scripts that are helpful when troubleshooting. The table below lists some of the
more useful options
Diagnostic Name Description/Usage
AutoInvoice Interface Lists Invoice interface data, Pro*C file versions and triggers
Data Collection Script
Oracle Receivables Lists and validates basic set-up of AutoInvoice, triggers, pro*C file versions
AutoInvoice Setup Test
Sales Order Diagnostic This script captures all of the important data relating to the order in the Order Entry system
Script
Accounts Receivable Extracts data from all the tables related to a specific AR transaction. Particularly helpful
Transaction Diagnostics when troubleshooting issues where AI invoices Transactions incorrectly
Customer Diagnostic Extracts data about a specific customer

Script
RDA Extracts file versions for a specific product
Search the catalog applicable to your release for instructions on how to run these scripts
Release 11i : Note 179661.1
Release 12.0.3 Note 464866.1
Release 12.0.4: Note 469721.1
Release 12.0.6+: Note 741601.1
Release 12.1.1 Note 783319.1
Release 12.1.2 Note 942527.1
11. Still Have Questions?
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a
discussion in the My Oracle Support Receivables Community.
To provide feedback on this note, click on the Rate this document link.
12. Logging a Service Request
This note and the auxiliary notes referenced within attempt to guide you to resolution of most known issues with
AutoInvoice. If you find that you require assistance after completing the steps outlined in this note please provide the
following information to expedite resolution of your issue:
Document 1075757.1 3/17/16, 7:05 PM
1) Can you replicate the same issue with a manual invoice?

2) Can you replicate this at will in AutoInvoice?
3) Do you have any research findings that would help us in understanding or troubleshooting this issue? If yes what?
4) Did this work before? If so what has changed?
5) If this is a problem with a specific invoice?
provide the AutoInvoice debug log referenced in Note 1079666.1.

provide the AutoInvoice Data Collection Test diagnostic and AutoInvoice Setup diagnostic referenced in Note
1079666.1.
REFERENCES
NOTE:1137414.1 - Information Center: Overview of AutoInvoice in Oracle Receivables (AR) 11.5 and later
NOTE:1138254.1 - Listing of AutoInvoice Error Messages and Troubleshooting Tips to Resolve each Error
NOTE:783319.1 - Oracle E-Business Suite Diagnostics Test Catalog for 12.1.1
NOTE:942527.1 - E-Business Suite Diagnostic Tests Catalog for 12.1.2
NOTE:1110573.1 - Troubleshooting Credit Memos in the Transaction Workbench and AutoInvoice in Receivables
NOTE:1112705.1 - AutoInvoice Error: Invalid Salesrep Number (SALESREP_NUMBER)
NOTE:1116934.1 - How To Setup And Troubleshoot Invoicing Rules and Accounting Rules
NOTE:1117544.1 - E-Business Tax (EBTax) Information Center
NOTE:1098583.1 - Troubleshooting AutoInvoice Receipt Method, Payment Method, Credit Card and Bank Account Errors
NOTE:1101855.1 - Troubleshooting Remit To Address in Oracle Receivables
NOTE:1132807.1 - Troubleshooting Unit of Measure Issues with AutoInvoice
NOTE:1146573.1 - Troubleshooting AutoInvoice: "Stuck in the Interface" issues: Interface line not created in AR and no
error is showing in the interface
NOTE:745968.1 - Troubleshooting AutoInvoice Tax Issues with R12 E-Business Tax (EBTax)
NOTE:1228525.1 - How to Import and Troubleshoot Distributions in AutoInvoice Using
RA_INTERFACE_DISTRIBUTIONS_ALL
NOTE:1294898.1 - Troubleshooting AutoInvoice: Process Stops Working, No Errors in Log File
NOTE:179661.1 - E-Business Suite Diagnostics 11i Test Catalog
NOTE:201241.1 - Troubleshooting AutoInvoice Date Derivation: GL Date, Invoice Date, Due Date, Ship Date, Billing Date,
Rule Date
NOTE:464866.1 - E-Business Suite Diagnostics Test Catalog for 12.0.3 RUP 3
NOTE:1090878.1 - Troubleshooting Transaction Types In Oracle Receivables
NOTE:1094863.1 - Troubleshooting AutoInvoice: Master Program Issues including Errors, Warnings and When No Data
Imports
NOTE:1096942.1 - How To Setup Freight For AutoInvoice And The Transactions Workbench
NOTE:1097660.1 - Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions
NOTE:469721.1 - Oracle E-Business Suite Diagnostics Test Catalog for 12.0.4 (RUP 4)
NOTE:741601.1 - Oracle E-Business Suite Diagnostics Test Catalog for 12.0.6 RUP 6
NOTE:1083756.1 - Troubleshooting Order Management Invoice Creation Through AutoInvoice
NOTE:1086146.1 - Troubleshooting AutoInvoice Tax Issues with R11.5 (11i) Receivables Tax Engine
NOTE:1089196.1 - Troubleshooting AutoInvoice Performance Issues
NOTE:1080995.1 - Troubleshooting AutoAccounting in AutoInvoice
NOTE:1118944.1 - Troubleshooting AutoInvoice - Sales Credits
NOTE:1121944.1 - Understanding and Troubleshooting Revenue Recognition in Oracle Receivables
NOTE:1127399.1 - Sample PLSQL Script to Call Autoinvoice Import Program RAXTRX Using
FND_REQUEST.SUBMIT_REQUEST in Release 12
NOTE:1127413.1 - Understanding And Troubleshooting AutoInvoice Purge Interface Tables
NOTE:100435.1 - Listing and Description of AutoInvoice Programs
NOTE:1084554.1 - Troubleshooting Grouping Rules In AutoInvoice
Document 1075757.1 3/17/16, 7:05 PM
NOTE:1086155.1 - Troubleshooting Line Ordering in AutoInvoice

NOTE:1086565.1 - How To Setup Document Sequences In Receivables
NOTE:1087122.1 - Troubleshooting Document Sequences in Receivables
NOTE:1088132.1 - Troubleshooting Transaction Batch Sources For AutoInvoice and Transactions Workbench
NOTE:1089026.1 - AutoInvoice Error: Invalid Warehouse ID (WAREHOUSE_ID) (xxx)
NOTE:1089172.1 - Troubleshooting Autoinvoice Import - Execution Report Errors (Request Status = Completed)
NOTE:1067797.1 - Setting Up Transaction Types In Oracle Receivables
NOTE:1067965.1 - How to Manage Line Ordering When Using AutoInvoice To Import Transactions
NOTE:1067993.1 - How To Use Grouping Rules With AutoInvoice
NOTE:1075757.1 - Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12
NOTE:1077555.1 - Troubleshooting Transaction Flexfields in AutoInvoice
NOTE:1067402.1 - AutoInvoice Setup for Release 12: A Case Study Using a Simple Script
NOTE:1079666.1 - How to Capture a Debug Log or Trace File and Diagnostics for AutoInvoice in 11i and R12
NOTE:1082238.1 - Troubleshooting AutoInvoice: Concurrent Request Failures (Request Status = Error)
NOTE:1083467.1 - How To Setup AutoInvoice For Optimal Performance
NOTE:1083494.1 - AutoInvoice Errors: Troubleshooting Payment Terms In AutoInvoice
NOTE:1313855.1 - Transactions Workbench: List of Known Issues Regarding Deposits and Guarantees
NOTE:120410.1 - Transactions Workbench: Overview of Commitments (Deposits and Guarantees)
Didn't find what you are looking for?

Auto Invoice Errors

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Auto Invoice Errors

Hochgeladen von

Copyright:

Verfügbare Formate

Document 1075757.

Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 (Doc ID

1. How Does AutoInvoice Work?

3. Using Diagnostics to Check Setup

4. Identifying What Went Wrong

Oracle Receivables - Version 11.5.10.0 and later

We highly recommend using the following notes:

1. How Does AutoInvoice Work?

Oracle EDI Gateway

3. Using Diagnostics to Check Setup

4. Identifying What Went Wrong

Common Causes when AutoInvoice doesn't Import or Imports Incorrectly

a. Import Failed: ERROR

AutoInvoice Debug Logs

raagtf()+ Current system time is 26-MAR-2010 17:07:57

b. Import Completed: Exception Report ERROR

For example, if the report output shows this:

c. Import Completed: Nothing Imported

d. Transaction Imported: Record is Incorrect

e. Master Program Failed: ERROR

f. Import Never Completes

a. Custom Integration or Data Migration Issues

b. Integration with Oracle Applications that Feed AutoInvoice

Troubleshooting AutoInvoice Integration with Oracle Project Billing

6. Troubleshooting Specific Steps in AutoInvoice

APP-11526: 0 arcerr()- Current system time is 21-MAY-2001 13:54:11arcsai() Not all

Please Correct Revenue (or Receivable or Freight or Tax) Account Assignment

Note 1080995.1 Troubleshooting AutoAccounting in AutoInvoice

An invoice can only reference a commitment

Invalid reference line attribute value

Note 1110573.1, Troubleshooting Credit Memos in Receivables

c. Customer, Addresses and Customer Contact

Invalid bill to customer id (ORIG_SYSTEM_BILL_CUSTOMER_ID)The Bill To address id must exist in Or

d. Currency and Exchange Rates

(Work in Process - check back soon)

e. Dates: Transaction Date, GL Date

f. Flexfields: Transaction, Global, Descriptive

Common error presentations discussed in this note include:

AutoInvoice terminated abnormally

All enabled segments of Transaction Flexfield must have a value

Grouping Rule Setup can be checked at:

i. Inventory Transactions (Warehouse, Items, etc)

To troubleshoot this issue, refer to:

k. Numbering: Document Sequencing and Transaction Numbering

Note 1086565.1 How To Setup Document Sequences In Receivables.

For invoice number ordering, review:

For Batch Numbering: Refer to:

Note 1088132.1 Troubleshooting Transaction Batch Sources For AutoInvoice

To learn more about AutoInvoice Purge, please refer to:

Note 1127413.1, Understanding and Troubleshooting AutoInvoice Purge.

n. Invoicing and Accounting Rules

You may encounter errors such as the following:

ORA-06512: at "APPS.ARP_AUTO_RULE", line 479

To learn more about Revenue Recognition, please refer to

Note 1121944.1, Understanding and Troubleshooting Revenue Recognition.

r. Sales Representatives, Sales Credits and Territories

Invalid Salesrep Number

Log File shows:

Transaction Numbering - Automatic or Manual

Class: Invoice, Credit Memo, Debit Memo, etc.

For more details on Troubleshooting AutoInvoice Transaction Types, review

Note 1090878.1, Troubleshooting - Transaction Types In Oracle Receivables.

Also you can refer to

Note 1067797.1, Setting Up Transaction Types In Oracle Receivables.