Search Results default_code_comb_id




Overview

PER_ASSIGNMENTS_X is an APPS-owned view within the Oracle E-Business Suite PER (Human Resources) product module. In EBS 12.1.1 and 12.2.2, it is a VALID database object that exposes assignment information as of the current system date (SYSDATE). The view is documented in the ETRM as "as of sysdate view," meaning its primary purpose is to provide the current effective row for each employee assignment rather than the full dated history stored in the underlying date-tracked tables. This makes it a convenient reporting and integration object for consumers who need the latest active assignment record without writing explicit effective-date predicates against the _F (date-tracked) tables. It returns the standard assignment attributes—assignment identifiers, effective dates, business group, job, position, grade, supervisor, payroll, location, and related flexfield attributes—alongside audit columns such as LAST_UPDATE_DATE, CREATED_BY, and OBJECT_VERSION_NUMBER.

Underlying Base Objects

According to the documented view metadata for ETRM 12.2.2, PER_ASSIGNMENTS_X references the following base objects:

  • PER_ASSIGNMENTS_F (VIEW) — the primary date-tracked source of assignment data. The _X view selects the currently effective row from this table based on effective dates.
  • HR_SECURITY (PACKAGE) — the Oracle HR security package that enforces security profile restrictions, ensuring users only see assignments for which they have access.
  • HR_GENERAL (PACKAGE) — the general HR utility package used to apply effective-date and business-group logic.

The view is the current-dated counterpart of PER_ASSIGNMENTS_F. Where the _F view contains all dated versions of each assignment, PER_ASSIGNMENTS_X filters to the row whose effective range encompasses SYSDATE, applying HR security through the referenced packages.

Key Columns

The view exposes the full column set of the assignment entity. Significant columns include:

Common Use Cases and Queries

PER_ASSIGNMENTS_X is typically used for current-state reporting: headcount and roster reports, supervisor lookups, payroll-interface extracts, and current assignment validations in downstream applications. Because it is already filtered to the current date and honors HR security, it simplifies queries that would otherwise require explicit effective-date logic against PER_ASSIGNMENTS_F. A typical query retrieving current assignments for a person might resemble:

  • SELECT pa.assignment_id, pa.person_id, pa.assignment_number, pa.job_id, pa.position_id, pa.supervisor_id FROM apps.per_assignments_x pa WHERE pa.person_id = :p_person_id;
  • SELECT pa.assignment_number, pa.normal_hours, pa.assignment_status_type_id FROM apps.per_assignments_x pa WHERE pa.primary_flag = 'Y' AND pa.business_group_id = :p_bg_id;
  • SELECT pa.assignment_id, pa.ass_attribute_category, pa.ass_attribute1 FROM apps.per_assignments_x pa WHERE pa.assignment_type = 'E';

Results are constrained by HR security, so queries return only assignments the running user is authorized to view. For historical or date-range analysis, developers should query PER_ASSIGNMENTS_F directly instead, since PER_ASSIGNMENTS_X exposes only the SYSDATE-effective row.