Results for “hrilv_emp_hrs_x”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HRILV_EMP_HRS_X is a read-only Oracle EBS view shipped within the HRI (Human Resources Intelligence) product family. It presents a simplified, filtered list of people records intended for use as an inline value-set or list-of-values source in Oracle HRMS forms, self-service pages, and DBA/reporting utilities. The view exposes a compact projection of the PER_PEOPLE_X entity table, reducing a wide person record to a small set of columns suitable for selection lists and lightweight lookups.

The view is defined with a WITH READ ONLY clause and a header tag indicating that it originated from the HRI view library (HRIVIEW.LDT, version 115.3, dated 2001/09/18). The _X suffix and the "X" designation in the HRI naming convention signal that this object belongs to the "extra" or extended view set used by HRI cross-product reporting rather than to the core HRMS schema. Because it is read-only, it cannot be used as a DML target; it functions strictly as a query surface.

The view is not implemented in every database. The ETRM metadata explicitly notes "Not implemented in this database" for the reference instance, meaning availability depends on whether HRI was licensed and installed in the environment. Implementations running only core HR without HRI may not have this view at all.

Underlying Base Objects

The view is defined over a single base object: PER_PEOPLE_X, the datetracked ("_X") version of the PER_PEOPLE table used by Oracle HRMS. The _X suffix indicates that the underlying table is date-effective, and the view therefore carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns derived from the datetrack framework.

No other base tables are documented as referenced. All joins are commented out in the view text (the /*JOINS*/ placeholder is empty), and the only runtime predicate applied is CURRENT_EMPLOYEE_FLAG = 'Y'. A secondary security predicate constrains BUSINESS_GROUP_ID using HR_GENERAL.GET_BUSINESS_GROUP_ID via an NVL expression, so the view automatically narrows results to the user's current business group when that function returns a value.

Key Columns

• ID — maps to PER_PEOPLE_X.PERSON_ID; the primary identifier for the person. This is the value typically returned by the list of values.
• VALUE — maps to PER_PEOPLE_X.FULL_NAME; the descriptive label shown to the user in a pick list.
• DATE_FROM — the datetrack EFFECTIVE_START_DATE for the row, indicating when the person record version became effective.
• DATE_TO — the datetrack EFFECTIVE_END_DATE; a high sentinel date indicates the current active version.
• BUSINESS_GROUP_ID — identifies the business group (legal employer) that owns the person record; also used by the built-in security predicate.
• CURRENT_EMPLOYEE_FLAG — restricted to 'Y' by the view logic, so every returned row represents a current employee.
• CURRENT_APPLICANT_FLAG — indicates whether the person is also flagged as a current applicant.
• CURRENT_EMP_OR_APL_FLAG — combined indicator that is 'Y' when the person is either a current employee or applicant.
• PERSON_TYPE_ID — foreign key to the person type (for example, Employee, Contingent Worker, Applicant).
• COMMENT_ID — reference to an associated comment/note record.

Common Use Cases and Queries

The view is most commonly used as the validation source for a parameter or value set requiring a current employee selection. A typical query returns the person identifier and name for the active business group:

SELECT id, value FROM hr.hrilv_emp_hrs_x ORDER BY value;

Because the business group predicate is embedded, the result set is automatically scoped and no additional WHERE clause on business group is normally required. To inspect the employee's person type alongside the lookup:

SELECT id, value, person_type_id, current_emp_or_apl_flag FROM hr.hrilv_emp_hrs_x WHERE person_type_id = :p_person_type;

Reporting consumers use the view to build fast pick lists and drill-down filters without writing the join against PER_PEOPLE_X directly. Note that since the view is read-only and ORACLE-published, it should never be referenced in DML, and query results are subject to the datetrack and business-group security behavior of the underlying PER_PEOPLE_X table.