Results for “altered_pa_request_id”

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

Overview

The view APPS.GHR_ELEMENT_ENTRY_VALUES_H_V is a history-mapping construct within the GHR — US Federal Human Resources product family in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in ETRM metadata, its stated purpose is the "Mapping of GHR_PA_HISTORY columns to PAY_ELEMENT_ENTRY_VALUES_F." In practice, the view exposes the audit and history trail captured in GHR_PA_HISTORY, filtered to rows whose TABLE_NAME equals 'PAY_ELEMENT_ENTRY_VALUES_F', and projects those archived values into a shape that resembles the element entry values entity.

The view does not store data. It is a read-only projection over the personnel action (PA) history framework, allowing consumers to inspect prior and current values of element entry value rows as they were affected by personnel actions. This makes it useful for audit reporting, retroactive change analysis, and integration where a reconstructed view of element entry value history is required without querying the history table directly.

Underlying Base Objects

The documented referenced base objects are:

• GHR_PA_HISTORY (synonym) — the source history table. All rows are drawn from this object, qualified by TABLE_NAME = 'PAY_ELEMENT_ENTRY_VALUES_F'.
• GHR_GENERAL (package) — supplies the RETURN_NUMBER function used to convert character-encoded INFORMATIONn columns into numeric identifiers.
• FND_DATE (package) — supplies CANONICAL_TO_DATE, used to convert canonically stored date strings into true DATE values.

The view therefore sits atop the generic PA history mechanism. The history table stores heterogeneous records in a denormalized INFORMATION1 through INFORMATION6 character columns plus a set of standard history attributes (process date, effective date, DML operation, request identifiers). The view's SELECT casts each INFORMATIONn column to its semantically correct type and renames it to its business meaning.

Key Columns

The view exposes the standard history attributes alongside the decoded value columns:

• PA_HISTORY_ID — primary identifier of the history record; the column users search for as pa_history_id.
• PROCESS_DATE, EFFECTIVE_DATE — when the history row was processed and its effective date.
• DML_OPERATION — the operation performed (insert, update, delete) on the underlying element entry value.
• PRE_VALUES_FLAG — indicates whether the row captures pre-change (prior) values or the new values.
• ALTERED_PA_REQUEST_ID, PA_REQUEST_ID, NATURE_OF_ACTION_ID — linkage to the personnel action request and the nature of action that produced the change.
• ELEMENT_ENTRY_VALUE_ID — derived via GHR_GENERAL.RETURN_NUMBER(INFORMATION1); the element entry value identifier.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — derived via FND_DATE.CANONICAL_TO_DATE(INFORMATION2/INFORMATION3); the date-effective bounds of the entry value.
• INPUT_VALUE_ID, ELEMENT_ENTRY_ID — derived via RETURN_NUMBER(INFORMATION4/INFORMATION5); the input value and element entry references.
• SCREEN_ENTRY_VALUE — SUBSTR(INFORMATION6, 1, 60); the user-entered display value, truncated to 60 characters.

Common Use Cases and Queries

Typical usage includes auditing element entry value changes tied to a personnel action, comparing pre-change and post-change values, and joining history back to the live element entry values for reconciliation. A representative query retrieves all history for a given element entry value:

• Filter by ELEMENT_ENTRY_VALUE_ID and order by PROCESS_DATE or PA_HISTORY_ID to reconstruct the change timeline.
• Filter by PRE_VALUES_FLAG = 'Y' to isolate prior values, or by DML_OPERATION to isolate deletes or updates.
• Join PA_REQUEST_ID to personnel action request tables to attribute changes to a specific action.

Because transformations occur at query time via packaged functions, consumers should expect the view to execute those conversions on every row retrieved; filtering on decoded columns therefore benefits from prior restriction on PA_HISTORY_ID or date ranges. The view remains a valid, read-only reporting and integration asset in both 12.1.1 and 12.2.2.