Search Results update_person_extra_info

Overview

The APPS.HR_PERSON_EXTRA_INFO_API package body is a public Oracle E-Business Suite PL/SQL API that manages "extra information" (also known as descriptive flexfield or attribute-level detail) associated with a person record in Oracle Human Resources. Extra information in HRMS is stored in the PER_PEOPLE_EXTRA_INFO table and lets applications capture arbitrary, customer-defined attributes beyond the standard person columns maintained by PER_ALL_PEOPLE_F. The package provides the supported programmatic interface for creating, maintaining, and removing those extra information rows, insulating callers from the underlying tables and their validation logic.

In EBS 12.1.1 and 12.2.2 this package is one of many HRMS business APIs sharing a common design pattern: a thin public API layer that validates input, calls an internal private package for business rules, and then delegates DML to generated table handlers (HR_PERSON_EXTRA_INFO_BK1, HR_PERSON_EXTRA_INFO_BK2, and HR_PERSON_EXTRA_INFO_BK3) and row-level insert/update/delete procedures (PE_PEI_INS, PE_PEI_UPD, PE_PEI_DEL). It relies on shared utilities (HR_API, HR_UTILITY) and, in 12.2.2, is referenced by roughly 21 other database objects, which confirms its role as a foundational integration point within the HRMS schema.

Key Procedures and Functions

Three public procedures constitute the documented interface of the package. These follow the standard HRMS API verb convention.

• CREATE_PERSON_EXTRA_INFO — Inserts a new extra information record for a person, populating the identified flexfield/attribute with the supplied values and recording the standard WHO columns.
• UPDATE_PERSON_EXTRA_INFO — Modifies the values of an existing extra information record previously created for a person.
• DELETE_PERSON_EXTRA_INFO — Removes an extra information record, either physically or through the standard HRMS API delete mechanism.

Each procedure is invoked with the standard HRMS API calling convention, supplying a p_validation_start_date, p_validation_end_date, the p_effective_start_date and p_effective_end_date, the p_object_version_number (required for update and delete), and a procedure-specific p_*_rec or scalar parameter set, plus the usual p_validate flag that allows callers to roll back a trial execution. On completion the API returns the assigned object version number and effective date range. Parameter lists are intentionally not enumerated here; refer to the package specification for exact signatures.

Tables Accessed

The package reads and writes the following documented tables (accessed through APPS synonyms):

• PER_PEOPLE_EXTRA_INFO — the primary data store for the extra information rows created, updated, or deleted by this API.
• PER_ALL_PEOPLE_F — the person master, used to resolve and validate the person for whom extra information is being maintained.
• PER_PHONES — accessed for phone-related extra information handling.

All DML is performed through the private table handlers rather than by direct SQL in the public procedures, ensuring that validation, effective-dating, and audit columns are consistently applied.

Usage Notes

This API is intended for any Oracle or custom code that needs to programmatically manage person extra information. Typical invocations include HRMS forms that maintain extra person detail, concurrent programs that mass-load or migrate extra information data, and custom PL/SQL integrations. Because it is the sanctioned entry point, custom code should call these procedures rather than inserting directly into PER_PEOPLE_EXTRA_INFO. As a governed, referenced dependency of some twenty-plus database objects in 12.2.2, the package carries the usual HRMS API contract: always use the p_validate flag during testing, respect the returned object version number for optimistic concurrency, and rely on the returned status codes and exceptions for error handling. The package body is VALID in the APPS schema and remains compatible across the 12.1.1 and 12.2.2 releases.