Results for “per_assignments”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PER_ASSIGNMENTS is a date-effective reporting view in the Oracle E-Business Suite Human Resources (PER) product module. It presents assignment records for employees, contingent workers, and other person types as they exist across effective-dated time periods. In EBS 12.1.1 and 12.2.2 the object is registered in the ETRM as a VALID view owned by the APPS schema, described simply as a "Date-effective view."

Because Oracle HRMS stores assignment history in date-tracked (datetrack) tables, a single logical assignment can have many rows, each governing a validity window defined by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. PER_ASSIGNMENTS exposes this history together with the security and session logic needed to return only rows the querying user is authorized to see. It is therefore the standard access point for reporting, interfaces, and integrations that need assignment data without directly navigating the datetracked base tables.

Underlying Base Objects

The documented referenced base objects for this view are:

• PER_ASSIGNMENTS_F (VIEW) — the primary source of assignment rows and columns.
• HR_SECURITY (PACKAGE) — supplies the security predicates that restrict rows to the security profile of the current responsibility.
• HR_GENERAL (PACKAGE) — supplies general HRMS date-effective and utility logic used in constructing the view.
• FND_SESSIONS (SYNONYM) — provides session context (for example, the effective date used to resolve the "current" row).

Functionally, PER_ASSIGNMENTS behaves as a secured, effective-date-aware projection over PER_ASSIGNMENTS_F. Queries against the view inherit the date-track filter and the security filter, so a row returned represents a valid assignment version for the session's effective date and the user's data access.

Key Columns

The view exposes the full column list of the assignment entity. Principal columns include:

• ASSIGNMENT_ID — primary identifier of the assignment; ASSIGNMENT_NUMBER is the user-facing number.
• PERSON_ID — the person to whom the assignment belongs; PRIMARY_FLAG distinguishes the primary assignment from secondary ones.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the datetrack validity window for the row.
• BUSINESS_GROUP_ID, ORGANIZATION_ID, PEOPLE_GROUP_ID — organizational context of the assignment.
• JOB_ID, GRADE_ID, POSITION_ID, LOCATION_ID, PAYROLL_ID, SUPERVISOR_ID — core assignment attributes and foreign keys to HR and payroll entities.
• ASSIGNMENT_STATUS_TYPE_ID, ASSIGNMENT_TYPE, EMPLOYMENT_CATEGORY, EMPLOYEE_CATEGORY — status and classification of the assignment.
• NORMAL_HOURS, FREQUENCY, PAY_BASIS_ID, HOURLY_SALARIED_CODE — working-time and pay-basis attributes.
• PROBATION_PERIOD, PROBATION_UNIT, DATE_PROBATION_END, NOTICE_PERIOD — terms-of-employment fields.
• ASS_ATTRIBUTE1 ... ASS_ATTRIBUTE30, ASS_ATTRIBUTE_CATEGORY — descriptive flexfield (DFF) segments.
• LAST_UPDATE_DATE, CREATED_BY, OBJECT_VERSION_NUMBER — standard audit and concurrency columns.

Common Use Cases and Queries

Typical scenarios include headcount and establishment reporting, supervisor/direct-report extraction, payroll interfaces needing assignment-to-payroll mappings, and integration extracts feeding downstream systems. Because the view is secured, it should be preferred over PER_ASSIGNMENTS_F for user-facing reports.

Example: current primary assignments for a business group.

• SELECT pa.assignment_id, pa.assignment_number, pa.person_id, pa.job_id, pa.organization_id, pa.supervisor_id, pa.effective_start_date, pa.effective_end_date FROM apps.per_assignments pa WHERE pa.primary_flag = 'Y' AND pa.business_group_id = :p_business_group_id;

Example: assignments effective on the current date.

• SELECT pa.assignment_id, pa.person_id, pa.assignment_status_type_id FROM apps.per_assignments pa WHERE TRUNC(SYSDATE) BETWEEN pa.effective_start_date AND NVL(pa.effective_end_date, TRUNC(SYSDATE)) AND pa.business_group_id = :p_business_group_id;

Example: join to person and supervisor details for a reporting extract.

• SELECT pa.assignment_number, p.full_name, mgr.full_name AS supervisor_name FROM apps.per_assignments pa, apps.per_all_people_f p, apps.per_all_people_f mgr WHERE pa.person_id = p.person_id AND pa.supervisor_id = mgr.person_id(+) AND TRUNC(SYSDATE) BETWEEN p.effective_start_date AND p.effective_end_date AND pa.business_group_id = :p_business_group_id;

When querying, always supply a business group or organizational predicate where possible, and join to other date-effective entities within their own effective windows to avoid row multiplication.