Results for “per_position_extra_info”

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

Overview

PER_POSITION_EXTRA_INFO is a Human Resources (PER) module table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema owned by HR. It stores the user-defined "extra information" (descriptive flexfield) details attached to a position record. While PER_ALL_POSITIONS carries the core position definition, this table holds the configurable, attribute-driven data captured against a position according to the information types defined for the enterprise. It is therefore a key extension point for customers who need to record site-specific position data without modifying the base position entity.

The table has 65 documented columns and is a child (detail) table in the PER schema. Under the ETRM heuristic Data Vault classification, this object is a link. It resolves the many-to-many style association between a position and an information type, carrying descriptive attributes in its flexfield columns and mapping to its parent PER_ALL_POSITIONS and its type definition table PER_POSITION_INFO_TYPES.

Key Information Stored

The primary key is the surrogate key POSITION_EXTRA_INFO_ID, enforced through the unique index PER_POSITION_EXTRA_INFO_PK. This is the column commonly searched as "position_extra_info_id" and is the identifier used to join the table to downstream shadow and interface tables. The key business columns include:

• POSITION_ID — foreign key to PER_ALL_POSITIONS, identifying the position the extra information belongs to.
• INFORMATION_TYPE — foreign key to PER_POSITION_INFO_TYPES, identifying which extra-information (DFF) structure applies.
• POEI_INFORMATION_CATEGORY and POEI_ATTRIBUTE_CATEGORY — the descriptive flexfield context / category qualifiers.
• POEI_INFORMATION1 … POEI_INFORMATION30 — the 30 flexfield segments holding the actual extra-information values.
• POEI_ATTRIBUTE1 … POEI_ATTRIBUTE20 — the 20 generic descriptive flexfield attribute columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the concurrent program tracking columns that identify the process that last wrote the row.
• OBJECT_VERSION_NUMBER — optimistic locking version used by the HR APIs.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.

Common Use Cases and Queries

Typical use cases include reporting on custom position attributes, validating that every position has a required extra-information type recorded, and extracting extra-information data for integrations. A basic query joins the table to its parents:

• SELECT poi.position_extra_info_id, poi.position_id, poi.information_type, poi.poei_information1 FROM per_position_extra_info poi WHERE poi.position_id = :position_id;
• Join to PER_ALL_POSITIONS to retrieve position names alongside extra information: SELECT p.name, poi.poei_information1 FROM per_all_positions p, per_position_extra_info poi WHERE p.position_id = poi.position_id;
• Filter by information type using PER_POSITION_INFO_TYPES to isolate a specific DFF structure.

Because the flexfield segment columns are generically named, reporting usually requires a value-set mapping or a view such as the descriptive flexfield view to translate segment numbers into meaningful labels.

Related Objects

• PER_ALL_POSITIONS — parent table; joined via POSITION_ID.
• PER_POSITION_INFO_TYPES — reference table; joined via INFORMATION_TYPE.
• PQH_PTE_SHADOW — shadow table referencing POSITION_EXTRA_INFO_ID.
• PQH_PTX_EXTRA_INFO — extra-information shadow table referencing POSITION_EXTRA_INFO_ID.
• HR_POSITION_API / PER_POSITION_API — the HR position APIs that insert, update, and validate rows in this table during position maintenance.

These relationships confirm the table as a detail extension off the core position entity, feeding downstream PQH (Public Sector/Position Management) shadow entities through the shared position_extra_info_id key.