Search Results in_miscellaneous




Overview
Explore in AI Chat

Overview

APPS.HR_IN_PERSON_EXTRA_INFO_API is a public API package in the Oracle E-Business Suite Human Resources (PER) module. It serves as the supported programmatic interface for maintaining "Person Extra Information" records—the descriptive flexfield-based (DFF) attribute structures that store installation-specific, non-standardized data against a person record in PER_PEOPLE_F. Typical uses include capturing visa categories, passport attributes, statutory identifiers, or other country-specific personal details configured as extra information types within an Information Type DFF.

The package encapsulates the DML and validation logic required to insert, update, and validate extra information rows, allowing external callers to manipulate this data without directly touching the underlying base tables. Because it is classified as an API in the ETRM metadata (owner APPS, delivered under version 120.0), it is the sanctioned integration point for person extra information and is referenced by four other packages, indicating its role as a building block for higher-level HR and localization APIs.

Key Procedures and Functions

The documented interface exposes four procedures:

  • CHECK_PERSON — A validation procedure that verifies a person exists and that the person belongs to the correct business group for the supplied legislation code. The source shows it queries PER_PEOPLE_F and raises the standard HR error messages HR_7220_INVALID_PRIMARY_KEY when the person is not found, and HR_7208_API_BUS_GRP_INVALID when the business group / legislation does not match the caller's context.
  • CREATE_IN_PERSON_EXTRA_INFO — Inserts a new person extra information row, accepting the person identifier and the full set of PEI_ATTRIBUTE flexfield columns. It supports the standard p_validate flag, which rolls back the work and returns success indicators without committing when set to true.
  • UPDATE_IN_PERSON_EXTRA_INFO — Modifies an existing person extra information row, again using the PEI_ATTRIBUTE column set and the standard validation-only mode.
  • CREATE_IN_PASSPORT_DETAILS and UPDATE_IN_PASSPORT_DETAILS — Specialized entry points for the passport-detail variant of the person extra information structure, handling create and update respectively for passport-specific attributes.

Parameter lists are intentionally not reproduced here; callers should consult the package specification for exact signatures. All procedures follow Oracle HR API conventions: an optional validation flag, IN-only parameters, and error propagation via HR_UTILITY.SET_MESSAGE and HR_UTILITY.RAISE_ERROR.

Tables Accessed

The primary base table read by the package is PER_PEOPLE_F, which stores person records and is consulted during check_person to confirm existence and derive the business group / legislation context. The create and update procedures write to the person extra information store (the PER_PERSON_EXTRA_INFO family of tables), populated through the PEI_ATTRIBUTE flexfield columns. Passport-specific routines target the corresponding passport detail structure. Because the package is owned by APPS, all access is performed through APPS synonyms. No tables are listed in the extracted ETRM metadata for this package, so the table references above are drawn from the documented source behaviour rather than a formal cross-reference snapshot.

Usage Notes

This API is typically invoked from three contexts: Oracle Forms-based HR self-service or professional-user pages that maintain person extra information, concurrent or batch programs that load or migrate person attributes, and custom PL/SQL extensions (localizations, conversion scripts, workflow handlers) that need to maintain extra information without direct DML. The four dependent packages identified in the metadata indicate that it is most often called indirectly from higher-level HR APIs rather than directly by end-user code.

Callers must always supply a valid person identifier and correct legislation / business group context; otherwise check_person will raise HR_7220 or HR_7208. The standard p_validate parameter should be used during testing to exercise the logic without committing changes. As with all Oracle HR APIs, the package should not be modified, and any custom logic must be layered on top of it before committing the session.