Results for “old_organization_id”

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

Overview

PER_MASS_MOVES is the HR schema table that stores the high-level definition of a mass move — a batch-driven reorganization in which a defined population of employees is transferred from one organization to another. Each row represents a single mass move header: the source and target organizations, the effective date on which the move takes effect, the processing status, and the batch identifier under which the move was executed. Individual employee-level and position-level details are not held here; they are held in the subordinate PER_MM_* detail tables that reference this header.

The object sits at the head of the mass move model and functions as the controlling record for the Oracle HRMS Mass Move process. No assignment, position, grade, or job requirement change can be processed without a parent row in PER_MASS_MOVES, making it the mandatory entry point for the feature.

From a Data Vault modeling perspective, the heuristic classification of this object is hub-leaning. The classification is derived from the foreign key topology: PER_MASS_MOVES is referenced by four downstream tables through the MASS_MOVE_ID column, but it references only a single parent, HR_ALL_ORGANIZATION_UNITS via BUSINESS_GROUP_ID. The MASS_MOVE_ID therefore behaves as a durable business key around which dependent detail records cluster, and PER_MASS_MOVES may be treated as a hub in a dimensional or vault-style model, with the descriptive attributes (status, reason, effective date, organizations) carried on a satellite.

Key Information Stored

The table is documented with 13 columns. The most significant are:

• MASS_MOVE_ID — the surrogate primary key, defined by the unique index PER_MASS_MOVES_PK. This is the value returned when users search on "mass_move_id" and is the join key to every dependent detail table.
• BUSINESS_GROUP_ID — the foreign key to HR_ALL_ORGANIZATION_UNITS, identifying the business group that owns the mass move and providing the multi-tenant partitioning of HR data.
• EFFECTIVE_DATE — the date on which the move takes effect and from which the resulting assignment and position records are dated.
• OLD_ORGANIZATION_ID — the source organization from which the affected assignments are moved.
• NEW_ORGANIZATION_ID — the destination organization to which the affected assignments are moved.
• STATUS — the processing state of the mass move, distinguishing records that are still being prepared from those that have been applied.
• REASON — the free-text or coded justification for the reorganization, retained for audit and reporting.
• BATCH_RUN_NUMBER — the batch identifier under which the mass move was submitted, allowing multiple runs to be traced and reconciled.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard Oracle Applications WHO columns, recording creation and last modification audit information.

The documented unique index, PER_MASS_MOVES_PK on MASS_MOVE_ID, is the only business-key candidate identified; no alternate unique key on the organizational or batch columns is documented.

Common Use Cases and Queries

The most frequent access pattern is retrieval of a specific mass move by its primary key, often followed by resolution of the detail lines. A representative query joins the header to the assignment-level detail:

• SELECT m.mass_move_id, m.effective_date, m.old_organization_id, m.new_organization_id, m.status, m.batch_run_number FROM per_mass_moves m WHERE m.mass_move_id = :mass_move_id;
• SELECT a.* FROM per_mm_assignments a WHERE a.mass_move_id = :mass_move_id;
• SELECT m.mass_move_id, m.batch_run_number, m.status FROM per_mass_moves m WHERE m.business_group_id = :p_business_group_id ORDER BY m.effective_date DESC;

Reporting use cases include auditing reorganizations by effective date, reconciling the volume of moves processed per BATCH_RUN_NUMBER, and identifying mass moves whose STATUS indicates incomplete processing. The table also supports impact analysis: joining OLD_ORGANIZATION_ID and NEW_ORGANIZATION_ID back to HR_ALL_ORGANIZATION_UNITS allows reporting of which departments gained or lost headcount during a given period.

Related Objects

PER_MASS_MOVES participates in one inbound parent relationship and four outbound child relationships:

• HR_ALL_ORGANIZATION_UNITS — parent of PER_MASS_MOVES through BUSINESS_GROUP_ID, defining the owning business group.
• PER_MM_ASSIGNMENTS — detail table of assignment-level moves, joined on MASS_MOVE_ID.
• PER_MM_JOB_REQUIREMENTS — detail table of job requirement changes for the move, joined on MASS_MOVE_ID.
• PER_MM_POSITIONS — detail table of position-level moves, joined on MASS_MOVE_ID.
• PER_MM_VALID_GRADES — detail table of valid grade definitions associated with the move, joined on MASS_MOVE_ID.

Together with its four PER_MM_* children, PER_MASS_MOVES forms the complete mass move entity group. Any query or extraction of mass move data should treat the header and these detail tables as a single logical unit, keyed by MASS_MOVE_ID.