Search Results pe_aei_upd




Overview
Explore in AI Chat

Overview

PE_AEI_UPD is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in the ETRM repository as an "OTHER" API type. It forms part of the Oracle Human Resources (HR) foundation layer that manages Assignment Extra Information — the flexible, descriptive, and developer-defined attributes attached to an employee assignment record through the DFF/KFF extra information framework. Within Oracle EBS 12.1.1 and 12.2.2, assignment extra information is the mechanism through which customers extend the PER_ASSIGNMENTS entity with additional columns and value sets without modifying base tables directly.

The package's role is to consolidate the write-side logic for these extra information rows. Rather than allowing dependent processes to issue direct DML against the underlying base table, PE_AEI_UPD centralises the update path, applying the HR API validation and security conventions expected by the rest of the HR schema. This design enforces consistency, supports the HR date-tracking and business-group security model, and provides a single point of control for extra information maintenance.

Key Procedures and Functions

The documented metadata records two total procedures/functions, one of which is named UPD. The primary documented entry point is UPD, whose purpose is to perform the update of assignment extra information records. Based on the standard HR API pattern and the package's position in the dependency chain, UPD accepts identification of the target assignment extra information row together with the new attribute values, validates them against the extra information definitions, and applies the change to the base table. The second documented routine complements UPD as part of the same maintenance interface — typically a private or helper routine handling validation, row locking, or the DFF context and attribute segment mapping that UPD relies upon. Because the ETRM entry does not expose formal parameter lists, the precise signature is not reproduced here; consumers should obtain it from the package specification in the database or from Oracle's developer documentation for their exact patch level, since signatures can vary between 12.1.1 and 12.2.2.

Tables Accessed

The documented table referenced by PE_AEI_UPD through APPS synonyms is PER_ASSIGNMENT_EXTRA_INFO. This is the base table that stores extra information rows for assignment records, with each row linked to an assignment and to a specific extra information definition or context. PE_AEI_UPD reads from this table to locate and validate the existing row and writes to it to persist the updated attribute values. Because the package operates through APPS synonyms, all access is subject to the standard APPS schema privileges and any row-level or business-group security applied at the HR layer.

Usage Notes

PE_AEI_UPD is referenced by two other packages — GHR_HISTORY_CASCADE and HR_ASSIGNMENT_EXTRA_INFO_API. The latter is the public, supported HR API surface for assignment extra information, and it delegates its update work to PE_AEI_UPD. GHR_HISTORY_CASCADE uses it in the context of cascading assignment history changes, ensuring that when historical assignment data is propagated or corrected, the associated extra information is updated consistently. PE_AEI_UPD also references HR_API and depends on PE_AEI_SHD, the shadow/date-tracked counterpart in the HR table-shadowing framework used for audit and history purposes.

In practice, PE_AEI_UPD is an internal, implementation-level package. Direct invocation from forms, concurrent programs, or custom code is not recommended; customers should call HR_ASSIGNMENT_EXTRA_INFO_API, which is the documented and supported entry point and which routes updates through PE_AEI_UPD. Custom extensions that must manipulate assignment extra information should therefore use the public API, preserving compatibility across 12.1.1 and 12.2.2 and remaining within Oracle's support boundary. As an APPS-owned package with VALID status, it is deployed and compiled in the standard EBS database, and its behaviour is governed by Oracle's proprietary licensing terms as noted in the ETRM documentation.