Search Results per_mass_moves_v




Overview
Explore in AI Chat

Overview

PER_MASS_MOVES_V is a view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the PER (Human Resources) product family and its documented purpose is to support the user interface. The view presents mass employee move (mass transfer/transfer batch) information in a denormalized, display-ready form by joining the underlying mass move records to organization unit descriptions for both the destination and source organizations. Rather than requiring the user interface or a reporting query to resolve organization names through separate lookups, PER_MASS_MOVES_V resolves the numeric organization identifiers into human-readable organization names, which makes it suitable for inquiry screens, concurrent report output, and lightweight integration extracts. Status is documented as VALID, indicating the compiled view is present and usable in the data dictionary.

Underlying Base Objects

The documented referenced base objects for this view are the PER_MASS_MOVES synonym (the base table holding the mass move transactions), the PER_ORGANIZATION_UNITS_V view (referenced twice, once for the new/destination organization and once for the source organization), and the HR_API package. The view text confirms the join logic: PER_MASS_MOVES is aliased MM, PER_ORGANIZATION_UNITS_V is aliased ORG for the destination organization, and PER_ORGANIZATION_UNITS_V is aliased ORG2 for the source organization. The WHERE clause binds MM.NEW_ORGANIZATION_ID to ORG.ORGANIZATION_ID and MM.OLD_ORGANIZATION_ID to ORG2.ORGANIZATION_ID. Because the view is built on PER_ORGANIZATION_UNITS_V rather than the base PER_ORGANIZATION_UNITS table, its name resolution inherits the organization-unit view's date-tracked and business-group-aware behavior. HR_API is referenced in Oracle ETRM as an associated implementation object; mass move processing in PER historically routes through HR_API procedures, so the view sits on top of data that this package maintains.

Key Columns

The physical column list and the aliased presentation columns are documented as follows. Identifying and control columns include ROW_ID (the ROWID of the PER_MASS_MOVES row, used by the UI to locate the record), MASS_MOVE_ID (the primary identifier of the mass move batch), BUSINESS_GROUP_ID (the business group context), EFFECTIVE_DATE (the effective date of the move), and BATCH_RUN_NUMBER (the sequence identifying the batch run). The critical columns for the user's search term are NEW_ORGANIZATION_ID and its resolved name, exposed as NEW_ORGANIZATION, which together describe the destination organization. The source side is exposed as SOURCE_ORGANIZATION_ID and SOURCE_ORGANIZATION, which map to the underlying OLD_ORGANIZATION_ID and its organization name. Additional columns are REASON (the reason recorded for the move) and STATUS (the processing state of the mass move). Note the naming distinction: the select list supplies ORG.NAME and ORG2.NAME, while the documented column list exposes them as NEW_ORGANIZATION and SOURCE_ORGANIZATION.

Common Use Cases and Queries

Typical uses include inquiry of pending and completed mass transfers, validation that a batch targets the intended new organization, and feed extracts for downstream HR or payroll interfaces. A representative query lists moves by destination organization:

  • SELECT mass_move_id, business_group_id, effective_date, new_organization_id, new_organization, source_organization, batch_run_number, reason, status FROM apps.per_mass_moves_v WHERE business_group_id = :p_business_group_id AND status = 'P' ORDER BY effective_date, batch_run_number;

  • Isolating a specific destination: SELECT * FROM apps.per_mass_moves_v WHERE new_organization_id = :p_new_organization_id;

  • Verifying batch scope: SELECT batch_run_number, COUNT(*) FROM apps.per_mass_moves_v WHERE mass_move_id = :p_mass_move_id GROUP BY batch_run_number;

Because the view joins two instances of PER_ORGANIZATION_UNITS_V, ensure the session's effective date and business group context are set appropriately so both the new and source organization names resolve. When performance matters, filter on MASS_MOVE_ID, BUSINESS_GROUP_ID, or the organization identifier columns rather than on the resolved name columns.