Search Results per_mm_assignments




Overview
Explore in AI Chat

Overview

The PER_MM_ASSIGNMENTS table is a core transactional object within the Oracle E-Business Suite Human Resources (PER) module. It serves as a staging and tracking repository for employee assignment records created or modified during a mass move operation. A mass move is a bulk data processing function used to transfer multiple employees between organizations, positions, or other assignment attributes simultaneously. This table's primary role is to maintain a precise, auditable record of all assignment-level changes defined as part of a mass move transaction before and after its submission, ensuring data integrity and supporting the reversal or review of such bulk operations.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships. Each row uniquely identifies a single assignment affected by a specific mass move event. The two-column primary key consists of MASS_MOVE_ID, which links to the parent transaction in the PER_MASS_MOVES table, and ASSIGNMENT_ID, which identifies the specific employee assignment from the PER_ALL_ASSIGNMENTS_F table (implied by the assignment context). Critical foreign key columns include POSITION_ID, linking to PER_ALL_POSITIONS, and GRADE_ID, linking to PER_GRADES, which store the target position and grade for the assignment as defined by the mass move. The table typically holds the proposed or confirmed new values for key assignment attributes as part of the bulk change.

Common Use Cases and Queries

The primary use case is auditing and reporting on historical mass move activities. Administrators may query this table to determine which assignments were altered in a specific mass move, often for compliance or troubleshooting. A common reporting pattern involves joining to PER_MASS_MOVES to get move details and to assignment/employee tables to see employee context. For example:

  • Identifying all assignments impacted by a completed mass move: SELECT paa.assignment_number, pef.full_name FROM per_mm_assignments pma JOIN per_all_assignments_f paa ON pma.assignment_id = paa.assignment_id JOIN per_all_people_f pef ON paa.person_id = pef.person_id WHERE pma.mass_move_id = :p_move_id;
  • Validating the target position and grade for assignments within a pending move before final submission.
  • Supporting data correction by providing a clear trail of bulk changes made to assignment records.

Related Objects

PER_MM_ASSIGNMENTS is centrally connected to several key HRMS tables via documented foreign key constraints, as per the provided metadata:

  • PER_MASS_MOVES: The parent table. The column PER_MM_ASSIGNMENTS.MASS_MOVE_ID references PER_MASS_MOVES, defining the mass move transaction that groups these assignment changes.
  • PER_ALL_POSITIONS: The column PER_MM_ASSIGNMENTS.POSITION_ID references PER_ALL_POSITIONS.POSITION_ID, storing the position designated for the assignment by the mass move.
  • PER_GRADES: The column PER_MM_ASSIGNMENTS.GRADE_ID references PER_GRADES.GRADE_ID, storing the grade designated for the assignment by the mass move.

Furthermore, while not listed in the provided foreign keys, the ASSIGNMENT_ID column inherently relates to the core PER_ALL_ASSIGNMENTS_F table, and the mass move process interfaces with standard HRMS APIs and forms for managing assignments.