Search Results activity_line4

Overview

APPS.HR_ESTABLISHMENTS_V is a reporting view in the Oracle E-Business Suite Human Resources (HR) module that exposes the establishment records defined within an organization hierarchy. An "establishment" in EBS terminology is an organizational unit that represents a physical or logical reporting location used primarily for regulatory reporting purposes, most notably EEO-1 and VETS-100 filings in the United States. The view is owned by the APPS schema and is available in both EBS 12.1.1 and 12.2.2, where users frequently search for it under the shorthand term "hr_estab."

The view does not store data itself; it is a curated projection of establishment information that joins the core organization definition with class information and compliance-specific flexfield segments. Its primary purpose is to give HR administrators, payroll analysts, and reporting developers a clean interface to identify which organizations qualify as establishments and to retrieve the associated regulatory attributes required for government filings.

Underlying Base Objects

The view is defined over two documented base objects, both accessed via synonyms in the APPS schema:

• HR_ALL_ORGANIZATION_UNITS — the master repository of organizational units, supplying core attributes such as name, dates, type, and address.
• HR_ORGANIZATION_INFORMATION — the descriptive flexfield and organization information store, referenced three times (aliased O2, O3, and O4) to retrieve class information and the EEO-1 and VETS-100 filing attributes.

The join logic is central to the view's behavior. The O2 alias is joined non-outer and filters on ORG_INFORMATION_CONTEXT of 'CLASS' with ORG_INFORMATION1 = 'HR_ESTAB' and ORG_INFORMATION2 = 'Y'. This means only organizations whose class information explicitly identifies them as an establishment are returned. The O3 and O4 aliases are outer-joined (indicated by the (+) syntax) to retrieve the 'Establishment EEO-1 Filing' and 'Establishment VETS-100 Filing' contexts respectively, so organizations lacking those compliance attributes still appear with null values in those columns.

Key Columns

• ORGANIZATION_ID — the primary identifier of the establishment organization.
• BUSINESS_GROUP_ID — the business group owning the establishment, exposed with a + 0 coercion.
• NAME — the establishment name.
• DATE_FROM / DATE_TO — effective dating for the establishment record.
• TYPE — the organization unit type.
• INTERNAL_ADDRESS_LINE and COMMENTS — descriptive location and note fields.
• LOCATION_ID — foreign key to the location/address definition.
• ORG_INFORMATION2, ORG_INFORMATION3 … ORG_INFORMATION11 (O3) — EEO-1 filing attribute segments.
• ORG_INFORMATION1, ORG_INFORMATION2 (O4) — VETS-100 filing attribute segments.

Common Use Cases and Queries

Typical uses include identifying establishments for regulatory reporting, populating EEO-1 and VETS-100 extracts, and building compliance dashboards.

SELECT organization_id,
       name,
       date_from,
       date_to,
       org_information1 vets100_flag
FROM   apps.hr_establishments_v
WHERE  business_group_id = :p_bg_id;

To locate establishments with active EEO-1 data:

SELECT organization_id, name
FROM   apps.hr_establishments_v
WHERE  org_information2 IS NOT NULL;

Because compliance segments are outer-joined, report writers should anticipate nulls and use NVL where appropriate.