Search Results npw_number




Overview
Explore in AI Chat

Overview

APPS.HRI_CL_PER_V is a Business Intelligence System (BIS) view owned by the APPS schema, registered in FND Design Data as HRI.HRI_CL_PER_V. It is a list-of-values view for People, exposing a denormalized, security-filtered roster of persons known to Oracle HRMS together with a null row that supports "all values" selection in LOV-enabled fields. The view is validated against Oracle E-Business Suite 12.1.1 and 12.2.2 and remains one of the standard lookup sources used by HRMS self-service pages, Oracle HRMS forms, and custom concurrent programs that must resolve a person identifier from a display name or from an applicant/employee classification.

Its documented "VALUE" column carries a fixed 302-character derivation, and ORDER_BY mirrors the same length, confirming that the view is designed for presentation rather than for bulk extraction. The presence of HR_SECURITY_FLAG_CODE and BG_SECURITY_FLAG_CODE indicates that row-level HR security is applied inside the view definition, so callers inherit the security profile of the querying session without writing additional predicates. This makes the view appropriate for LOVs and pickers that must not leak records outside a user's authorized business group or organization hierarchy.

Underlying Base Objects

The documented dependency list shows that HRI_CL_PER_V is defined over APPS.HRI_CL_PER_N_V, which supplies the secured person rows, combined with PUBLIC.DUAL to inject the null row. Supporting program units referenced during compilation include HR_BIS, HR_GENERAL, and HR_SECURITY, which perform the business-group and security-profile resolution, plus FND_PROFILE for profile option evaluation. The view is itself referenced by APPS.HRI_CL_PER_CCMGR_V, forming a two-tier LOV hierarchy in which the CCMGR view narrows the same person population for a specific picker context. No base tables are documented at the view's immediate level; the physical tables are reached through HRI_CL_PER_N_V and the HR_BIS/HR_SECURITY package logic beneath it.

Key Columns

Common Use Cases and Queries

The most frequent use is driving a People LOV in a custom OAF page, Oracle Forms block, or concurrent program parameter. Restricting the population to employees and applicants uses the searched column directly:

SELECT id, value, emp_or_apl_flag_code, employee_number, applicant_number
FROM apps.hri_cl_per_v
WHERE business_group_id = :p_business_group_id
AND nvl(emp_or_apl_flag_code, 'X') IN ('EMP', 'APL')
ORDER BY order_by;

A second pattern resolves a display name to a person identifier during inbound integration processing, using FULL_NAME or KNOWN_AS with an effective-date filter so that only currently valid rows are matched. A third pattern joins the view to HRI_CL_PER_CCMGR_V when a manager-scoped picker is required, relying on the parent view to supply the secured population before the CCMGR view applies its narrower criteria. Because the view is security-enabled, queries should not add manual BUSINESS_GROUP_ID or organization predicates beyond the intended context; doing so can conflict with HR_SECURITY resolution and produce unexpected empty result sets.