Results for “delete_position_extra_info”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.HR_POSITION_EXTRA_INFO_API package body provides the supported PL/SQL interface for maintaining descriptive and flexfield-based extra information associated with positions in Oracle Human Resources. Positions are core workforce objects in Oracle E-Business Suite, and beyond the standard attributes stored on the position record itself, organizations frequently need to capture additional user-defined data such as cost center references, headcount approval codes, security classifications, or statutory reporting attributes. The PER_POSITION_EXTRA_INFO table stores this data as information type rows containing key flexfield segments and descriptive flexfield attribute columns.
This package encapsulates the business logic, validation, and derived-value processing required to insert, modify, and remove those extra information rows programmatically, without requiring direct DML against the underlying table. Because it is classified as a public API within the ETRM repository, it is the recommended integration point for external and custom code that must maintain position extra information in a manner consistent with the Oracle HRMS data model. The package is owned by APPS and its source header identifies the shipped file as pepoiapi.pkb, confirming it is a delivered Oracle component present in both the 12.1.1 and 12.2.2 releases.
Key Procedures and Functions
The package exposes three documented procedures, comprising a complete create, update, and delete lifecycle for position extra information records:
CREATE_POSITION_EXTRA_INFO— Creates a new extra information row for a specified position. It accepts the position identifier, the information type that governs which segments apply, the descriptive flexfield attribute category, and the corresponding attribute and information segment values. A validation-only mode is supported so that callers can verify data without committing a row.UPDATE_POSITION_EXTRA_INFO— Modifies an existing position extra information row, allowing changes to the information type, flexfield category, and segment values. Validation and date-effective handling are performed internally before the update is applied.DELETE_POSITION_EXTRA_INFO— Removes an existing extra information row from the position. This procedure supports the correction or retirement of obsolete supplemental data while preserving referential integrity within the HRMS schema.
All three procedures follow the standard Oracle HRMS API conventions, including a boolean validation parameter defaulting to false and the use of the g_package package variable for consistent error message routing.
Tables Accessed
The package operates against a single documented base table, referenced through its APPS synonym:
PER_POSITION_EXTRA_INFO— Stores the supplemental descriptive and key flexfield information for each position. The create procedure inserts rows into this table, the update procedure modifies existing rows, and the delete procedure removes them. The table is keyed by position and information type and contains thePOEI_ATTRIBUTEandPOEI_INFORMATIONsegment columns exposed in the procedure signatures.
Because the package is a delivered API, additional internal access to validation and lookup tables may occur implicitly, but PER_POSITION_EXTRA_INFO is the only table documented in the ETRM metadata for this object.
Usage Notes
HR_POSITION_EXTRA_INFO_API is typically invoked from Oracle HRMS forms when a user maintains position extra information through the Position window, where the form calls the API rather than performing direct table manipulation. It is also frequently called from custom PL/SQL, concurrent programs, and data conversion or interface routines that load or synchronize position data from external systems such as payroll, budgeting, or third-party HR applications. The ETRM metadata records that the package is referenced by five other packages, indicating its role as a shared service within the HRMS API layer.
Developers should call these procedures within a properly initialized HRMS session, honoring the validation parameter to preview results before committing, and should avoid direct DML on PER_POSITION_EXTRA_INFO to ensure that validation rules and any dependent processing remain consistent across releases 12.1.1 and 12.2.2.