Search Results supervisor_employee_number




Overview
Explore in AI Chat

Overview

APPS.HRIBV_SUPV_HRCHY_X is a read-only Oracle EBS view that exposes denormalized supervisor–subordinate hierarchy information for reporting and integration purposes. It is part of the Oracle HRMS intelligence/analytic layer, evidenced by its naming convention (HRI = Human Resources Intelligence) and its derivation from the underlying HRI_CS_SUPH_X_V collection view. The view resolves the raw surrogate identifiers held in lower-level hierarchy tables into human-readable attributes, including business group name, supervisor and subordinate person names, employee numbers, and absolute hierarchy levels.

The object is defined with the WITH READ ONLY clause, meaning it cannot be the target of DML. Its primary role is to serve as a convenient, security-aware source for queries, BI Publisher reports, discoverer worksheets, and downstream interfaces that need to flatten an organizational reporting line into a single row per supervisor/subordinate relationship. The user search term "supervisor_employee_number" maps directly to the view's SUPERVISOR_EMPLOYEE_NUMBER column, which is one of its most frequently filtered attributes.

Underlying Base Objects

The view is a join across four documented objects. The driving object is HRI_CS_SUPH_X_V, a hierarchy collection view that supplies the core supervisor/subordinate rows, absolute levels, assignment identifiers, person identifiers, and business group identifiers. HR_ALL_ORGANIZATION_UNITS_TL provides the translated (language-sensitive) business group name via BGRT.NAME, restricted to the session language using the userenv('LANG') predicate. Two instances of PER_PEOPLE_X — aliased PER and PER2 — resolve the supervisor and subordinate person records respectively, yielding FULL_NAME and EMPLOYEE_NUMBER.

The view additionally depends on HR_GENERAL for the DECODE_LOOKUP function call that converts the YES_NO lookup code into a display value, and on HR_SECURITY and HR_PERSON_NAME, which are invoked indirectly through PER_PEOPLE_X to enforce row-level security and formatted name resolution. Because all four top-level objects are views or synonyms rather than base tables, the object functions as an abstraction layer, insulating consumers from the physical detail of the HR hierarchy tables.

Key Columns

Common Use Cases and Queries

A typical use is retrieving all direct and indirect subordinates beneath a named supervisor. The following query returns the reporting line for a given employee number:

  • SELECT supervisor_employee_number, supervisor_person_name, subordinate_employee_number, subordinate_person_name, subordinate_level FROM apps.hribv_supv_hrchy_x WHERE supervisor_employee_number = :emp_num ORDER BY subordinate_level;
  • SELECT subordinate_employee_number, subordinate_person_name FROM apps.hribv_supv_hrchy_x WHERE supervisor_person_id = :person_id AND subordinate_primary_asg_flag = 'Yes';
  • SELECT supervisor_business_group, COUNT(DISTINCT subordinate_person_id) FROM apps.hribv_supv_hrchy_x GROUP BY supervisor_business_group;

Because the view is read-only and security-enabled through the underlying person views, it is well suited to self-service reporting, span-of-control analysis, and reconciliation of supervisor hierarchies against PER_ASSIGNMENTS. Queries should filter on indexed underlying identifiers where possible, as the textual joins to HR_ALL_ORGANIZATION_UNITS_TL and PER_PEOPLE_X carry translation and security overhead.