Search Results ghr_position_extra_info_h_v




Overview
Explore in AI Chat

Overview

GHR_POSITION_EXTRA_INFO_H_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, residing in the GHR – US Federal Human Resources product family. Its documented purpose is the mapping of GHR_PA_HISTORY columns into the shape of PER_POSITION_EXTRA_INFO. In other words, the view presents the denormalized, generic information columns of the US Federal HR personnel action history table as a typed projection whose column list matches the Position Extra Information entity.

This view is not a conventional reporting view over a single base table. It is a mapping or translation layer, converting the positionally-encoded INFORMATION columns of the history table into named, length-constrained columns. As such, it functions as a bridge between the historical/staging representation of personnel action data and the logical PER_POSITION_EXTRA_INFO structure, which is relevant to EBS reporting, data migration, and integration with the Federal HR personnel action processing framework.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

Because the SELECT list truncates at INFORMATION34 in the documented excerpt, the view likely exposes additional INFORMATION-based columns beyond those shown, consistent with the wide column range used by the Federal HR action framework.

Key Columns

  • PA_HISTORY_ID — primary identifier of the underlying history row; the join key back to GHR_PA_HISTORY.
  • PROCESS_DATE and EFFECTIVE_DATE — the processing timestamp and the effective (business) date of the action.
  • DML_OPERATION — indicates the operation type recorded for the row (insert, update, delete), supporting audit and replay logic.
  • PRE_VALUES_FLAG — signals whether the row carries pre-change (before-image) values.
  • ALTERED_PA_REQUEST_ID and PA_REQUEST_ID — links to the personnel action request that produced the row.
  • NATURE_OF_ACTION_ID — classification of the personnel action.
  • POSITION_EXTRA_INFO_ID — derived via GHR_GENERAL.RETURN_NUMBER(INFORMATION1); the surrogate key for the extra information record.
  • POSITION_ID — derived via GHR_GENERAL.RETURN_NUMBER(INFORMATION4); identifies the position to which the extra information applies.
  • INFORMATION_TYPE (from INFORMATION5, 40 chars) and POEI_INFORMATION_CATEGORY (from INFORMATION6, 30 chars) — the descriptive type and category of the extra information.
  • POEI_INFORMATION1 … POEI_INFORMATION27+ — the mapped descriptive fields, each derived as SUBSTR(INFORMATION, 1, 150), carrying the actual position extra information payload.

Common Use Cases and Queries

Typical scenarios include validating Federal HR personnel action history against position extra information, reconstructing before-and-after images for audit, and extracting position extra information during data migration or interface development.

  • Retrieving extra information for a specific position:
SELECT POSITION_EXTRA_INFO_ID, POSITION_ID, INFORMATION_TYPE,
       POEI_INFORMATION_CATEGORY, POEI_INFORMATION1
FROM   APPS.GHR_POSITION_EXTRA_INFO_H_V
WHERE  POSITION_ID = :p_position_id;
  • Filtering by effective date range for a period-based audit:
SELECT PA_HISTORY_ID, PA_REQUEST_ID, NATURE_OF_ACTION_ID,
       DML_OPERATION, PRE_VALUES_FLAG, EFFECTIVE_DATE
FROM   APPS.GHR_POSITION_EXTRA_INFO_H_V
WHERE  EFFECTIVE_DATE BETWEEN :p_start AND :p_end
ORDER  BY EFFECTIVE_DATE;

Because the view is documented as VALID in the ETRM repository, it is safe to query directly in supported EBS 12.1.1 and 12.2.2 environments. However, it should be treated as a mapping layer rather than a base entity: consumers requiring authoritative data should join to PER_POSITION_EXTRA_INFO or GHR_PA_HISTORY as appropriate, using PA_HISTORY_ID or POSITION_EXTRA_INFO_ID as the linking keys.