Search Results hr_trn_shd




Overview
Explore in AI Chat

Overview

HR_TRN_SHD is a shadow (audit) package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the Oracle HRMS training (OLT) subsystem and serves as the audit-trail mechanism for the HR training APIs. The suffix "SHD" identifies the package as a shadow copy: rather than performing the primary business validation and insert, update, or delete logic itself, it records the before and after images of training-related API transactions so that changes to training records can be audited and traced back to the originating API call.

The package's documented API classification is OTHER, and its dependency list ties it directly to HR_API and HR_UTILITY, the shared Oracle HRMS API infrastructure that supplies date-tracked row handling, API transaction bookkeeping, and error signalling. Because the body is VALID and is not referenced by any other database object, it is invoked internally by the HR training APIs rather than acting as a public entry point for customer extensions.

Key Procedures and Functions

The documented unit exposes six procedures and functions. Their names indicate the following responsibilities:

  • RETURN_API_DML_STATUS — Returns the DML status of the currently executing API transaction, allowing the caller to determine whether a training API operation succeeded, failed, or was skipped.
  • CONSTRAINT_ERROR — Handles constraint violations raised during shadow processing, converting Oracle integrity errors into the HRMS API error-handling model.
  • API_UPDATING — Indicates whether an API-driven update is currently in progress, used to gate shadow-row creation so that only genuine API changes are recorded.
  • LCK — Encapsulates the locking logic applied to the shadowed training records before images are written.
  • CONVERT_ARGS — Normalises or converts incoming API arguments into the form required for shadow storage.

No parameter lists are documented in the ETRM metadata, and none should be assumed; signatures should be inspected directly in the database before any custom call is attempted.

Tables Accessed

Two tables are referenced through APPS synonyms. HR_API_TRANSACTIONS is the central transaction register for HRMS APIs and is used to associate each shadow record with its originating API call and transaction identifier. ALL_CONSTRAINTS is a data dictionary view queried to validate constraint names and integrity rules encountered while processing the shadow rows. Reads and writes against the training entities themselves are performed indirectly through the associated HR_TRN_SHD table and the HR_API package rather than being issued directly by this body.

Usage Notes

HR_TRN_SHD is a support package and is not intended for direct invocation from forms, concurrent programs, or custom code. It is called indirectly whenever the Oracle Training Administration APIs persist changes, and it participates in the standard HRMS date-tracked update cycle. Because it is referenced by five other packages but references none in return, it sits near the bottom of the dependency chain and should not be modified or wrapped. Customers requiring audit reporting on training changes should query the shadow tables and HR_API_TRANSACTIONS rather than calling this package. Any diagnostic work should follow Oracle's documented HRMS API debugging procedures, and the package should be treated as Oracle proprietary, confidential internal code.