Search Results org_information3




Overview
Explore in AI Chat

Overview

APPS.HR_TAX_UNITS_V is a denormalized reporting view that consolidates organizational unit attributes and their associated tax, statutory, and reporting-related descriptive flexfield (DFF) values into a single flat structure. In Oracle EBS 12.1.1 and 12.2.2, the view is owned by the APPS schema and is primarily used by payroll, tax reporting, and U.S. statutory filing processes that must resolve a tax unit's identity, address, and filing configuration in one access path. Rather than joining HR_ALL_ORGANIZATION_UNITS to HR_ORGANIZATION_INFORMATION multiple times for each DFF context, the view pre-joins these relationships so that downstream reports, concurrent programs, and interfaces can query a single row per organization unit.

The view is frequently implicated when users search for org_information2, because its SELECT list exposes multiple aliased ORG_INFORMATION2 columns drawn from distinct DFF contexts. This naming overlap is a common source of confusion in ad hoc queries, since the same column label appears several times with different semantic meanings depending on which alias (O2, O4, O5, O8, O9, O10) it originates from.

Underlying Base Objects

Per the documented ETRM metadata, HR_TAX_UNITS_V is defined over the following base objects:

  • HR_ALL_ORGANIZATION_UNITS (synonym) — the driving table, aliased as O.
  • HR_ALL_ORGANIZATION_UNITS_TL (synonym) — provides the translated organization name, aliased as OTL.
  • HR_ORGANIZATION_INFORMATION (synonym) — joined multiple times (aliases O2 through O10) to retrieve DFF context rows.
  • HR_LOCATIONS (view) — supplies address components, aliased as L.
  • HR_GENERAL (package) — referenced indirectly for HR utility logic.

All joins to HR_ORGANIZATION_INFORMATION are outer joins (denoted by the (+) operator), meaning an organization unit will still return a row even when a given DFF context has not been populated. The single inner join to HR_LOCATIONS (alias O3, with O.ORGANIZATION_ID = O3.ORGANIZATION_ID) means a valid location must exist for the row to appear. Each DFF alias carries a distinct ORG_INFORMATION_CONTEXT filter, including 'Employer Identification', 'EEO-1 Filing', 'VETS-100 Filing', and 'W2 Reporting Rules'.

Key Columns

  • ORGANIZATION_ID, BUSINESS_GROUP_ID — primary keys identifying the unit and its business group.
  • NAME — translated organization name from the TL table.
  • DATE_FROM / DATE_TO — effective dating of the unit.
  • INTERNAL_ADDRESS_LINE, COMMENTS, TYPE, LOCATION_ID — core unit attributes.
  • ORG_INFORMATION1..ORG_INFORMATION5 — flattened DFF segments. Multiple ORG_INFORMATION2 columns are projected from contexts such as 'EEO-1 Filing' (O4), 'VETS-100 Filing' (O5), and others (O8, O9, O10), each representing a distinct DFF segment value.
  • ADDRESS_LINE_1..3, TOWN_OR_CITY, POSTAL_CODE, COUNTRY — location address fields; a DECODE supplies region based on location style ('US' vs 'CA').

Common Use Cases and Queries

Typical usage includes U.S. statutory reporting (EEO-1, VETS-100, W-2), tax unit validation, and integration extracts requiring consolidated unit and DFF data.

Sample query retrieving EEO-1 related values:

SELECT organization_id, name, org_information2 FROM apps.hr_tax_units_v WHERE business_group_id = :p_bg_id;

Because ORG_INFORMATION2 is projected multiple times, best practice is to reference the view's positional columns explicitly or wrap it in an inline view with aliases to avoid ambiguity.