Search Results rules_steps_update




Overview
Explore in AI Chat

Overview

PER_SPINAL_POINTS_PKG is an Oracle EBS Human Resources (PER) package owned by the APPS schema and classified under the ETRM as an "OTHER" API. Its name derives from "Spinal Points," the internal EBS term for the ordered, sequential points (or steps) that define the progression criteria within a salary grade or grade rule structure. In Oracle HRMS, a "spinal point" represents a discrete position within a grade's progression path, and this package provides the validation, sequencing, and identifier-resolution logic that supports maintenance of those points and their associated steps.

The package is declared AUTHID CURRENT_USER, meaning that it executes with the privileges of the invoking session rather than the definer, so callers must themselves hold the necessary privileges on the underlying tables. The header dates from the original release (pespo01t.pkh, version 115.0), indicating that the package is a long-standing component of the HRMS grade-rule infrastructure rather than a recent addition. The ETRM metadata for 12.2.2 records five documented procedures and confirms that the package is referenced by zero other packages, implying it is invoked directly by forms or custom code rather than serving as a shared dependency for other PL/SQL units.

Key Procedures and Functions

  • CHK_UNQ_POINT — Validates that a spinal point value is unique within the context of a given spinal-points entity, excluding the current row during updates. It enforces the business rule that no two active points within the same progression structure may share the same point designation.
  • CHK_UNQ_SEQ — Performs the analogous uniqueness check for the sequence number assigned to a point. It prevents duplicate ordering values within the same parent spinal-points record, preserving a deterministic progression order.
  • RULES_STEPS_UPDATE — Coordinates updates between a spinal point and its associated steps, propagating changes so that the step definitions remain consistent with the parent point record. This supports the linkage between points and the grade-rule framework.
  • GET_ID — Resolves or generates the primary identifier for a spinal point. It accepts an IN OUT identifier parameter, allowing the caller to supply a value or receive a newly derived one, which is typical of EBS APIs that need to support both insert and update paths.
  • STB_DEL_VALIDATION — The procedure associated with the user's search term "stb_del_validation." It implements deletion validation for spinal-point records: before a point or its parent spinal-points entity is removed, this routine checks for dependent data — such as remaining steps, grade-rule references, or child points — and raises an error if deletion would violate referential integrity. The "STB" prefix follows the naming convention of the underlying spinal-points table family (per_spinal_points / per_spinal_point_steps), and the procedure is the gatekeeper that forms and concurrent processes call prior to issuing a DELETE.

Tables Accessed

  • PER_SPINAL_POINTS — The base table holding spinal-point definitions. Read and validated by CHK_UNQ_POINT and STB_DEL_VALIDATION; written via GET_ID and RULES_STEPS_UPDATE.
  • PER_SPINAL_POINTS_S — The date-tracked (or translated) shadow table for the same entity. Accessed to verify effective-dated or language-specific rows during uniqueness and deletion checks.
  • PER_SPINAL_POINT_STEPS_F — The steps table linked to each spinal point. Referenced by RULES_STEPS_UPDATE and by STB_DEL_VALIDATION to detect dependent step rows that block deletion.
  • PAY_GRADE_RULES_F — The grade-rule definition table. Accessed to determine whether a spinal point is referenced by an active grade rule, which is a primary reason STB_DEL_VALIDATION would reject a deletion request.

All four tables are accessed through APPS synonyms, consistent with the package's APPS ownership and CURRENT_USER authorization model.

Usage Notes

This package is a back-end validation utility rather than a user-facing API. It is typically invoked from Oracle Forms (notably the Spinal Points and Grade Rules maintenance forms in the HRMS grade-rule setup flow) and may be called from concurrent programs or custom PL/SQL that performs bulk maintenance of spinal-point data. Developers writing custom code that inserts, updates, or deletes rows in PER_SPINAL_POINTS or PER_SPINAL_POINT_STEPS_F should call the uniqueness procedures before committing and must call STB_DEL_VALIDATION before any delete, since the package itself does not raise validation errors unless explicitly invoked. Because the package is referenced by no other packages, there is no automatic enforcement of these rules outside the standard forms; custom integrations bear responsibility for invoking the checks directly. Standard practice is to call these routines within the same transaction as the DML, so that validation failures roll back cleanly.