Search Results ghr_mass_salary_criteria_s




Overview

The HR.GHR_MASS_SALARY_CRITERIA table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the U.S. Federal Human Resources (GHR) module. Its primary function is to store granular eligibility criteria for mass salary actions. A mass salary action is a batch process used to apply salary increases or adjustments to a defined group of employees. This table allows a single mass salary action, defined in the parent GHR_MASS_SALARIES table, to be subdivided by specific personnel attributes, enabling targeted increases for different employee subgroups within the same batch operation.

Key Information Stored

The table's structure is designed to link criteria to a parent action and define the specific increase rules. The key columns include:

  • MASS_SALARY_CRITERIA_ID: The primary key, uniquely identifying each criteria record. It is populated from the sequence GHR_MASS_SALARY_CRITERIA_S.
  • MASS_SALARY_ID: The foreign key linking the criteria to its parent mass salary action in the GHR_MASS_SALARIES table. This is the column referenced by the user's search term "mass_salary_id".
  • PAY_PLAN and PAY_RATE_DETERMINANT: These columns define the eligibility criteria, typically representing federal personnel attributes like GS, SES, or EJ pay plans and their associated rate determinants.
  • INCREASE_PERCENT: This critical column stores the specific percentage increase to be applied to employees who match the defined PAY_PLAN and PAY_RATE_DETERMINANT criteria.
  • Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): These audit columns track the creation and modification history of each record.

Common Use Cases and Queries

This table is central to executing and auditing targeted federal pay adjustments. A common scenario is implementing an annual pay raise where different increase percentages are mandated for distinct pay plan groups. Administrators would create one mass salary action, then populate multiple rows in this table to specify, for example, a 4.1% increase for GS employees and a 3.5% increase for EJ employees. For reporting and validation, common SQL queries include retrieving all criteria for a specific action or identifying the applicable increase for a given pay plan.

-- Retrieve all criteria for a specific mass salary action
SELECT PAY_PLAN, PAY_RATE_DETERMINANT, INCREASE_PERCENT
FROM HR.GHR_MASS_SALARY_CRITERIA
WHERE MASS_SALARY_ID = :p_mass_salary_id
ORDER BY PAY_PLAN;

-- Audit recent mass salary criteria changes
SELECT MSC.*, MS.MASS_SALARY_NAME
FROM HR.GHR_MASS_SALARY_CRITERIA MSC
JOIN HR.GHR_MASS_SALARIES MS ON MSC.MASS_SALARY_ID = MS.MASS_SALARY_ID
WHERE MSC.LAST_UPDATE_DATE > TRUNC(SYSDATE - 7);

Related Objects

The table exists within a tightly defined schema for mass salary processing. Its primary relationships are:

  • GHR_MASS_SALARIES: The parent table, referenced via the foreign key constraint GHR_MASS_SALARY_CRITERIA_FK1 on the MASS_SALARY_ID column. This defines the overarching batch action.
  • GHR_MASS_SALARY_CRITERIA_PK: The primary key index on MASS_SALARY_CRITERIA_ID.
  • GHR_MASS_SALARY_CRITERIA_FK2: A non-unique index on the PAY_PLAN column, likely supporting lookups and validation logic within the application.
  • GHR_MASS_SALARY_CRITERIA_S: The database sequence that populates the primary key values.
The table is stored in the APPS_TS_INTERFACE tablespace, indicating its role in supporting batch data processing workflows within the GHR module.