Anda di halaman 1dari 11



To provide the basic steps to be able to test Autoinvoice.



For anyone wanting to be able to test Autoinvoice or anyone requiring a

starting point to understanding how to setup autoinvoice.

This is an introductory level example and does not attempt to explain

every step. This is for a simple line transaction without the use of
tax lines, credits, or accounting distributions.

If you need further explanation on any of the points listed below then
refer to the manuals regarding Autoinvoice. (see RELATED DOCUMENTS for

Quick Steps to run an example AutoInvoice Import

The following document will attempt to give the necessary steps to
enable you
to run autoinvoice for one invoice line.

Step required in AR
1. Grouping Rule Name: RH AI GROUP
- Class: Invoice
- Optional field: Interface_line_attribute1

2. Source name: RH AI Invoice

- Type: Invoice
- Grouping Rule: RH AI GROUP
- In the remaining options select the right hand side option in all
cases except the unit of measure, for this choose value.

3. DFF 'Line Transaction Flexfield'

- Two Segments: interface_line_attribute1 and 2
- Use value set of 15char and take defaults.

4. Tax Code:
-Name: GST_OZY
-Type: Sales Tax
-Rate 10% CR
-Allow Excempt checked
-Inclusive Tax checked
-Allow Inclusive override checked
(Note this example uses inclusive tax to create a tax line).

5. Customer and Address:

Customer Name: RH AI Customer
An Address with a bill usage with the tax on the bill usage set to
Use examine to get the customer_id and the address_id and update
the script below.
Currently the customer_id and address_id are set to 1256 and 1325.
6. The term_id is 4 (You can determine this by querying the payment
and using examine to get the value for term_id).
7. Autoaccounting for Revenue set to transaction type for all segments
and ensure the transaction type 'Invoice' has the accounts defined.
- revenue
- autoclearing
- freight
- receivable
- tax
- unbilled receivable
- unearned revenue

For one run all you need is:

insert into ra_interface_lines_all
'RH AI Invoice',
from dual

Insert into ra_interface_salescredits_all

'1005' from dual

How to run AutoInvoice

1. Interface - Autoinvoice
2. Select the program name
3. Only need to enter the first three parameters.


For 10.7 see the Open Interfaces Manual.

For 11 see the chapter on using autoinvoice.

Other notes useful to Autoinvoice include:


Please do all of the following:

A) Make sure AR System Option: Max memory size is set to 5000000 (5Megs).
Make sure to count the zeros. 50000000 is too high and 500000 is too low.

While you are on this screen, also set log file message level to 1.
Navigation: Receivables, Setup, system Options, Trans and Customers tab

B) Make sure Profile Option: AR:Maximum lines per invoice is set to NULL at
responsibility level.

C) Make sure set Profile Option: AR: Autoinvoice Gather Statistics is set to NO at
responsibility level.

D) Make sure to set Profile Option FND: Debug Log Enabled to NO at responsibility

E) Make sure Profile Option: MO: Operating Unit is setup correctly at the responsibility

F)Make sure that executable program "Gather Apps Schema Statististics"

has been run within the last 24 hours or other regular frequency
determined by DBA. If not, please run this executable now.
This executable also needs to be setup as a scheduled job to run at night
when the system load is lowest.
It should be scheduled to run every 24 hours or other frequency
determined by DBA.

G) DBAs make sure autoinvoice concurrent incompatibilities are set up for RAXTRX
and RAXMTR jobs.
Example autoinvoice incompatibility setups: Setting Up Incompatibilities for

Navigation: SysAdmin, Concurrent Program, Define, Query Up RAXTRX

Program: Autoinvoice Import Program

Short Name: RAXTRX
Application: Receivables

Application - Name - Scope - Type

------------ ------ ------ -----
Receivables - Archive Restart - Set - Global
Receivables - Purge - Set - Global
Receivables - Archive and Purge - Set - Global
Receivables - Archive Preview - Set - Global
Receivables - Refresh AR Transactions Summary Table - Set - Global
Projects - PRC:Tieback Invooices from Receivables - Program - Global
Projects - PRC: Interface Invoices to Receivables - Program - Global
Process Manufacturing - Financials AR Update - Program - Global
Order Management - Initialize Credit Summaries Table - Program - Global
Collections - IEX: Populate UWQ Summary Table - Set - Domain
Asia/Pacific Localizations India - Interface Invoices to Receivables - Set - Domain
Grants Accounting - GMS: Interface Invoices to Receivables - Program - Global

