Search Results pqh_fr_progression_point_pkg




Overview
Explore in AI Chat

Overview

PQH_FR_PROGRESSION_POINT_PKG is an Oracle EBS Applications (APPS) PL/SQL package belonging to the Public Sector / Human Resources (PQH) product family, with the "FR" component identifying French-specific localization functionality. The package supports the French HR progression-point model, which governs how employees advance through grade steps and how associated salary rates are recalculated when a progression point is applied. In Oracle HRMS, grade rate and progression-point rules determine the pay value an employee receives as they move along a grade's step structure; the French localization adds statutory and collective-agreement-driven logic to that process. This package encapsulates the server-side logic that derives and updates the salary rate tied to a given progression point, keeping the resulting pay value consistent with the grade rules for the assignment's spine and step. The object is registered as VALID in the APPS schema and is classified as an OTHER API. Its dependency footprint is narrow: it depends only on SYS.STANDARD, and it is referenced by the PER_PSP_RKU package (the parent-spine run-time keeper/utility) in addition to internal self-references. This compact dependency profile indicates a focused utility package rather than a broad payroll driver, and it is intended to be called during progression-point evaluation and salary-rate derivation rather than as a standalone entry point.

Key Procedures and Functions

The ETRM documentation records a single documented program unit in this package:

  • UPDATE_SAL_RATE_FOR_POINT — Updates the salary rate associated with a progression point. This routine is the operational core of the package: given the progression context, it determines and applies the correct salary rate so that the employee's grade step and point value reflect the appropriate pay. It is the only documented procedure or function, confirming the package's single-responsibility design. No parameter list is documented, and parameter signatures should not be assumed; callers must consult the deployed package specification directly.

Tables Accessed

The package references two tables through APPS synonyms:

  • PAY_GRADE_RULES_F — The grade rules table. This supplies the rule definitions (effective-dated) that determine how pay elements such as salary rates are computed for a grade and its step or point values. It is read to obtain the applicable grade-rule logic used when deriving the rate for the progression point.
  • PER_PARENT_SPINES — The parent-spine table storing the hierarchical spine and step definitions that make up the grade progression structure. This provides the point/step context against which the salary rate is resolved and updated.

Together, these tables supply the rule and structural inputs required to compute a progression-point salary rate and write the resulting value. This is consistent with the package's dependency on PER_PSP_RKU, which operates on the same parent-spine data.

Usage Notes

PQH_FR_PROGRESSION_POINT_PKG is not an end-user-facing screen; it is invoked indirectly. Because it is referenced by PER_PSP_RKU, it is typically executed as part of the progression/spine processing flow, for example when a progression point is applied to an assignment and the corresponding salary rate must be refreshed. Practically, this occurs through:

  • French-localized HR forms and UI actions that trigger progression-point evaluation;
  • Concurrent programs or batch processes that recalculate payroll-relevant grade and step values in bulk;
  • Custom code or extensions that call the API to update a rate for a specific point, provided the caller supplies the correct context.

Because the package specification is not fully documented, integrators should inspect the deployed specification in the target instance before invoking UPDATE_SAL_RATE_FOR_POINT directly. Behavior can also differ between EBS 12.1.1 and 12.2.2 through the underlying HRMS grade-rules infrastructure, so testing against the specific release and applied patches is advisable.