Search Results per_add_upd




Overview
Explore in AI Chat

Overview

PER_ADD_UPD is an Oracle Applications (APPS) PL/SQL package that forms part of the Oracle Human Resources (PER) schema foundation within Oracle E-Business Suite 12.1.1 and 12.2.2. Its object name, combining the "PER_" prefix with the "ADD_UPD" suffix, indicates that the package is concerned with the handling of address-related data for persons and other HR entities. The package is classified as a generic API (API classification: OTHER) rather than a public, supported business API, and it carries a VALID status in the ETRM repository.

Functionally, PER_ADD_UPD provides internal logic used to consolidate, convert, and update address definitions and related records. Because it is referenced by several higher-level APIs — including HR_PERSON_ADDRESS_API, HR_APPLICANT_API, and GHR_HISTORY_CASCADE — it serves as a supporting utility layer beneath the address management functionality exposed by those packages. It also depends directly on HR_API and PER_ADD_SHD, indicating that it leverages shared HR API infrastructure and shadow (audit/history) table maintenance routines for the PER_ADDRESSES entity.

Key Procedures and Functions

The documented metadata lists three procedures or functions within the package. Parameter lists are not exposed in the ETRM record and are therefore not reproduced here; only documented purpose is described.

  • UPD — The primary update routine. Based on the package name and its dependency on PER_ADDRESSES, this procedure performs insert, update, or synchronization operations against address records, likely as a wrapper or internal handler invoked by the higher-level address APIs.
  • CONVERT_DEFS — A conversion routine. Its name suggests that it transforms or normalizes address definitions, possibly bridging legacy or flexible-field address structures to the standard PER_ADDRESSES model. Conversions of this nature are commonly required during upgrades, data migrations, or when reconciling descriptive flexfield-driven address attributes.
  • PER_ADD_UPD — The package body itself appears in the dependency list, consistent with internal self-referencing or recursive calls, and may also denote an internal helper routine sharing the package name.

Tables Accessed

The single documented table referenced through an APPS synonym is PER_ADDRESSES. This is the core HR table holding address records for persons, locations, and related entities, keyed to the PER_ADDRESSES business group structure. PER_ADD_UPD reads and writes PER_ADDRESSES in support of the update and conversion routines described above. The dependency on PER_ADD_SHD additionally indicates that the package participates in maintaining the shadow table for PER_ADDRESSES, where prior versions of address rows are retained to support audit history and the DateTrack (effective-dating) mechanism used throughout Oracle HRMS.

Usage Notes

PER_ADD_UPD is an internal, non-public package. It is not intended to be invoked directly by custom code; Oracle does not document it as a supported API surface. Instead, it is called indirectly through the four packages that reference it: HR_PERSON_ADDRESS_API, HR_APPLICANT_API, GHR_HISTORY_CASCADE, and IRC_GLOBAL_REMAP_PKG. These callers span person address maintenance, applicant (recruitment) processing, history cascade operations, and iRecruitment global remapping.

Typical invocation therefore occurs when a user or process updates an address through an Oracle Forms-based HR window, runs an HRMS concurrent program that touches address data, or executes a supported API such as HR_PERSON_ADDRESS_API. During upgrades or data conversions involving address definitions, CONVERT_DEFS may be exercised as part of the broader migration path. For 12.1.1 and 12.2.2, developers should treat PER_ADD_UPD as read-only with respect to design: it should not be called directly, and any custom address logic should be built on the supported HR_PERSON_ADDRESS_API rather than this internal package.