Results for “ghr_groupbox_users_uk”

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

Overview

HR.GHR_GROUPBOX_USERS is a seed-data table within the Oracle EBS Human Resources (HR) schema that defines the membership roster of a Groupbox. A Groupbox is the logical container used by the HR security and workflow infrastructure to bundle a set of users together with a defined set of functional roles, allowing the same population to be granted initiator, requester, approver, or reviewer privileges across multiple business flows without redefining the membership each time. The table is registered in the application dictionary under the design data reference GHR.GHR_GROUPBOX_USERS and carries a status of VALID at 12.1.1 and 12.2.2. It resides in the APPS_TS_SEED tablespace, consistent with its role as setup and reference data rather than transactional data.

From a dimensional modeling perspective, the heuristic Data Vault classification for this object is satellite-leaning: it describes the attributes and role assignments of members belonging to a parent Groupbox, rather than acting as an independent business hub. The parent entity is represented by HR.GHR_GROUPBOXES, and this table functions as a dependent, descriptive record hanging from that parent. Modeling exercises that reconstruct a raw vault would typically treat the Groupbox as the hub and this table as its satellite.

Key Information Stored

The table contains fourteen documented columns. The most significant are:

• GROUPBOX_USER_ID — the surrogate primary key of the table, defined by the unique index GHR_GROUPBOX_USERS_PK and populated from the sequence GHR_GROUPBOX_USERS_S. This is the column most commonly referenced by the search term groupbox_user_id.
• GROUPBOX_ID — a mandatory foreign key to HR.GHR_GROUPBOXES, identifying the parent Groupbox to which the member belongs.
• USER_NAME — the application user name of the member.
• INITIATOR_FLAG, REQUESTER_FLAG, AUTHORIZER_FLAG, PERSONNELIST_FLAG, APPROVER_FLAG, REVIEWER_FLAG — six role indicator columns that determine which workflow or security functions the named user may perform within the Groupbox.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.

Two unique indexes are documented. GHR_GROUPBOX_USERS_PK enforces uniqueness on the surrogate key GROUPBOX_USER_ID alone. GHR_GROUPBOX_USERS_UK enforces the composite business key of GROUPBOX_ID and USER_NAME, confirming that a given user name may appear only once per Groupbox.

Common Use Cases and Queries

Typical uses include resolving membership of a Groupbox for security reviews, reporting which users hold a given role such as Approver or Authorizer, and joining membership to workflow routing data. A simple membership listing for a Groupbox is:

SELECT b.groupbox_name, u.user_name, u.approver_flag, u.reviewer_flag
FROM   hr.ghr_groupbox_users u,
       hr.ghr_groupboxes b
WHERE  u.groupbox_id = b.groupbox_id
AND    u.groupbox_id = :p_groupbox_id;

To identify all members holding a specific role within a Groupbox, filter on the corresponding flag column, for example WHERE authorizer_flag = 'Y'. Because the composite unique key is (GROUPBOX_ID, USER_NAME), lookups by user name across Groupboxes should include the Groupbox context to avoid ambiguity. Privileged-user audits commonly join these rows to FND_USER to confirm the account is active.

Related Objects

The most significant related objects are:

• HR.GHR_GROUPBOXES — the parent table, joined via GHR_GROUPBOX_USERS.GROUPBOX_ID = GHR_GROUPBOXES.GROUPBOX_ID; this is the only documented foreign key relationship for the table.
• FND_USER — the application user repository, joined on USER_NAME to resolve user status and personnel details.
• The GHR workflow and security package APIs that consume Groupbox membership when resolving role-based routing.

Because GROUPBOX_USER_ID is a leaf surrogate key referenced by index only, downstream objects typically resolve membership through the (GROUPBOX_ID, USER_NAME) business key rather than the primary key itself.