Results for “per_mm_positions_v”

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

Overview

PER_MM_POSITIONS_V is a view owned by the APPS schema in Oracle E-Business Suite, belonging to the PER (Human Resources) product family. Per the ETRM 12.1.1 / 12.2.2 documentation, its stated purpose is to support the Oracle Forms user interface rather than to serve as a public integration or reporting API. Specifically, it backs the mass movement of positions workflow, exposing the rows staged in PER_MM_POSITIONS together with the descriptive and attribute data the form needs to render each position moving to a new organization, job, or definition. Because it is a UI-support view, its column list and join logic are driven by the requirements of that form, and it should be treated as an internal object: Oracle does not guarantee its shape across patches or upgrades, and it is not listed as a supported interface.

Underlying Base Objects

The documented base objects are FND_PROFILE (package), HR_GENERAL (package), HR_ORGANIZATION_UNITS (view), HR_POSITIONS (view), HR_SECURITY (package), and the synonyms PER_JOBS, PER_JOBS_TL, PER_MASS_MOVES, PER_MM_ASSIGNMENTS, and PER_MM_POSITIONS. The view text confirms these relationships. PER_MM_POSITIONS is the driving table, supplying the staged mass-move rows. It is joined to PER_MASS_MOVES on MASS_MOVE_ID for header context, to HR_POSITIONS on POSITION_ID to retrieve the current position record (restricted to the latest definition via EFFECTIVE_END_DATE), to PER_JOBS and PER_JOBS_TL on JOB_ID for the job name in the user's language, and to HR_ORGANIZATION_UNITS twice — once for the current organization and once, through the mass-move header, for the new organization. PER_MM_ASSIGNMENTS is outer-joined on POSITION_ID and is also referenced for security filtering within the form logic. HR_GENERAL supplies the decode functions that resolve the latest position and position-definition names, and HR_SECURITY enforces organization-level security.

Key Columns

• TARGET_JOB_ID — the job identifier to which the position is being moved; the column most directly associated with the reported search term.
• POSITION_ID / NEW_POSITION_ID — the current position and, where applicable, the replacement position being introduced by the move.
• NEW_POSITION_DEFINITION_ID and DEACTIVATE_OLD_POSITION — the definition applied to the new position and the flag controlling whether the source position is end-dated.
• MASS_MOVE_ID — foreign key to PER_MASS_MOVES, identifying the mass-move batch the row belongs to.
• JOB_ID, JOB_DEFINITION_ID, NAME — the job and its translated name for the target job.
• ORGANIZATION_ID, current and new organization names — the from/to organization context of the move.
• SEGMENT1 through SEGMENT30 — the position key flexfield segments, expanded so the form can display and validate the position key.
• DEFAULT_FROM, SELECT_POSITION, POSITION_MOVED — form-state flags indicating defaulting behavior, row selection, and completion status.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the form.
• ROWID — included for row identification and updateable-view behavior.

Common Use Cases and Queries

Typical usage is diagnostic: confirming which target job a mass position move will apply, verifying batch membership, or extracting staged rows for reconciliation. The following query lists mass-move position rows with their target job and organization context:

SELECT mass_move_id,
       position_id,
       new_position_id,
       target_job_id,
       name,
       organization_id
FROM   apps.per_mm_positions_v
WHERE  target_job_id = :p_job_id;

To inspect a single batch, filter on MASS_MOVE_ID; to find rows where the source position is end-dated, filter on DEACTIVATE_OLD_POSITION = 'Y'. Because the view is defined with outer joins and grouped columns, it may not be updateable in all contexts, and any DML should be performed against PER_MM_POSITIONS through the supported concurrent program or form. For interface work, prefer the base tables PER_MM_POSITIONS and PER_MASS_MOVES over this view.