My Oracle Support Banner

Using Vertex Q Series and Troubleshooting the Integration with R12 E-Business Tax (EBTax) (Doc ID 761438.1)

Last updated on JULY 14, 2022

Applies to:

Oracle Payables - Version 12.2.9 to 12.2.9 [Release 12.2]
Oracle Receivables - Version 12.0.0 and later
Oracle E-Business Tax - Version 12.0 and later
Information in this document applies to any platform.
EXECUTABLE:RAXTRX - Autoinvoice Import Program
FORM:ARXTWMAI.FMB - Transactions


E-Business Tax (EBTax) Information Center > EBTax Features > Partner Integration and APIs > Note 761438.1


We are actively trying to build up participation in our EBTax community. We'd love your input, ideas, collaboration and solutions to be part of the experience. Check us out at on the E-Business Tax communities page

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Troubleshooting Steps
 1.  This note does not provide "steps to implement". For this type of instruction please refer to the Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide (12.0.X , 12.1.1, 12.1.2) and/or <Note 763205.1> titled How to Install Vertex Q-Series 3.3 Integration with R12 and load rate and geocode data
 2. How Oracle EBTax integrates with Vertex
 2. Troubleshooting possible defects and bugs related to vertex tax calculation
 3. Differences between EBTax calculations and Vertex Calculations
 4. Special Setup Requirements for Vertex
     a. Make sure that you have the "Default Tax Classification" checkbox checked on the transaction type
     b. Make sure that you have tax rate codes as follows if these were not seeded by Vertex:
     c. Make sure all tax exceptions are defined only in Vertex
     d. Make sure you define the "STATE", "COUNTY" and "CITY" tax rate codes manually Before your First Tax Rate Load
 5. Loading only the Vertex Rate File
    a)  Finding out what version of the Rate file has been loaded
 6. Troubleshooting possible implementation causes for taxes that fail to calculate
     a. Make sure your version is supported
     b. Confirm that profile option is set
     c. Confirm that the Zxtxptnr.Sh installation script installed the vertex objects. 
     d. Make certain you have a regime and taxes defined
     e. Verify that you have properly defined the service subscriptions
     f. Make sure you have selected the tax calculation method of "Tax Regime Determination"
     g. Create the party tax profile for your Legal Entity* that owns the operating units where you will use vertex for tax calculation as well as for each operating unit.
     h. Make Certain that you have run the concurrent requests to complete the tax partner plugin request.
     i. Make certain that you have successfully loaded the most recent location and rate file.
     j. Verify that your combination of state, county, city and zip code exist in EBTax.  (Also - How to find Geocodes)
     k. Run the Geography Name Referencing Program. 
     l. Make sure you have corrected all addresses created and used prior to loading vertex
     m. Summary of Debug Log entries and meaning
 7. ORA-08176: consistent read failure after DB Upgrade
 8. Troubleshooting When Vertex Rate File Does Not Properly Load
 9. Annual Maintenance
 10. Vertex Installation
 11. Vertex Exemptions
 12. Unable to Link Customer/Suppliers with correct City
 13. Changing Tax Partners - Limitations
 14. Upgrades from 11i
 15. Zip + 4
 16. Logging a Service Request
 17. Contact Vertex for Support

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.