Search Results ghr_mass_realignment




Overview

The GHR_MASS_REALIGNMENT table is a core data object within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a repository for defining and storing the criteria necessary to execute mass realignment processes. In the context of federal HR operations, mass realignment is a critical administrative function for reorganizing personnel, positions, and organizational hierarchies in bulk, often in response to legislative changes, agency restructuring, or large-scale workforce management initiatives. This table does not store the realignment transactions themselves but holds the parameterized definition of the realignment to be performed, serving as a configuration and control point for the associated GHR process.

Key Information Stored

The table's primary identifier is the system-generated MASS_REALIGNMENT_ID, which is the primary key. A unique key constraint on the NAME column ensures each realignment criteria set has a distinct identifier. The table's columns primarily store foreign keys that define the scope and target of the realignment. Key reference data includes OLD_ORGANIZATION_ID and NEW_ORGANIZATION_ID to specify the source and destination organizations. It also stores identifiers for the old organizational (OLD_ORG_STRUCTURE_VERSION_ID) and position (OLD_POS_STRUCTURE_VERSION_ID) structure versions to establish the baseline context. The table links to personnel offices (PERSONNEL_OFFICE_ID and TARGET_PERSONNEL_OFFICE_ID) and can be associated with a personnel action request (PA_REQUEST_ID) for workflow integration. The TARGET_POSITION_ORG_ID further defines the destination organization for positions.

Common Use Cases and Queries

The primary use case is the setup and execution of a batch process to move multiple employees, positions, or organizational units from one part of the hierarchy to another. Administrators would populate a record in this table via the GHR application interface, defining the "from" and "to" parameters. A typical reporting query might join this table to organization units to list all configured realignment criteria:

  • SELECT mr.NAME, old_org.NAME AS OLD_ORG, new_org.NAME AS NEW_ORG FROM HR.GHR_MASS_REALIGNMENT mr JOIN HR.HR_ALL_ORGANIZATION_UNITS old_org ON mr.OLD_ORGANIZATION_ID = old_org.ORGANIZATION_ID JOIN HR.HR_ALL_ORGANIZATION_UNITS new_org ON mr.NEW_ORGANIZATION_ID = new_org.ORGANIZATION_ID WHERE mr.PERSONNEL_OFFICE_ID = :p_poi_id;

Another common operational query would validate the existence of referenced objects before process execution by checking for null foreign keys or joined records.

Related Objects

The GHR_MASS_REALIGNMENT table has defined foreign key relationships with several fundamental EBS HR and GHR tables, as documented in the ETRM metadata. These relationships are critical for enforcing data integrity and enabling joins for reporting and process logic:

  • HR_ALL_ORGANIZATION_UNITS: Linked via OLD_ORGANIZATION_ID, NEW_ORGANIZATION_ID, and TARGET_POSITION_ORG_ID to validate and describe the source and destination organizations.
  • PER_ORG_STRUCTURE_VERSIONS: Linked via OLD_ORG_STRUCTURE_VERSION_ID to specify the version of the organization hierarchy being realigned from.
  • PER_POS_STRUCTURE_VERSIONS: Linked via OLD_POS_STRUCTURE_VERSION_ID to specify the version of the position hierarchy being realigned from.
  • GHR_POIS (Personnel Office): Linked via PERSONNEL_OFFICE_ID and TARGET_PERSONNEL_OFFICE_ID to associate the realignment with the responsible and target personnel offices.
  • GHR_PA_REQUESTS: Linked via PA_REQUEST_ID to optionally tie the mass realignment criteria to a specific personnel action request for audit and approval tracking.