Results for “per_assignments_f”

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

Overview

PER_ASSIGNMENTS_F is a secure, date-effective view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PER (Human Resources) product family and is documented in ETRM as a "Secure view based on the corresponding _ALL_ table." In the Oracle EBS data model, the _F suffix denotes a date-tracked (effectively dated) entity, while the secure designation indicates that row-level access is filtered through Oracle HRMS security profiles rather than exposing the full dataset.

The view presents assignment records — the link between a person and the organizational attributes of their employment, such as job, position, grade, payroll, location, and supervisor. Because it enforces security, the rows returned depend on the responsibility and security profile of the querying user. This makes PER_ASSIGNMENTS_F the standard access point for reports, concurrent programs, and integrations that must respect HRMS security, while PER_ALL_ASSIGNMENTS_F remains the unrestricted base for internal processing.

Underlying Base Objects

The ETRM metadata lists three referenced base objects: HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), and PER_ALL_ASSIGNMENTS_F (SYNONYM). PER_ALL_ASSIGNMENTS_F is the date-effective _ALL_ table that physically stores all assignment rows across business groups. The synonym resolves to the underlying table at runtime. HR_SECURITY supplies the security profile logic that determines which business groups, organizations, and people a user may see, while HR_GENERAL provides supporting HRMS utility functions invoked during view resolution (for example, date-effective or business-group context handling). The view therefore projects the full column list of PER_ALL_ASSIGNMENTS_F but restricts visibility through the security packages, returning only rows the current user is authorized to access.

Key Columns

• ASSIGNMENT_ID — Primary key identifying the assignment; joins to assignment-related child tables.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective boundaries; queries typically filter on SYSDATE between these values to obtain the current record.
• PERSON_ID — Foreign key to the person; the individual holding the assignment.
• BUSINESS_GROUP_ID — The business group governing the assignment, central to security filtering.
• ORGANIZATION_ID, JOB_ID, POSITION_ID, GRADE_ID, LOCATION_ID — Organizational and job attributes of the assignment.
• PAYROLL_ID, SET_OF_BOOKS_ID — Payroll and ledger context used in payroll and costing integrations.
• SUPERVISOR_ID, PRIMARY_FLAG, MANAGER_FLAG — Reporting hierarchy and assignment role indicators.
• ASSIGNMENT_NUMBER, ASSIGNMENT_TYPE, ASSIGNMENT_STATUS_TYPE_ID — Identification and status of the assignment.
• LAST_UPDATE_DATE, CREATED_BY, OBJECT_VERSION_NUMBER — Audit and optimistic locking columns for interfaces.
• ASS_ATTRIBUTE1–30 — Descriptive flexfield segments for client-specific data.

Common Use Cases and Queries

PER_ASSIGNMENTS_F is used for secure headcount, supervisor, and assignment-detail reporting. A frequent pattern retrieves current primary assignments for the running user's secured business groups:

• SELECT papf.full_name, pa.assignment_number, pa.primary_flag, pa.supervisor_id FROM per_assignments_f pa, per_all_people_f papf WHERE pa.person_id = papf.person_id AND pa.primary_flag = 'Y' AND SYSDATE BETWEEN pa.effective_start_date AND pa.effective_end_date AND SYSDATE BETWEEN papf.effective_start_date AND papf.effective_end_date;
• Joining to PER_JOBS_F, PER_POSITIONS, or HR_ALL_ORGANIZATION_UNITS for descriptive job, position, and organization detail.
• Feeding interfaces and extracts that must honor HRMS security, where PER_ALL_ASSIGNMENTS_F would expose unauthorized rows.

Because the view enforces security and date-effectiveness, queries should always include effective-date predicates and be executed under a responsibility whose security profile covers the intended population.