Results for “per_assignments_v12”

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

Overview

PER_ASSIGNMENTS_V12 is an APPS-owned database view in the Oracle E-Business Suite Human Resources (PER) product. It is classified in the E-Business Suite Technical Reference Manual (ETRM) as an "as of sysdate" view, meaning it resolves assignment records effective as of the current system date rather than requiring the caller to supply an effective date. The view is valid in both Oracle EBS 12.1.1 and 12.2.2 and is defined over PER_ASSIGNMENTS_F, the date-tracked (datetracked) base view for employee assignments.

The view exposes the principal attributes of an assignment, including organizational placement, job, position, grade, supervisor, payroll, assignment status, working hours, probation and review parameters, and a comprehensive set of descriptive flexfield (DFF) columns (ASS_ATTRIBUTE1 through ASS_ATTRIBUTE30 and ASS_ATTRIBUTE_CATEGORY). Because it filters to the "as of today" effective row, it is widely used in reports, concurrent programs, Fast Formulas, and integration extracts that need the currently active assignment record without applying datetrack logic explicitly.

Underlying Base Objects

According to documented ETRM metadata for 12.2.2, the view is defined over the following objects:

• PER_ASSIGNMENTS_F (VIEW) — the datetracked assignments entity; the primary source of the view's column list.
• HR_SECURITY (PACKAGE) — supplies the security predicates that restrict rows according to the security profile of the querying user, enforcing organization and supervisor-based access.
• HR_GENERAL (PACKAGE) — provides general HR utility logic referenced in the view definition.
• FND_SESSIONS (SYNONYM) — the applications session table, used to obtain session context such as the effective date.

The view therefore inherits both the datetrack semantics of PER_ASSIGNMENTS_F and the row-level security enforced by HR_SECURITY, and it materializes a single "current" row per assignment qualifying under the session date.

Key Columns

Among the columns the view exposes, several are of particular importance for reporting and integration:

• ASSIGNMENT_ID, ASSIGNMENT_NUMBER, ASSIGNMENT_SEQUENCE — identity and ordering of the assignment.
• PERSON_ID — the person to whom the assignment belongs.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — the datetrack boundaries of the returned record.
• BUSINESS_GROUP_ID, ORGANIZATION_ID, PEOPLE_GROUP_ID — enterprise and organizational context.
• JOB_ID, POSITION_ID, GRADE_ID, SUPERVISOR_ID, LOCATION_ID, PAYROLL_ID — placement and pay references.
• ASSIGNMENT_STATUS_TYPE_ID, PRIMARY_FLAG, ASSIGNMENT_TYPE, MANAGER_FLAG — status and role indicators.
• HOURLY_SALARIED_CODE — indicates whether the assignment is treated as hourly or salaried, which is the term the user searched on.
• NORMAL_HOURS, FREQUENCY, PAY_BASIS_ID — working-time and pay-basis attributes.
• DATE_PROBATION_END, PROBATION_PERIOD, PROBATION_UNIT, PERF_REVIEW_PERIOD, SAL_REVIEW_PERIOD — review and probation timing.
• ASS_ATTRIBUTE_CATEGORY and ASS_ATTRIBUTE1–30 — the assignment DFF structure.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER — standard audit and concurrency columns.

Common Use Cases and Queries

The view is most often used when a report or interface must evaluate an assignment as of the current date. A typical query listing active hourly and salaried assignments is:

• Filter by PRIMARY_FLAG = 'Y' to isolate the primary assignment.
• Filter by ASSIGNMENT_STATUS_TYPE_ID or by HOURLY_SALARIED_CODE to classify the workforce.
• Join to PER_PEOPLE_F, PER_JOBS, PER_POSITIONS, and HR_ALL_ORGANIZATION_UNITS to enrich the result.

A representative statement is: SELECT pa.assignment_id, pa.assignment_number, pa.person_id, pa.hourly_salaried_code, pa.normal_hours FROM apps.per_assignments_v12 pa WHERE pa.primary_flag = 'Y' AND pa.hourly_salaried_code = 'H';. Because HR_SECURITY is applied within the view definition, results are automatically scoped to the querying user's security profile, which makes the view suitable for both self-service reporting and controlled integration extracts.