Search Results ghr_events_uk

Overview

The GHR_EVENTS table is a core data object within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. As indicated by its description, its primary function is to store various events. In the context of federal HR, these events typically represent significant occurrences or transactions within an employee's service record, such as appointments, separations, transfers, or pay adjustments. The table serves as a master repository for event definitions and metadata, enabling the structured processing and tracking of personnel actions and other critical HR workflows mandated for US federal government agencies.

Key Information Stored

Based on the provided ETRM metadata, the table's structure centers on a unique event identifier and a code. The primary key constraint GHR_EVENTS_PK is defined on the EVENT_ID column, ensuring each record is uniquely identifiable. A separate unique key constraint, GHR_EVENTS_UK, is enforced on the CODE column, indicating that the event code itself must also be unique within the system. This suggests CODE is a critical business identifier for events. The foreign key relationship reveals that the table also contains a column named GHR_EVENTS_PA_REQUEST_ID (or a similarly named column referenced by this foreign key), which links the event to a specific personnel action request in the GHR_PA_REQUESTS table, establishing a direct connection between an event definition and its initiating administrative action.

Common Use Cases and Queries

This table is fundamental for queries that need to list or validate defined event types within the federal HR system. Common use cases include generating lookup lists for application forms, validating input for personnel action processing, and supporting reporting on event frequencies. A typical query would retrieve the event code and description for reference, often joined to related request data. For example:

• SELECT code, <description_column> FROM hr.ghr_events WHERE <condition> ORDER BY code;
• Joining to the related personnel action request table: SELECT e.code, pr.request_number FROM hr.ghr_events e, hr.ghr_pa_requests pr WHERE e.pa_request_id = pr.pa_request_id; (assuming column name mappings).

The table is also the parent for the GHR_EVENT_HISTORY table, meaning queries tracking the historical instances or status changes of specific events would originate from GHR_EVENTS.

Related Objects

The ETRM documentation explicitly defines two key relationships for the GHR_EVENTS table. First, it has a foreign key relationship with the GHR_PA_REQUESTS table, linking events to the personnel action requests that trigger them. Second, it is the parent table referenced by the GHR_EVENT_HISTORY table via the EVENT_ID column, indicating that GHR_EVENT_HISTORY stores transactional or status records associated with each master event definition. These relationships position GHR_EVENTS as a central reference point between the request initiation (GHR_PA_REQUESTS) and the subsequent event tracking history (GHR_EVENT_HISTORY) within the GHR module's data model.