Search Results remove_grade_from_grdldr

Overview

The APPS.PQH_GSP_UTILITY package is a shared utility package within the Oracle EBS Public Sector / Human Resources compensation framework. The GSP prefix denotes Grade Step Progression, a feature that governs how employees advance through grades and steps in an approved grade ladder or spinal point structure. This package provides the underlying business logic required to evaluate grade and step eligibility, validate configuration data, calculate rates and salaries, and move data between the HR and Benefits staging areas during a Grade Step Progression run.

In Oracle EBS 12.1.1 and 12.2.2, the package holds a VALID status in the APPS schema and is classified as an OTHER type API. It is not an end-user facing interface; rather, it is an internal workhorse invoked by the broader GSP processing architecture. Its central role is to centralize the validation, lookup, and calculation routines that multiple GSP components depend on, ensuring consistent behavior across progression processing.

Key Procedures and Functions

ETRM documents 85 procedures and functions. Representative entries illustrate the scope:

• GSP_PLAN_TYPE_EXISTS / GET_PGM_TYP / GET_GSP_PLNTYP_STR_DATE — determine whether a plan type exists, return the program type, and derive the plan type start date used to control eligibility windows.
• CHK_GRADE_EXIST_IN_GL / CHK_PROFILE_EXISTS / CHK_GRD_DETAILS — validation checks verifying that a grade exists in the grade ladder, that a profile is defined, and that grade detail configuration is complete before processing proceeds.
• REMOVE_GRADE_FROM_GRDLDR / REMOVE_STEP_FROM_GRADE / ENDDATE_GRADE_LADDER — maintain the grade ladder and step structures, removing or end-dating entries as configuration changes.
• USE_POINT_OR_STEP / GET_STEP_DTLS / GET_STEP_PRG_RULE_HGRID_NAME — resolve whether progression uses spinal points or steps and retrieve step detail and progression rule grid metadata.
• GET_STANDARD_RATE / GET_CUR_SAL / GET_CAGR_NAME — retrieve the applicable standard rate, the current salary, and the collective agreement name used in rate determination.
• DELETE_TRANSACTION / DEL_GL_DETAILS_FROM_STAGE — remove transaction and staging records during cleanup or rollback of a progression run.
• GET_STATUS / DISPLAY_ICON / ENABLE_DISABLE_START_ICON — support the progression UI by returning processing status and controlling icon display and enablement.

Tables Accessed

The package reads and writes through APPS synonyms covering HR and Benefits entities:

• PER_GRADES, PER_PARENT_SPINES, PER_SPINAL_POINTS — grade, spine, and spinal point definitions used for ladder and step validation.
• PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F — employee assignment and person records supplying the current salary and eligibility context.
• PER_COLLECTIVE_AGREEMENTS — collective agreement data used in rate and progression rule resolution.
• BEN_PGM_F, BEN_PL_F, BEN_PLIP_F, BEN_PL_TYP_F, BEN_OIPL_F, BEN_OPT_F, BEN_PGM_EXTRA_INFO — Benefits program, plan, option, and extra information tables used to synchronize compensation objects.
• BEN_COPY_ENTITY_RESULTS, PQH_COPY_ENTITY_TXNS — copy/results and transaction staging tables supporting data movement between HR and Benefits.
• FND_CURRENCIES_VL — currency validation for monetary amounts.

Usage Notes

PQH_GSP_UTILITY is referenced by at least 15 dependent packages, including PQH_GSP_RATES, PQH_GSP_STAGE_TO_BEN, PQH_GSP_STAGE_TO_HR, PQH_GSP_POST_PROCESS, PQH_GSP_HR_TO_STAGE, PQH_GSP_SYNC_COMPENSATION_OBJ, PQH_GSP_GRD_STEP_REMOVE, PQH_GSP_PROCESS_LOG, PQH_EMPLOYEE_SALARY, and PER_CAGR_UTILITY_PKG. It is also referenced by the PQH_GSP_ELECTABLE_CHOICE_V view.

Because of this dependency density, the package is invoked indirectly during Grade Step Progression concurrent program runs, GSP setup forms, and any custom extension that manipulates grade ladders or step progression. Direct calls should be avoided in customizations; developers extending GSP functionality should invoke the documented wrapper packages instead, so that validation and staging behavior remains consistent with delivered processing.