Results for “pe_pei_shd”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PE_PEI_SHD is a shadow (suffix "_SHD") package body owned by the APPS schema in Oracle E-Business Suite. Its name follows the naming convention applied to internal helper packages that accompany the public People Extra Information (PEI) API layer within the Oracle Human Resources (PER/PE) product family. The package operates on the PER_PEOPLE_EXTRA_INFO table, which stores the configurable "Extra Information" (Descriptive Flexfield) attribute values captured against a person record. Rather than exposing a broad public interface, PE_PEI_SHD provides the low-level plumbing that the main PEI maintenance APIs rely upon: row locking, concurrency and update-tracking checks, argument coercion, and constraint-related error handling. In ETRM the object is classified with API classification OTHER and is reported with status VALID. It is referenced by eight other database objects, confirming its role as an internal dependency rather than an entry point invoked directly by forms or concurrent programs.

Key Procedures and Functions

The ETRM metadata documents four units within this package body:

  • LCK — Performs the row-level locking routine for PEI records. It is the standard lock helper used to obtain a consistent, serialized view of a PER_PEOPLE_EXTRA_INFO row before an update or delete is attempted, preventing concurrent modifications from colliding.
  • API_UPDATING — Signals or tracks whether the PEI row is currently being modified through the API. It supports the package's concurrency model by allowing callers to distinguish API-driven updates from other DML and to apply the correct validation or audit behaviour.
  • CONVERT_ARGS — Normalizes and converts incoming argument values into the datatypes and internal representations expected by the PEI processing logic. This centralizes value translation so that the higher-level PEI APIs receive consistently typed inputs.
  • CONSTRAINT_ERROR — Handles Oracle integrity-constraint exceptions raised during PEI DML, mapping low-level database errors into meaningful messages or states used by the calling API.

No parameter signatures are published in the ETRM document; the descriptions above reflect the documented unit names and their evident purpose only.

Tables Accessed

Two data sources are documented for this package body:

  • PER_PEOPLE_EXTRA_INFO — The primary object of interest. The package reads and writes this table when locking, validating and updating the extra information attribute values held for a person. All locking and update-tracking logic in LCK and API_UPDATING centres on rows of this table.
  • ALL_CONSTRAINTS — The data dictionary view over constraints. Its presence indicates that the package inspects constraint definitions, presumably to validate attribute values or to interpret which integrity rule was violated when raising the constraint-error condition.

Both tables are accessed through APPS synonyms, consistent with standard EBS coding practice. The package itself references HR_API and HR_UTILITY, so it also depends on the shared HR API infrastructure for error handling and utility routines.

Usage Notes

PE_PEI_SHD is not designed for direct invocation by end users, Oracle Forms, or concurrent programs. The ETRM record states that it is not referenced by any database object in the reverse direction, yet it references eight other packages and is itself called from the PEI API layer. Accordingly, it is invoked indirectly whenever a caller runs the public People Extra Information maintenance APIs that add, update or delete PEI attribute values. Custom code and extensions that manipulate PER_PEOPLE_EXTRA_INFO should route through those supported public APIs rather than calling PE_PEI_SHD directly, since the shadow layer assumes an established API context for locking and update-tracking. Because the package ships as part of the APPS schema in both 12.1.1 and 12.2.2, its behaviour is governed by the standard HR API validation rules for descriptive flexfield data. Any error surfaced through CONSTRAINT_ERROR should be interpreted in light of the HR_API conventions used by the surrounding People APIs.