Search Results zx_jurisdictions_b_pk1

Overview

The ZX_JURISDICTIONS_B table is a core repository within the Oracle E-Business Tax (ZX) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It serves as the master table for defining and storing tax jurisdictions. A tax jurisdiction represents a specific geographical or political area, such as a city, county, state, or country, that has the authority to levy a particular tax. This table is fundamental to the tax determination engine, enabling the system to accurately identify the applicable tax rules and rates based on the transaction's location. Its integrity is critical for ensuring compliant and precise tax calculations across all business transactions, including invoices, purchases, and receipts.

Key Information Stored

The table's structure is designed to uniquely identify a jurisdiction within the context of a specific tax regime and tax. As defined by its primary key, the essential columns are TAX_REGIME_CODE, TAX, and TAX_JURISDICTION_CODE. These columns collectively form a unique identifier for every jurisdiction record. While the provided metadata does not list all columns, typical supplementary columns in this and related ZX tables would include descriptive fields like NAME, DESCRIPTION, and ENABLED_FLAG. The table also commonly contains effective date columns (EFFECTIVE_FROM and EFFECTIVE_TO) for managing the lifecycle of jurisdiction definitions, along with standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing.

Common Use Cases and Queries

Primary use cases involve tax setup, validation, and reporting. Tax administrators reference this table when configuring new tax jurisdictions or auditing existing ones. A common reporting query retrieves all active jurisdictions for a given tax regime and tax to verify setup completeness. For example:

• SELECT tax_jurisdiction_code, name FROM zx_jurisdictions_b WHERE tax_regime_code = 'US_SALES_TAX' AND tax = 'STATE' AND enabled_flag = 'Y' AND SYSDATE BETWEEN effective_from AND NVL(effective_to, SYSDATE);

During transaction processing, the E-Business Tax engine joins this table with rate and rule definitions to determine the correct tax. Troubleshooting tax determination errors often involves verifying that a valid jurisdiction exists for the transaction's ship-to or bill-to location.

Related Objects

The ZX_JURISDICTIONS_B table sits at the center of the E-Business Tax schema. It has a direct foreign key relationship with the ZX_RATES_B table, where specific tax rates are defined for each jurisdiction. The primary key columns (TAX_REGIME_CODE, TAX, TAX_JURISDICTION_CODE) are referenced as foreign keys in numerous other tax configuration and transaction tables. Key related objects include ZX_JURISDICTIONS_TL for translated jurisdiction names, ZX_JURISDICTIONS_DENORM for performance-optimized queries, and ZX_LINES_DET_FACTORS where the determined jurisdiction for a transaction line is stored. The ZX_JURISDICTIONS_B_PK1 primary key constraint ensures data integrity for all these dependent relationships.