Search Results per_sbt_bus




Overview
Explore in AI Chat

Overview

PER_SBT_SHD is a shadow (or "SHD") row-handling package in the Oracle E-Business Suite Human Resources (PER) schema module, owned by the APPS schema. In Oracle HRMS, a shadow package is a generated companion to a base table-handling package that manages the interface between a base table and its associated "_SHD" shadow table, which is used by the DateTrack architecture to preserve row history across effective-date changes. The shadow table mirrors the columns of its base table and stores dated row versions so that past, present, and future records remain queryable.

The primary business object associated with PER_SBT_SHD is the "Subjects Taken" entity — the record of a person's educational or qualification-related subject enrollment, stored in the PER_SUBJECTS_TAKEN base table and the PER_SUBJECTS_TAKEN_TL translated table. The package maintains the shadow-table representation of these records so that HRMS forms and DateTrack-aware APIs can insert, update, and delete subject records while preserving full temporal history. As indicated by the metadata, PER_SBT_SHD is referenced by several sibling packages — PER_SBT_BUS, PER_SBT_DEL, PER_SBT_INS, PER_SBT_UPD — which are the business, delete, insert, and update entry points that delegate shadow-table maintenance to this package. The API classification recorded in ETRM is OTHER, reflecting that this is a low-level, supporting utility package rather than a directly callable business API.

Key Procedures and Functions

The ETRM metadata documents five procedures or functions within PER_SBT_SHD. Their described purposes are as follows:

  • CONSTRAINT_ERROR — Handles constraint violation conditions raised during shadow-table manipulation, providing error-handling behavior for the package.
  • API_UPDATING — Signals or manages the API-updating state, used to coordinate shadow-row updates when the base record is modified through the API layer.
  • LCK — Provides row-locking support, ensuring shadow rows are locked appropriately during concurrent DateTrack operations.
  • ADD_LANGUAGE — Supports insertion of translated (TL) rows in the appropriate language, aligning shadow data with the multilingual translation architecture.
  • CONVERT_ARGS — Converts or normalizes argument values passed into the package, typically to harmonize data types or DateTrack parameters.

The listing of these five routines is exhaustive per the documented metadata; no additional procedures or functions are recorded.

Tables Accessed

PER_SBT_SHD accesses the following tables through APPS synonyms:

  • ALL_CONSTRAINTS — The data dictionary view used to inspect constraint definitions at runtime, supporting the package's CONSTRAINT_ERROR handling and integrity checks.
  • FND_LANGUAGES — The Applications language definition table, read to determine installed languages and drive the ADD_LANGUAGE logic for translation rows.
  • PER_SUBJECTS_TAKEN — The base "Subjects Taken" table; the principal data object whose shadow rows this package maintains.
  • PER_SUBJECTS_TAKEN_TL — The translated (TL) companion of the base table, holding language-specific descriptive columns.

These accesses reflect the package's dual role: enforcing referential and constraint integrity while populating both base and translation shadow rows for the DateTrack history model.

Usage Notes

PER_SBT_SHD is an internal, generated-style utility and is not intended for direct invocation by end users or custom extensions. It is invoked indirectly through its sibling packages — PER_SBT_BUS, PER_SBT_DEL, PER_SBT_INS, and PER_SBT_UPD — which the HRMS "Subjects Taken" form and related DateTrack APIs call when a user inserts, updates, or deletes subject records. In Oracle EBS 12.1.1 and 12.2.2, the same pattern applies: the base table package orchestrates business rules, and PER_SBT_SHD performs the corresponding shadow-table insert, update, delete, locking, and language-row maintenance. Customizations should call the supported PER_SBT_BUS API rather than PER_SBT_SHD directly, since the shadow package assumes the surrounding DateTrack context established by the business layer.