Results for “per_mm_assignments_v”

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

Overview

PER_MM_ASSIGNMENTS_V is an APPS-owned database view in the Oracle E-Business Suite Human Resources (PER) product, classified with a status of VALID in the ETRM repository. Its documented purpose is to support the user interface, specifically the mass move of assignments functionality within Oracle HRMS. The view consolidates assignment records that have been staged or processed through a mass move operation, enriching the raw mass-move rows in PER_MM_ASSIGNMENTS with descriptive attributes drawn from person, assignment, location, grade, status, person type, and tax unit sources.

Because the view is exposed as a single denormalized result set, it is convenient for reporting and integration scenarios where a developer or analyst needs to present mass-move candidate assignments together with their human-readable context. The view is defined in the APPS schema and inherits the standard Oracle EBS multi-org and language-handling conventions, including use of USERENV('LANG') to localize translated columns.

Underlying Base Objects

The view is defined over a substantial set of referenced objects. Documented base objects for the 12.2.2 ETRM entry include HR_GENERAL (PACKAGE), HR_LOCATIONS_ALL_TL (SYNONYM), HR_LOCATIONS_NO_JOIN (VIEW), HR_PERSON_NAME (PACKAGE), HR_PERSON_TYPE_USAGE_INFO (PACKAGE), HR_SECURITY (PACKAGE), HR_TAX_UNITS_V (VIEW), PER_ASSIGNMENTS_F (VIEW), PER_ASSIGNMENT_STATUS_TYPES (SYNONYM), PER_ASSIGNMENT_STATUS_TYPES_TL (SYNONYM), PER_GRADES_TL (SYNONYM), PER_MASS_MOVES (SYNONYM), PER_MM_ASSIGNMENTS (SYNONYM), PER_MM_POSITIONS (SYNONYM), PER_PEOPLE_F (VIEW), PER_PERSON_TYPES (SYNONYM), and PER_PERSON_TYPES_TL (SYNONYM).

Functionally, PER_MM_ASSIGNMENTS is the driving table, providing the ROWID and primary mass-move columns. It is joined to PER_ASSIGNMENTS_F and PER_PEOPLE_F by ASSIGNMENT_ID and PERSON_ID respectively, and to PER_MASS_MOVES by MASS_MOVE_ID. Position information is resolved through PER_MM_POSITIONS, which must share the same MASS_MOVE_ID as the parent mass move. Location, grade, assignment status type, and person type descriptions are resolved through their respective translation tables using outer joins and language checks, ensuring that a row is returned even when optional descriptive attributes are missing. The tax unit description is resolved through HR_TAX_UNITS_V.

Key Columns

• ROW_ID — the ROWID of the underlying PER_MM_ASSIGNMENTS row, used for row identification in the UI.
• ASSIGNMENT_ID — the assignment identifier linking to PER_ASSIGNMENTS_F and PER_PEOPLE_F.
• ASSIGNMENT_MOVED — flag indicating whether the assignment has already been moved by the mass move process.
• DEFAULT_FROM — the default effective start date applied to the mass move.
• MASS_MOVE_ID — the parent mass move record in PER_MASS_MOVES.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/forms layer.
• POSITION_ID — the position associated with the staged assignment.
• SELECT_ASSIGNMENT — selection indicator used by the UI to control which assignments are included.
• FULL_NAME — person full name, derived via HR_PERSON_NAME.
• LOCATION_CODE — location code from HR_LOCATIONS_ALL_TL.
• GRADE_ID / GDT.NAME — grade identifier and translated grade name.
• USER_STATUS — the user-facing assignment status from PER_ASSIGNMENT_STATUS_TYPES_TL.
• USER_PERSON_TYPE — resolved at runtime by HR_PERSON_TYPE_USAGE_INFO.GET_USER_PERSON_TYPE.
• TAX_UNIT_ID / TAX_UNIT_NAME (TAX.NAME) — the tax unit identifier and its name from HR_TAX_UNITS_V. This is the element returned for the searched term "tax_unit_name".
• ASSIGNMENT_TYPE — the assignment type from PER_ASSIGNMENTS_F.

Common Use Cases and Queries

The view is typically queried when reviewing or extracting mass move assignment data, particularly where tax unit and location context are required. A representative query retrieving tax unit names alongside assignment details follows.

• Reporting mass move candidates with person, assignment, grade, status, location, and tax unit context.
• Reconciling assignments selected for a mass move against PER_ASSIGNMENTS_F before the move is applied.
• Extracting tax unit assignment data for payroll or legislative reporting where the tax unit name is the primary attribute of interest.
• Feeding downstream integrations that require a flattened assignment snapshot.

Sample SQL:

SELECT assignment_id, full_name, location_code, name AS grade_name, user_status, tax_unit_id, name AS tax_unit_name
FROM apps.per_mm_assignments_v
WHERE mass_move_id = :p_mass_move_id;

Because the view applies HR_SECURITY and language-dependent logic, queries should be run with a valid FND session context so that USERENV('LANG') resolves correctly and security predicates behave as intended.