Search Results ghr_routing_groups_pk




Overview
Explore in AI Chat

Overview

The GHR_ROUTING_GROUPS table is a core reference table within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS). It serves as a master repository for defining and managing routing groups, which are logical collections of approvers or reviewers used in the federal personnel action workflow. The table's primary role is to provide a centralized definition of a routing group, identified by a unique name and a system-generated ID. This definition is then referenced by various transactional and configuration objects across the GHR module to control the routing and approval flow for documents such as personnel action requests and position descriptions, ensuring compliance with federal agency-specific business rules.

Key Information Stored

The table's structure is designed to uniquely identify and describe each routing group. The most critical columns, as indicated by the provided metadata, are the primary key columns. The ROUTING_GROUP_ID column is the system-generated, numeric primary key (GHR_ROUTING_GROUPS_PK) used for all internal foreign key relationships. The NAME column holds the unique, user-defined identifier for the routing group (enforced by the GHR_ROUTING_GROUPS_UK unique key) and is the value typically presented in application user interfaces. While the explicit metadata does not list other columns, a typical implementation would likely include standard Oracle columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY for auditing purposes.

Common Use Cases and Queries

This table is central to configuring and analyzing approval workflows. Common use cases include administrative setup of new routing groups, troubleshooting workflow issues by verifying group definitions, and generating reports on which routing groups are assigned to various documents. A fundamental query to retrieve all defined routing groups is: SELECT routing_group_id, name FROM ghr_routing_groups ORDER BY name;. To investigate the usage of a specific routing group, a developer or analyst might join to related tables: SELECT rg.name, COUNT(pd.position_description_id) AS pd_count FROM ghr_routing_groups rg LEFT JOIN ghr_position_descriptions pd ON rg.routing_group_id = pd.routing_group_id GROUP BY rg.name, rg.routing_group_id;. This helps identify groups that are unused or heavily utilized.

Related Objects

As per the foreign key relationships documented, the GHR_ROUTING_GROUPS table is a parent to several key transactional and setup tables. The ROUTING_GROUP_ID column is referenced by:

  • GHR_GROUPBOXES: Links routing groups to specific groupboxes (logical containers for routing list members).
  • GHR_PA_REQUESTS: Associates a personnel action request with a specific routing group for its approval chain.
  • GHR_POSITION_DESCRIPTIONS: Assigns a routing group to control the review/approval workflow for a position description.
  • GHR_ROUTING_LISTS: Defines the specific sequence of approvers (the routing list members) that belong to a given routing group.
This network of relationships positions GHR_ROUTING_GROUPS as a critical hub in the GHR module's workflow architecture.