1/11/2018 Document 728906.

PowerView is On [My Core Products] Product Line: Internal ... ERP (Available) (0) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates

Give Feedback...

How To Diagnose E-Business Tax Issues In Procurement (Doc ID 728906.1) To Bottom

In this Document Was this document helpful?

Purpose Yes
No
Troubleshooting Steps
TESTCASE INFORMATION
Document Details
DOCUMENTATION
SETUP
Type:
DIAGNOSTICS Status: TROUBLESHOOTING
PROCESSING OVERVIEW Last PUBLISHED
Major
14-Dec-2017
LOGGING Update:
14-Dec-2017
Last
TRACING Update:
TROUBLESHOOTING TIPS
KNOWN REGRESSIONS
Related Products
DATA AND QUERIES
Oracle iProcurement
CODE FILES Oracle Purchasing
Oracle E-Business Tax
PATCHES
References
Information Centers
Information Center: Oracle
APPLIES TO: iProcurement [1381102.2]

Information Center:
Purchasing FAQ [1586684.2]
Oracle iProcurement - Version 12.0.0 to 12.1.3 [Release 12 to 12.1]
Oracle Purchasing - Version 12.0 to 12.1.3 [Release 12 to 12.1] Information Center:
Oracle E-Business Tax - Version 12.0 to 12.1.3 [Release 12.0 to 12.1] Procurement Suite Index
Information in this document applies to any platform. [1391332.2]
iProcurement - Version: 12.0 to 12.0.4 Information Center:
Purchasing [1391694.2]

Information Center: Oracle E-

Business Tax - Payables
Release 12 and Later
[1383309.2]
PURPOSE

E-Business tax was introduced in release 12 as a central solution that caters to all tax requirements across applications. Document References
Individual products have uptaken E-Business tax for all its tax requirements. This guide will help in diagnosis of issues related to
Oracle E-Business Tax
E-business tax within Procurement. Procurement calls e-business tax API's for processing its tax related requirements in release Documentation Resources,
12. The following types of procurement transactions will invoke e-business tax for tax related services. Release 12 [397158.1]

FAQ: Purchasing Integration

1. Requisitions With E-Business Tax
2. Standard POs, Planned POs [398841.1]
3. Blanket Releases and Scheduled Releases
Oracle E-Business Tax Release
4. Charges on Payment Lines
12 Known Issues [406376.1]

E-Business tax engine will process the related information provided and return back requested tax related services to How to obtain and read a
procurement. This article will provide you with tips and techniques that can be used to troubleshoot e-business tax issues in debug logfile for R12 E-
Business Tax (EBTAX)
procurement. [417238.1]

E-Business Tax : What does

TROUBLESHOOTING STEPS this seeded regime
determination set do?
[422699.1]
TESTCASE INFORMATION
Show More
There are multiple conditions and setups that would cause tax issues in procurement. The following questions would help in
briefly identifying the investigation areas. Recently Viewed

'Exception 023' :
Is this an upgrade or a new implementation of the application? Is this issue related to tax classifications that have been An Unexpected Error has
Occurred During Tax
upgraded or with setups that have been done after implementation? Calculation when Submitting
Is this issue related with setup of taxes? Have you defined the regime to rate flow for the tax? Please refer Note Purchase Orders for
464243.1 for setups required. Approval [735395.1]
Is the tax subscription at legal entity or is operating unit owning tax content? (Navigation - Tax Managers: Parties: Party E-Business Tax For Oracle
Tax Profiles > Party Tax Profiles) Purchasing [464243.1]
What is the 'Regime Determination Set' for the configuration owner? (Navigation - Tax Managers: Defaults and Controls: R12 Unexpected Error
Configuration Owner Tax Options > Enter subscription owner (provided in the tax regime) and the application name (in Occurred During Tax
our case 'Purchasing') > Click on 'Go' > Click on 'Update' pencil icon against the event for which tax is being setup > Calculation. Exception: 013
[437693.1]

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_a… 1/10
1/11/2018 Document 728906.1
Scroll down to find the value of 'Regime Determination Set') "Unexpected Error During
If the issue is due to tax error or incorrect tax classification defaulting, have you ensured to define defaults or a rule in e- Tax Calculation" While
Saving And Approving
business tax for calculating your tax status, tax rate and tax jurisdiction? Purchase Order [733127.1]
If the issue is due to tax error or incorrect tax classification defaulting, then have you ensured that effective dates on
Saving a Transaction with
each of the entity (Tax regime, tax, tax status, tax jurisdiction, tax rate and tax rules) are within the range of your Compounding Tax and Zero
transaction dates? (0) Line Amount Error - An
Is the issue due to override behavior of tax? Please refer Note 458218.1 'Ability to Override Tax Calculated In E-Business Unexpected Error Has
Tax' for further details of this behavior in release 12. Occurred. Please Contact
Your System Administrator
[1922252.1]
Show More

