Search Results igc_cc_group_user_pk

Overview

IGC_CC_GROUP_USERS is a table owned by the IGC schema within the Oracle E-Business Suite Contract Commitment (IGC) module. Its documented description is "Group assignments to users," meaning it stores the mapping between Contract Commitment groups and the application users who belong to them. The table is marked VALID at release levels 12.1.1 and 12.2.2 and physically contains 23 documented columns.

The table functions strictly as an association or junction object. It carries no descriptive attributes of the group or the user themselves; instead it records which user is assigned to which group, allowing the IGC application to resolve group membership for workflow routing, approval hierarchies, and security filtering.

Under a heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a link table. It resolves a many-to-many relationship between groups and users through two foreign keys and a composite primary key, which is the classic signature of a link entity rather than a hub or satellite.

Key Information Stored

Only a small subset of the 23 columns carries true business meaning. The remainder are standard Oracle EBS "WHO" audit columns and the generic DFF attribute set (ATTRIBUTE1 through ATTRIBUTE15 plus CONTEXT).

• CC_GROUP_ID — Identifies the Contract Commitment group. Part of the composite primary key and a foreign key back into the group definition table.
• USER_ID — Identifies the application user assigned to the group. Part of the composite primary key and a foreign key to FND_USER.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking who last touched a membership row and when.
• CREATION_DATE, CREATED_BY — Record creation audit columns.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — The descriptive flexfield segment storage, available for client-specific extension of membership records.

The surrogate primary key constraint is IGC_CC_GROUP_USER_PK, which is defined over (CC_GROUP_ID, USER_ID). A unique index, IGC_CC_GROUP_USER_U1, is also defined on the same (CC_GROUP_ID, USER_ID) pair. Because the surrogate primary key and the business-key unique index coincide, the true business key of this table is the combination of the group and the user — no surrogate single-column identifier exists beyond that composite.

Common Use Cases and Queries

Typical scenarios include listing the members of a group for approval routing, determining which groups a given user belongs to, and auditing group membership changes.

• List all users in a group: SELECT user_id FROM igc_cc_group_users WHERE cc_group_id = :group_id;
• Find all groups for a user: SELECT cc_group_id FROM igc_cc_group_users WHERE user_id = :user_id;
• Join to FND_USER to resolve user names for reporting.
• Audit recently changed memberships using LAST_UPDATE_DATE.

Because the table holds no descriptive columns, reporting almost always requires a join to the user directory and to the group header table to produce meaningful output.

Related Objects

The most significant relationships are documented through its foreign keys.

• FND_USER — joined via IGC_CC_GROUP_USERS.USER_ID = FND_USER.USER_ID. Supplies user identity, name, and status.
• IGC_CC_GROUP_USERS (self-referencing) — the CC_GROUP_ID relationship points into the group definition object, enabling joins between membership rows and group headers.
• IGC_CC_GROUP_USER_PK / IGC_CC_GROUP_USER_U1 — the primary key and unique index constraints that enforce uniqueness of each group-user pair.

Together these relationships confirm the table's role as a link between the IGC group entity and the EBS user directory, making it the authoritative source for Contract Commitment group membership.