Search Results per_apl_shd




Overview
Explore in AI Chat

Overview

PER_APL_SHD is a shadow (private) 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 Human Resources (PER) product family and, based on the dependency metadata, is directly associated with the PER_APPLICATIONS table — the datastore that holds validation and reference data such as application types, lookup values, and related descriptive columns used throughout HRMS and self-service modules.

The "_SHD" suffix denotes a shadow package: a private implementation layer generated to support a public synonym or a read-consistency wrapper around the underlying base object. Shadow packages typically expose a small, controlled set of helper routines used by Oracle's own API infrastructure rather than by customer code. The package body is documented as VALID at the time of extraction, and it is classified as an OTHER API, meaning it does not conform to the standard HRMS date-tracked, business-group secured API template (such as the HR_API pattern).

Key Procedures and Functions

The ETRM metadata records five documented program units within the package body:

  • RETURN_API_DML_STATUS — Returns the DML status of the most recent API operation, allowing callers to determine whether an insert, update, or delete succeeded within the shadow package's transactional context.
  • CONSTRAINT_ERROR — Handles integrity constraint violations raised during DML against the underlying tables, providing a controlled hook for trapping and interpreting Oracle constraint exceptions rather than allowing raw ORA- errors to propagate.
  • API_UPDATING — Indicates whether the package is currently executing an update path, and is typically used to suppress or branch behaviour during recursive or nested API invocation.
  • LCK — Implements row-level locking semantics, ensuring that concurrent sessions modify the same PER_APPLICATIONS record in a serialised fashion.
  • CONVERT_ARGS — Performs argument conversion and normalisation before the arguments are passed to the shadow layer's internal DML routines, reconciling datatype or format differences between the calling interface and the underlying table columns.

These routines are private helpers rather than published, supported entry points. Parameter lists are intentionally not exposed here, as the package is not documented for direct customer invocation.

Tables Accessed

The package body references PER_APPLICATIONS as its principal data object, accessed via the APPS synonym. PER_APPLICATIONS stores application definitions used by HRMS lookups and validation logic; the shadow package reads from and writes to it to maintain application reference data.

It also references ALL_CONSTRAINTS, the data dictionary view listing constraint definitions on accessible tables. This access is consistent with the CONSTRAINT_ERROR routine, which consults constraint metadata to map raised ORA- errors back to the specific integrity rule that was violated. Dependencies further include the HR_API and HR_UTILITY utility packages, and the STANDARD core package.

Usage Notes

PER_APL_SHD is not referenced by any other database object and is not intended for direct customer use. It is invoked indirectly — typically through Oracle Forms, concurrent programs, or Oracle's own HRMS APIs that require shadow-layer DML, locking, and error-handling support for PER_APPLICATIONS.

Because the package is a private shadow implementation, the supported extension point for application reference data remains the public, documented HRMS APIs. Custom code should not call PER_APL_SHD directly; doing so risks breakage during patching or upgrade, since the package body may be regenerated without notice. Use it only as a diagnostic reference when tracing DML or constraint failures affecting PER_APPLICATIONS.