Search Results delete_plan_for_grade




Overview
Explore in AI Chat

Overview

The APPS.PQH_GSP_SYNC_COMPENSATION_OBJ package is a component of the Oracle EBS Grade/Step Progression (GSP) framework used by Oracle Advanced Benefits and the Compensation Workbench. Its principal business function is to keep the benefits compensation model synchronized with changes made to the grade and grade-step (spine) structures defined in Oracle Human Resources. When a planner defines a grade, a grade rule, or a spinal point step and attaches a benefits compensation plan, activity rate, or variable rate to that definition, the corresponding Benefit object definitions — plans, plan types, options, activity base rates, variable rates, and option-in-plan relationships — must be created, updated, or removed so that eligibility and rate processing remain consistent.

This package provides the programmatic plumbing that performs those insert and delete operations. It is effectively a maintenance utility rather than a user-facing API: it is invoked indirectly by the grade and spine business logic whenever structural changes to compensation-related grade data occur. The object is documented in ETRM as VALID in the APPS schema and is classified as an OTHER API, meaning it is not intended as a public integration interface, although it can be called from custom code with care.

Key Procedures and Functions

Six documented procedures constitute the public surface of the package. They divide cleanly into creation and deletion operations:

  • CREATE_OIPL_FOR_STEP — Creates the option-in-plan (OIPL) association rows required when a spinal point step is linked to a compensation plan, ensuring the step is represented as a valid plan option.
  • CREATE_OPTION_FOR_POINT — Creates the Benefit option record corresponding to a spinal point, so that the point can participate in plan enrollment and rate calculation.
  • DELETE_PLAN_FOR_GRADE — Removes the compensation plan association tied to a grade when that grade is no longer compensation-bearing or the plan link is severed.
  • DELETE_STD_RT_FOR_GRADE_RULE — Deletes the standard rate definition associated with a grade rule, typically when the grade rule is modified or removed.
  • DELETE_OPTION_FOR_POINT — Deletes the Benefit option that was previously generated for a spinal point.
  • DELETE_OIPL_FOR_STEP — Deletes the option-in-plan rows created for a spinal point step, reversing the effect of CREATE_OIPL_FOR_STEP.

No parameter lists are documented in the ETRM metadata, and none should be assumed; callers should inspect the package specification in the target instance before invoking these procedures directly.

Tables Accessed

The package reads and writes a defined set of Benefits and HR tables through APPS synonyms. The Benefits tables include BEN_PL_F, BEN_PL_TYP_F, and BEN_PL_TYP_OPT_TYP_F (plan, plan type, and plan type/option type definitions), BEN_OPT_F (options), BEN_OIPL_F (option-in-plan relationships), BEN_PLIP_F (plan-in-program), and the rate tables BEN_ACTY_BASE_RT_F and BEN_ACTY_VRBL_RT_F. From the HR side it touches PAY_GRADE_RULES_F for grade rule definitions and the spine structures PER_PARENT_SPINES, PER_SPINAL_POINTS, and PER_SPINAL_POINT_STEPS_F. These tables supply the grade, point, and step context that the package translates into Benefits compensation objects.

Usage Notes

The package is referenced by six other APPS packages — PAY_PGR_DEL, PER_GRADE_SPINES_PKG, PER_GRD_BUS, PER_PSP_DEL, PER_SPS_DEL, and PER_SPS_INS — which confirms that it is driven by grade/step progression business events rather than by direct user invocation. In normal operation it fires when users save changes to grades, grade rules, or spinal points through the Grade/Step Progression and Compensation Workbench forms, and when concurrent processes such as grade deletion or spine deletion run. It is not exposed as a standalone concurrent program. Customizations should prefer the supported PER and PAY business APIs; if this package must be called directly, it should be invoked in the correct transactional context and only after the underlying grade or spine change has been committed, because the procedures assume the HR-side rows already exist. Because the ETRM record classifies it as OTHER, Oracle support may treat direct calls as unsupported.