Search Results current_applicant_flag

Overview

The APPS.HRI_CL_PER_EMP_HX_V view is a Human Resources Intelligence (HRI) object that exposes employee history records in a denormalized, key-flexfield-friendly structure. It is owned by the APPS schema and is a read-only view, as indicated by the WITH READ ONLY clause in the underlying view text. In Oracle EBS 12.1.1 and 12.2.2, HRI objects are used primarily for HR analytics, data extraction, and integration with external or downstream reporting environments, including the Enterprise Data Warehouse (EDW) and similar business intelligence targets.

The view was retrieved in the context of the search term "current_emp_or_apl_flag", which corresponds to one of the columns projected by the view — CURRENT_EMP_OR_APL_FLAG. This flag distinguishes whether a person is currently an employee or an applicant, making the view useful for filtering populations by status when generating extracts or KFF-driven value sets.

The object is documented with the columns ID, VALUE, DATE_FROM, DATE_TO, BUSINESS_GROUP_ID, CURRENT_EMPLOYEE_FLAG, CURRENT_APPLICANT_FLAG, CURRENT_EMP_OR_APL_FLAG, PERSON_TYPE_ID, and COMMENT_ID. Its primary source is the PER_PEOPLE_X view, supplemented by a sentinel row from DUAL annotated with the NA_EDW marker.

Underlying Base Objects

The documented referenced base objects for APPS.HRI_CL_PER_EMP_HX_V are:

• PER_PEOPLE_X (VIEW) — the principal source of person rows in the main SELECT of the view text.
• HR_BIS (PACKAGE), HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE) — HR packages invoked indirectly through the PER_PEOPLE_X view to supply business logic such as name formatting, security filtering, and date handling.
• DUAL (SYNONYM) — used to inject a single placeholder row (ID = -1, flags = 'NA_EDW') covering the full temporal range from HR_GENERAL.START_OF_TIME to HR_GENERAL.END_OF_TIME.

The UNION ALL construct in the view text draws the primary population from PER_PEOPLE_X where CURRENT_EMPLOYEE_FLAG = 'Y', and then appends the NA_EDW sentinel row. This design is common in HR Intelligence Key Flexfield (KFF) views, where a synthetic "NA_EDW" row enables value-set and extract processes to handle null or "not applicable" cases in an EDW context.

Key Columns

• ID — PERSON_ID of the employee, or -1 for the sentinel row. This is the KFF ID segment.
• VALUE — FULL_NAME of the person, or an empty string for the sentinel row. This is the KFF value segment.
• DATE_FROM / DATE_TO — Effective date range derived from PER_PEOPLE_X.EFFECTIVE_START_DATE and EFFECTIVE_END_DATE; the sentinel row spans START_OF_TIME to END_OF_TIME.
• BUSINESS_GROUP_ID — Business group identifier for the person, or -1 for the sentinel.
• CURRENT_EMPLOYEE_FLAG — 'Y' for current employees; 'NA_EDW' for the sentinel row. This is the filter predicate used in the main SELECT.
• CURRENT_APPLICANT_FLAG — Indicates whether the person is currently an applicant; 'NA_EDW' for the sentinel.
• CURRENT_EMP_OR_APL_FLAG — Indicates whether the person is currently an employee or an applicant. This is the column associated with the user's search term and is frequently used in downstream filters.
• PERSON_TYPE_ID — Person type reference; -1 for the sentinel row.
• COMMENT_ID — Comment identifier; -1 for the sentinel row.

Because only rows where CURRENT_EMPLOYEE_FLAG = 'Y' are returned from PER_PEOPLE_X, the primary population of the view is limited to active employees.

Common Use Cases and Queries

The view is typically queried to populate key flexfield value sets, build or refresh HR extracts into the EDW, or join to other HRI views and facts through PERSON_ID. Because the view is read-only, it is safe for reporting workloads.

A simple lookup by the search term's flag might resemble:

SELECT id,
       value,
       current_emp_or_apl_flag
FROM   apps.hri_cl_per_emp_hx_v
WHERE  current_emp_or_apl_flag = 'Y';

A typical extract that excludes the sentinel row uses:

SELECT id, value, date_from, date_to, business_group_id
FROM   apps.hri_cl_per_emp_hx_v
WHERE  id <> -1;

A join with PER_ALL_PEOPLE_F for richer attributes:

SELECT h.id, h.value, p.email_address
FROM   apps.hri_cl_per_emp_hx_v h,
       apps.per_all_people_f   p
WHERE  h.id = p.person_id
AND    h.id <> -1
AND    SYSDATE BETWEEN p.effective_start_date AND p.effective_end_date;

Because the view draws on HR_SECURITY indirectly, results are subject to the security profile of the querying user, which makes it appropriate for both enterprise-wide ETL and user-scoped reporting within Oracle EBS 12.1.1 and 12.2.2.