Search Results per_employees_x




Overview
Explore in AI Chat

Overview

PER_EMPLOYEES_X is a date-effective (datetracked) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER — Human Resources product family. The view presents a consolidated, current-row perspective of employee records by joining the core person, assignment, and period-of-service entities and restricting output to the single effective-dated row that applies to the system date (TRUNC(SYSDATE)). Because Oracle HRMS stores person and assignment data in datetracked _F tables that hold multiple time-bounded row versions, PER_EMPLOYEES_X removes the burden of constructing the BETWEEN SYSDATE logic from the caller, exposing a flat, report-friendly result set. Its status is documented as VALID in ETRM for both 12.1.1 and 12.2.2, and it is referenced widely by reporting, extracts, and integration interfaces that require the currently active employee record without the complexity of the underlying date-effective joins. It is a view only; no physical storage or materialization is associated with it.

Underlying Base Objects

The documented view text defines PER_EMPLOYEES_X over three primary sources:

ETRM additionally lists HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY as referenced package objects. These are called indirectly through the underlying person views and enforce name formatting and security (security profile) behaviour, which is significant because the view is subject to HR security at the person level when accessed through standard HRMS APIs and forms.

Key Columns

The projection carries three categories of data. Person identity columns include PERSON_ID, PARTY_ID, EMPLOYEE_NUMBER, FULL_NAME, FIRST_NAME, MIDDLE_NAMES, LAST_NAME, TITLE, LIST_NAME, GLOBAL_NAME, LOCAL_NAME, EMAIL_ADDRESS, and EXPENSE_CHECK_SEND_TO_ADDRESS. Assignment columns include ASSIGNMENT_ID, ORGANIZATION_ID, LOCATION_ID, SUPERVISOR_ID, SET_OF_BOOKS_ID, and DEFAULT_CODE_COMB_ID. Business group context is supplied by BUSINESS_GROUP_ID, and service history by ACTUAL_TERMINATION_DATE. The descriptive flexfield is exposed across ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30. Standard who-columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also included. Note that the view exposes only the currently effective datetracked row; historical versions are not returned.

Common Use Cases and Queries

Typical applications include point-in-time employee listings, active headcount extracts, feeder files for payroll or third-party interfaces, and security-filtered assignment reports. A representative query retrieving active employees for a business group is:

  • SELECT person_id, employee_number, full_name, supervisor_id, organization_id FROM apps.per_employees_x WHERE business_group_id = :p_bg_id ORDER BY employee_number;
  • SELECT full_name, email_address, location_id FROM apps.per_employees_x WHERE supervisor_id = :p_supervisor; — direct-report listing for a manager.
  • SELECT employee_number, actual_termination_date FROM apps.per_employees_x WHERE TRUNC(actual_termination_date) BETWEEN :p_start AND :p_end; — termination analysis for a period.

Because the view applies TRUNC(SYSDATE) internally, it cannot be used to obtain historical assignment or person versions. For date-effective as-of queries against past dates, developers should query PER_PEOPLE_F and PER_ALL_ASSIGNMENTS_F directly with explicit EFFECTIVE_START_DATE and EFFECTIVE_END_DATE predicates, or use the corresponding HRMS APIs (for example, the HR_GENERAL and HR_SECURITY packages) to respect security and business-group filtering. Callers should also be aware that the termination-date subquery logic restricts the assignment row returned, and that the view is dependent on the calling session's effective HR security context.