Search Results subord_primary_asg_flag_code




Overview

HRIBV_SUPV_HRCHY_ROLLUP_X is a read-only Oracle EBS view owned by the APPS schema and delivered as part of the HRI (Human Resources Intelligence) product family. It exposes the supervisor-to-subordinate hierarchical rollup used by HR Intelligence reporting, collapsing the multi-level supervisory chain into a single denormalized result set. The view is defined with the WITH READ ONLY clause, confirming it is intended strictly for query and reporting consumption rather than DML.

The view answers the recurring question of "who reports into whom, and at what supervisor level," which is why it surfaces the SUPERVISOR_LEVEL column directly. In 12.1.1 and 12.2.2 it is a reporting convenience layer over the HRI supervisor hierarchy summary, joined to person and organization lookups so that names and business group labels are already resolved for the consumer.

Underlying Base Objects

The documented definition draws from the HRI supervisor hierarchy summary table (HRI_SUPV_HRCHY_SUMMARY), self-joined as SVL and SSVL to associate each supervisor/subordinate pair with its reporting-organization relationship. Supporting lookups and descriptive entities are joined as follows:

ETRM 12.2.2 additionally records referenced base objects HRI_CS_SUPH_X_V, HR_BIS, HR_PERSON_NAME and HR_SECURITY. HR_SECURITY is significant because HR Intelligence views typically enforce row-level security so that a user only sees hierarchy data they are authorized to view.

Key Columns

Common Use Cases and Queries

Typical scenarios include supervisor rollup reports, span-of-control analysis, headcount-by-supervisor extracts and feeding downstream HR dashboards. Because the view is read-only and already resolved, it is well suited to ad hoc SQL and BI Publisher data models. A representative query:

  • SELECT supervisor_person_name, supervisor_level, subordinate_person_name, subordinate_level FROM apps.hribv_supv_hrchy_rollup_x WHERE supervisor_level = :p_level ORDER BY supervisor_person_name, subordinate_level;
  • Filtering by supervisor_business_group for a specific legal entity or business group.
  • Restricting results with HR security by querying as an application user rather than a privileged schema.

Consumers should treat the view as reporting-only and expect its result set to be governed by HR_SECURITY.