Search Results per_cont_workers_current_x




Overview
Explore in AI Chat

Overview

PER_CONT_WORKERS_CURRENT_X is a date-effective view owned by the APPS schema within the PER – Human Resources product family of Oracle E-Business Suite. It presents the current, effective-dated record of contingent workers by joining person, assignment, and period-of-placement information and filtering to the row that is effective as of the current date. Because it is a "current" view, callers do not need to supply an effective date or write the standard TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date predicate themselves.

The view is used primarily for reporting and integration of contingent worker data — non-employees engaged through a vendor, staffing agency, or procurement channel. It exposes vendor, purchase order, and assignment attributes alongside person attributes, and it is commonly the target of concurrent programs, BI Publisher reports, and inbound/outbound interfaces that must resolve the present state of a contingent worker's assignment rather than its historical versions. The object is documented as VALID in the ETRM repository for release 12.2.2 and applies equally to 12.1.1, where the underlying PER date-effective schema is unchanged.

Underlying Base Objects

According to the ETRM metadata, the view is defined over the following documented base objects:

  • PER_PEOPLE_F (view) — the date-effective person record, aliased P. Supplies person identifiers, name components, NPW number, current-NPW flag, e-mail address, party/global/local/list names, and the 30 person attributes plus attribute category.
  • PER_ALL_ASSIGNMENTS_F (synonym) — the date-effective assignment record, aliased A. Supplies organization, assignment, vendor, purchase order, location, supervisor, and set-of-books information.
  • PER_PERIODS_OF_PLACEMENT (synonym) — the placement record, aliased PP, contributing ACTUAL_TERMINATION_DATE.
  • HR_GENERAL (package) — used to derive effective-date and session context values such as the business group and current date.
  • HR_PERSON_NAME (package) — used to render the formatted person name from the name components.
  • HR_SECURITY (package) — applied so the view honours the row-level security (security profile) of the querying user.

The view therefore inherits the standard EBS date-effective and security semantics of the PER schema rather than reading a single physical table.

Key Columns

Common Use Cases and Queries

Typical scenarios include generating rosters of active contingent workers for a business group, validating vendor and PO details during invoice or procurement reconciliation, and populating downstream interfaces with current NPW data. Because HR_SECURITY is referenced, the view returns only persons within the caller's security profile, and because HR_GENERAL supplies the effective date, it is not suited to historical reporting — use the underlying _F tables with an explicit date for point-in-time analysis.

Retrieve current contingent workers for a business group:

  • SELECT person_id, npw_number, full_name, vendor_id, po_header_id FROM per_cont_workers_current_x WHERE business_group_id = :p_bg_id AND current_npw_flag = 'Y';

List contingent workers with their supplier and expiration:

  • SELECT w.full_name, w.vendor_employee_number, w.vendor_assignment_number, w.actual_termination_date FROM per_cont_workers_current_x w ORDER BY w.full_name;

Join to purchasing for PO detail:

  • SELECT w.full_name, p.segment1 po_number, w.billing_title FROM per_cont_workers_current_x w, po_headers_all p WHERE w.po_header_id = p.po_header_id;