Search Results per_spinal_point_steps_s




Overview
Explore in AI Chat

Overview

APPS.PER_SPINAL_POINT_STEPS_PKG is a PL/SQL package body within the Oracle E-Business Suite human resources schema. It provides the data-access and validation layer for spinal point steps, the incremental pay progression points that sit beneath spinal points on a grade scale. Spinal points form the backbone of public-sector and graded pay structures in Oracle HRMS, and each spinal point may be subdivided into numbered steps representing incremental progression. The package encapsulates the inserts, updates, deletions, and uniqueness checks required to maintain these step definitions consistently across localization and legislative configuration screens.

In Oracle EBS 12.1.1 and 12.2.2, the package is owned by APPS, holds VALID status, and is classified as an OTHER API rather than a public business API. It depends on APP_EXCEPTION, FND_MESSAGE, HR_GRADE_SCALE_API, and HR_UTILITY, confirming that it participates in the standard HR error-handling and grade-scale validation framework. Its declared dependencies include PER_ALL_ASSIGNMENTS_F, PER_SPINAL_POINTS, PER_SPINAL_POINT_PLACEMENTS_F, PER_SPINAL_POINT_STEPS, PER_SPINAL_POINT_STEPS_F, and — most importantly for the searched term — PER_SPINAL_POINT_STEPS_S, the sequence and surrogate-key source for the step entity.

Key Procedures and Functions

The documented package exposes eight procedures and functions:

  • INSERT_ROW — Creates a new spinal point step record, populating the base table and its translation/date-tracked companions.
  • LOCK_ROW — Acquires a row-level lock on an existing step record to enforce optimistic concurrency control during multi-user editing.
  • UPDATE_ROW — Applies modifications to an existing step definition, maintaining date-tracked history.
  • DELETE_ROW — Removes a step record, subject to the deletion checks below.
  • DEL_CHKS_DEL — Performs the soft-delete pre-checks, verifying that no dependent data (such as placements) prevents removal.
  • DEL_CHKS_ZAP — Performs the hard-delete (ZAP) pre-checks, the more restrictive variant used when purging data entirely.
  • CHK_UNQ_STEP_POINT — Validates that a step number is unique within its parent spinal point, preventing duplicate progression points.
  • POP_FLDS — Populates the derived and display fields of the step record, typically invoked after a query or a DML operation.

The naming convention (DML_ROW, DEL_CHKS, CHK_UNQ, POP_FLDS) follows the standard Oracle Forms server-side API pattern, indicating the package was generated to support a maintenance form.

Tables Accessed

The package reads and writes PER_SPINAL_POINT_STEPS_S, the base table keyed by the sequence identifier, together with its date-tracked and translated counterparts PER_SPINAL_POINT_STEPS_F and PER_SPINAL_POINT_STEPS. It validates the parent entity via PER_SPINAL_POINTS and checks for dependent assignments or placements through PER_SPINAL_POINT_PLACEMENTS_F and PER_ALL_ASSIGNMENTS_F, which is essential before permitting a delete. It also references HR_GRADE_SCALE_API for grade-scale consistency and HR_UTILITY for common date and lookup helpers.

Usage Notes

PER_SPINAL_POINT_STEPS_PKG is not a public API and is referenced by three other database objects. It is normally invoked indirectly through the Spinal Point Steps maintenance form or through grade-scale configuration concurrent processes rather than by custom code. Developers integrating spinal point data should prefer the supported HR_GRADE_SCALE_API where possible, reserving direct calls to this package for forms-based maintenance or controlled data migration, and should always respect the lock-before-update sequence to avoid concurrency conflicts.