Search Results per_organization_units_v




Overview
Explore in AI Chat

Overview

PER_ORGANIZATION_UNITS_V is an Oracle E-Business Suite view owned by the APPS schema within the PER (Human Resources) product family. Its documented description in the ETRM repository is simply "Used to support user interface," indicating that it is not a public API but rather a presentation-layer construct intended to back Oracle Forms or OAF-based maintenance screens within the Human Resources organization hierarchy. The view is marked VALID and is available in both EBS 12.1.1 and 12.2.2.

Functionally, the view denormalizes the base organization units table into a form that is directly consumable by an HR user interface. It joins translated organization names, organization type and internal/external lookup meanings, and work day information into a single flattened result set. For reporting and integration developers, this makes PER_ORGANIZATION_UNITS_V a convenient read-only source for organization unit attributes without needing to manually reproduce the multi-table join logic.

Underlying Base Objects

The documented references in ETRM 12.2.2 are:

The view text confirms an outer-join pattern against HR_LOOKUPS for both TYPE and INTERNAL_EXTERNAL_FLAG, and against HR_ORGANIZATION_INFORMATION filtered on ORG_INFORMATION_CONTEXT = 'WORK DAY INFORMATION'. The translation table is joined on ORGANIZATION_ID and LANGUAGE = USERENV('LANG'), so the NAME returned reflects the session language of the querying user.

Key Columns

The view exposes the full HR_ALL_ORGANIZATION_UNITS column set plus several derived columns:

Common Use Cases and Queries

Typical uses include validating organization setup, building HR extracts, and resolving decoded lookup meanings without additional joins. A basic query returns active organization units with their decoded types:

SELECT organization_id,
       name,
       organization_type,
       internal_external_meaning,
       date_from,
       date_to
FROM   apps.per_organization_units_v
WHERE  TRUNC(SYSDATE) BETWEEN date_from
                          AND NVL(date_to, TRUNC(SYSDATE))
ORDER  BY name;

Filtering by organization type is common when populating downstream applications with only, for example, departments or business groups. Because the view uses the USERENV('LANG') multilingual join, the NAME column will automatically be returned in the language of the executing session; consumers running in batch should set the NLS_LANG environment variable appropriately to ensure predictable results. As the view is read-only and intended for user interface support, integrations should not treat it as an API for DML; updates must go through the HR_API package or the standard HR forms.