Search Results pei_attribute
Overview
APPS.HR_IN_PERSON_EXTRA_INFO_API is a public PL/SQL API belonging to the Human Resources (PER) product family. It is registered under the ETRM classification "API" and is licensed for use with Oracle Human Resources. The package provides programmatic access to person extra information records specific to India localization requirements. Its display name in the ETRM repository is "Person Extra Information for India," reflecting the fact that the API is concerned with country-specific statutory and biographical data held against a person record.
The core business function of the package is to create and maintain extra information that does not fit within the standard person model. The documented header indicates that for the extra information type IN_MISCELLANEOUS, a record is created for the person, and the API validates that both the person and the required information type exist before writing to the database. A p_validate parameter is provided so that callers can perform validation alone without committing changes.
Key Procedures and Functions
The ETRM metadata documents four procedures in this package:
- CREATE_IN_PERSON_EXTRA_INFO — Creates miscellaneous extra information for a person. The documented example centers on the
IN_MISCELLANEOUSinformation type, which produces a record for the identified person. Prerequisites are that the person exists and that the extra person information type exists. On success the miscellaneous record is created; on failure no record is created and an error is raised. - CREATE_IN_PASSPORT_DETAILS — Creates passport-related extra information for a person, following the same validation and creation pattern as the miscellaneous variant but targeting the passport detail attributes of the India localization.
- UPDATE_IN_PERSON_EXTRA_INFO — Updates an existing miscellaneous extra information record for a person, allowing previously captured values to be revised while preserving the standard validation behaviour.
- UPDATE_IN_PASSPORT_DETAILS — Updates existing passport detail information held against a person record.
Across the create procedures the parameter set includes p_person_id to identify the person and p_pei_attribute_category together with p_pei_attribute1 through p_pei_attribute5 to describe the descriptive flexfield context and its segments.
Tables Accessed
The documented metadata lists no referenced tables accessed via APPS synonyms, so the underlying physical tables are not enumerated in the repository extract. Functionally, the package operates against the person extra information entity — the PER_PERSON_EXTRA_INFO table and its associated descriptive flexfield columns (PEI_ATTRIBUTE_CATEGORY and PEI_ATTRIBUTE1 through PEI_ATTRIBUTE). These columns are the direct target of the pei_attribute search term. The API also implicitly depends on person records and on the extra information type setup, since the documented prerequisites require both to exist before a write can succeed.
Usage Notes
The package is typically invoked from Oracle Forms, from concurrent programs, or from custom PL/SQL code that needs to maintain India-specific person extra information without bypassing the standard validation and security logic of the Human Resources product. The ETRM metadata notes that it is referenced by four other packages, indicating that it forms part of a dependency chain within the PER schema and may be called indirectly by higher-level APIs.
Callers should supply p_validate => TRUE during development and testing to confirm that prerequisite records exist and that the descriptive flexfield context supplied through p_pei_attribute_category is valid for the target pei_attribute segments. Because the API raises an error and leaves the database unchanged when validation fails, exception handling should be implemented around every invocation. Direct DML against the underlying tables is not recommended, as it would bypass the validation and licensing controls enforced by this package.