DOCUMENTATION

Following are some of documentation available for e-business tax which also contains details of its interface with Oracle
Purchasing:

Page 4-115 to 116 Oracle® Purchasing User's Guide Release 12 Part No. B28669-01
Oracle® E-Business Tax Implementation Guide Release 12 Part No. B25960-01
Oracle® E-Business Tax User Guide Release 12 Part No. B25959-01
Oracle® E-Business Tax Reporting Guide Release 12 Part No. B31346-01
Following article in metalink provides a complete list of documentation available in e-business tax.

Note 397158.1 - Oracle E-Business Tax Documentation Resources, Release 12

In addition the following white paper and FAQ's specific to procurement are available on metalink.

White paper: Note 464243.1 - E-Business Tax For Oracle Purchasing

FAQs

Note 398841.1 - FAQ Purchasing Integration With E-Business Tax

Note 560339.1 - EBTAX: FAQ and Considerations

SETUP

The setups for procurement can be obtained by referring to Note 464243.1 (Page 36 to 41) which contains viewlets as well as
details of the setups required for defaulting taxes for purchase orders.

Tax setups are based on 'Regime Determination Set' defined in the configuration owner tax option to which the tax regime is
subscribing for the application and event for which this tax is calculated. For upgrade customers Standard Tax Classification
Code (STCC) is the defaulted as 'Regime Determination Set' in the configuration owner tax option for the 'Operating Unit Owning
Tax Content'. If so all the steps mentioned in Note 464243.1 (Page 36 to 41) are required to start defaulting taxes in
requisitions, purchase orders and releases.

If the 'Regime Determination Set' in the configuration owner tax option is set to 'Determine Applicable Regimes', the taxes will
be location based i.e. the taxes will be defaulted based on rules and defaults applicable at location where the tax needs to be
calculated. The following setups mentioned in Note 464243.1 are required to start defaulting taxes in requisitions, purchase
orders and releases.

1. Set up Tax Regime

2. Set up Tax
3. Setup Tax Status
4. Setup Tax Jurisdiction Code
5. Setup Tax Rate
6. Setup Tax Recovery Rate (Optional based on tax recovery)
7. Setup Tax Rules
8. Update tax to enable tax for transactions

For customers using iProcurement, some of the tax attributes will only be visible if they set these fields to be displayed using
page personalization. Please follow instructions in Note 552107.1 to enable these fields both in the iProcurement requisition edit
and view pages as well as notifications.

DIAGNOSTICS

The following diagnostic script is available that help validate the tax setups in e-business tax.

Note 462877.1 - E-Business Tax Setup Test

PROCESSING OVERVIEW

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_a… 2/10
1/11/2018 Document 728906.1
E-Business Tax was introduced as a single point solution for managing transaction-based tax across the entire E-Business Suite.
E-Business tax maintains the tax setups and rules (Tax content). Individual applications request e-business tax services through
an API call. E-Business tax calculates the tax based upon the rules, setups and the transaction data. The results are returned
back to the calling application. Following diagram describes the architecture of e-business tax.

E-Business tax services needs to be called whenever there is a create/update/cancel/delete action on the purchase documents.
Following are the steps for processing the tax on purchase documents.

