Results for “perf_review_period_frequency”

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

Overview

PER_ASSIGNMENTS_F2 is a secure database view owned by the APPS schema in Oracle E-Business Suite, belonging to the PER (Human Resources) product family. It exposes assignment information — the relationship between a person and the organization, job, position, and payroll to which they are assigned for a given period of time. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, the object is a VIEW with a status of VALID, and its stated description is a "Secure view based on the corresponding _ALL_ table."

The "_F2" suffix denotes that the view implements row-level security filtering, in contrast to the base table (PER_ALL_ASSIGNMENTS_F) which stores data for all business groups. In Oracle HRMS, security is enforced through the HR_SECURITY package, and this view applies the current user's security profile against the business group, organization, and person records. It is therefore the recommended access point for reports, concurrent programs, and integrations that must respect HR security, rather than querying the underlying _ALL table directly.

Underlying Base Objects

The documented ETRM metadata identifies three referenced base objects:

• PER_ALL_ASSIGNMENTS_F (SYNONYM) — the primary datastore. This is the "_ALL" table holding assignments across all business groups. PER_ASSIGNMENTS_F2 selects from it and is filtered by the security logic applied to the synonym.
• HR_SECURITY (PACKAGE) — supplies the row-level security predicates that restrict visible assignments to those the current user is authorized to see.
• HR_GENERAL (PACKAGE) — provides supporting HR utility functions used in conjunction with security and assignment processing.

Conceptually, the view projects the full set of columns from PER_ALL_ASSIGNMENTS_F but applies a WHERE clause generated from HR_SECURITY, effectively returning only assignments within the user's authorized business groups and organizations.

Key Columns

The view text exposes a wide column set. Among the most significant for reporting and integration are:

• ASSIGNMENT_ID — unique primary key of the assignment; the primary join key to PER_ALL_ASSIGNMENTS_F and dependent tables.
• PERSON_ID — the person to whom the assignment belongs.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity range of the assignment record; these, with ASSIGNMENT_ID, form the effective-dated primary key.
• BUSINESS_GROUP_ID, ORGANIZATION_ID, LOCATION_ID — the organizational context used for security filtering and reporting.
• JOB_ID, POSITION_ID, GRADE_ID, PAYROLL_ID, PEOPLE_GROUP_ID — the core assignment attributes defining role and compensation structure.
• ASSIGNMENT_TYPE, ASSIGNMENT_NUMBER, PRIMARY_FLAG, SUPERVISOR_ID, NORMAL_HOURS, FREQUENCY — descriptive and operational attributes of the assignment.
• ASS_ATTRIBUTE1..30 and ATTRIBUTE_CATEGORY — the descriptive flexfield (DFF) segments configured at implementation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — standard WHO columns and optimistic locking used by the API layer.

Common Use Cases and Queries

Because it enforces HR security, PER_ASSIGNMENTS_F2 is the correct view for user-facing reports, BI Publisher data models, and interfaces. Typical uses include listing current active assignments for a person, producing headcount or assignment-by-organization extracts, and feeding downstream modules (Payroll, OTL, Projects) with secured assignment data.

A representative query returning active assignments for the current business group is:

SELECT pa.assignment_id, pa.person_id, pa.assignment_number,
       pa.effective_start_date, pa.effective_end_date,
       pa.job_id, pa.position_id, pa.organization_id, pa.primary_flag
FROM   apps.per_assignments_f2 pa
WHERE  TRUNC(SYSDATE) BETWEEN pa.effective_start_date AND pa.effective_end_date
AND    pa.primary_flag = 'Y';

When reporting across all business groups regardless of the caller's security profile — for example in a system administrator diagnostic or a data migration — the base table PER_ALL_ASSIGNMENTS_F must be used instead, since PER_ASSIGNMENTS_F2 will silently omit rows the user is not authorized to view. Understanding this distinction is essential when troubleshooting reports that appear to be missing assignment records.