Search Results per_people_x




Overview
Explore in AI Chat

Overview

HRIBV_SUPV_HRCHY_X is a read-only Oracle EBS view owned by the APPS schema and defined in the Human Resources Intelligence (HRI) product family. HRI is documented in ETRM as an obsolete module, though its objects frequently remain valid in Oracle EBS 12.1.1 and 12.2.2 environments because they are retained for backward compatibility with historical reports and custom extensions. The view exposes a flattened, denormalized representation of the supervisor hierarchy: each row pairs a supervisor with a subordinate and supplies the names, levels, and assignment identifiers for both parties, along with the business group context.

The view text carries a 2001 header comment ($HEADER: HRIVIEW.LDT 115.3), reflecting its origin as part of the early HRI HR intelligence reporting layer. Its role is essentially reporting and integration: it lets downstream queries and interfaces resolve hierarchy relationships without joining the underlying summary table to person and organization entities themselves. The trailing WITH READ ONLY clause confirms that no DML is permitted against it.

Underlying Base Objects

The documented base objects for this view are HRI_CS_SUPH_X_V (VIEW), HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM), HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), and PER_PEOPLE_X (VIEW). Structurally, the view selects from HRI_SUPV_HRCHY_SUMMARY (aliased SVL) as its driving source, joined to HR_ALL_ORGANIZATION_UNITS_TL (BGRT) for the supervisor business group name and to PER_PEOPLE_X (PER and PER2) for the supervisor and subordinate person names respectively.

The two PER_PEOPLE_X joins correlate on PERSON_ID for the supervisor (SVL.SUPV_PERSON_ID = PER.PERSON_ID) and the subordinate (SVL.SUB_PERSON_ID = PER2.PERSON_ID). The business group join is an outer join (BGRT.ORGANIZATION_ID (+)) constrained by BGRT.LANGUAGE (+) = USERENV('LANG'), so the view returns rows even when no translated organization name exists for the session language. HR_GENERAL is invoked for the lookup decode, while HR_PERSON_NAME and HR_SECURITY support the underlying name resolution and row-level access behavior inherited through PER_PEOPLE_X.

Key Columns

Common Use Cases and Queries

Typical scenarios include rebuilding supervisory organization charts, validating hierarchy integrity, and extracting supervisor-to-subordinate pairs for downstream analytics or third-party integration.

SELECT supervisor_person_name,
       subordinate_person_name,
       supervisor_level,
       subordinate_level,
       subordinate_primary_asg_flag
FROM   apps.hribv_supv_hrchy_x
WHERE  supervisor_business_group_id = :p_business_group_id
ORDER BY supervisor_level, supervisor_person_name;

Because the view is read-only and joins PER_PEOPLE_X, results respect the security profile applied to the person view. A narrower query returning identifiers only is preferable for bulk interfaces:

SELECT supervisor_person_id,
       supervisor_assignment_id,
       subordinate_person_id,
       subordinate_assignment_id
FROM   apps.hribv_supv_hrchy_x;

Given the obsolete HRI status, new development should target supported HRMS hierarchy views; HRIBV_SUPV_HRCHY_X should be treated as a legacy compatibility object and validated against the target release before use.