Results for “per_assignments_v7”

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

Overview

PER_ASSIGNMENTS_V7 is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered under the PER (Human Resources) product module. Its documented purpose in the ETRM metadata is simply "Used to support user interface," which places it in the family of internal UI-support views that Oracle forms and self-service pages rely on rather than a view intended for direct customer reporting. The view is listed with a status of VALID in ETRM 12.2.2 and is also present in the 12.1.1 code line.

Functionally, PER_ASSIGNMENTS_V7 exposes assignment-level data — the link between a person and the organization, job, position, and payroll to which they are assigned — enriched with denormalized descriptive names. It sits above the core assignment table PER_ASSIGNMENTS_F and joins in related descriptive entities such as jobs, locations, organizations, and people, so that a form or page can render meaningful labels without issuing multiple lookups. Because it is a view, it inherits the row-level dating and the DateTrack effective-date semantics of the underlying PER_ASSIGNMENTS_F table.

Underlying Base Objects

The documented base objects reveal the structure of the view. The driving object is PER_ASSIGNMENTS_F, the dated assignment entity. PER_PEOPLE_F supplies person context, and the PL/SQL package HR_PERSON_NAME is used to resolve person names. The view joins PER_JOBS_TL (via JBT) for the translated job name, HR_ORGANIZATION_UNITS (HOU) for the organization name, and HR_LOCATIONS_ALL_TL (LOC) for location data. GL_SETS_OF_BOOKS (GSB) supplies the set-of-books name, while HR_COMMENTS provides the comment reference and FND_DESCR_FLEX_CONTEXTS_TL supports the descriptive flexfield attribute context (ASS_ATTRIBUTE_CATEGORY and ASS_ATTRIBUTE1 through ASS_ATTRIBUTE30).

Several base objects are packages and helper routines rather than tables: HR_GENERAL supplies DECODE_POSITION_LATEST_NAME, used to resolve the latest position name; HR_SECURITY applies the security profile so that only permitted rows are visible; and HR_LOCATIONS_NO_JOIN and HR_ORGANIZATION_UNITS act as supporting views. Supervisor and person names are resolved through references such as SUP.FULL_NAME.

Key Columns

• ASSIGNMENT_ID — primary key of the assignment row; the join key to many downstream tables.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — DateTrack dating columns that define the validity window of the row.
• PERSON_ID, ASSIGNMENT_NUMBER, ASSIGNMENT_SEQUENCE, PRIMARY_FLAG — identify the person and distinguish primary from secondary assignments.
• ORGANIZATION_ID (HOU.NAME), JOB_ID (JBT.NAME), POSITION_ID, GRADE_ID, LOCATION_ID — the core assignment attributes, with organization and job names resolved.
• SUPERVISOR_ID (SUP.FULL_NAME), MANAGER_FLAG — supervisory relationship information.
• PAYROLL_ID, SET_OF_BOOKS_ID (GSB.NAME), PAY_BASIS_ID, FREQUENCY, NORMAL_HOURS — payroll and compensation basics.
• ASS_ATTRIBUTE_CATEGORY, ASS_ATTRIBUTE1–30 — the descriptive flexfield context and attribute values.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard audit columns inherited from PER_ASSIGNMENTS_F.

Common Use Cases and Queries

Although the view exists to support the user interface, it is frequently referenced in ad-hoc reporting because it conveniently supplies resolved names. A typical query retrieves current assignments for active employees in a business group:

• SELECT assignment_id, person_id, assignment_number, assignment_status_type_id, organization_id, job_id, position_id, supervisor_id, primary_flag FROM apps.per_assignments_v7 WHERE effective_end_date = hr_api.g_effective_end_date_of_time AND primary_flag = 'Y';
• Join to PER_PEOPLE_V7 or PER_PERSON_NAMES_F for person name, or filter by supervisor_id to list direct reports.
• Use the descriptive flexfield columns (ass_attribute_category and ass_attribute1–30) to extract assignment-level DFF reporting.

Because it is an internal UI view, consumers should treat its column list as subject to change across patches and are advised to confirm availability before hard-coding it into custom code.