Search Results expense_check_address_flag




Overview
Explore in AI Chat

Overview

PER_EMPLOYEES_CURRENT_X is a date-effective (current-row) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER – Human Resources product family. It is documented in ETRM for releases 12.1.1 and 12.2.2 and is reported with a status of VALID. The view presents the intersection of person records, primary employee assignments, and periods of service, filtered so that only rows effective as of the current system date are returned. Because the filter is anchored on TRUNC(SYSDATE), the view behaves as a "current state" snapshot rather than a time-sliced historical view; it returns at most one effective row per person/assignment combination at query time.

The primary role of this view is to simplify reporting and integration against Oracle HRMS. Instead of joining PER_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_PERIODS_OF_SERVICE manually and managing effective date ranges, consumers can query PER_EMPLOYEES_CURRENT_X directly to retrieve the current employee population with assignment context. It is commonly used by downstream modules (Payroll, OTL, applications built on the HRMS APIs), custom reports, interfaces, and extracts.

Underlying Base Objects

The documented base objects underpinning this view are:

  • PER_PEOPLE_F (VIEW) — the date-effective person/employee datastore, aliased as P.
  • PER_ALL_ASSIGNMENTS_F (SYNONYM) — the date-effective assignment datastore, aliased as A.
  • PER_PERIODS_OF_SERVICE (SYNONYM) — the period-of-service header, aliased as B.
  • HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE) — supporting packages commonly referenced by the view and its environment.

Joins are established on PERSON_ID between PER_PEOPLE_F and PER_ALL_ASSIGNMENTS_F, and on PERIOD_OF_SERVICE_ID between PER_ALL_ASSIGNMENTS_F and PER_PERIODS_OF_SERVICE. The current-row restriction is implemented by the pair of BETWEEN effective-date predicates, one against PER_PEOPLE_F and one against PER_ALL_ASSIGNMENTS_F.

Key Columns

Common Use Cases and Queries

Typical use cases include current headcount reporting, feeding downstream HRMS integrations, populating name/email lookups, and validating assignment context for employees active today.

  • Current headcount by organization: SELECT ORGANIZATION_ID, COUNT(*) FROM APPS.PER_EMPLOYEES_CURRENT_X GROUP BY ORGANIZATION_ID.
  • Supervisor-to-report lookups: SELECT EMPLOYEE_NUMBER, FULL_NAME FROM APPS.PER_EMPLOYEES_CURRENT_X WHERE SUPERVISOR_ID = :p_supervisor_id.
  • Contact/email extract: SELECT EMPLOYEE_NUMBER, FULL_NAME, EMAIL_ADDRESS FROM APPS.PER_EMPLOYEES_CURRENT_X WHERE EMAIL_ADDRESS IS NOT NULL.
  • Assignment/COA verification for Payroll or OTL: join on PERSON_ID or ASSIGNMENT_ID to retrieve SET_OF_BOOKS_ID and DEFAULT_CODE_COMB_ID.

Because the view embeds TRUNC(SYSDATE) predicates, results change with the system date and are not suitable for point-in-time historical reporting; for that, query PER_PEOPLE_F and PER_ALL_ASSIGNMENTS_F directly with an explicit effective date. Performance can be sensitive to the effective-date filters, so queries should be limited to needed columns and, where possible, restricted by BUSINESS_GROUP_ID or ORGANIZATION_ID.