Search Results hri_cl_per_v




Overview
Explore in AI Chat

Overview

HRI_CL_PER_V is a reporting view historically shipped with the Human Resources Intelligence (HRI) module in Oracle E-Business Suite. HRI was an early Oracle HRMS analytics product that predated the Oracle HRMS Intelligence family and the later Oracle Business Intelligence Applications. In Oracle EBS 12.1.1 and 12.2.2 the module is classified as obsolete, and its objects are retained only for backward compatibility. The view is not implemented in a standard 12.2.2 database, meaning no corresponding object exists in the shipped schema; any environment that references it must have obtained the definition from an earlier installation or from a custom installation script.

The view presents a denormalized, reporting-friendly projection of person records drawn from PER_ALL_PEOPLE_F. Its distinguishing feature is a set of derived code columns that collapse the several worker-classification flags maintained by Oracle HRMS into single-character indicators. The most notable of these is CWK_FLAG_CODE, the identifier that surfaces contingent-worker status. In HRMS terminology a contingent worker is a non-payrolled person engaged through an agency or similar arrangement, recorded in PER_ALL_PEOPLE_F through the CURRENT_NPW_FLAG column (NPW meaning non-payrolled worker). The HRI view renames that flag to CWK_FLAG_CODE to align with the HRI reporting vocabulary, in which contingent workers were a distinct analytical population. The view also exposes a display VALUE column, built by concatenating the first initial, a period, and the last name, intended for use in LOVs and list-based reports.

Underlying Base Objects

The view text is defined solely over PER_ALL_PEOPLE_F, the effective-dated date-tracked table that stores all person records in Oracle HRMS, including employees, applicants, and contingent workers. No other base objects are documented in the ETRM metadata. The view is declared WITH READ ONLY, so it cannot be used as the target of DML; it is purely a query surface. Because PER_ALL_PEOPLE_F is date-tracked, the START_DATE, END_DATE, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE columns exposed by the view carry the row's effective dating directly, and any query that needs a current picture must filter on the effective dates or use the database date-tracked view conventions. The BUSINESS_GROUP_ID column preserves the operating unit context under which the person record was created.

Key Columns

Note that the documented column list contains minor naming variations (PER_NAME_ADJUNCT and HONOR) relative to the view text (PRE_NAME_ADJUNCT and HONORS); the view text is the authoritative definition.

Common Use Cases and Queries

The principal use case is a compact person list for reporting and integration, particularly where worker classification matters. A query returning current contingent workers would read:

SELECT ID, VALUE, FULL_NAME, NPW_NUMBER FROM HRI_CL_PER_V WHERE CWK_FLAG_CODE = 'Y';

A broader workforce listing that separates the three populations uses the individual flag columns:

SELECT EMPLOYEE_NUMBER, FULL_NAME, EMP_FLAG_CODE, CWK_FLAG_CODE, APL_FLAG_CODE FROM HRI_CL_PER_V ORDER BY LAST_NAME, FIRST_NAME;

Because the view is read only and not implemented by default in 12.2.2, consumers should treat it as legacy. New development should query PER_ALL_PEOPLE_F directly, or the supported date-tracked views such as PER_PEOPLE_F, and derive the flag columns locally rather than depending on HRI_CL_PER_V. Where a legacy report or interface still references CWK_FLAG_CODE, the equivalent logic is NVL(CURRENT_NPW_FLAG,'N') against PER_ALL_PEOPLE_F.