Results for “per_org_structure_elements_v2”

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

Overview

PER_ORG_STRUCTURE_ELEMENTS_V2 is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER (Human Resources) product family. ETRM documents its purpose concisely as "used to support user interface" — in practice it serves as a denormalized, language-aware projection of the organization structure hierarchy that forms the backbone of the Organization Hierarchy and Position Control windows. Rather than forcing report authors and integrations to re-join the version, element, structure, and translation tables, the view collapses that join path into a single relational source that returns one row per organization structure element with its parent organization name and the position control indicator already resolved.

The view is present and valid in both the 12.1.1 and 12.2.2 codelines, and its definition is materially identical in each. It is therefore a safe dependency in custom concurrent programs, Discoverer workbooks, BI Publisher data models, and inbound/outbound interfaces that must navigate the parent-child relationships between organizations.

Underlying Base Objects

ETRM lists five referenced base objects, all consumed through APPS synonyms: PER_ORG_STRUCTURE_ELEMENTS, PER_ORG_STRUCTURE_VERSIONS, PER_ORGANIZATION_STRUCTURES, HR_ALL_ORGANIZATION_UNITS, and HR_ALL_ORGANIZATION_UNITS_TL. The join logic is as follows:

• PER_ORG_STRUCTURE_ELEMENTS (POSE) is the driving table, supplying the element key, child and parent organization identifiers, the audit columns, and POSITION_CONTROL_ENABLED_FLAG.
• PER_ORG_STRUCTURE_VERSIONS (POSV) is joined on ORG_STRUCTURE_VERSION_ID and links each element to a specific version of an organization hierarchy.
• PER_ORGANIZATION_STRUCTURES (POS) is joined through POSV.ORGANIZATION_STRUCTURE_ID to supply the structure (hierarchy) name.
• HR_ALL_ORGANIZATION_UNITS (POU) is joined to POSE.ORGANIZATION_ID_PARENT to validate the parent organization and to reach its translated name.
• HR_ALL_ORGANIZATION_UNITS_TL (POUTL) supplies the parent organization display name, filtered by USERENV('LANG') so that rows return in the session's current language.

Note that the view exposes the parent organization name only; the child organization name is not resolved within this view and must be obtained separately from HR_ALL_ORGANIZATION_UNITS_TL when required.

Key Columns

The view returns ORG_STRUCTURE_ELEMENT_ID as the primary element identifier, accompanied by ROWID, ORG_STRUCTURE_VERSION_ID, and ORG_STRUCTURE_HIERARCHY, which carries the structure name from PER_ORGANIZATION_STRUCTURES. Both sides of the relationship are exposed as ORGANIZATION_ID_PARENT and ORGANIZATION_ID_CHILD, while PARENT_NAME provides the translated parent organization name.

POSITION_CONTROL_ENABLED_FLAG is the column most frequently sought by implementers. It is carried directly from PER_ORG_STRUCTURE_ELEMENTS and indicates whether position control is enabled for the parent organization node within the hierarchy. Values are the standard EBS Yes/No flags. Because the flag is stored at the element (hierarchy edge) level rather than on the organization itself, the same organization can legitimately appear as position-controlled in one hierarchy and not in another; any query that filters or groups on this flag must therefore be constrained by ORG_STRUCTURE_VERSION_ID or ORG_STRUCTURE_HIERARCHY to return meaningful results.

Standard WHO audit columns are also present, including CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, along with the concurrent request columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include validating position-control configuration before a payroll or budgeting cycle, extracting organization hierarchies for downstream reporting, and auditing hierarchy version history. A representative query returning position-controlled nodes in a named hierarchy:

• SELECT organization_id_parent, organization_id_child, parent_name, position_control_enabled_flag, org_structure_hierarchy
• FROM apps.per_org_structure_elements_v2
• WHERE org_structure_hierarchy = :p_hierarchy_name
• AND position_control_enabled_flag = 'Y'
• ORDER BY organization_id_parent, organization_id_child;

For version comparisons, join the view back to PER_ORG_STRUCTURE_VERSIONS on ORG_STRUCTURE_VERSION_ID and filter on DATE_FROM/DATE_TO. Because the view does not expose a date-effective predicate itself, callers must apply effective-date logic explicitly. Filtering on BUSINESS_GROUP_ID is also good practice in multi-business-group implementations.