Академический Документы
Профессиональный Документы
Культура Документы
-------
If you need further explanation on any of the points listed below then
refer to the manuals regarding Autoinvoice. (see RELATED DOCUMENTS for
these)
Step required in AR
1. Grouping Rule Name: RH AI GROUP
- Class: Invoice
- Optional field: Interface_line_attribute1
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).
RELATED DOCUMENTS
-----------------
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
level.
E) Make sure Profile Option: MO: Operating Unit is setup correctly at the responsibility
level.
G) DBAs make sure autoinvoice concurrent incompatibilities are set up for RAXTRX
and RAXMTR jobs.
Example autoinvoice incompatibility setups: Setting Up Incompatibilities for
Autoinvoice
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
at
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
the
ManageTaxReqPG.xml to input tax data. To enable E-Business tax functionality in
iProcurement,
personalization changes are required to render the list of values (LOV) for tax input. By
default,
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:
BillingLinesRN:
Column: (TaxClassCol)
Column: (TxnBusinessCatCol)
Column: (ProdFiscalClassCol)
Column: (ProdTypeCol)
Column: (IntendedUseCol)
Column: (UserFiscalClassCol)
Column: (AssessableValCol)
Column: (ProdCatCol)
Troubleshooting Details
AutoInvoice Overview
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
rules.
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.
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.
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.
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.
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
transaction
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.
References
Note 737320.1 - Troubleshooting eBusiness Tax Reporting Issues in Release 12
Note 750064.1 - Using and Troubleshooting Tax Exemptions in Release 12 eBusiness
Tax
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
Keywords
AGIS ; TAX~REPORTING ; AUTOINVOICE~IMPORT~PROGRAM ; EXCEPTION~
REPORT ;