Search Results first_step_api

Overview

PER_GRADE_SPINES_PKG is an Oracle EBS Application Object Library package owned by the APPS schema and classified as an "OTHER" API. It encapsulates the business logic that governs Grade Spines within Oracle Human Resources and Oracle Payroll. A grade spine represents the structural ladder that maps grades to spinal points and spinal steps, forming the foundation of seniority-based and progression-based pay models used extensively in public sector and unionized environments. The package provides both the base table maintenance operations (insert, update, delete, lock) and the progression logic needed to open, advance, and close a grade spine as an employee moves through spinal points. It is a low-level utility package rather than a public, end-user-facing API, and Oracle documents it with a VALID status in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes twelve documented procedures and functions, which fall into three functional groups.

• INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW — Core DML procedures that maintain rows in the grade spine tables. They perform the standard insert, pessimistic lock, update, and delete operations expected of an EBS table-handler package, and are typically called from the Grade Spine maintenance form or from loader code.
• STB_DEL_VALIDATION and CHK_UNQ_GRADE_SPINE — Validation routines. STB_DEL_VALIDATION enforces referential integrity before a spine row is deleted, preventing orphaned spinal point or step records. CHK_UNQ_GRADE_SPINE checks that a grade spine definition is unique, blocking duplicate spine definitions for the same grade and effective dates.
• FIRST_STEP and FIRST_STEP_API — Progression entry points that determine the initial spinal step for an assignment or spine. The _API variant is the callable, supported wrapper used by external code.
• CHK_LOW_CEILING — Validation that guards the lower ceiling of the spine, ensuring a placement does not fall below the spine's defined minimum.
• GET_GSPINE_END, CLOSE_GSPINE, OPEN_GSPINE — Lifecycle procedures. GET_GSPINE_END returns the end point of a spine range; OPEN_GSPINE and CLOSE_GSPINE set the effective lifespan of a spine record, allowing historical spines to be retired cleanly while preserving audit history.

Tables Accessed

The package reads and writes the following tables via APPS synonyms: PER_GRADE_SPINES_F and PER_GRADE_SPINES_S (the date-tracked and translated base tables holding spine definitions); PER_PARENT_SPINES (the parent-child hierarchy of spines); PER_SPINAL_POINTS and PER_SPINAL_POINT_PLACEMENTS_F (the discrete pay points and their placements); PER_SPINAL_POINT_STEPS_F and PER_SPINAL_POINT_STEPS_S (the steps within each spinal point); and PER_ALL_ASSIGNMENTS_F, which links employee assignments to a spine so that progression logic can be evaluated for a specific person. These tables together supply all data required for open, advance, and close operations.

Usage Notes

PER_GRADE_SPINES_PKG is invoked indirectly rather than directly by end users. It is referenced by PQH_GSP_UTILITY, the Grade Spine utility package in the Public Sector/HR progression stack, which calls it from concurrent programs, the Grade Spine form, and progression batch processes. Because the package is owned by APPS and marked VALID, it is safe for custom code to call the documented procedures, but the _API variants should be preferred over the raw DML procedures. Direct table DML should be avoided; all inserts, updates, and deletes on grade spine data should be routed through this package to preserve validation, uniqueness, and effective-date integrity. Customizations should treat the procedure signatures as fixed and rely on the package only through its published entry points.