Search Results per_sps_bus




Overview
Explore in AI Chat

Overview

APPS.PER_SPS_BUS is a business-layer PL/SQL package within the Oracle E-Business Suite Human Resources (PER) schema. Its name follows the standard Oracle naming convention in which the suffix _BUS denotes a business rules package, positioned above the corresponding table-handling (_TBL) and row-handling (_API) layers in the Oracle Forms server-side architecture. The acronym "SPS" refers to the Spinal Point System, the grade-and-step progression model used to define pay structures for positions and assignments. Grading and spinal-point progression are commonly associated with public-sector, health-service and education implementations, particularly those following UK-style pay frameworks.

PER_SPS_BUS encapsulates the validation logic applied to spinal point step definitions before they are persisted to, or removed from, the underlying base tables. It centralises legislative and security-group context resolution, enabling the same validation rules to be reused across multiple entry points rather than being duplicated in every form or concurrent program. The package is marked VALID in the documented environment and is classified as OTHER in the ETRM API classification, meaning it is an internal support package rather than a published, date-tracked public API with formal backward-compatibility guarantees.

Key Procedures and Functions

The ETRM metadata documents six callable units within the package:

  • SET_SECURITY_GROUP_ID — Establishes the security group context for the current session or transaction so that subsequent validations operate against the correct business group and its associated data partitions.
  • RETURN_LEGISLATION_CODE — Returns the legislation code applicable to the current operating context. This value drives legislation-specific branching in the validation logic and ensures only rules valid for the installation's legislative regime are applied.
  • INSERT_VALIDATE — Performs business-rule validation for a new spinal point step record prior to insertion. It is the gatekeeper invoked before a record is committed to the base tables.
  • UPDATE_VALIDATE — Validates modifications to an existing spinal point step record, ensuring that updates do not violate referential, legislative or progression-consistency rules.
  • DELETE_VALIDATE — Determines whether an existing spinal point step record may be removed, taking into account dependencies such as existing placements or assignments.
  • CHK_DELETE — A supporting check routine used in conjunction with delete processing to confirm that no blocking references remain before a deletion is permitted.

No parameter lists are documented in the available metadata, and none should be assumed; the signatures are internal and subject to change between patch levels.

Tables Accessed

The package references the following base tables through APPS synonyms:

  • PER_SPINAL_POINT_STEPS_F — The primary spinal point step definition table; the central subject of the insert, update and delete validation logic.
  • PER_SPINAL_POINTS — Holds the spinal point catalog used to resolve and cross-validate point definitions.
  • PER_GRADE_SPINES_F — Associates grade structures with spinal configurations, supporting grade-level consistency checks.
  • PER_SPINAL_POINT_PLACEMENTS_F — Records placements of employees onto spinal points, and is the principal dependency consulted by delete validation.
  • HR_ALL_POSITIONS_F — The positions definition table, consulted where validation must account for position-level usage.
  • PER_ALL_ASSIGNMENTS_F — The assignments table, consulted to determine whether an employee assignment depends on the step being validated.

In addition, the package references SYS.STANDARD for PL/SQL built-in constructs and PER_SPS_SHD, a shadow/audit table maintained for the spinal point structure.

Usage Notes

PER_SPS_BUS is not an end-user entry point. It is invoked internally by the four generated DML wrapper packages that reference it — PER_SPS_INS, PER_SPS_UPD, PER_SPS_DEL and PER_SPS_BUS itself — which are in turn called by Oracle Forms and by the row-handling layer when spinal point step data is maintained. Customisations that must preserve table integrity should route writes through the same insert, update and delete entry points rather than bypassing them with direct DML, because the validation rules enforced by this package are not otherwise replicated at the database level. Because the package is classified as OTHER rather than a public API, its internal interfaces, including the parameter signatures of the six documented units, should be treated as unstable across patches and upgrades. Consultants extending spinal point functionality are advised to call the sanctioned wrapper packages and to confine custom logic to their own packages, avoiding direct dependency on PER_SPS_BUS internals.