Results for “ghr_groupboxes”

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

Overview

GHR_GROUPBOXES is a transactional configuration table owned by the HR schema and delivered as part of the GHR — US Federal Human Resources product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores the definitions of groupboxes that are consumed by the Oracle Workflow engine for routing and notification purposes within federal HR processing. In functional terms, a groupbox represents a named distribution group: a container that binds a set of recipients to a routing construct so that workflow-generated notifications, approvals, and disbursements can be addressed to the group rather than to individual users.

From a dimensional modeling perspective, the ETRM heuristic classifies GHR_GROUPBOXES as a hub. This is a suggested classification derived from the foreign key topology: the table carries a single-column surrogate primary key and a unique business key, and it is referenced by multiple downstream tables, which is characteristic of a hub entity in a Data Vault model. Analysts building a vault layer should treat GROUPBOX_ID as the hub key and NAME as the business key, with descriptive attributes (display name, description, e-mail address) modeled as a satellite.

Key Information Stored

The table comprises eleven documented columns. The most significant are the following:

• GROUPBOX_ID — the surrogate primary key, enforced by the GHR_GROUPBOXES_PK index. It uniquely identifies each groupbox record and is the column propagated into all child tables.
• NAME — the business key, enforced by the unique index GHR_GROUPBOXES_UK1. It provides the human-readable, system-unique identifier for the groupbox and is the value users recognize when selecting a routing target.
• ROUTING_GROUP_ID — the foreign key to GHR_ROUTING_GROUPS. It ties each groupbox to its parent routing definition, establishing the grouping hierarchy used by the workflow engine.
• DISPLAY_NAME — the label presented in the user interface, which may differ from the internal NAME.
• DESCRIPTION — free-text explanation of the groupbox purpose, typically used for administrative reference.
• EMAIL_ADDRESS — the distribution address associated with the groupbox, used when workflow notifications are delivered by e-mail rather than by in-application notification.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard Oracle EBS WHO columns that provide the audit trail for record creation and modification.

The distinction between the surrogate key (GROUPBOX_ID) and the business key (NAME) is important for integration: external interfaces should resolve to GROUPBOX_ID before writing child records, while end users and reporting layers typically operate on NAME or DISPLAY_NAME.

Common Use Cases and Queries

The principal use case is administrative: determining which groupboxes exist, which routing group each belongs to, and which recipients are attached. A typical query joining the parent routing group is:

• SELECT g.GROUPBOX_ID, g.NAME, g.DISPLAY_NAME, r.NAME FROM HR.GHR_GROUPBOXES g, HR.GHR_ROUTING_GROUPS r WHERE g.ROUTING_GROUP_ID = r.ROUTING_GROUP_ID;

Investigating group membership for a specific groupbox requires joining to GHR_GROUPBOX_USERS on GROUPBOX_ID, which yields the set of users who receive notifications. Audit and troubleshooting scenarios frequently join to GHR_PA_ROUTING_HISTORY and GHR_PD_ROUTING_HISTORY to reconstruct which groupbox was targeted during a historical routing event. Personal-information and routing-list scenarios similarly traverse GHR_POIS and GHR_ROUTING_LIST_MEMBERS via GROUPBOX_ID. Reporting on dormancy or duplication is also common, since the NAME uniqueness constraint means any apparent duplicate indicates a data-quality or interface defect.

Related Objects

GHR_GROUPBOXES participates in a well-defined set of relationships in the HR schema:

• GHR_ROUTING_GROUPS — referenced by GHR_GROUPBOXES.ROUTING_GROUP_ID; the parent routing definition.
• GHR_GROUPBOX_USERS — references GHR_GROUPBOXES.GROUPBOX_ID; holds the user membership of each groupbox.
• GHR_PA_ROUTING_HISTORY — references GHR_GROUPBOXES.GROUPBOX_ID; captures personnel-action routing history.
• GHR_PD_ROUTING_HISTORY — references GHR_GROUPBOXES.GROUPBOX_ID; captures position-description routing history.
• GHR_POIS — references GHR_GROUPBOXES.GROUPBOX_ID; links groupboxes to personal information records.
• GHR_ROUTING_LIST_MEMBERS — references GHR_GROUPBOXES.GROUPBOX_ID; associates groupboxes with routing list membership.

These dependencies confirm the hub role of the table: it is a widely referenced parent whose surrogate key anchors routing, membership, and history data across the GHR module. Deletion or renumbering of GROUPBOX_ID values would therefore ripple through the entire routing subsystem, and any purge activity should respect these referential constraints.