1. Populate the PO tax attributes to global temporary tables and use eTax API to populate eTax additional tax
attributes to eTax global temporary table.
2. Call eTax API to Calculate tax.
3. Call eTax API for recovery calculation and distributing it on the purchase document.
4. Store the recoverable and non-recoverable components of the tax in PO Distribution tables

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_a… 3/10
1/11/2018 Document 728906.1

Following are the tax determinations steps used by e-business tax to calculate tax when the API is invoked from purchasing.

LOGGING

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_a… 4/10
1/11/2018 Document 728906.1
FND Debug logging can be enabled to troubleshoot e-business tax issues. This gives details code execution status and also
provides details of the exceptions captured during tax calculation errors. FND debug should is used primarily to troubleshoot
issues that are caused due to exceptions during tax calculation.

Steps to enable FND logging is available in the white paper (Note 464243.1, Page-46 E-business Tax - A Purchasing
Perspective).

1. Set the following profile options on at user level for the user saving the purchase order.

FND: Debug Log Enabled = 'Y'

FND: Debug Log Level = 'Statement'
FND: Debug Log Module = %

2. Now change the responsibility to purchasing and open the Purchase Order/Requisition Form where this issue is
happening and enter the details.

3. Obtain the AUDSID. For obtaining this, perform the following from just before opening Purchase Order
Requisition form. Go to Help->About Oracle Applications, you will find the AUDSID field. (Sometime AUDSID is not
available for a few customers Please ignore this step in such a case)

4. Navigate to the point right before the error message (For e.g.. just before saving the purchase
order/requisition) or the issue occurs.

5. Obtain the max log sequence using the following query.

SQL> select max(log_sequence)

from fnd_log_messages;

6. Reproduce the error/issue (For e.g. save the purchase order/requisition to get the error message)

7. Please obtain the debug log using the following query.

