Search Results subro_absolute_level

Overview

The view APPS.PJI_DIS_SUP_ROHRCHY_V is a Project Intelligence (PJI) discoverer view that exposes resource hierarchy data combined with subordinate rollup information. It is a denormalized, reporting-oriented object intended primarily for Oracle Discoverer workbooks and other ad hoc analytical reporting against project resource hierarchies. The view flattens supervisor / subordinate / subordinate-of-subordinate relationships into a single row per hierarchy path, allowing report authors to navigate multi-level resource rollups without writing recursive SQL.

Its status is VALID and it is owned by the APPS schema, which is typical for EBS reporting views that reside alongside the applications tables. Because it belongs to the PJI product, its consumption is intended for Project Intelligence and Project Management reporting contexts rather than for transactional processing. In Oracle EBS 12.1.1 and 12.2.2 the view definition and column set remain consistent, making it a stable reporting artifact across both releases.

Underlying Base Objects

Although referenced base objects are not separately documented in the ETRM metadata, the view text reveals its dependencies clearly. It joins four objects:

• HRI_CS_SUPHRO_V — the supervisor/subordinate hierarchy source view (aliased MGR) that supplies the level and person/assignment identifiers.
• PER_ALL_PEOPLE_F aliased SUP — resolves the supervisor person's full name.
• PER_ALL_PEOPLE_F aliased SUB — resolves the subordinate person's full name.
• PER_ALL_PEOPLE_F aliased SUBRO — resolves the subordinate-of-subordinate person's full name.

The join is date-effective: the hierarchy EFFECTIVE_START_DATE must fall between each person record's EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. Only rows where PRIMARY_HIERARCHY_FLAG_CODE = 'Y' are returned, restricting output to the primary resource hierarchy. The HRI_CS_SUPHRO_V object is part of the Oracle Human Resources Intelligence common schema, which underpins several PJI reporting views.

Key Columns

The view exposes hierarchy depth and relationship columns together with identity and date attributes:

• SUP_ABSOLUTE_LEVEL — absolute hierarchy level of the supervisor.
• SUB_ABSOLUTE_LEVEL and SUB_RELATIVE_LEVEL — absolute and relative levels of the subordinate.
• SUBRO_ABSOLUTE_LEVEL, SUBRO_SUP_RELATIVE_LEVEL, SUBRO_SUB_RELATIVE_LEVEL — the columns most relevant to the search term "subro_absolute_level", describing the subordinate-of-subordinate's absolute level and its relative position to both the supervisor and subordinate. This is the value commonly filtered to target a specific rollup depth.
• SUP_PERSON_ID / SUB_PERSON_ID / SUBRO_PERSON_ID and the matching ASSIGNMENT_ID columns — the three parties in the hierarchy path.
• SUP_NAME / SUB_NAME / SUBRO_NAME — full names resolved from PER_ALL_PEOPLE_F.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — validity window of the hierarchy row.

Common Use Cases and Queries

Typical uses include building Discoverer reports on resource rollups, reconciling time or cost by management hierarchy, and extracting hierarchy extracts for downstream analytics. A representative query filtering on the level columns is:

• SELECT sup_name, sub_name, subro_name, subro_absolute_level FROM apps.pji_dis_sup_rohrchy_v WHERE subro_absolute_level = 3 AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
• Filtering on subro_sup_relative_level or subro_sub_relative_level to isolate direct versus indirect rollups.

Because person names are sourced from date-effective records, queries should always constrain on EFFECTIVE_START_DATE / EFFECTIVE_END_DATE to avoid duplicate or stale rows returning across the hierarchy.