Setting Up Incompatibilities for Autoinvoice

Navigation: SysAdmin, Concurrent Program, Define,

Program: Autoinvoice Master Program

Short Name: RAXMTR
Application: Receivables

Application Name - Scope - Type

---------------- ----- ----
Receivables - Autoinvoice Master Program - Program - Domain <=== Very important !
Receivables - Archive Restart - Set - Global
Receivables - Purge - Set - Global
Receivables - Archive and Purge - Set - Global
Receivables - Archive Preview - Set - Global
Receivables - Refresh AR Transactions Summary Table - Set - Global
Inventory - Create Intercompany AR Invoices - Set - Global
Process Manufacturing Financials - AR Update - Program - Global

H) DBAs make sure that all autoinvoice related indexes are set up
per the Receivables Users Guide as appropriate.

I) When there are signal 11s or other problems with autoinvoice, it is best to leave
the first parameter in the Autoinvioce Master kick off screen which is
Number of Instances set to the default of 1.
The setting for Profile Option: AR:Maximum lines per invoice is by default set to NULL
responsibility level. This is the correct setting and will automatically engage
addititional instances (also known as workers or RAXTRX jobs) at approximately
100,000 lines.

iProcurement does not use the same E-Business Tax interface as core purchasing to open
ManageTaxReqPG.xml to input tax data. To enable E-Business tax functionality in
personalization changes are required to render the list of values (LOV) for tax input. By
the LOV objects listed below are not rendered. To see the columns for each of these
LOVs, the columns
must be rendered. The affected region and columns include:
Column: (TaxClassCol)
Column: (TxnBusinessCatCol)
Column: (ProdFiscalClassCol)
Column: (ProdTypeCol)
Column: (IntendedUseCol)
Column: (UserFiscalClassCol)
Column: (AssessableValCol)
Column: (ProdCatCol)

To implement, follow the navigation steps below:

1. Select the Functional Administrator responsibility

2. Click on the Personalization tab
3. Enter the following data:
Application: Oracle iProcurement
Document Path: /oracle/apps/icx/por/req/webui/CheckoutLinesPG
4. Click on the 'Go' button
5. Click on the respective Personalize Page column icon
6. Enter the appropriate responsibility and organization information
6. Click on the 'Apply' button
7. Click on the 'Complete View' radio button
8. Click on the 'Expand All' hyperlink
9. Locate each of the column objects listed above and click on it's respective Personalize
10. Change the 'Rendered' value at the desired level (i.e. Site, Organization, and
to "true"
11. Click on the 'Apply' button
12. Click on the 'Return to Application Catalog Page' hyperlink at the bottom of the page.
13. Click on the 'Close Window' hyperlink at the top of the page
14. Log into iProcurement
15. Create a requisition and navigate to the 'Requisition Information: Edit Lines' page and
on the 'Billing' tab. The rendered columns will display on the requisition line.

Troubleshooting Details
AutoInvoice Overview

AutoInvoice is used to generate invoices from a wide variety of sources. Oracle

Applications such as OKS (Contracts), Projects, Order Management and AGIS
(advanced global intercompany) are just a few sources that use AutoInvoice to generate
invoices. In addition to Oracle Application modules, AutoInvoice is available for use as
a tool to migrate data during an implementation and to integrate Oracle Receivables with
a legacy Order Management system.

How are Taxes Calculated

Taxes can be generated in one of two ways.

1) Transactions can be created with appropriate attributes defined such as bill_to, ship to,
warehouse_id and AutoInvoice can call eBusiness Tax to calculate taxes using your tax

2) Transactions can be passed into the interface tables with a pre-calculated tax line.

Note: Oracle Applications that calculate tax typically generate an estimated tax in their
respective user interfaces (such as Order Management screens) but do not pass this tax
line to AR. Taxes are recalculated at the time of invoicing as this is the point where the
tax liability is incurred.

General Debugging Tips

Always begin the process of AutoInvoice testing by upgrading to the latest tax validation
code. This is done by applying the latest patch for the file zxapdefvalpkgb.pls. As of the
publication date for this document, the most current available version of this file is
120.73.12000000.21 available through Patch 8249726 . This can also be found by
choosing the patch download option, advanced search option and entering the file name.

Debugging Manual Tax Lines

Loading Manual Tax Lines

Note 731149.1 documents in detail the steps recommended for creating manual tax lines
and importing into AR.

