Search Results per_mm_positions




Overview
Explore in AI Chat

Overview

The PER_MM_POSITIONS table is a transactional data store within the Oracle E-Business Suite Human Resources (PER) module. Its primary function is to serve as a staging and tracking table for positions created or modified during a mass move operation. A mass move is a bulk organizational restructuring process, such as transferring a group of employees and their associated positions from one business group or department to another. This table does not hold the master definition of positions; instead, it records the relationship between the original positions and the newly created or target positions generated by the mass move process. Its role is critical for maintaining data integrity and auditability during complex HR reorganizations in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to link a mass move transaction to the specific positions involved. Its primary key is a composite of MASS_MOVE_ID and POSITION_ID, ensuring a unique record for each position processed within a given mass move. Key columns, as indicated by the foreign key relationships, include MASS_MOVE_ID, which links to the parent transaction in PER_MASS_MOVES; POSITION_ID, which references the original position in PER_ALL_POSITIONS; and NEW_POSITION_ID, which references the newly created position in PER_ALL_POSITIONS after the move. Other significant foreign keys are NEW_POSITION_DEFINITION_ID (linking to PER_POSITION_DEFINITIONS) and TARGET_JOB_ID (linking to PER_JOBS), which define the target characteristics for the position as part of the reorganization.

Common Use Cases and Queries

The primary use case is auditing and reporting on mass move activities. Administrators can query this table to generate a list of all positions affected by a specific reorganization event or to verify the outcome of a mass move. A typical query would join PER_MM_POSITIONS with PER_MASS_MOVES for transaction details and PER_ALL_POSITIONS (twice) to get both the original and new position names or codes. For example:

  • Identifying all new positions created by a mass move: SELECT mm_pos.mass_move_id, orig_pos.name orig_position, new_pos.name new_position FROM per_mm_positions mm_pos, per_all_positions orig_pos, per_all_positions new_pos WHERE mm_pos.position_id = orig_pos.position_id AND mm_pos.new_position_id = new_pos.position_id AND mm_pos.mass_move_id = :p_mass_move_id;
  • Troubleshooting errors in a mass move process by examining the staged position data before final submission.
  • Validating that the target job and position definition were correctly applied during the move operation.

Related Objects

PER_MM_POSITIONS is centrally connected to several core HRMS tables. Its existence is dependent on the parent transaction table, PER_MASS_MOVES. The most critical relationships are with the position master tables: it references the source position in PER_ALL_POSITIONS via POSITION_ID and the resultant position in the same table via NEW_POSITION_ID. It also links to PER_POSITION_DEFINITIONS for the target position's template and to PER_JOBS for the target job assignment. This network of foreign keys ensures that all data referenced in the mass move staging area is valid and consistent with the application's master data, enforcing critical business rules during organizational changes.