Search Results new_organization

Overview

APPS.PER_MASS_MOVES_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2). It exposes data related to mass movement of employees between organizations, that is, the batch process used to reassign one or more assignments from a source organization to a new organization. The view is classified by Oracle as a "supplementary view used to simplify forms coding," and Oracle explicitly warns that it is not intended for direct querying or data alteration, as its definition and column set may change dramatically in subsequent minor or major releases. Its FND design data name is PER.PER_MASS_MOVES_V, and its status is VALID in the ETRM metadata.

The qualifying concept for this view is the "new organization" — the destination organization to which personnel records are moved. The view makes both the numeric organization identifier and the resolved organization name available, so reports and forms can display human-readable values without additional lookups.

Underlying Base Objects

The documented dependency list identifies the following referenced objects:

• HR_API (PACKAGE) — supplies the API logic, such as name resolution or validation surrounding the mass move process.
• PER_MASS_MOVES (SYNONYM) — points to the base table holding the mass move transaction records.
• PER_ORGANIZATION_UNITS_V (VIEW) — the organization unit view used to resolve organization identifiers to descriptive names.

PER_MASS_MOVES_V is not referenced by any other database object, so it is a terminal, presentation-layer view. Because it joins the base mass move table with organization unit data, it provides denormalized, display-ready records rather than raw transactional rows.

Key Columns

• ROW_ID (ROWID) — unique row identifier for the view record.
• MASS_MOVE_ID (NUMBER) — primary identifier of the mass move transaction.
• BUSINESS_GROUP_ID (NUMBER) — business group (enterprise) context for the record.
• EFFECTIVE_DATE (DATE) — date on which the mass move takes effect.
• NEW_ORGANIZATION_ID (NUMBER) — identifier of the destination (new) organization.
• NEW_ORGANIZATION (VARCHAR2 240) — resolved name of the destination organization, the value most directly tied to the "new_organization" search.
• SOURCE_ORGANIZATION_ID (NUMBER) and SOURCE_ORGANIZATION (VARCHAR2 240) — identifier and name of the origin organization.
• BATCH_RUN_NUMBER (NUMBER) — batch grouping for the mass move run.
• REASON (VARCHAR2 240) — business reason recorded for the move.
• STATUS (VARCHAR2 60) — current processing state of the mass move.

Common Use Cases and Queries

Typical uses include auditing organization reassignments, reporting pending versus completed mass moves, and validating that a batch moved personnel into the intended new organization. Because the view is read-only in intent, queries should be restricted to reporting. A basic retrieval is:

SELECT MASS_MOVE_ID, EFFECTIVE_DATE, SOURCE_ORGANIZATION, NEW_ORGANIZATION, BATCH_RUN_NUMBER, REASON, STATUS FROM APPS.PER_MASS_MOVES_V;

To isolate moves into a specific destination organization:

SELECT MASS_MOVE_ID, NEW_ORGANIZATION_ID, NEW_ORGANIZATION, EFFECTIVE_DATE, STATUS FROM APPS.PER_MASS_MOVES_V WHERE NEW_ORGANIZATION_ID = :p_org_id AND BUSINESS_GROUP_ID = :p_bg_id;

Aggregate reporting by destination organization and status is also common:

SELECT NEW_ORGANIZATION, STATUS, COUNT(*) FROM APPS.PER_MASS_MOVES_V GROUP BY NEW_ORGANIZATION, STATUS;

Consumers should treat column names and semantics as version-sensitive and rely on supported APIs, such as HR_API, rather than writing directly against this view.