Results for “ghr_routing_groups_uk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR.GHR_ROUTING_GROUPS is a seed data table within the Oracle E-Business Suite HR schema that stores routing group definitions used by the Oracle Human Resources (HRMS) routing and approval framework. The object is registered under FND Design Data as GHR.GHR_ROUTING_GROUPS and holds a status of VALID in both 12.1.1 and 12.2.2. It resides in the APPS_TS_SEED tablespace with a PCT Free of 10, reflecting its role as relatively static configuration data rather than high-volume transactional data.

A routing group functions as a logical container that governs how routing lists, groupboxes, position descriptions, and personnel action requests are organized and directed through approval workflows. From a Data Vault modeling perspective, the metadata's heuristic classification is hub-leaning: ROUTING_GROUP_ID behaves as a durable business key, and the table chiefly records the existence of routing group entities rather than transactional state or time-variant attributes. The two descriptive columns (NAME, DESCRIPTION) are limited in scope, which reinforces the hub interpretation; a satellite construct would normally be created to hold those descriptive attributes separately.

Key Information Stored

The table comprises eight documented columns. The most significant are:

• ROUTING_GROUP_ID — NUMBER(15), the surrogate primary key generated from the sequence GHR_ROUTING_GROUPS_S. This is the value most users search for when they enter "routing_group_id" into a query tool.
• NAME — VARCHAR2(30), the business name of the routing group. This column is backed by the unique index GHR_ROUTING_GROUPS_UK, making NAME the documented business-key candidate alongside the surrogate key.
• DESCRIPTION — VARCHAR2(100), free-text description of the routing group's purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard Oracle "WHO" audit columns, populated automatically by the GHR_ROUTING_GROUPS_WHO database trigger attached to the table.

The distinction between the surrogate key (ROUTING_GROUP_ID) and the business key (NAME) is important when integrating with external systems or when performing upserts; joins across the EBS HR schema consistently use ROUTING_GROUP_ID rather than NAME.

Common Use Cases and Queries

Typical scenarios include verifying which routing group a personnel action request belongs to, auditing groupbox configuration, and reconciling routing lists against their parent groups. A straightforward lookup by surrogate key is:

• SELECT routing_group_id, name, description FROM hr.ghr_routing_groups WHERE routing_group_id = :p_id;
• SELECT routing_group_id, name FROM hr.ghr_routing_groups WHERE UPPER(name) LIKE UPPER(:p_name||'%');
• SELECT p.pa_request_id, g.name FROM hr.ghr_pa_requests p JOIN hr.ghr_routing_groups g ON p.routing_group_id = g.routing_group_id;
• SELECT l.routing_list_id, g.name FROM hr.ghr_routing_lists l JOIN hr.ghr_routing_groups g ON l.routing_group_id = g.routing_group_id;

Reporting queries frequently aggregate child records to count how many groupboxes, position descriptions, or routing lists are attached to each routing group. Because the table is seed data, changes are typically delivered through patch or setup, not end-user DML.

Related Objects

Four child tables reference this table through the ROUTING_GROUP_ID foreign key column:

• HR.GHR_GROUPBOXES — groupboxes assigned to a routing group; join on ROUTING_GROUP_ID.
• HR.GHR_PA_REQUESTS — personnel action requests routed through the group; join on ROUTING_GROUP_ID.
• HR.GHR_POSITION_DESCRIPTIONS — position descriptions linked to a routing group; join on ROUTING_GROUP_ID.
• HR.GHR_ROUTING_LISTS — the routing lists that execute within a group; join on ROUTING_GROUP_ID.

The APPS synonym GHR_ROUTING_GROUPS exposes the table to application code, while the trigger GHR_ROUTING_GROUPS_WHO maintains its audit columns. The table does not itself reference any parent database object, confirming its position as a top-level hub in the routing configuration model.