Results for “ghr_groupboxes_uk1”

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

Overview

HR.GHR_GROUPBOXES is a seed data table in the Oracle E-Business Suite HR schema that defines the group boxes available to the Oracle Workflow routing infrastructure. A group box represents a named distribution container associated with an e-mail address, allowing notification and approval routing to be driven by logical groupings rather than by individual recipients. The table resides in the APPS_TS_SEED tablespace, confirming its role as a repository for seeded configuration data referenced across routing and notification processes.

The table is structured as a hub in a Data Vault modeling sense, based on its foreign key topology. It carries a single-column surrogate primary key, GROUPBOX_ID, and its foreign keys point outward to GHR_ROUTING_GROUPS, while five dependent tables (GHR_GROUPBOX_USERS, GHR_PA_ROUTING_HISTORY, GHR_PD_ROUTING_HISTORY, GHR_POIS, and GHR_ROUTING_LIST_MEMBERS) reference back to it through GROUPBOX_ID. This hub classification should be treated as a heuristic modeling suggestion derived from the FK structure rather than a documented architectural decision.

Key Information Stored

The table contains eleven documented columns. The most important are:

• GROUPBOX_ID — NUMBER(15). The primary key, generated from the sequence GHR_GROUPBOXES_S. This is the surrogate identifier referenced by all dependent child tables.
• ROUTING_GROUP_ID — NUMBER(15). Foreign key to GHR_ROUTING_GROUPS, placing each group box within a broader routing group hierarchy.
• NAME — VARCHAR2(30). The group box name and the business-key candidate, enforced by the unique index GHR_GROUPBOXES_UK1.
• DISPLAY_NAME — VARCHAR2(80). The user-facing name presented in routing and notification interfaces.
• DESCRIPTION — VARCHAR2(100). Free-text description of the group box purpose.
• EMAIL_ADDRESS — VARCHAR2(240). The e-mail address associated with the group box, used when routing notifications are delivered to the group.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard Oracle "Who" audit columns tracking creation and modification metadata.

The distinction between the surrogate primary key (GROUPBOX_ID) and the business-key candidate (NAME via GHR_GROUPBOXES_UK1) is significant: integration and data migration efforts should resolve group boxes by NAME, while all FK relationships and API calls should use GROUPBOX_ID.

Common Use Cases and Queries

Typical uses include reporting on configured group boxes, validating routing group membership, and troubleshooting notification delivery failures. A standard lookup joins the group box to its routing group:

SELECT gb.GROUPBOX_ID, gb.NAME, gb.DISPLAY_NAME, gb.EMAIL_ADDRESS, rg.NAME routing_group FROM HR.GHR_GROUPBOXES gb, HR.GHR_ROUTING_GROUPS rg WHERE gb.ROUTING_GROUP_ID = rg.ROUTING_GROUP_ID;

To identify group boxes that have no users assigned—a frequent cause of undelivered notifications—an outer join to GHR_GROUPBOX_USERS is effective:

SELECT gb.GROUPBOX_ID, gb.NAME FROM HR.GHR_GROUPBOXES gb, HR.GHR_GROUPBOX_USERS gu WHERE gb.GROUPBOX_ID = gu.GROUPBOX_ID(+) AND gu.GROUPBOX_ID IS NULL;

Historical diagnostics can traverse GHR_PA_ROUTING_HISTORY and GHR_PD_ROUTING_HISTORY by GROUPBOX_ID to reconstruct which group received a given notification.

Related Objects

• GHR_ROUTING_GROUPS — parent of GHR_GROUPBOXES via ROUTING_GROUP_ID.
• GHR_GROUPBOX_USERS — child table mapping users to group boxes through GROUPBOX_ID.
• GHR_ROUTING_LIST_MEMBERS — child table associating routing list members with group boxes via GROUPBOX_ID.
• GHR_POIS — child table referencing group boxes through GROUPBOX_ID, typically for point-of-contact or notification integration.
• GHR_PA_ROUTING_HISTORY and GHR_PD_ROUTING_HISTORY — historical routing tables storing GROUPBOX_ID to record past notification distribution.

The unique index GHR_GROUPBOXES_UK1 on NAME and the non-unique index GHR_GROUPBOXES_FK1 on ROUTING_GROUP_ID both reside in APPS_TS_SEED, supporting efficient lookups by business key and by parent routing group respectively.