Results for “default_from”

50+ results




Overview
Explore in AI Chat

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

Overview

PER_MM_POSITIONS is a Human Resources (PER) application table in Oracle E-Business Suite, owned by the HR schema. It serves as an intermediate or staging table that holds positions defined as part of a mass move operation. Mass moves are bulk reorganizations executed through the Mass Move functionality, in which many employees, positions, or assignments are transferred simultaneously from one organizational configuration to another. PER_MM_POSITIONS captures, for each mass move, the set of source positions affected and the target position configuration that the move is intended to produce.

From a data-warehouse or Data Vault modeling perspective, the FK structure indicates a link classification. The primary key is composite, comprising MASS_MOVE_ID and POSITION_ID, and the table resolves many-to-many style associations between mass move headers (PER_MASS_MOVES), source positions (PER_ALL_POSITIONS via POSITION_ID), and target positions or position definitions. This is consistent with a link entity that records relationships rather than descriptive attributes about a single business key.

Key Information Stored

The table contains 45 documented columns against a physical schema in HR. The most significant columns are:

  • MASS_MOVE_ID — Foreign key to PER_MASS_MOVES and part of the composite primary key identifying the mass move to which the row belongs.
  • POSITION_ID — Foreign key to PER_ALL_POSITIONS and the second component of the primary key, identifying the source position being evaluated by the mass move.
  • NEW_POSITION_ID — Foreign key to PER_ALL_POSITIONS identifying the target position created or assigned as a result of the mass move.
  • NEW_POSITION_DEFINITION_ID — Foreign key to PER_POSITION_DEFINITIONS, pointing to the definition used for the new position.
  • TARGET_JOB_ID — Foreign key to PER_JOBS, identifying the job to be associated with the moved position.
  • DEFAULT_FROM — Effective date from which the mass move defaults should apply.
  • DEACTIVATE_OLD_POSITION — Flag indicating whether the source position should be deactivated after the move.
  • SELECT_POSITION — Flag indicating whether the position was selected for processing in the mass move.
  • POSITION_MOVED — Flag indicating whether the position has actually been moved.
  • SEGMENT1 through SEGMENT30 — Key flexfield segments capturing the position definition attributes for the mass move.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the ORM layer.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — Standard WHo-column audit attributes.

The unique index PER_MM_POSITIONS_PK (MASS_MOVE_ID, POSITION_ID) is the documented business-key candidate and surrogate primary key.

Common Use Cases and Queries

Typical usage includes auditing which positions were involved in a mass move, verifying whether specific positions were successfully moved, and extracting the target configuration for downstream reporting.

A representative query joining to the mass move header:

  • SELECT pmm.MASS_MOVE_ID, pmm.POSITION_ID, pmm.NEW_POSITION_ID, pmm.TARGET_JOB_ID, pmm.POSITION_MOVED FROM PER_MM_POSITIONS pmm WHERE pmm.MASS_MOVE_ID = :mass_move_id;

Another pattern joins source and target positions to their descriptive rows in PER_ALL_POSITIONS, allowing reconciliation between the pre-move and post-move org structure. Reporting extracts frequently filter on POSITION_MOVED = 'Y' to measure mass-move completion, or on DEACTIVATE_OLD_POSITION to audit which legacy positions were retired.

Related Objects

  • PER_ALL_POSITIONS — Referenced twice: via POSITION_ID (source position) and NEW_POSITION_ID (target position).
  • PER_MASS_MOVES — Parent table referenced by MASS_MOVE_ID; holds the mass move header.
  • PER_POSITION_DEFINITIONS — Referenced by NEW_POSITION_DEFINITION_ID; source of new position definitions.
  • PER_JOBS — Referenced by TARGET_JOB_ID; supplies the job for the moved position.

These relationships make PER_MM_POSITIONS a central link between mass move processing, position definitions, jobs, and the position hierarchy itself.