Search Results sup_absolute_level




Overview

APPS.HRI_CL_PER_CCMGR_V is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered under the FND Design Data object HRI.HRI_CL_PER_CCMGR_V and is documented with a status of VALID. The view exposes a hierarchical listing of people together with the cost centers to which they belong and the managers responsible for those cost centers. In ETRM terminology, it functions as a List of Values for cost centers and their managers, meaning it is intended primarily as a lookup source for reporting, Discoverer workbooks, and other BIS-driven inquiries that need to resolve a cost center manager within an organizational hierarchy.

The view is closely associated with the query term sup_absolute_level, a column that reflects the absolute depth of a supervisor node in the reporting hierarchy. Because the view exposes both supervisor and subordinate identifiers—SUP_PERSON_ID and SUB_PERSON_ID—as well as their hierarchical levels, it supports navigation and qualification of management relationships across cost centers.

Underlying Base Objects

The ETRM dependency metadata lists the following objects referenced by HRI_CL_PER_CCMGR_V:

  • APPS.HRI_CL_PER_V — the core person-level view supplying person attributes and hierarchy context.
  • APPS.HRI_CS_PER_ORGCC_CT — a collection/table supplying organization cost center relationships.
  • APPS.HRI_CS_SUPH_X_V — the supervisor hierarchy extraction view providing the supervisor/subordinate structure and absolute level values.
  • FND_PROFILE — used via profile options to resolve session context and security.
  • HR_GENERAL, HR_SECURITY, and HR_BIS — package dependencies used for person data retrieval, row-level security enforcement, and BIS plumbing respectively.

The view therefore sits on top of the HRI (Human Resources Intelligence) BIS layer, which pre-joins and denormalizes HR person, supervisor hierarchy, and cost center data so that reporting tools do not have to reconstruct these relationships at runtime.

Key Columns

  • ID (NUMBER) — surrogate identifier for the row.
  • VALUE (VARCHAR2, 302) — the display value used in list-of-values contexts, typically the concatenated cost center / manager label.
  • PARENT_ID (NUMBER, 15) — reference to the parent node in the hierarchy, enabling recursive traversal.
  • START_DATE, END_DATE (DATE) — validity window for the relationship.
  • SUP_PERSON_ID, SUB_PERSON_ID (NUMBER, 15) — the supervisor (manager) and subordinate person identifiers.
  • SUP_ABSOLUTE_LEVEL, SUB_ABSOLUTE_LEVEL (NUMBER, 15) — absolute depth of the supervisor and subordinate nodes within the supervisor hierarchy, independent of any cost center grouping.
  • SUB_RELATIVE_LEVEL (NUMBER, 15) — depth of the subordinate relative to the queried supervisor, used for relative-level filtering.

Common Use Cases and Queries

Typical uses include resolving the manager of a given cost center, building organization charts for a cost center, and driving LOV pickers that let a user select a manager-limited cost center. Sample SQL against the view:

SELECT id, value, sup_person_id, sub_person_id, sup_absolute_level, sub_absolute_level, sub_relative_level FROM apps.hri_cl_per_ccmgr_v WHERE sup_person_id = :p_manager_id AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE);

To list all direct reports of a manager regardless of cost center:

SELECT sub_person_id, value FROM apps.hri_cl_per_ccmgr_v WHERE sup_person_id = :p_manager_id AND sub_relative_level = 1;

To obtain the full subtree beneath a manager, query without the relative-level predicate and let the application or a hierarchical query (CONNECT BY on parent_id) walk the structure. Because the view enforces HR security through HR_SECURITY, results are automatically filtered to the rows the connecting user is permitted to see.