Results for “jurisdiction_code”

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

Overview

The view APPS.PAY_US_TAX_UNIT_SCHOOLS_V is a lightweight reporting object in the Oracle E-Business Suite Payroll (PAY) module. It is registered in the ETRM metadata as a VALID view owned by the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2. The ETRM description field simply records the object as "Retrofitted - Retrofitted," indicating that the definition was migrated or regenerated as part of a patch or upgrade cycle rather than being documented through a formal functional narrative.

Functionally, the view presents the distinct combination of eight-character jurisdiction codes and their associated tax unit identifiers for United States payroll tax processing. It serves as a filtered reference set that isolates school district jurisdictions — the eight-character codes typical of US school district tax reporting — from the broader set of reporting jurisdictions held in the underlying assignment reporting data. Because it is a view rather than a table, it carries no independent storage and always reflects the current state of its base object at query time. Its role is primarily as a convenience or lookup object for reports, concurrent programs, and integration extracts that need a deduplicated list of jurisdiction-to-tax-unit pairings for school-related US tax units.

Underlying Base Objects

The view is defined over a single documented base object: PAY_US_ASG_REPORTING, which is exposed in the APPS schema as a synonym. That base object is a US-specific assignment reporting entity within the Payroll module that stores jurisdiction-level reporting attributes linked to payroll assignments.

The view text is minimal and relies entirely on that base object:

• SELECT DISTINCT JURISDICTION_CODE, TAX_UNIT_ID FROM PAY_US_ASG_REPORTING WHERE LENGTH(JURISDICTION_CODE) = 8

Two characteristics of this definition are important. First, the DISTINCT keyword removes duplicate jurisdiction/tax unit combinations, so the view returns a reference list rather than transaction-level detail. Second, the predicate LENGTH(JURISDICTION_CODE) = 8 restricts output to exactly eight-character jurisdiction codes, which is the discriminator used here to isolate school district jurisdictions from other US tax jurisdictions (such as seven-character codes used for other tax types). Because the view performs no joins and no outer-join logic, its row count and performance profile are governed entirely by the volume and indexing of PAY_US_ASG_REPORTING.

Key Columns

The view exposes only two columns, both inherited directly from the base object:

• JURISDICTION_CODE — The jurisdiction identifier for the assignment reporting record. In this view it is constrained to eight characters in length, which is the filter that scopes the view to school district jurisdictions. This value drives tax calculation and reporting grouping at the jurisdiction level.
• TAX_UNIT_ID — The identifier of the tax unit associated with the jurisdiction. It is the foreign key linking the jurisdiction to the tax unit definition used by US payroll tax processing, allowing downstream logic to resolve the correct withholding or reporting entity.

No descriptive name, effective date, or attribute columns are exposed. Consumers requiring additional detail, such as tax unit names or assignment-level context, must join back to other PAY tax and jurisdiction tables using these two identifiers.

Common Use Cases and Queries

The view is typically used to obtain a deduplicated list of school district jurisdiction and tax unit pairings for reporting, validation, and data-migration scenarios. A basic query retrieves the full reference set:

• SELECT jurisdiction_code, tax_unit_id FROM apps.pay_us_tax_unit_schools_v ORDER BY jurisdiction_code;

For validation work, the view can confirm whether a specific jurisdiction resolves to a tax unit:

• SELECT tax_unit_id FROM apps.pay_us_tax_unit_schools_v WHERE jurisdiction_code = :p_jurisdiction;

Because the view returns only two columns, joins are usually required to enrich the output. A common pattern joins to the tax unit definition to resolve the tax unit name for reporting extracts, or joins to assignment-level reporting data when a full detail listing (rather than the distinct pairing) is required. The view is also useful as a driver in concurrent program parameters or LOV definitions where only the distinct eight-character jurisdiction codes are needed. Consumers should note that the view is read-only, carries no indexes of its own, and inherits whatever indexing exists on PAY_US_ASG_REPORTING; high-frequency access should be evaluated against that base object's access path.