Search Results per_workforce_current_x




Overview
Explore in AI Chat

Overview

PER_WORKFORCE_CURRENT_X is a date-effective, read-only view owned by the APPS schema and delivered as part of the Oracle Human Resources (PER) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows the standard EBS extension convention: the _X suffix designates an "extension" or interface-style view that flattens and joins data from multiple HR entities, while CURRENT indicates that the view resolves the current effective row rather than exposing the full date-tracked history. Functionally, the view presents one consolidated record per current workforce person, merging person-level attributes (name, employee number, e-mail, descriptive flexfield segments, party and global name identifiers) with the employee's current assignment attributes (organization, supervisor, location, assignment type, project title, billing title) and selected placement/vendor details. Because it is date-effective, the row returned reflects the state in effect on the effective date supplied by the underlying HR date-tracked tables. In reporting and integration terms, it is the canonical "who works here now" projection and is commonly consumed by custom reports, extracts, interfaces, and third-party integrations that require a single current row per worker without issuing the multi-table, date-effective joins against the base HR tables themselves.

Underlying Base Objects

The view is not a physical table; it resolves at runtime against the following documented base objects. Person rows derive from the PER_PEOPLE_F view over PER_ALL_PEOPLE_F, which supplies the effective-dated person attributes and the attributes/attribute category columns exposed in the view. Assignment-level columns derive from PER_ALL_ASSIGNMENTS_F, accessed through the APPS synonym, supplying ORGANIZATION_ID, ASSIGNMENT_ID, SUPERVISOR_ID, SUPERVISOR_ASSIGNMENT_ID, LOCATION_ID, VENDOR_ID, VENDOR_EMPLOYEE_NUMBER, VENDOR_ASSIGNMENT_NUMBER, VENDOR_SITE_ID, PO_HEADER_ID, PO_LINE_ID, DEFAULT_CODE_COMB_ID, and SET_OF_BOOKS_ID. Termination context comes from PER_PERIODS_OF_SERVICE, joined through the period of service on the person and assignment, yielding ACTUAL_TERMINATION_DATE. Placement and vendor staffing attributes come from PER_PERIODS_OF_PLACEMENT. The PACKAGE references — HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY — are invoked by the view's SQL rather than stored data: HR_GENERAL provides date-effectivity and business group resolution, HR_PERSON_NAME formats the name columns (FULL_NAME, LIST_NAME, LOCAL_NAME, GLOBAL_NAME), and HR_SECURITY applies the row-level security predicate so the query only returns workers the run-as user is permitted to see. Callers should therefore treat the view with the same security implications as querying PER_ALL_PEOPLE_F directly.

Key Columns

Person identity is conveyed by PERSON_ID, PARTY_ID, EMPLOYEE_NUMBER, NPW_NUMBER, FULL_NAME, FIRST_NAME, MIDDLE_NAMES, LAST_NAME, and PRE_NAME_ADJUNCT, with EMAIL_ADDRESS and EXPENSE_CHECK_SEND_TO_ADDRESS for communication data. The CURRENT_EMPLOYEE_FLAG and CURRENT_NPW_FLAG columns indicate whether the person is a current employee or a current non-payroll worker, and BUSINESS_GROUP_ID scopes the row to its HR business group. Assignment columns include ASSIGNMENT_ID, ASSIGNMENT_TYPE, ORGANIZATION_ID, LOCATION_ID, SUPERVISOR_ID, and SUPERVISOR_ASSIGNMENT_ID. Financial and project columns are SET_OF_BOOKS_ID, DEFAULT_CODE_COMB_ID, PROJECT_TITLE, and BILLING_TITLE (aliased from A.TITLE). Vendor and procurement columns (VENDOR_ID, VENDOR_EMPLOYEE_NUMBER, VENDOR_ASSIGNMENT_NUMBER, VENDOR_SITE_ID, PO_HEADER_ID, PO_LINE_ID) support contractor and contingent-worker scenarios. ACTUAL_TERMINATION_DATE provides termination context from the period of service. ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 expose the person descriptive flexfield, and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) record audit information.

Common Use Cases and Queries

Typical uses include headcount and current-worker extracts, supervisor/org reporting, and vendor or PO-linked contingent-worker reconciliation. A basic current-employee query:

  • SELECT p.employee_number, p.full_name, p.email_address, a.organization_id, a.supervisor_id, a.assignment_type FROM apps.per_workforce_current_x p, apps.per_workforce_current_x a WHERE p.person_id = a.person_id AND p.current_employee_flag = 'Y'; — note that person and assignment attributes are projected into the same row, so a single-table filter normally suffices: SELECT employee_number, full_name, organization_id, supervisor_id FROM apps.per_workforce_current_x WHERE current_employee_flag = 'Y';
  • Vendor/contingent worker listing: filter on current_npw_flag = 'Y' and select vendor_id, vendor_employee_number, and po_header_id.
  • Termination review: order by actual_termination_date and restrict to non-null values.
  • HR security applies, so results are limited to the run-as user's accessible business groups and organizations; ETRM notes the HR_SECURITY package dependency accordingly. For historical "as of" reporting, use the underlying date-effective tables with an explicit effective date rather than this CURRENT view.