Results for “hr_tax_units_v”

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

Overview

HR_TAX_UNITS_V is an APPS-owned database view in the Oracle E-Business Suite PER (Human Resources) product family. Per the ETRM documentation, its stated purpose is "used to support user interface." It is a denormalized, reporting-oriented view that consolidates a single organization unit record with its associated tax, filing, and reporting attributes. The view resolves a common EBS design pattern: organization-level descriptive and legislative attributes are stored as row-wise, context-driven rows in HR_ORGANIZATION_INFORMATION rather than as discrete columns. HR_TAX_UNITS_V pivots those context rows into a flat, single-row-per-organization projection that a form, concurrent program, or report can consume directly.

The name and column composition indicate the view is focused on tax and regulatory reporting units — for example, employer identification, EEO-1, VETS-100, and W-2 reporting rules. Because the name reflects UI support rather than a business API, the view should be treated as a read-only reporting artifact. Its column set and join semantics are dictated by the consuming user interface and should not be assumed stable across patches. The view carries a VALID status in the ETRM metadata.

Underlying Base Objects

The documented ETRM 12.2.2 metadata lists the referenced base objects as HR_ALL_ORGANIZATION_UNITS (synonym), HR_ALL_ORGANIZATION_UNITS_TL (synonym), HR_GENERAL (package), HR_LOCATIONS (view), and HR_ORGANIZATION_INFORMATION (synonym). The view text confirms these relationships. HR_ALL_ORGANIZATION_UNITS supplies the organization identity, business group, name, effective dates, type, and address line. HR_LOCATIONS supplies the address attributes (address lines, town or city, region, postal code, and country), and HR_GENERAL is invoked in the user-facing layer for organizational naming logic. HR_ALL_ORGANIZATION_UNITS_TL underpins the translated name resolution.

The view text shows HR_ORGANIZATION_INFORMATION joined many times — aliases O2 through O10 — once for each ORG_INFORMATION_CONTEXT of interest. Each alias is an outer join to the organization, and each is filtered by a specific context via ORG_INFORMATION_CONTEXT (+). Consequently, every context becomes its own ORG_INFORMATION1...N columns, exposing the flexfield segments associated with that context. The ORG_INFORMATION_CONTEXT value is the discriminator that determines which of the context-specific attributes each alias contributes.

Key Columns

• ORGANIZATION_ID — Primary identifier joining to HR_ALL_ORGANIZATION_UNITS and all information aliases.
• BUSINESS_GROUP_ID — Business group owning the organization; the + 0 coercion forces numeric treatment.
• NAME — Organization unit name.
• DATE_FROM / DATE_TO — Effective dating of the organization record.
• TYPE — Internal organization classification.
• LOCATION_ID, ADDRESS_LINE_1..3, TOWN_OR_CITY, POSTAL_CODE, COUNTRY — Location details from HR_LOCATIONS; the region is chosen dynamically via DECODE(L.STYLE, 'US', L.REGION_2, 'CA', L.REGION_1, ' '), reflecting US vs. Canadian address formatting.
• O2.ORG_INFORMATION1 — Employer Identification context value.
• O4.ORG_INFORMATION1..5 — EEO-1 Filing attributes.
• O5.ORG_INFORMATION1..2 — VETS-100 Filing attributes.
• O6.ORG_INFORMATION1, O7.ORG_INFORMATION1 — W2 Reporting Rules and related context values.
• O8.ORG_INFORMATION1..4 and O9.ORG_INFORMATION1..7, O10.ORG_INFORMATION1..2 — Additional legislative reporting contexts.

Common Use Cases and Queries

The view is typically queried to retrieve a legal-entity or reporting-unit profile without hand-coding multiple outer joins against HR_ORGANIZATION_INFORMATION. A representative query:

SELECT organization_id, name, org_information1, town_or_city, country
FROM   apps.hr_tax_units_v
WHERE  organization_id = :p_org_id;

Analysts use it to validate that employer identification, EEO-1, and W-2 reporting contexts are populated for each organization before running regulatory extracts:

SELECT organization_id, name
FROM   apps.hr_tax_units_v
WHERE  org_information1 IS NULL;

Because each context is a separate outer-joined alias, a NULL in a given context column simply means that context is absent for the organization — this is a useful data-quality signal. When reproducing the view's logic, users should remember that the ORG_INFORMATION_CONTEXT filter is applied to each alias independently and that failing to mimic the outer joins will silently drop organizations lacking any one context. The view is read-only and intended for query and reporting, not for direct DML.