Search Results ghr_pa_history




Overview
Explore in AI Chat

Overview

The GHR_PA_HISTORY table is a core data object within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. As a table in the HR schema, its primary function is to serve as a comprehensive audit and historical log. It permanently stores a record of all transactions performed on specific, related tables within the GHR module. This design is critical for maintaining a complete, immutable audit trail for personnel actions (PA), which is a fundamental requirement for federal HR compliance and reporting. The table enables historical analysis, supports audit inquiries, and provides the data necessary to reconstruct the sequence of changes to personnel records over time.

Key Information Stored

The table's structure is centered on linking transaction records to the specific personnel action requests that generated them. Its primary key is the system-generated PA_HISTORY_ID, which uniquely identifies each historical entry. The most significant foreign key columns define its core relationships: PA_REQUEST_ID links the history entry directly to its source transaction in the GHR_PA_REQUESTS table. The NATURE_OF_ACTION_ID column associates the history with a specific type of personnel action (e.g., hire, promotion, termination) as defined in the GHR_NATURE_OF_ACTIONS table. Notably, the ALTERED_PA_REQUEST_ID column provides a link to a modified or subsequent personnel action request, allowing the system to track chains of related transactions and amendments. While the provided metadata does not list all columns, the table inherently stores details such as the before-and-after values of changed data, the effective date of the change, and likely timestamps and identifiers for the initiating user or process.

Common Use Cases and Queries

The primary use case for GHR_PA_HISTORY is auditing and historical reporting on personnel actions. Federal HR analysts use this data to verify the correctness of personnel records, investigate the history of an employee's position or pay changes, and generate compliance reports. A typical query would join this table to GHR_PA_REQUESTS and GHR_NATURE_OF_ACTIONS to produce a human-readable audit log.

  • Sample Query for Transaction History:
    SELECT gph.PA_HISTORY_ID, gpr.PA_REQUEST_NUMBER, gnoa.NATURE_OF_ACTION_CODE, gph.EFFECTIVE_DATE
    FROM HR.GHR_PA_HISTORY gph
    JOIN HR.GHR_PA_REQUESTS gpr ON gph.PA_REQUEST_ID = gpr.PA_REQUEST_ID
    JOIN HR.GHR_NATURE_OF_ACTIONS gnoa ON gph.NATURE_OF_ACTION_ID = gnoa.NATURE_OF_ACTION_ID
    WHERE gpr.PERSON_ID = :person_id
    ORDER BY gph.EFFECTIVE_DATE DESC;
  • Use Case: Reconstructing the complete history of all personnel actions for a specific employee for a records review or audit.
  • Use Case: Identifying all transactions of a specific nature of action (e.g., separations) that occurred within a given timeframe for agency-wide reporting.

Related Objects

GHR_PA_HISTORY is intrinsically linked to several key tables in the GHR module, forming a central part of the personnel action transaction model.

  • GHR_PA_REQUESTS: This is the primary parent table. GHR_PA_HISTORY records the transactional outcome of requests stored here, linked via PA_REQUEST_ID and ALTERED_PA_REQUEST_ID.
  • GHR_NATURE_OF_ACTIONS: A critical reference table that classifies the type of each recorded transaction via the NATURE_OF_ACTION_ID foreign key.
  • GHR_PA_HISTORY_PK: The primary key constraint ensuring the uniqueness of each history record.
  • While not listed in the metadata, it is highly probable that custom reports, Oracle Business Intelligence (OBIEE) subject areas, and standard GHR APIs will reference or populate this table to fulfill audit and reporting requirements.