Results for “per_assignments_v5”

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

Overview

PER_ASSIGNMENTS_V5 is a user-interface support view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the PER (Human Resources) product family and exposes assignment-level records drawn primarily from PER_ALL_ASSIGNMENTS_F, decorated with decoded lookup meanings, translated names, and supervisor and location attributes. The view is not a transactional object; it is a read-only presentation layer used by HR forms, self-service pages, and downstream reporting or integration extracts that require assignment data in a form already resolved for display.

Its defining characteristic is the systematic pairing of an identifier column with a corresponding meaning or description column. Business keys such as CHANGE_REASON, GRADE_ID, JOB_ID, POSITION_ID, and ORGANIZATION_ID are accompanied by decoded values derived from lookups, translation tables (the _TL objects), and the HR_GENERAL package. This design shifts decoding effort from the calling application into the database, which is why the view is frequently referenced when a user searches for a column such as change_reason_meaning.

Underlying Base Objects

The documented reference list for PER_ASSIGNMENTS_V5 includes PER_ALL_ASSIGNMENTS_F, PER_ASSIGNMENTS_F2, PER_ALL_PEOPLE_F, PER_GRADES and PER_GRADES_TL, PER_JOBS and PER_JOBS_TL, HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL and HR_LOCATIONS_NO_JOIN, PER_ASSIGNMENT_STATUS_TYPES with its _TL and amendment equivalents (PER_ASS_STATUS_TYPE_AMENDS, PER_ASS_STATUS_TYPE_AMENDS_TL), PER_RECRUITMENT_ACTIVITIES, PER_CONTRACTS_F, PER_COLLECTIVE_AGREEMENTS, PER_ALL_VACANCIES, HR_COMMENTS, and BEN_PGM_F.

PER_ALL_ASSIGNMENTS_F is the driving table; PER_ASSIGNMENTS_F2 supplies the secured assignment set, and HR_SECURITY is invoked to apply security profile restrictions. HR_GENERAL supplies the DECODE_LOOKUP and DECODE_POSITION_LATEST_NAME functions that resolve the meaning columns, while FND_SESSIONS provides session context. Translation objects contribute the language-specific descriptive names exposed as D_ prefixed columns. The effective end date of 31-12-4712 is converted to NULL through a DECODE, presenting open-ended assignments as unbounded.

Key Columns

• ASSIGNMENT_ID, ROW_ID, ASSIGNMENT_NUMBER, ASSIGNMENT_SEQUENCE: primary identifier, row locator, and the human-readable assignment reference.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, D_EFFECTIVE_END_DATE: date-tracked validity, with the high date nulled for display.
• PERSON_ID, BUSINESS_GROUP_ID, ORGANIZATION_ID, D_ORGANIZATION_ID: person and organizational context, the latter decoded to a name.
• CHANGE_REASON and CHANGE_REASON_MEANING: the reason code and its decoded meaning, obtained via HR_GENERAL.DECODE_LOOKUP against the APL_ASSIGN_REASON lookup type. This pair is the object of the common change_reason_meaning search.
• STATUS, PER_SYSTEM_STATUS: user status and system status, resolved through NVL across the assignment status type and amendment translation tables.
• SUPERVISOR_ID, SUPERVISOR_NAME, SUPERVISOR_EMPLOYEE_NUMBER: supervisor identification, falling back to the NPW number where no employee number exists.
• GRADE_ID, JOB_ID, POSITION_ID with D_ columns: grade, job, and position identifiers with decoded names.
• FREQUENCY_MEANING and PROBATION_UNIT_MEANING: additional decoded lookup values for payroll frequency and probation units.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include assignment listings for an organization, change-reason analysis for audit and reporting, and integration extracts that must present human-readable values rather than coded identifiers. A representative query retrieving assignments with decoded change reasons is:

• SELECT assignment_id, assignment_number, person_id, change_reason, change_reason_meaning, effective_start_date, effective_end_date
• FROM apps.per_assignments_v5
• WHERE effective_end_date IS NULL OR effective_end_date > SYSDATE
• ORDER BY person_id, effective_start_date;

A second pattern filters by organization and supervisor for managerial reporting, joining PERSON_ID to PER_ALL_PEOPLE_F where the display name of record is required, since the view does not expose the assignment holder's full name directly. Because HR_SECURITY participates in the definition, results are constrained by the security profile of the connected user, which makes the view suitable for self-service and restricted reporting contexts. Direct DML against the view is not supported; assignment maintenance must be performed against the base tables or through the supported HR APIs.