Search Results per_all_assignments




Overview
Explore in AI Chat

Overview

PER_ALL_ASSIGNMENTS is a date-effective view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides within the PER (Human Resources) product family and exposes assignment-level data for employees, contingent workers, and other assignment holders. In Oracle HRMS, an assignment represents the relationship between a person and an organization, capturing the terms under which the person works — their job, position, grade, location, payroll, supervisor, and associated statutory and compensation attributes. Because assignments are date-tracked, changes such as a promotion, transfer, or supervisor reassignment are retained as dated rows rather than overwritten, and the view is designed to surface this date-effective information for reporting and integration purposes.

The view is widely referenced in custom reports, interfaces, and extracts where historical or current assignment details are required. It is also commonly joined with person, position, job, and payroll objects to produce workforce analytics, headcount reporting, and data feeds into external systems.

Underlying Base Objects

According to the ETRM metadata for 12.2.2, the view is defined over two documented referenced objects: PER_ALL_ASSIGNMENTS_F (exposed via a synonym) and FND_SESSIONS (also exposed via a synonym).

  • PER_ALL_ASSIGNMENTS_F is the core date-effective ("_F" denotes "date-effective") base table that stores all assignment records, including the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns that govern row validity over time. PER_ALL_ASSIGNMENTS is the view layer over this table and inherits its date-effective behavior.
  • FND_SESSIONS is an Oracle Application Object Library table that tracks active user sessions. Its inclusion indicates the view applies session-context logic, typically to filter or resolve data relative to the current session's business group or effective date context.

Because the view delegates to PER_ALL_ASSIGNMENTS_F, it reflects the same effective-dating model: a single assignment may be represented by multiple rows spanning contiguous date ranges.

Key Columns

The view exposes a broad set of columns. Significant ones include:

Common Use Cases and Queries

Typical uses include current headcount reporting, historical assignment tracking, supervisor hierarchies, and persons-per-organization extracts. Because of effective dating, queries generally restrict rows to a point in time or to the current date.

  • Current active assignments for a person or business group.
  • Assignment history showing job, position, or supervisor changes over time.
  • Feeds joining to PER_ALL_PEOPLE_F for person detail.
SELECT assignment_id,
       person_id,
       assignment_number,
       organization_id,
       job_id,
       supervisor_id,
       effective_start_date,
       effective_end_date
FROM   apps.per_all_assignments
WHERE  person_id = :p_person_id
AND    TRUNC (SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Consumers should treat PER_ALL_ASSIGNMENTS as a read-only, date-effective reporting view over PER_ALL_ASSIGNMENTS_F, and always apply effective-date predicates to avoid returning multiple historical rows for a single assignment.