My Oracle Support Banner

R12: Invoice Actions: Troubleshooting Tax errors: 'User-Defined exception', 'An unexpected Error has occurred', 'A mandatory constraint to generate unique...violated' and others (Doc ID 1313644.1)

Last updated on AUGUST 20, 2021

Applies to:

Oracle Payables - Version 12.0.1 to 12.2.6 [Release 12.0 to 12.2]
Information in this document applies to any platform.
Payables Invoices Entry form - APXINWKB
Payables Batch Validation Program - APXAPRVL


This article will help you solve most unhandled exceptions in the integration between Payables and eBTax (old version of this article is still available here <Note 1365130.1>, as of Oct-2011 it is no longer maintained).

Several of the scenarios in this document have had different root causes since R12 introduction (e.g: ZX_LINES_SUMMARY_U1 constraint violated has had numerous causes), this article provides the last solution available which includes all previous ones.

How to find your scenario

The user interface (e.g: APXINWKB) or the Batch Validation Process (APXAPRVL) post generic errors whenever an unhandled exception occurs in the Tax Engine. Example:

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
 How to find your scenario
 Generic errors you will first observe in the UI or APXAPRVL
Troubleshooting Steps

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