Search Results ghr_pa_routing_history




Overview
Explore in AI Chat

Overview

The GHR_PA_ROUTING_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. It functions as a detailed audit and tracking log for the routing workflow of Personnel Action (PA) Requests. In the context of federal HR processes, a PA Request represents a formal proposal for a personnel action, such as a promotion or reassignment, which must be reviewed and approved through a defined chain of authority. This table records the complete chronological history of a request's movement through its approval routing list, capturing each stage, responsible party, and associated action details. Its role is critical for compliance, reporting, and providing transparency into the request's lifecycle.

Key Information Stored

The table stores transactional history linked to a specific PA Request. Its primary key is the system-generated identifier, PA_ROUTING_HISTORY_ID. The most significant foreign key is PA_REQUEST_ID, which ties each history record to its parent request in the GHR_PA_REQUESTS table. Other essential foreign keys define the context of the routing event: ROUTING_LIST_ID (GHR_ROUTING_LISTS), GROUPBOX_ID (GHR_GROUPBOXES), and the NATURE_OF_ACTION_ID and SECOND_NATURE_OF_ACTION_ID (GHR_NATURE_OF_ACTIONS). The NOA_FAMILY_CODE, linked to GHR_FAMILIES, further categorizes the nature of action. While the provided metadata does not list all columns, typical data would include timestamps for routing events, the action taken (e.g., forwarded, approved, returned), the ID of the user or position who acted, and potentially comments.

Common Use Cases and Queries

This table is primarily used for audit reporting and process analysis. Common scenarios include generating a complete audit trail for a specific PA Request, analyzing routing bottlenecks, and verifying procedural compliance. A fundamental query retrieves the full routing history for a request, often joined with descriptive tables for clarity.

  • Sample Query - Full Routing History for a Request:
    SELECT rh.*, rl.ROUTING_LIST_NAME, noa.NATURE_OF_ACTION
    FROM HR.GHR_PA_ROUTING_HISTORY rh,
    HR.GHR_ROUTING_LISTS rl,
    HR.GHR_NATURE_OF_ACTIONS noa
    WHERE rh.PA_REQUEST_ID = :p_request_id
    AND rh.ROUTING_LIST_ID = rl.ROUTING_LIST_ID(+)
    AND rh.NATURE_OF_ACTION_ID = noa.NATURE_OF_ACTION_ID(+)
    ORDER BY rh.CREATION_DATE;
  • Use Case - Process Duration Analysis: Analysts query this table to calculate the time a request spent at each routing step or with each group, identifying stages that cause delays.

Related Objects

GHR_PA_ROUTING_HISTORY is centrally connected to several key GHR tables via foreign key constraints, forming the backbone of the PA request workflow.

  • GHR_PA_REQUESTS: The parent table for all personnel action requests.
  • GHR_ROUTING_LISTS: Defines the sequence of approval steps (the routing list) assigned to a request.
  • GHR_GROUPBOXES: Represents the organizational groups (e.g., offices, divisions) involved in the routing process.
  • GHR_NATURE_OF_ACTIONS: Provides the descriptive code and meaning for the primary and secondary personnel actions.
  • GHR_FAMILIES: Categorizes nature of actions into broader families for reporting and rule definition.