Search Results ghr_routing_lists




Overview
Explore in AI Chat

Overview

The GHR_ROUTING_LISTS 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. It functions as the master definition table for routing lists, which are critical components of the workflow and approval processes for federal personnel actions. A routing list defines a specific sequence or group of individuals or positions responsible for reviewing and approving personnel documents, such as Position Descriptions (PDs) or Personnel Actions (PAs). The table's primary role is to store the unique identifier and name for each configured routing list, providing a central reference point for the GHR module's routing and approval engine.

Key Information Stored

The table's structure, as indicated by its primary and unique keys, is designed to ensure the integrity and uniqueness of routing list definitions. The most critical columns include the system-generated primary key, ROUTING_LIST_ID, which uniquely identifies each list across the system. The NAME column holds the unique, user-defined identifier for the routing list, such as "HQ_PD_APPROVAL" or "REGION_A_HIRING_MGRS." The table also contains a foreign key column, ROUTING_GROUP_ID, which links the list to its parent grouping in the GHR_ROUTING_GROUPS table, allowing for logical organization of multiple routing lists.

Common Use Cases and Queries

This table is primarily referenced in scenarios involving the setup, audit, and troubleshooting of approval workflows. Common use cases include generating a master list of all defined routing lists for configuration review or identifying which lists are associated with a specific routing group. A typical query would join GHR_ROUTING_LISTS with GHR_ROUTING_GROUPS to provide a comprehensive view.

  • Sample Query: SELECT grl.ROUTING_LIST_ID, grl.NAME, grg.GROUP_NAME FROM HR.GHR_ROUTING_LISTS grl JOIN HR.GHR_ROUTING_GROUPS grg ON grl.ROUTING_GROUP_ID = grg.ROUTING_GROUP_ID ORDER BY grg.GROUP_NAME, grl.NAME;
  • Reporting Use Case: This table serves as a key dimension in historical reporting on approval timelines. Analysts can join GHR_ROUTING_LISTS with history tables (like GHR_PA_ROUTING_HISTORY) to analyze the efficiency and usage patterns of different approval chains over time.

Related Objects

As shown in the foreign key metadata, GHR_ROUTING_LISTS has integral relationships with several other GHR tables, forming the backbone of the routing architecture. It is a child of GHR_ROUTING_GROUPS. Crucially, it is a parent table to the member detail table GHR_ROUTING_LIST_MEMBERS, which stores the actual approvers (e.g., person_id, position_id) in sequence. Furthermore, the routing list is linked to transactional history through the GHR_PA_ROUTING_HISTORY and GHR_PD_ROUTING_HISTORY tables, which record each instance where a specific routing list was used in the approval process for a Personnel Action or Position Description, respectively.