Results for “per_workforce_x”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PER_WORKFORCE_X is a date-effective view owned by the APPS schema in Oracle E-Business Suite, defined within the PER (Human Resources) product module. It exposes a denormalized, reporting-oriented projection of workforce data by joining person records to assignment records and related service and placement information. The "_X" suffix denotes a cross-product or "extension" view whose column set is deliberately broad, spanning core HR attributes alongside attributes typically consumed by Oracle Projects, Oracle Payables, and expense-related flows. In EBS 12.1.1 and 12.2.2 the object is documented as VALID and is referenced through the ETRM (E-Business Suite Technical Reference Manual) as a date-effective view. Its principal role is to provide a single, stable query surface for workforce reporting, third-party integrations, and personalization logic that would otherwise require multi-table joins against PER_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_PERIODS_OF_SERVICE. Because it is a view rather than a table, no direct DML is supported against it; consumers read it and rely on the underlying date-effective tables to supply row-level currency based on effective dates.
Underlying Base Objects
The ETRM metadata lists the objects on which PER_WORKFORCE_X depends: PER_PEOPLE_F (VIEW), PER_ALL_ASSIGNMENTS_F (SYNONYM), PER_PERIODS_OF_PLACEMENT (SYNONYM), PER_PERIODS_OF_SERVICE (SYNONYM), and three HR PL/SQL packages — HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. The view text confirms this structure: person-level columns are sourced from the PER_PEOPLE_F alias P (EMPLOYEE_NUMBER, FULL_NAME, EMAIL_ADDRESS, PARTY_ID, ATTRIBUTE1 through ATTRIBUTE30, and the standard WHO columns), while assignment-level columns are sourced from the PER_ALL_ASSIGNMENTS_F alias A (ORGANIZATION_ID, ASSIGNMENT_ID, SUPERVISOR_ID, SUPERVISOR_ASSIGNMENT_ID, SET_OF_BOOKS_ID, DEFAULT_CODE_COMB_ID, LOCATION_ID, PROJECT_TITLE, TITLE, VENDOR_ID, and ASSIGNMENT_TYPE). Period-of-service data, such as ACTUAL_TERMINATION_DATE, is supplied via the alias PS from PER_PERIODS_OF_SERVICE. The PL/SQL package dependencies reflect that the view participates in HR security and name-formatting conventions: HR_SECURITY governs row-level access by business group and security profile, HR_PERSON_NAME supplies formatted name derivations, and HR_GENERAL provides general HR utilities invoked during view evaluation.
Key Columns
The view exposes a wide column set that can be grouped functionally.
- Person identifiers and names: PERSON_ID, PARTY_ID, EMPLOYEE_NUMBER, NPW_NUMBER, FULL_NAME, FIRST_NAME, MIDDLE_NAMES, LAST_NAME, PRE_NAME_ADJUNCT, GLOBAL_NAME, LOCAL_NAME, LIST_NAME, EMAIL_ADDRESS.
- Employment status: CURRENT_EMPLOYEE_FLAG and CURRENT_NPW_FLAG indicate whether the person is presently an employee or a non-payroll worker; BUSINESS_GROUP_ID scopes the record to its legislative business group.
- Assignment context: ASSIGNMENT_ID, ORGANIZATION_ID, LOCATION_ID, ASSIGNMENT_TYPE, SUPERVISOR_ID, SUPERVISOR_ASSIGNMENT_ID, PROJECT_TITLE, and BILLING_TITLE (the billed form of the assignment title).
- Financial defaults: SET_OF_BOOKS_ID and DEFAULT_CODE_COMB_ID, used when assignments feed Payables or Projects accounting.
- Contingent worker and procurement data: VENDOR_ID, VENDOR_EMPLOYEE_NUMBER, VENDOR_ASSIGNMENT_NUMBER, VENDOR_SITE_ID, PO_HEADER_ID, and PO_LINE_ID, supporting contractor and purchase-order-linked engagements.
- Termination and audit: ACTUAL_TERMINATION_DATE from the period of service, plus CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, and the thirty generic ATTRIBUTE columns with ATTRIBUTE_CATEGORY for descriptive flexfield data.
Common Use Cases and Queries
Typical scenarios include headcount and roster reporting by organization, supervisor-hierarchy extracts, contractor and purchase-order reconciliation, and integration feeds that require both person and assignment attributes on a single row. Because PER_WORKFORCE_X is date-effective, queries should constrain the effective window where currency matters, although the view itself exposes only the currently effective denominator in most standard EBS deployments. A representative query follows.
SELECT EMPLOYEE_NUMBER, FULL_NAME, ORGANIZATION_ID, ASSIGNMENT_ID, SUPERVISOR_ID, EMAIL_ADDRESS, ACTUAL_TERMINATION_DATE FROM APPS.PER_WORKFORCE_X WHERE BUSINESS_GROUP_ID = :p_business_group_id AND CURRENT_EMPLOYEE_FLAG = 'Y' ORDER BY FULL_NAME;
For contingent worker analysis, filtering on CURRENT_NPW_FLAG = 'Y' and non-null VENDOR_ID isolates vendor-linked assignments. Integrators should note that row visibility is subject to HR_SECURITY; the same query may return different result sets depending on the security profile of the connected user or the responsibility used to run the report.
-
View: PER_WORKFORCE_X 12.2.2
Date-effective view.
APPS.PER_WORKFORCE_X·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore PER module →
-
View: PER_WORKFORCE_X 12.1.1
Date-effective view.
APPS.PER_WORKFORCE_X·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore PER module →
-
VIEW: APPS.PER_WORKFORCE_X 12.1.1
-
VIEW: APPS.PER_WORKFORCE_X 12.2.2
-
View: PO_BUYER_NAME_NUM_V 12.2.2
APPS.PO_BUYER_NAME_NUM_V·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore PO module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1