Search Results pe_pei_upd




Overview
Explore in AI Chat

Overview

PE_PEI_UPD is a PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Human Resources (HR) module. Its name follows the HR naming convention for person extra information processes, where "PE" denotes the People subsystem, "PEI" denotes Person Extra Information, and "UPD" denotes an update routine. The package functions as a low-level maintenance utility responsible for writing and updating rows in the person extra information infrastructure, which stores the flexible, descriptive attribute values captured against an employee, applicant, or contact record. These values populate the descriptive flexfield segments and additional "Extra Information" types configured by the customer in the HR setup screens.

Oracle classifies the package as an "OTHER" API rather than a public, supported business API. This classification indicates that PE_PEI_UPD is intended for internal use by other EBS product code rather than direct invocation by customer extensions. Its role is to isolate the physical update logic for person extra information records so that multiple higher-level APIs and concurrent processes can share a single, consistent write path.

Key Procedures and Functions

The documented package surface exposes two procedures and functions, collectively identified as UPD (the update entry point). Consistent with Oracle's practice for internal maintenance packages, the interface is deliberately narrow and centered on applying changes to existing person extra information rows.

  • UPD — The primary update routine. It applies changes to person extra information records, synchronizing the row maintained in the PER_PEOPLE_EXTRA_INFO table with the values supplied by the calling program. Because the ETRM metadata does not publish a parameter list, integrators should not assume a stable signature; the routine is subject to change between releases and is not part of the public API contract.
  • Additional wrapper/overload (UPD) — The metadata counts two procedures/functions, indicating that the update logic is exposed through more than one entry point, typically to accommodate different calling contexts (for example, single-row updates versus set-based or cascade operations). These wrappers ultimately converge on the same underlying write logic against person extra information.

No documented function returns values to the caller, reinforcing the package's role as a procedural maintenance utility rather than a query service.

Tables Accessed

The package accesses two documented objects through APPS synonyms:

  • PER_PEOPLE_EXTRA_INFO — The primary target of the update logic. This table stores the actual extra information values associated with a person record, keyed by person, information type, and effective dating. PE_PEI_UPD writes and maintains rows in this table as the system of record for personal descriptive data.
  • FND_USER — The Applications user table, referenced to capture or validate the user identity associated with an update. This supports standard EBS audit columns such as LAST_UPDATED_BY and the tracking of which user or process performed the change.

Additional references documented in ETRM include the HR_API package (for common HR utilities and business-group validation), the PE_PEI_SHD shadow package (for concurrency and row-locking consistency), and the SYS.STANDARD package used internally by PL/SQL. These are supplemental dependencies rather than data targets.

Usage Notes

PE_PEI_UPD is typically invoked indirectly. The dependency list shows it is referenced by three other packages: HR_PERSON_EXTRA_INFO_API, GHR_HISTORY_CASCADE, and PE_PEI_UPD itself. HR_PERSON_EXTRA_INFO_API is the supported business API through which customer code and forms should create or change extra information; it delegates the physical write to PE_PEI_UPD. GHR_HISTORY_CASCADE invokes the package when cascading historical date-tracked changes across extra information records.

Because the package is not a published API, custom development should avoid calling PE_PEI_UPD directly. Direct calls risk breakage during patching or upgrades, as the signature and behavior are not guaranteed. The recommended alternative is to route all person extra information maintenance through HR_PERSON_EXTRA_INFO_API, which enforces business rules, date-track validation, and security before reaching the internal update layer. When troubleshooting unexpected changes to person extra information in Oracle EBS 12.1.1 or 12.2.2, PE_PEI_UPD is a useful diagnostic landmark: enabling trace or profiling on this package reveals which upstream API or concurrent process actually performed the modification.