Search Results per_spp_shd




Overview
Explore in AI Chat

Overview

PER_SPP_SHD is a package body in the APPS schema that implements the seed data handler (SHD) logic for Spinal Point Placements in Oracle E-Business Suite Human Resources. Spinal point placements represent the association between an employee assignment and a defined spinal point on a pay scale or grade structure. The _SHD suffix denotes that this package supports seed data handling used by Oracle's data migration and installation utilities, particularly the Data Loader / Data Installer framework (DT_API) and HR datapump mechanisms. It coordinates the loading, updating, and validation of spinal point placement records, ensuring that effective-dated rows conform to business rules before they are committed to the base tables.

The package is classified under the OTHER API category in ETRM 12.2.2. It is a valid, compiled object in both 12.1.1 and 12.2.2 and is not referenced by any other database object, indicating that it acts as a terminal entry point invoked directly by the seed data infrastructure or by administrators running migration processes.

Key Procedures and Functions

The documented package exposes eight procedures and functions. Their purposes are as follows:

  • RETURN_API_DML_STATUS — Returns the DML status flag maintained by the package, indicating whether prior insert, update, or delete operations completed successfully. This is used by the calling seed data framework to determine the outcome of the last API call.
  • CONSTRAINT_ERROR — Handles constraint violations raised during processing, translating low-level Oracle errors into meaningful application-level messages for the seed data framework.
  • API_UPDATING — Signals or tracks that the package is currently performing an update operation, allowing callers to distinguish update activity from other DML modes.
  • FIND_DT_UPD_MODES — Determines the applicable datetrack (DT) update modes for the operation, identifying how effective-dated changes should be applied to spinal point placements.
  • FIND_DT_DEL_MODES — Determines the applicable datetrack delete modes, governing how effective-dated rows are terminated or removed.
  • UPD_EFFECTIVE_END_DATE — Updates the effective end date of an existing spinal point placement row, supporting date-tracked corrections and terminations.
  • LCK — Acquires the necessary row locks on spinal point placement records to prevent concurrent modification during seed data loading.
  • CONVERT_ARGS — Converts incoming argument values into the data types and formats expected by the underlying HR API calls, bridging the seed data loader's generic argument structure to the specific API signature.

Tables Accessed

The package references three base tables through APPS synonyms:

  • PER_SPINAL_POINT_PLACEMENTS_F — The primary effective-dated table holding spinal point placement records. The package inserts, updates, and terminates rows here.
  • PER_ALL_ASSIGNMENTS_F — The assignment table, consulted to validate that the assignment associated with a spinal point placement exists and is effective for the relevant date range.
  • ALL_CONSTRAINTS — The data dictionary view used to identify and validate constraint definitions during error handling and mode determination.

In addition, the package depends on DT_API, FND_MESSAGE, HR_API, HR_PUMP_UTILS, and HR_UTILITY, which supply the datetrack, messaging, and datapump services it relies upon.

Usage Notes

PER_SPP_SHD is not intended for direct invocation by end users. It is typically called by the Oracle seed data and data migration framework, including datapump-based loads that import spinal point placement records into a target environment. Developers writing custom data conversion routines for spinal point placements may invoke this package through DT_API rather than calling its procedures directly, since the framework manages argument conversion, DML status tracking, and error translation. Because the package holds row locks and manipulates effective dates, it should be executed during controlled maintenance windows and never concurrently with online updates to the same records. The package is not referenced by any other database object, so it functions strictly as an entry point for external seed data processes.