SQL> select *
from fnd_log_messages
where log_sequence > <output from step5>
and (module like 'ZX%' or module like 'zx%)
and audsid = <audsid from step 3 above>
order by log_sequence;

Note: If the AUDSID is not available please use the following query to retrieve the tax log.

SQL> select *
from fnd_log_messages
where log_sequence > <output from step5>
and (module like 'ZX%' or module like 'zx%)
and user_id = (SELECT user_id FROM fnd_user where user_name ='&Username')
order by log_sequence;

Note: Username is the user for which the FND Debug was set up.

8. Reset the profile set in step 1 in order to inactivate FND Debug from logging debug messages to the database.

For further details please refer also to following note available for tax debug.

Note 417238.1 - How to obtain tax debug logfile when using application version 12 or higher

TRACING

Database trace provides troubleshooting information when there is a error while tax is calculated. This can occur when
creating/modifying/cancelling/deleting a purchase document. Most of the times the trace helps you retrieve error messages and
details stored in global temporary tables.

Form Applications

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_a… 5/10
1/11/2018 Document 728906.1
The below instructions can be used when attempting the save the purchase transaction from the form application.

1. Just before saving the PO/Requisition, turn trace on by:

Help > Diagnostics > Trace > Trace with Binds

2. Once the transaction is save stop the trace immediately by.

Help > Diagnostics > Trace > No Trace

2. You will get a message showing the location of the trace file.

3. Please retrieve trace with tkprof. Run the trace file through tkprof as follows:
tkprof <filename>.trc <filename>.out explain=<apps username/apps password>

example: tkprof file1234.trc file1234.out explain=<APPS/APPS>

OA Framework/Self Service Application

The below instructions can be used when attempting the save the purchase transaction from the Buyer's Workbench/
iProcurement/Sourcing.

a. Set the FND: Diagnostics profile:

Responsibility = System Administrator
Navigation: Profile > System
User: Enter User name
Query the Profile: 'FND: Diagnostics'
Set the 'FND: Diagnostics' profile to Yes at User level

b. Login to Buyers Workcenter/iProcurement responsibility under the same user the profile was set for.

c. Turn Trace on:

Click the Diagnostic link at the top of the page
It shows two options: Show Log and Set Trace Level
Select 'Set Trace Level'
Click Go.
Select one of the following options:
Disable Trace - used to end the trace
Trace (Regular) - just like a forms trace
Trace with Binds - record the bind variables in the trace
Trace with waits - Good for performance issues
Trace with binds and waits - combines both of the above
Click Save.

d. Save the requisition/purchase order to reproduce the issue.

Multiple trace files may be generated in the usual trace directory.

e. Turn trace off:

Select the Diagnostic link
Click on option: Set Trace Level
Note all of the trace numbers listed
Click Go
Select: Disable Trace
Click Save

You will be able to find trace identifiers on the screen. Note the values available in the screen.

f. Find the trace directory.

Get the location of user_dump_dest. Log into SQL*Plus as the apps user.
select value from V$PARAMETER where name = 'user_dump_dest'

g. Find the trace file for your process using the identifiers found in step e. The trace filenames will contain these
identifiers.

Go to the directory you found in step 1 (in UNIX, use cd).

Look for a file (.trc) that was created at the time you started
your process (in UNIX, use ls -ltr *<identifier value>*).

h. Run tkprof with explain plan.

i. Go to a directory in which you have write privilege (in UNIX, use cd).
Run tkprof:
tkprof <full path to trace file> <output file name> explain=<apps username/apps password>

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_a… 6/10
1/11/2018 Document 728906.1

TROUBLESHOOTING TIPS

Troubleshooting tips are based on what could go wrong. We have identified the following types of issues in e-business tax
integration with procurement.

Tax Calculation Errors

This error occurs when tax calculation call errors. Most of the tax calculation errors are due to validation errors in related setups
interfacing e-business tax (incorrect location in TCA), incorrect defaulting logic in e-business tax setups or inappropriate rule
derivations for the transaction.

Tips

1. Depending upon the regime subscription option e.g. party specific, common configuration or common with party override,
check following tax set ups. Check that every set up entity is effective for the transaction date. Check that one status is
default and every status has a default rate. In case of jurisdiction specific rates, check that every jurisdiction has a default
rate.Ensure that defaulting logic is clearly defined in your regime to rate flow (Tax setups). If the defaulting is missing,
there should be a rule to complete the calculation the tax on the transaction.
2. Ensure that all the rules defined for the tax are within the range of the transaction date.
3. If defaults are available for the tax. Try to disabling the rules and try checking if any specific rule is causing the error.
4. Check the default place of supply or the rule for the tax. There should be at least one valid jurisdiction for the place of
supply determined.
5. If you do not want the tax to be applicable on purchase documents then disabling tax applicability for purchase
documents from the configuration owner tax option may eliminate the error. Please refer to Note 461254.1 for detailed
steps for disabling tax on requisitions.
6. In case the tax error continues to occur, please refer to the 'LOGGING' section to produce the tax debugs. The tax
debugs will contain details of tax calculation error that will help us narrow down to the actual code that is erroring.

Oracle Support can internally can view the following note for reading errors found in the debug:

Tax Defaulting Issues

Sometimes taxes are not defaulted for a transaction even though tax setups have been defined. Also there are issues where
incorrect tax is defaulted. These issues occur due to incorrect setups or rules.

Tips

1. Determine the configuration owner subscription - Party tax profile of Operating Unit. Check whether the OU has
subscribed to LE setups. Depending upon the set up above check whether the configuration owner has subscribed to the
regime. Check the configuration option e.g. party specific configurations. When these setups are incorrect, it will lead to
tax not getting calculated and consequently the defaulting does not happen.
2. For the configuration owner (OU or LE) as determined above check the Configuration Owner Tax Option for the event
class. Check the Regime Determination Set. For location-based taxes it should be Determine Applicable Regime. Check
the Tax Applicability flag. If the tax is not applicable for the configuration owner, then tax will not be calculated and
consequently the defaulting does not happen.
3. If this is not a location based tax and the tax is applicable to a supplier, then please check the Party Tax Profile of the
Third Party (supplier) and third party site (supplier site). Check for the Tax Applicability flag at main tab and at
registration tab. They should be applicable so that the tax will be defaulted.
4. In case there are many rules and the tax defaulted is incorrect then check the precedence of the rules. Try to disable the
rules and check if you get the correct results. Change the order of the rules or create/modify rules as per your
requirement.
5. Check if any exceptions exist that may be preventing the defaulting.
6. In case the incorrect tax still continues to default, then use the tax simulator (Note 464243.1, please review the viewlet
and Page-45 E-business Tax - A Purchasing Perspective)to find the rules that are getting applied for the defaulted tax.
Check how they are getting applied.

Tax Override Issues

Override in e-business tax is possible and the behavior is dependent on the regime determination set (Refer Note 422699.1 E-
Business Tax : What does this seeded regime determination set do?) in the configuration owner tax option. Please refer to Note
458218.1 for more details about the behavior of tax override in e-business tax.

Tips

1. Most of the issues are due to override being prevented. If the regime determination set in configuration owner is
'Determine Applicable Regimes', then a tax calculation error occurs when attempting to override which consequently
prevents tax override. In such cases we can use the tax debug to find the error, please refer to the 'LOGGING' section to
produce the tax debugs.
2. If the issue is to prevent override then you would need to control it at tax setup level.

Upgrade Issues

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_a… 7/10
1/11/2018 Document 728906.1
After upgrade to 11i, a new Regime Determination Template Standard Tax Classification Code (STCC) will be created during the
upgrade using determining factor of Tax Classification Code - which will indicate that the tax calculation would be based on the
old Release 11i approach. This will be available as 'Regime Determination Set' on the configuration tax owner option for the
'Operating Unit Owning Tax Content'. When the template is STCC, a shortcut approach is used to calculate taxes based on the
passed Tax Classification Code. This is a special Regime Determination Template which does not use Location based Determining
Factors. Override behavior will also be as it was in 11i. Most of the upgrade issues have been due expectation mismatch as
compared to the behavior in previous versions (R11i,R11,R10).

Tips

1. Confirm if the problem is a known issue/regression due to architectural change.

2. If the issue is only with transactions that have been created prior to upgrade then check if any new rules had been
created or the 'Regime Determination Set' has been changed for the configuration owner.

KNOWN REGRESSIONS

1. User updated Tax Code on the requisition lines will no longer be carried over to the PO document during autocreate. The
Tax Classification will always be re-defaulted on the PO document.
2. Recovery Rate field at the distributions level will no longer be defaulted based on the Tax Code and will no longer display
the default recovery rate of the transaction. Override of recovery rate will be subject to controls setup within e-business
tax.
3. Tax cannot be modified through AutoCreate requisition 'Modify' action, as the tax is re-defaulted on the PO regardless of
the tax in the requisition.
4. Detailed tax information based on tax classification will not be available in the requisition. For requisitions, users will only
be able to view the tax amounts (total, recoverable and non-recoverable).
5. PO documents cannot be reserved or submitted for approval if tax calculation error has occurred.
6. Users will no longer be able to view summarized tax information. Currently users are able to view the tax lines
summarized by tax codes. EBTax will only support displaying detail tax lines for PO documents.
7. Users will no longer be able to specify Tax Code through the PO Preferences form.
8. Users will no longer be able to modify Tax Code in Autocreate’s requisition modify action.
9. For requisitions, users will only be able to view the tax amounts (total, recoverable and non-recoverable) but not the
detail tax information based on tax code.
10. Users will no longer be able to specify Tax Code on the RFQs and Quotations form. Appropriate tax attributes will be
defaulted when the Quotations is turned into a PO.
11. PO documents cannot be reserved or submitted for approval if tax calculation error has occurred.
12. Tax calculation error in PDOI will create imported documents with 'Approved' status or 'Initiate Approval' parameter set to
‘Yes’ as ‘Incomplete’ or ‘Requires Reapproval’.
13. Tax calculation error in Requisition Import will create imported requisitions with 'Approved' status as 'Incomplete'.
14. Importing of tax lines will not be supported on imported documents for purchasing.
15. Withholding tax and offset taxes are not supported in Procurement.

DATA AND QUERIES

Detailed data flow and queries are included in the white paper (Note 464243.1, Page-42 E-business Tax - A Purchasing
Perspective ). Purchase order and release tax line information is stored in ZX_LINES table and tax distribution for the tax lines
which include the recoverable and non recoverable component are stored in ZX_REC_NREC_DIST table. For requisitions the
detailed tax lines are not stored. The PO_REQ_DISTRIBUTIONS_ALL table is updated directly with the recoverable and non
recoverable amounts.

CODE FILES

Following table shows the code objects involved, and of concern to procurement.

Package PO_TAX_INTERFACE_PVT.plb This is the main pl/sql routine which calls e-business tax API calculate_tax
Body whenever Purchasing requires to calculate tax.
Package PO_TAX_INTERFACE_PVT.pls This contains the specifications for the package PO_TAX_INTERFACE_PVT
Specification mentioned above.
XML ManageTaxPoPG.xml This is the web page that is invoked on clicking Action -> Manage Tax from the
'Enter Purchase Orders' form
XML ManageTaxRelPG.xml This is the web page that is invoked on clicking Action -> Manage Tax from the
'Enter Releases' form
XML ManageTaxReqPG.xml This is the web page that is invoked on clicking Tools -> Manage Tax from the
'Enter Requisitions' form
Java ManageTaxPoCO.java This is the main controller class called from the 'Manage Tax' page on the 'Enter
Purchase Orders' form. Manages the search and other controls on this page.
Page context is set based on the po_header_id. If Addition Tax Information
button is pressed, it will invoke the e-business tax 'Additional Tax Information
UI'.
Java ManageTaxRelCO.java This is the main controller class called from the 'Manage Tax' page on the 'Enter
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_a… 8/10
1/11/2018 Document 728906.1
Releases' form. Manages the search and other controls on this page. Page
context is set based on the po_header_id and the po_release_id. If Addition Tax
Information button is pressed, it will invoke the e-business tax 'Additional Tax
Information UI'.
Java ManageTaxReqCO.java This is the main controller class called from the 'Manage Tax' page on the 'Enter
Requisition' form. Manages the search and other controls on this page. Page
context is set based on the requisition_header_id. If Addition Tax Information
button is pressed, it will invoke the e-business tax 'Additional Tax Information
UI'.

The following steps explain how this can be useful in investigating possible similar issues;

Check any errors or logs related to the issue, and note the code objects and files mentioned.
Check the version of these files in the instance exhibiting the problem.
Search the patches available for later releases of these files, and match the patch descriptions to the issue encountered.
Apply as relevant.
To find patches: Visit Metalink > Patches and Updates > Advanced Search > Complete: Product / Release / Platform /
Patch / Includes File [Enter file] > Click Go.

PATCHES

Oracle Support maintains the following patch guide for all e-business tax issues;

Note 406376.1 - Oracle E-Business Tax Release 12 Known Issues

In addition, since the process shares many Purchasing features and code functionality, it is also worth verifying these patches.

Tax Calculation Errors

Note Abstract

Note Error Occurred During Tax Calculations. Tax Currency Code Is NULL
602762.1

Note Can Not Approve Purchase Requisition With Exception: 013 And Tax Log Shows 'ORA-00001:
556365.1 UNIQUE CONSTRAINT (ZX.ZX_DETAIL_TAX_LINES_GT_U1) '

Note Exception 023 When Approving PO

466548.1

Note E-Business Tax Calculation Issues After Entering The Next Line/ Deleting Shipments/ Adding New
458320.1 Shipments in Purchase Order

Tax Defaulting Issues

Note 578178.1 - Purchase Orders Tax Code Is Not Being Defaulted As Per The Tax Rule
Tax Override Issues

Note 560296.1 - Not Able To Change/Update Tax For Rejected Requisitions And Purchase Orders
Upgrade Issues

Note Abstract
Note 602172.1 Revise Upgraded Purchase Order And Tax Classification Code Is Removed
Note 560047.1 R12 Upgrade Script Zxpotrxmigupd.Sql Performance Is Slow
Note 556212.1 After Installation RUP4 The System Does not Calculate Tax In AP, AR and PO
Note 554641.1 Tax Not Calculated After Upgrade to 12.0.4

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_a… 9/10
1/11/2018 Document 728906.1

Other Issues

Note 466953.1 -PO Output For Communication Report Showing Tax As 'N' Even Though Tax Classification Is Populated
On The Purchase Order
REFERENCES

NOTE:397158.1 - Oracle E-Business Tax Documentation Resources, Release 12

NOTE:398841.1 - FAQ: Purchasing Integration With E-Business Tax
NOTE:406376.1 - Oracle E-Business Tax Release 12 Known Issues
NOTE:417238.1 - How to obtain and read a debug logfile for R12 E-Business Tax (EBTAX)
NOTE:422699.1 - E-Business Tax : What does this seeded regime determination set do?
NOTE:458218.1 - Ability to Override Tax Calculated In E-Business Tax
NOTE:458320.1 - E-Business Tax Calculation Issues After Entering The Next Line/ Deleting Shipments/ Adding New Shipments in
Purchase Order
NOTE:461254.1 - R12: Is It Possible To Disable Tax Call in Purchasing?
NOTE:462877.1 - R12.0.[3-4] : E-Business Tax Setup Test (Verify and display Tax setup details for a given tax code)
NOTE:464243.1 - E-Business Tax For Oracle Purchasing
NOTE:466548.1 - R12.0:Approving A Purchase Order Gives Exception: 023 - An Unexpected Error Has Occurred - Tax Calculation
NOTE:549867.1 - How to read an eBTax Debug Log file, what to look for, common errors
NOTE:552107.1 - How To Enable E-Business tax Functionality In iProcurement Release 12
NOTE:554641.1 - Tax Not Calculated After Upgrade to 12.0.4
NOTE:556212.1 - After Installation RUP4 The System Does not Calculate Tax In AP, AR and PO
NOTE:556365.1 - Can Not Approve Purchase Requsition With Exception: 013 And Tax Log Shows 'ORA-00001: UNIQUE
CONSTRAINT (ZX.ZX_DETAIL_TAX_LINES_GT_U1) '
NOTE:560047.1 - R12 Upgrade Script Zxpotrxmigupd.Sql Performance Is Slow
NOTE:560296.1 - Not Able To Change/Update Tax For Rejected Requisitions And Purchase Orders
NOTE:560339.1 - EBTAX: FAQ and Considerations For iProcurement
NOTE:578178.1 - Purchase Orders Tax Code Is Not Being Defaulted As Per The Tax Rule
NOTE:602172.1 - Revise Upgraded Purchase Order And Tax Classification Code Is Removed
NOTE:602762.1 - Error Occurred During Tax Calculations. Tax Currency Code Is NULL
Didn't find what you are looking for? Ask in Community...

Attachments
Architecture (104.4 KB)
Process Flow (54.51 KB)
Tax Determination (22.29 KB)

Related
Products
Oracle E-Business Suite > Procurement > Procurement > Oracle iProcurement > Other issues > Other (Not already categorized)
Oracle E-Business Suite > Procurement > Procurement > Oracle Purchasing > E-Business Tax Issues > E-Business Tax Issues
Oracle E-Business Suite > Financial Management > Financials Common Modules > Oracle E-Business Tax > Tax Calculation

Keywords
CALCULATE TAX; E-BUSINESS TAX; INFORMATION; PURCHASE ORDER; TAX CALCULATION; TAX INFORMATION; TAX OPTIONS; TAX RATE; TAX RULES; TAX STATUS; TROUBLESHOOT
Errors
ORA-1

Back to Top
Copyright (c) 2018, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=440235752309012&parent=DOCUMENT&sourceId=735395.1&id=728906.1&_… 10/10