Results for “p_position_extra_info_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.HR_POSITION_EXTRA_INFO_API is a public Oracle E-Business Suite PL/SQL API that creates and maintains extra information attached to positions. It is registered under the PER product and is licensed for use with Oracle Human Resources. The package provides the supported programmatic interface for the PER_POSITION_EXTRA_INFO entity, which stores user-defined or flexfield-driven supplemental data keyed to a position and an information type. Because it is designated with a public scope in the ETRM repository, it is the sanctioned entry point for applications and integrations that must insert, change, or remove position extra information without writing directly to the underlying table.

The package header carries the identifier pepoiapi.pkh, confirming its place within the HR position schema. Its business purpose is to let HR implementations capture attributes beyond the standard position definition, such as regulatory classifications, bargaining unit codes, or other descriptive flexfield content, while enforcing the validation and referential rules that Oracle HRMS expects for position data.

Key Procedures and Functions

The documented API surface consists of three procedures, following the standard Oracle HRMS create, update, and delete pattern.

• CREATE_POSITION_EXTRA_INFO — Creates a new extra information record for a given position. The caller supplies the position identifier, the information type that classifies the extra information, an attribute category that determines which descriptive flexfield structure applies, and the corresponding poei_attribute descriptive flexfield segments. The API requires that the position and the position information type already exist before it is invoked. On success the position extra information row is created; on failure no row is created and an error is raised.
• UPDATE_POSITION_EXTRA_INFO — Modifies an existing position extra information record, allowing the descriptive flexfield segments and related attributes to be changed for a position and information type combination already on file.
• DELETE_POSITION_EXTRA_INFO — Removes a position extra information record that is no longer required.

All three procedures observe the conventional p_validate parameter: when it is set to true, only validation is performed and the database remains unchanged; when it is false and all checks pass, the database is modified.

Tables Accessed

The package operates on a single documented table, accessed through its APPS synonym: PER_POSITION_EXTRA_INFO. This table holds one row per position and information type combination, together with the attribute category context value and the poei_attribute descriptive flexfield columns. The create procedure inserts into this table, the update procedure modifies existing rows, and the delete procedure removes them. Because the table is the sole repository for position extra information, all validation performed by the API ultimately protects the integrity of these rows.

Usage Notes

HR_POSITION_EXTRA_INFO_API is typically invoked by the Position Extra Information maintenance window in Oracle HRMS, by concurrent programs that load or migrate position attributes, and by custom PL/SQL, OAF pages, or conversion routines that must populate position extra information in bulk. It is also referenced by five other packages in the ETRM repository, indicating that it functions as a shared building block within the HR position stack.

Callers searching for "per_position" should note that the API is the supported alternative to direct DML or ad hoc SQL against PER_POSITION_EXTRA_INFO. When invoking it, ensure that the position record and the position information type exist, supply the correct attribute category so that the intended descriptive flexfield structure is used, and exercise the p_validate option during testing before committing changes in production.