Search Results per_position_extra_info

Overview

The PER_POSITION_EXTRA_INFO table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically in releases 12.1.1 and 12.2.2. It functions as a flexible, extensible repository for storing supplemental information related to positions within the organization. Its primary role is to support the Oracle HRMS Information Types framework, allowing organizations to define and capture custom attributes for positions beyond the standard fields available in the main position definition table (PER_ALL_POSITIONS). This design enables tailored data collection to meet specific business, compliance, or reporting requirements without requiring customization of the core application tables.

Key Information Stored

The table's structure is designed to hold key-value pairs of extra information, linked to both a specific position and a defined information type. The most critical columns include:

• POSITION_EXTRA_INFO_ID: The primary key and unique identifier for each record in this table.
• POSITION_ID: A foreign key that links the extra information to a specific position defined in the PER_ALL_POSITIONS table.
• INFORMATION_TYPE: A foreign key that identifies the category or structure of the extra information being stored, as defined in the PER_POSITION_INFO_TYPES table (e.g., 'Position Budget Details', 'Physical Requirements').
• PEI_INFORMATION_CATEGORY: Typically used to further categorize the information within a given type, often for internal application logic.
• PEI_INFORMATION1 through PEI_INFORMATION30: These are the primary columns for storing the actual custom data. The meaning of the data in each column is determined by the definition of the associated INFORMATION_TYPE.

Common Use Cases and Queries

This table is central to reporting and data extraction involving custom position attributes. A common use case is generating reports that combine standard position data with organization-specific details, such as cost center codes, physical location requirements, or budget approval authorities. For auditing or data validation, queries often join this table to the main position and information type tables. A typical reporting query pattern is:

SELECT pap.position_id, pap.name position_name,
ppit.system_information_type,
ppei.pei_information1, ppei.pei_information2
FROM per_all_positions pap,
per_position_extra_info ppei,
per_position_info_types ppit
WHERE pap.position_id = ppei.position_id
AND ppei.information_type = ppit.information_type
AND ppit.system_information_type = 'MY_CUSTOM_INFO_TYPE';

Data is primarily managed through the Oracle HRMS user interface or via dedicated APIs (such as the HR_POSITION_API), which handle the validation and population of this table.

Related Objects

PER_POSITION_EXTRA_INFO is integral to the HR information architecture and has defined relationships with several key tables, as documented in the ETRM metadata:

• PER_ALL_POSITIONS: The primary parent table. The relationship is maintained via the foreign key PER_POSITION_EXTRA_INFO.POSITION_ID referencing PER_ALL_POSITIONS.POSITION_ID. This links every piece of extra information to a master position record.
• PER_POSITION_INFO_TYPES: The defining table for information types. The relationship is maintained via the foreign key PER_POSITION_EXTRA_INFO.INFORMATION_TYPE referencing PER_POSITION_INFO_TYPES.INFORMATION_TYPE. This ensures that all stored data conforms to a pre-defined structure and validation rules.

These relationships ensure data integrity and are essential for any meaningful query or integration involving custom position data.