Search Results ghr_wgi_pkg




Overview
Explore in AI Chat

Overview

The concurrent program GHR_WGI_PROCESS is delivered by the Oracle E-Business Suite GHR - US Federal Human Resources product. Its user-facing name is Process Automatic WGI, and it is enabled by default in the documented environment. The program initiates the automatic Within-Grade Increase (WGI) process, which is the mechanism used by US Federal agencies to apply scheduled step increases within a grade under the federal pay system. As the name implies, the program is designed to execute automated WGI processing rather than requiring manual intervention for each eligible employee.

The user search term ghr_wgi_pkg corresponds directly to the executable backing this concurrent program. GHR_WGI_PKG is the PL/SQL package that implements the WGI processing logic and serves as the executable referenced by the concurrent program definition.

Execution Details

The documented execution characteristics for GHR_WGI_PROCESS are as follows:

  • Product: GHR - US Federal Human Resources
  • User Name: Process Automatic WGI
  • Description: Start automatic WGI process
  • Enabled: Yes
  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: GHR_WGI_PKG
  • Execution File: ghr_wgi_pkg.ghr_wgi_process
  • Subroutine Name: (none specified in the documented metadata)

Because the execution method is a PL/SQL Stored Procedure, the program is invoked directly by the concurrent manager through the package procedure identified in the execution file. The Argument Method is Standard, indicating that arguments are submitted using the standard Oracle Application Object Library parameter mechanism. The executable short name (GHR_WGI_PKG) and the execution file reference (ghr_wgi_pkg.ghr_wgi_process) confirm that the entry point resides in a package specification whose procedure ghr_wgi_process performs the automatic WGI evaluation and update.

How to Run

The program is submitted through the standard Submit Requests (SRS) window, typically accessed via the Requests > Run path in the navigator or via the SRS form directly. Users select the program by its user-facing name, Process Automatic WGI, and then provide any required parameters as prompted.

Because the ETRM documentation records the argument method as Standard, the parameter list is defined by the concurrent program's AOL parameter definitions rather than by a custom argument method. In practice, agencies configure WGI processing parameters such as the effective date, the processing range or population, and the criteria for identifying eligible employees. Administrators should verify the active parameter definitions for their specific release and configuration before submission, as the documented metadata excerpt does not enumerate individual parameters.

Given that the process updates personnel actions and related pay information, it is advisable to run it in a controlled manner, verify the resulting output, and confirm that any errors are reviewed through the concurrent request log and output file. The standard concurrent manager diagnostics apply, including log and output inspection for failures.

Related Objects

The following objects are commonly associated with and should be considered alongside GHR_WGI_PROCESS:

  • GHR_WGI_PKG — the PL/SQL package that implements the automatic WGI process and serves as the concurrent program executable.
  • Oracle HRMS / GHR WGI interface tables — staging structures used to collect eligible employees and resulting WGI actions prior to validation and update.
  • HRMS personnel action and assignment APIs — invoked by the process to create or update employee assignments and salary/WGI actions in Oracle HRMS.
  • Payroll-related setup and elements — used downstream when the resulting within-grade increases feed into payroll calculations.
  • Concurrent request log and output — the standard diagnostic artifacts for verifying the results of each run.

The package and its concurrent program definition are part of the GHR federal human resources configuration, and any customization or extension should be validated against the supported Oracle EBS 12.1.1 and 12.2.2 releases.