Search Results ghr_mass_salaries




Overview
Explore in AI Chat

Overview

The GHR_MASS_SALARIES table is a core data object within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as the central repository for defining, managing, and tracking mass salary actions. These actions are critical administrative processes for applying standardized salary adjustments, such as general increases or locality pay updates, across a large population of federal employees. The table stores the master definition of each mass salary action, including its selection criteria, processing parameters, and overall execution status, thereby orchestrating a complex, batch-oriented HR operation.

Key Information Stored

The table's primary purpose is to define the header-level attributes of a mass salary action. Its key columns, as indicated by its constraints, include the unique identifier MASS_SALARY_ID (primary key) and the NAME of the action (a unique key). Crucially, it establishes relationships to other foundational entities via foreign keys: PA_REQUEST_ID links to the GHR_PA_REQUESTS table, associating the salary action with a formal personnel action request. ORGANIZATION_ID references HR_ALL_ORGANIZATION_UNITS to scope the action to a specific organizational unit, while PERSONNEL_OFFICE_ID links to GHR_POIS to designate the responsible personnel office. Additional columns, implied by its function, would store status flags (e.g., 'DRAFT', 'SUBMITTED', 'PROCESSED'), effective dates, and control parameters for the batch process.

Common Use Cases and Queries

The primary use case is the creation and monitoring of mass salary adjustments. An HR administrator defines a new action in the GHR application interface, which creates a record in this table. Subsequent processes use this record to identify which employee population to update based on linked criteria. Common reporting and audit queries involve joining this table to its related criteria and request tables. For example, to list all pending mass salary actions with their associated personnel office, one might use a query such as: SELECT gms.NAME, gms.MASS_SALARY_ID, gpo.OFFICE_NAME FROM HR.GHR_MASS_SALARIES gms, HR.GHR_POIS gpo WHERE gms.PERSONNEL_OFFICE_ID = gpo.PERSONNEL_OFFICE_ID AND gms.STATUS = 'PENDING';. Another critical query pattern retrieves all details for a specific action for validation before submission or for troubleshooting a processed run.

Related Objects

GHR_MASS_SALARIES sits at the center of a small data model. It has a direct one-to-many relationship with the GHR_MASS_SALARY_CRITERIA table, which stores the detailed selection rules (e.g., pay plan, grade, step) for the action. As documented, it is a child table to three key reference entities: GHR_PA_REQUESTS (for the governing personnel action), HR_ALL_ORGANIZATION_UNITS (for organizational scope), and GHR_POIS (Personnel Office). In application logic, it is heavily referenced by the concurrent programs and PL/SQL APIs that perform the actual mass salary calculation and update processes within the GHR module.