Results for “zx_exceptions”

40 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ZX_EXCEPTIONS is a transactional configuration table in the Oracle E-Business Tax (ZX) module. It stores tax rate exceptions that apply to specific inventory items or product fiscal classifications. Each row defines the percentage of the original tax rate that is treated as an exception during tax calculation, allowing organizations to override or reduce the standard rate for a defined product, organization, or jurisdiction combination. The table occupies a central position in the tax determination engine, since its rows are linked directly to calculated tax lines.

Based on the foreign key topology, the object exhibits a satellite-leaning Data Vault classification. It carries descriptive exception attributes and effective-dated qualifiers tied to a natural business key, which is consistent with satellite modeling rather than a pure hub or link. The primary key, ZX_EXCEPTIONS_PK, is defined on TAX_EXCEPTION_ID.

Key Information Stored

ZX_EXCEPTIONS contains 50 documented columns. The most business-significant columns are:

The unique index ZX_EXCEPTIONS_U1 enforces TAX_EXCEPTION_ID. The business-key candidate ZX_EXCEPTIONS_U2 spans TAX_REGIME_CODE, TAX, TAX_STATUS_CODE, TAX_RATE_CODE, CONTENT_OWNER_ID, EFFECTIVE_FROM, PRODUCT_ID, INVENTORY_ORG_ID, CLASSIFICATION_TYPE_CODE, CLASSIFICATION_CODE, TAX_JURISDICTION_ID, EXCEPTION_CLASS_CODE, EXCEPTION_REFERENCE_NUMBER, EXCEPTION_STATUS_CODE, EXCEPTION_REASON_CODE, and DUPLICATE_EXCEPTION. Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER, REQUEST_ID, PROGRAM_*) and fifteen ATTRIBUTE columns are also present.

Common Use Cases and Queries

Typical uses include reviewing exceptions effective for a given item and organization, verifying the rate modifier applied to a tax line, and auditing exception configuration by regime or jurisdiction.

  • Listing active exceptions for an item and organization within a date range, filtering on EFFECTIVE_FROM and EFFECTIVE_TO.
  • Joining ZX_LINES to ZX_EXCEPTIONS on TAX_EXCEPTION_ID to explain how a calculated tax amount was derived.
  • Reporting exceptions by exception class or reason to support tax compliance reviews.
  • Detecting duplicate or overlapping exceptions using the business-key columns and DUPLICATE_EXCEPTION.

A representative pattern joins exception configuration to computed lines:

  • SELECT e.tax_exception_id, e.tax_regime_code, e.rate_modifier FROM zx_exceptions e WHERE e.product_id = :product_id AND e.inventory_org_id = :org_id AND TRUNC(SYSDATE) BETWEEN e.effective_from AND NVL(e.effective_to, SYSDATE) ;
  • SELECT l.tax_line_id, l.tax_exception_id, e.rate_modifier FROM zx_lines l, zx_exceptions e WHERE l.tax_exception_id = e.tax_exception_id ;

Related Objects

  • ZX_LINES — references ZX_EXCEPTIONS via TAX_EXCEPTION_ID, recording the exception applied to each calculated tax line.
  • ZX_LINES_SUMMARY — references ZX_EXCEPTIONS via TAX_EXCEPTION_ID for summarized tax results.
  • ZX_REP_TRX_DETAIL_T — reporting detail table referencing TAX_EXCEPTION_ID.
  • ZX_DETAIL_TAX_LINES_GT and ZX_IMPORT_TAX_LINES_GT — staging global temporary tables that carry TAX_EXCEPTION_ID during processing.
  • MTL_SYSTEM_ITEMS_B — referenced by PRODUCT_ID, defining the item scope.
  • HR_ALL_ORGANIZATION_UNITS — referenced by INVENTORY_ORG_ID, defining the organization scope.
  • ZX_DET_FACTOR_TEMPL_B — referenced by DET_FACTOR_TEMPL_CODE for the determining factor template.