Search Results mass_move_id




Overview
Explore in AI Chat

Overview

The HR.PER_MASS_MOVES table is a core data structure within the Oracle E-Business Suite Human Resources (HRMS) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master definition table for a "mass move" operation, a critical business process used to transfer multiple employees, positions, or jobs from one organization to another in a single, controlled transaction. This table holds the high-level metadata for each mass move request, defining the source and target organizations, the effective date of the change, and the overall status of the process. Its primary role is to act as a parent record, providing a unique identifier (MASS_MOVE_ID) that links to detailed assignment, position, and job requirement data stored in related child tables, thereby ensuring data integrity and auditability during large-scale organizational restructuring.

Key Information Stored

The table's columns capture the essential parameters and lifecycle of a mass move. The primary key, MASS_MOVE_ID, uniquely identifies each mass move request. The BUSINESS_GROUP_ID ties the operation to a specific business group for security and data partitioning. The OLD_ORGANIZATION_ID and NEW_ORGANIZATION_ID are foreign keys to HR_ALL_ORGANIZATION_UNITS, defining the source and destination of the move. The EFFECTIVE_DATE is crucial, dictating when the organizational changes become active in the system. The STATUS column tracks the progression of the mass move through system-assigned states such as 'Unprocessed', 'Complete', 'Complete with Warnings', or 'In-Error'. Additional columns like REASON provide a user-defined purpose, BATCH_RUN_NUMBER facilitates batch processing identification, and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide full auditability.

Common Use Cases and Queries

This table is central to administrative reporting and troubleshooting of mass organizational changes. Common operational queries include reviewing all pending moves, auditing completed actions, or diagnosing failed processes. A typical reporting query would join PER_MASS_MOVES with HR_ALL_ORGANIZATION_UNITS to display organization names instead of IDs.

  • Find all mass moves for a specific business group with a status of 'In-Error':
    SELECT mass_move_id, reason, effective_date, status FROM hr.per_mass_moves WHERE business_group_id = &bg_id AND status = 'In-Error';
  • List recent mass moves with source and target organization details:
    SELECT pmm.mass_move_id, pmm.effective_date, src_org.name OLD_ORG, tgt_org.name NEW_ORG, pmm.status FROM hr.per_mass_moves pmm, hr_all_organization_units src_org, hr_all_organization_units tgt_org WHERE pmm.old_organization_id = src_org.organization_id AND pmm.new_organization_id = tgt_org.organization_id AND pmm.creation_date > SYSDATE - 30 ORDER BY pmm.creation_date DESC;

Related Objects

PER_MASS_MOVES has a defined relationship with several key child tables, forming the backbone of the mass move functionality. The primary key MASS_MOVE_ID is referenced as a foreign key in tables that store the detailed components of the move: PER_MM_ASSIGNMENTS (for employee assignments), PER_MM_POSITIONS (for positions), PER_MM_JOB_REQUIREMENTS, and PER_MM_VALID_GRADES. This ensures all detailed changes are linked to a single master definition. Furthermore, the table has a foreign key constraint on BUSINESS_GROUP_ID referencing HR_ALL_ORGANIZATION_UNITS, enforcing valid business group data. Administrators and developers should reference these related tables to obtain a complete picture of any mass move transaction.