Search Results routing_group_id




Overview
Explore in AI Chat

Overview

The HR.GHR_ROUTING_GROUPS table is a core reference table within the Oracle E-Business Suite (EBS) Global Human Resources (GHR) module, specifically for versions 12.1.1 and 12.2.2. It functions as a master repository for defining distinct routing groups. In the context of GHR's workflow and approval processes, a routing group is a logical container that associates a specific type of personnel action or request with a predefined list of approvers or reviewers. This table's primary role is to provide a centralized, unique definition for these groups, which are then referenced by various transactional entities to enforce consistent approval routing logic across the application.

Key Information Stored

The table stores the essential metadata for each routing group definition. The primary and most critical column is ROUTING_GROUP_ID, a mandatory 15-digit numeric primary key uniquely identifying each record, populated from the sequence GHR_ROUTING_GROUPS_S. The NAME column is a mandatory 30-character unique identifier for the group, serving as the primary user-facing key. A DESCRIPTION field of up to 100 characters allows for a more detailed explanation of the group's purpose. As with most EBS tables, it includes standard "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing and tracking record history.

Common Use Cases and Queries

This table is central to configuring and auditing approval workflows. Common use cases include administrative setup of new routing groups for different personnel action types, troubleshooting workflow issues by verifying group definitions, and generating reports on all configured routing paths. A fundamental query to retrieve all routing groups is directly provided by the ETRM:

SELECT ROUTING_GROUP_ID, NAME, DESCRIPTION, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE FROM HR.GHR_ROUTING_GROUPS;

To find a specific group by its user-friendly name or to validate its existence (often a precursor to linking it in a transaction), a query filtering on the NAME column is typical. Integration and data migration scripts will heavily reference the ROUTING_GROUP_ID to maintain referential integrity when populating dependent transactional tables.

Related Objects

HR.GHR_ROUTING_GROUPS is a parent table referenced by several key transactional tables via foreign key relationships on the ROUTING_GROUP_ID column, demonstrating its central role. As per the metadata, these dependent objects include:

  • GHR_GROUPBOXES: Likely links routing groups to specific UI containers or functional areas.
  • GHR_PA_REQUESTS: Associates personnel action requests with a specific approval routing group.
  • GHR_POSITION_DESCRIPTIONS: Ties position description records to their designated approval routing.
  • GHR_ROUTING_LISTS: The most direct relationship; this table stores the ordered list of approvers (e.g., by position or person) for a given ROUTING_GROUP_ID.
The table is indexed via a unique primary key (GHR_ROUTING_GROUPS_PK on ROUTING_GROUP_ID) and a unique key (GHR_ROUTING_GROUPS_UK on NAME) to ensure data integrity and performance.