Results for “ghr_groupbox_users”

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

Overview

The GHR_GROUPBOX_USERS table resides in the HR schema and forms part of the GHR product module (US Federal Human Resources) within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to define the members of a Groupbox. Conceptually, a Groupbox is a named collection of users assembled for routing, review, authorization, or workflow participation, and this table captures the individual membership records that populate each group.

Under a heuristic Data Vault classification derived from its foreign key topology, GHR_GROUPBOX_USERS is assessed as satellite-leaning. In modeling terms, this suggests the table primarily stores descriptive or qualifying attributes attached to a parent entity, rather than acting as an independent hub of business keys or a pure associative link. The parent entity is GHR_GROUPBOXES, and each row qualifies a single user's role within a given group.

Key Information Stored

The table is documented with fourteen columns, the most operationally significant of which are summarized below.

• GROUPBOX_USER_ID — The surrogate primary key defined by the GHR_GROUPBOX_USERS_PK constraint. This is the column most frequently searched (e.g., “groupbox_user_id”) and is used to uniquely identify a single membership row.
• GROUPBOX_ID — Foreign key to GHR_GROUPBOXES; identifies which group the membership record belongs to. It is also part of the business-key unique index.
• USER_NAME — Identifies the FND user who is a member of the group. Combined with GROUPBOX_ID, it forms the unique index GHR_GROUPBOX_USERS_UK, making (GROUPBOX_ID, USER_NAME) the business-key candidate for this table.
• INITIATOR_FLAG, REQUESTER_FLAG, AUTHORIZER_FLAG, PERSONNELIST_FLAG, APPROVER_FLAG, REVIEWER_FLAG — Role-bearing flag columns that define which workflow or functional capacity the named user holds within the group. These flags drive routing and authorization behavior.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard EBS WHO columns providing audit lineage for each membership record.

Distinguishing the surrogate key (GROUPBOX_USER_ID) from the business key (GROUPBOX_ID + USER_NAME) is essential when writing lookups, since applications may resolve memberships by either path.

Common Use Cases and Queries

Typical scenarios involve determining which users belong to a group, which users hold a specific role, and auditing membership changes.

• List members of a group: SELECT USER_NAME, GROUPBOX_ID FROM HR.GHR_GROUPBOX_USERS WHERE GROUPBOX_ID = :p_groupbox_id;
• Identify users with approver rights: SELECT USER_NAME FROM HR.GHR_GROUPBOX_USERS WHERE APPROVER_FLAG = 'Y';
• Find a membership by business key: SELECT GROUPBOX_USER_ID FROM HR.GHR_GROUPBOX_USERS WHERE GROUPBOX_ID = :p_id AND USER_NAME = :p_user;
• Join to the parent group to obtain group descriptions alongside member names.

Reporting commonly reconciles these flags against workflow assignments and security reviews to validate that authority roles are correctly staffed.

Related Objects

• GHR_GROUPBOXES — Parent table; join on GHR_GROUPBOX_USERS.GROUPBOX_ID = GHR_GROUPBOXES.GROUPBOX_ID. The sole documented foreign key relationship.
• FND_USER — Logical reference for USER_NAME, used to resolve user identity, email, and status.
• HR.GHR_GROUPBOX_USERS_PK / HR.GHR_GROUPBOX_USERS_UK — Constraint indexes enforcing surrogate and business-key uniqueness.
• Oracle Workflow routing definitions — Consume the role flags (APPROVER_FLAG, REVIEWER_FLAG, etc.) to direct notifications and approvals.
• GHR Federal HR groupbox maintenance forms and concurrent programs that manage membership records.