Search Results hri_cl_per_ccmgr_v

Overview

The view APPS.HRI_CL_PER_CCMGR_V is a Human Resources Intelligence (HRI) component delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. HRI is the analytical layer that supports Oracle HRMS reporting, workforce intelligence, and the Oracle Daily Business Intelligence for HRMS dashboards. This particular view supplies a date-effective, tree-structured result set that describes the current "cost center manager" relationship between employees and their supervisors. It is designed to be consumed by HRI collection programs and hierarchy-based visualizations, where each row represents a person, the person's parent node, and the effective dating of both the person record and the supervisory relationship.

Unlike transactional HRMS views that simply join PER_ASSIGNMENTS_F to PER_PEOPLE_F, this view restricts output to the current hierarchy level and applies stringent currency checks. The final predicate SHR1.SUB_RELATIVE_LEVEL <= 1 limits the result to top-level and one-level-deep supervisor entries, which suits organizational chart rendering and management roll-up reporting.

Underlying Base Objects

The view is defined entirely over three primary objects and two correlated subqueries:

• HRI_CS_SUPH_V — the HRI supervisor hierarchy view, aliased as SHR1. It supplies the person-to-supervisor mapping and the SUB_RELATIVE_LEVEL hierarchy depth attribute.
• PER_PEOPLE_F — the date-effective person table, aliased as CCPEO. It provides PERSON_ID, FULL_NAME, and the effective start/end dates.
• PER_ASSIGNMENTS_F — the date-effective assignment table, aliased as ASG. It provides SUPERVISOR_ID as the PARENT_ID value and restricts rows to primary assignments (PRIMARY_FLAG = 'Y').

Two EXISTS subqueries further constrain the result set. The first verifies that each subject person has CURRENT_EMPLOYEE_FLAG = 'Y' in PER_PEOPLE_F. The second joins HR_ORGANIZATION_INFORMATION, PER_PEOPLE_F, HR_ALL_ORGANIZATION_UNITS, and the supervisor hierarchy view to confirm the individual is associated with an organization through an "ORGANIZATION NAME ALIAS" context. All effective dating is resolved with TRUNC(SYSDATE), so only currently valid records are returned. The view carries the WITH READ ONLY clause, making it non-updatable.

Key Columns

• ID — sourced from CCPEO.PERSON_ID; the unique identifier of the employee node.
• VALUE — sourced from CCPEO.FULL_NAME; the display label for the node.
• PARENT_ID — sourced from ASG.SUPERVISOR_ID; the identifier of the employee's supervisor and the parent link in the hierarchy tree.
• START_DATE / END_DATE — the effective dates copied from PER_PEOPLE_F, defining when the node record is valid.
• SUP_PERSON_ID — derived from SHR1.SUP_PERSON_ID; identifies the supervisor person associated with the current row.

Common Use Cases and Queries

Typical use is to feed HRI hierarchy collectors or ad-hoc organizational reports. A representative query is:

• SELECT id, value, parent_id FROM hri_cl_per_ccmgr_v;
• SELECT v.value employee, p.value manager FROM hri_cl_per_ccmgr_v v, hri_cl_per_ccmgr_v p WHERE v.parent_id = p.id;
• SELECT id, value FROM hri_cl_per_ccmgr_v WHERE sup_person_id = :p_supervisor_id;

Because all predicates use SYSDATE, results reflect only current, active employment and assignments. Rows belonging to employees without primary assignments or without current employee status are excluded, which should be accounted for when reconciling against PER_ALL_PEOPLE_F.