Search Results ghr_event_history




Overview
Explore in AI Chat

Overview

The GHR_EVENT_HISTORY table is a core transactional object within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a detailed audit and process tracking log, specifically designed to record the sequence of events that occur during two critical federal HR processes: the Request for Personnel Action (RPA) workflow and the definition or modification of a Position. By maintaining a chronological history of these events, the table provides essential traceability, supports compliance reporting, and enables process monitoring for federal personnel actions, which are governed by stringent regulatory requirements.

Key Information Stored

The table's primary purpose is to capture discrete events with associated metadata. While the full column list is not detailed in the provided metadata, its structure is anchored by key identifiers. The primary key column, EVENT_HISTORY_ID, ensures each recorded event is unique. A critical foreign key column, EVENT_ID, links each history record to its corresponding event definition in the related GHR_EVENTS table. Typical data stored in such a history table would include timestamps of when the event occurred, the type of action performed, the user or process responsible for the action, the system status before and after the event, and references to the specific RPA or Position being acted upon. This creates a complete audit trail for each transaction.

Common Use Cases and Queries

This table is primarily accessed for auditing, troubleshooting, and generating process status reports. Common use cases include reconstructing the complete lifecycle of an RPA to understand approval delays, verifying procedural compliance for an audit, and diagnosing errors in a stalled position definition. A typical query would join GHR_EVENT_HISTORY to GHR_EVENTS to get the human-readable event name and filter for a specific RPA or Position ID to see its entire history. For example:

  • SELECT eh.event_history_id, e.event_name, eh.creation_date FROM hr.ghr_event_history eh, hr.ghr_events e WHERE eh.event_id = e.event_id AND eh.rpa_id = :p_rpa_num ORDER BY eh.creation_date;
  • Reporting on the frequency and duration of specific event types across all RPAs in a given period.
  • Identifying all positions that triggered a specific error event during their definition process.

Related Objects

The GHR_EVENT_HISTORY table has documented dependencies within the GHR schema. Its primary relationship is defined by a foreign key constraint linking its EVENT_ID column to the GHR_EVENTS table. This indicates that for every record in the history, the EVENT_ID must correspond to a valid, predefined event type in the GHR_EVENTS lookup table. While not listed in the provided excerpt, it is architecturally certain that GHR_EVENT_HISTORY would also contain foreign keys (such as RPA_ID or POSITION_ID) linking directly to the main transactional tables it audits, like GHR_REQUEST_PERSON_ACTIONS for RPAs. This table is likely referenced by various GHR process APIs and standard audit reports within the federal HR product.