Results for “mass_realignment_id”

20 results




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

Overview

GHR_MASS_REALIGNMENT is a transactional table owned by the HR schema and delivered as part of the GHR - US Federal Human Resources product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the selection criteria and target attributes that define a mass realignment event, a Federal HR process used to reassign groups of employees from an existing organizational or positional structure to a new one. Each row captures one realignment definition, including the source organization, the destination organization, the affected position structures, and the personnel office context under which the action is executed.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is a link. The table is dominated by foreign key references to conformed dimensions such as HR_ALL_ORGANIZATION_UNITS, PER_ORG_STRUCTURE_VERSIONS, PER_POS_STRUCTURE_VERSIONS, and GHR_POIS, and it resolves the many-to-many relationships among those entities for a given realignment event. This classification is a modeling suggestion rather than a documented Oracle construct.

Key Information Stored

The table contains 38 documented columns. The most significant are:

Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Typical usage includes tracking the progress of realignment actions, validating source-to-target organization mappings before execution, and reporting on historical realignment activity for audit or Congressional reporting. A common query pattern joins the table to organization and personnel-office dimensions:

  • Listing active realignments with their effective dates by status.
  • Joining to HR_ALL_ORGANIZATION_UNITS on both OLD_ORGANIZATION_ID and NEW_ORGANIZATION_ID to render source and target organization names.
  • Joining to GHR_PA_REQUESTS via PA_REQUEST_ID to correlate the realignment to the underlying personnel action request.
  • Aggregating realignments by BUSINESS_GROUP_ID or PERSONNEL_OFFICE_ID for workload reporting.

A basic pattern is:

SELECT name, effective_date, status FROM hr.ghr_mass_realignment WHERE business_group_id = :bg AND status = 'ACTIVE';

Related Objects

The following objects are the most significant dependencies based on documented foreign keys:

  • HR_ALL_ORGANIZATION_UNITS – referenced three times (OLD_ORGANIZATION_ID, NEW_ORGANIZATION_ID, TARGET_POSITION_ORG_ID).
  • GHR_POIS – referenced twice (PERSONNEL_OFFICE_ID, TARGET_PERSONNEL_OFFICE_ID).
  • PER_ORG_STRUCTURE_VERSIONS – referenced via OLD_ORG_STRUCTURE_VERSION_ID.
  • PER_POS_STRUCTURE_VERSIONS – referenced via OLD_POS_STRUCTURE_VERSION_ID.
  • GHR_PA_REQUESTS – referenced via PA_REQUEST_ID.

These relationships make GHR_MASS_REALIGNMENT a central link between organization structures, personnel office setups, and personnel action requests within the Federal HR data model.