Search Results hr_sp_placement_api




Overview
Explore in AI Chat

Overview

The APPS.HR_SP_PLACEMENT_API package is a public, server-side PL/SQL API that belongs to the Oracle Human Resources (HR) module of Oracle E-Business Suite. Its name reflects its function: it manages Spinal Point Placements (SPP), the records that capture an employee's position on a salary or progression spine — a graded pay structure widely used in public sector, education, healthcare, and other unionized or regulated environments where pay advancement is tied to defined spinal points rather than free-form grades.

The package encapsulates the business rules, validation logic, and data manipulation required to create, amend, and remove spinal point placement records on behalf of an assignment. By isolating this logic within a supported API, Oracle allows both its own internal components and customer extensions to manipulate spinal point placements in a consistent, validated manner rather than writing directly against the underlying table. In ETRM 12.2.2 the package is documented with an API classification of API and carries a VALID status in the APPS schema, confirming it is a supported entry point.

Key Procedures and Functions

The ETRM metadata documents five callable entities in total, of which three public procedures are named:

  • CREATE_SPP — Inserts a new spinal point placement record. This procedure applies the placement of an assignment onto a specific spinal point, typically with an effective date that establishes the point on the employee's progression timeline.
  • UPDATE_SPP — Modifies an existing spinal point placement. It is used when an employee moves to a different spinal point, for example following an annual increment, a re-grading, or a correction to an earlier entry.
  • DELETE_SPP — Removes a spinal point placement record, supporting reversal or cleanup of placements entered in error or superseded by later restructuring.

Because only the procedure names are exposed in the documented metadata, the exact parameter signatures are not reproduced here; implementers should reference the package specification in the database for precise argument lists. The remaining two documented entities are consistent with these three core operations.

Tables Accessed

The package operates against a single documented base table accessed via its APPS synonym:

  • PER_SPINAL_POINT_PLACEMENTS_F — the date-tracked (datetracked) table that stores spinal point placement rows for assignments. The _F suffix indicates this is the "future" or current-version table in Oracle HR's datetrack model, with corresponding history maintained in the _T (history) sibling. CREATE_SPP, UPDATE_SPP, and DELETE_SPP read and write this table, while the datetrack framework manages effective dating and audit history.

The package also depends on the shared APPS.HR_API utility package and the SYS.STANDARD package, which supply common date-track helpers, validation routines, and exception handling used across the HR API family.

Usage Notes

HR_SP_PLACEMENT_API is a low-level building block rather than an end-user-visible component. It is typically invoked indirectly: the ETRM dependency data shows it is referenced by nine other packages, including HR_ASSIGNMENT, HR_ASSIGNMENT_INTERNAL, HR_PROCESS_ASSIGNMENT_STEP_SS, HRSPINE, PER_CAGR_APPLY_RESULTS_PKG, PER_SPP_INS, PQH_FR_ASSIGNMENT_API, PQH_FR_SPEED, and PQH_GSP_POST_PROCESS. These callers drive spinal point placement from assignment maintenance, collective agreement (CAGR) processing, grade/step progression (GSP), and French public-sector (PQH_FR) payroll flows.

From a customization perspective, developers extending spinal point behavior should call CREATE_SPP, UPDATE_SPP, and DELETE_SPP rather than issuing DML against PER_SPINAL_POINT_PLACEMENTS_F directly, ensuring datetrack integrity and downstream assignment processing remain intact. Direct table access bypasses the validations and the datetrack and business-group security enforced by this API.