Importing Taxes with Latin Tax Engine

Note 737699.1 and Note 778911.1 documents required steps to take before trying to
import taxes through AutoInvoice with the Latin Tax Engine.

Debugging Taxes Calculated by the eBusiness Tax Engine

Step 1 Try to replicate in AR Transaction Workbench

The first step in debugging tax calculations in Autoinvoice is always to validate that the
taxes work as expected in the Transaction Workbench form in AR. If they fail to work in
the workbench form it is easier and faster to diagnose the issue using the manual entry
Tip: When troubleshooting integration issues from OM you should be sure to attempt the
replication in AR by entering a transaction that includes an inventory item and

Step 2 Obtain a Tax Debug Log

If the problem cannot be replicated in the transactions form, advanced troubleshooting is
required. Just as with manual tax lines, this will involve the creation of a debug log.
Follow the instructions from Note 417238.1 to create the log.

Tax Debug logs are not the same as Autoinvoice debug logs. Be sure to follow the
instructions in the note above to pull the proper log file.

ERROR from eBusiness Tax - return code = 2 is a generic error handling message that is
returned by the ebtax code to AR autoinvoice whenever an error happens during tax
calculation. In order to troubleshoot this error a tax debug log is required.

Once created and exported to a text file or spreadsheet the log can be searched for error
strings. These can often be used in conjunction with the concurrent request log file and
exception report to keyword search and find known issues and fixes.

Step 3 Check the following list of commonly encountered problems

Note 603799.1AR Reports and Vertex show Transaction Number As '~$~$$$'

Note 745340.1Autoinvoice Fails With Message "This Tax Rate Is Not Active"
Note 786000.1Credit Memo's fail with "System Cannot find tax Rate"
Note 779616.1 Exemptions not applied when invoices imported through autoinvoice

Intercompany Taxes

Release 12 includes the Advanced Global Intercompany Invoice (AGIS) feature. This
provides a responsibility that is used to generate intercompany invoices. Once generated
in AGIS, a workflow background process is run to create the invoice in the AutoInvoice
interface tables. AutoInvoice is then run to generate the invoice in Oracle Receivables.

In order to keep the taxes in synch between AR and AP, the workflow process that
populates the AP interface table does not start until the AR invoices are complete. Once
completed a business event triggers the relevent transactional data to be passed to the AP
interface tables including some of the tax attributes from the AR record. Although some
of these tax attributes stored on the AR transaction are referenced by the workflow when
the AP invoice is generated, the AP tax setup must be complete in order for taxes to be in
synch. Note that the fix for Bug 7718598 must be applied for the AR attributes to be
properly copied.
Note: Although the attributes are shared, AP code is separate from AR. If you find that
the AR and AP invoices are not in synch at the completion of the processing you should
contact the AP support team to evaluate your tax setup and rules.

Logging a Service Request

If you have applied the latest validation code and errors are still occurring a Service
Request may be required. When logging a SR the following should be attempted and the
results documented or provided in your SR.

1) Attempt to enter a manual tax line in the transaction workbench. Document the
outcome. When performing this step, be sure to mirror exactly your autoinvoice record. If
a warehouse and inventory item are on the imported record, enter them on the manual
transaction as well.
2) Create a single transaction in the interface table with only one tax line and one non-tax
line (do not include freight unless your test relates to taxation of freight)
3) Run the Autoinvoice Interface Data Collection Script from Note 306017.1 for the
4) Enable Debug as documented in Note 417238.1
5) Run AutoInvoice
6) Retrieve the Debug logs using the instructions from step 4 and running the script for
the concurrent request ID associated with the AutoInvoice Import Program.

Upload the concurrent request logs, output files, debug logs and data collection scripts
when creating your SR.

Please note that even when a manual tax line is passed in, EBTax must be fully
configured. The eBusiness Tax engine will assign all tax attributes (Regime, Tax, Tax
Status, Jurisdiction and Tax Rate) to the tax record so that it is available for tax reporting.

Note 737320.1 - Troubleshooting eBusiness Tax Reporting Issues in Release 12
Note 750064.1 - Using and Troubleshooting Tax Exemptions in Release 12 eBusiness
Note 761438.1 - Using Vertex and Troubleshooting the Integration with R12 eBTax
Note 784692.1 - Troubleshooting Latin Tax Release 12 Tax Calculation Issues
Note 789455.1 - Troubleshooting Order Management Release 12 E*Business Tax
Calculation Issues