Search Results ghr_pd_routing_history




Overview
Explore in AI Chat

Overview

The GHR_PD_ROUTING_HISTORY table is a core data object within the Oracle E-Business Suite US Federal Human Resources (GHR) module, specifically for releases 12.1.1 and 12.2.2. It serves as a detailed audit and tracking log for the routing and approval workflow of Position Descriptions (PDs). In the federal HR context, a Position Description is a critical document defining a job's duties, responsibilities, and qualifications. The routing process involves circulating this document through a series of reviewers and approvers, often defined by organizational hierarchies or specific routing lists. This table captures the complete historical record of each step in that workflow, enabling compliance reporting, process transparency, and status tracking for every Position Description.

Key Information Stored

The table's primary purpose is to chronicle routing events. Its structure is centered on linking a Position Description to its routing path and recording the action taken. The primary key, PD_ROUTING_HISTORY_ID, uniquely identifies each historical entry. The most critical foreign key columns define the core relationships: POSITION_DESCRIPTION_ID links to the specific PD in the GHR_POSITION_DESCRIPTIONS table; ROUTING_LIST_ID references the predefined list of approvers in GHR_ROUTING_LISTS; and GROUPBOX_ID connects to the organizational group or "box" in GHR_GROUPBOXES from which an approver may be drawn. Additional columns typically store data such as the sequence of the routing step, the action performed (e.g., "APPROVED", "RETURNED"), the person who took the action, associated comments, and timestamps for each event.

Common Use Cases and Queries

This table is essential for audit reports, workflow analysis, and user inquiries into PD status. A common use case is generating a complete audit trail for a specific Position Description to demonstrate compliance with federal personnel procedures. Another is analyzing routing bottlenecks by examining the time between sequential history entries. A typical query would join GHR_PD_ROUTING_HISTORY to GHR_POSITION_DESCRIPTIONS to retrieve the routing history for all PDs associated with a particular organization or document number. For example:

  • SELECT pd.document_number, rh.* FROM ghr_pd_routing_history rh, ghr_position_descriptions pd WHERE rh.position_description_id = pd.position_description_id AND pd.document_number = 'PD-12345' ORDER BY rh.creation_date;

This provides a chronological log of all routing actions for the specified document.

Related Objects

The GHR_PD_ROUTING_HISTORY table is centrally connected to several key GHR tables via documented foreign key relationships. These relationships are fundamental to its integrity and reporting utility.

  • GHR_POSITION_DESCRIPTIONS: The parent table for the Position Description itself. Joined via GHR_PD_ROUTING_HISTORY.POSITION_DESCRIPTION_ID.
  • GHR_ROUTING_LISTS: The table defining the list of individuals or roles in an approval sequence. Joined via GHR_PD_ROUTING_HISTORY.ROUTING_LIST_ID.
  • GHR_GROUPBOXES: The table storing organizational group structures used in federal routing. Joined via GHR_PD_ROUTING_HISTORY.GROUPBOX_ID.

These relationships ensure that every entry in the routing history is explicitly tied to a valid PD, a defined routing path, and an organizational context.