Search Results igc_cc_group_user_u1

Overview

The IGC.IGC_CC_GROUP_USERS table is a core setup object within the Oracle E-Business Suite Procurement Contracts and Approvals infrastructure, owned by the IGC schema. It stores the assignment of individual application users to specific approval groups, enabling the approval routing logic that governs contract and document authorization. Where IGC_CC_GROUPS defines the approval group itself, IGC_CC_GROUP_USERS resolves the many-to-many relationship between those groups and the users who belong to them. As documented in the ETRM metadata, for each group there can be several rows in this table sharing the same CC_GROUP_ID but carrying different USER_ID values.

From a Data Vault modeling perspective, the heuristic classification for this object is link. This classification reflects its role as a relationship resolver between two distinct hubs — the group entity and the user entity — rather than an independent business entity or a descriptive satellite.

Key Information Stored

The table comprises 23 documented columns. The most significant are:

• CC_GROUP_ID (NUMBER) — Approval group defining column; identifies the group to which a user is assigned.
• USER_ID (NUMBER, length 15) — User defining column; foreign key to FND_USER.USER_ID identifying the assigned individual.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking the most recent modification, the responsible user, and the operating system login.
• CREATION_DATE, CREATED_BY — Standard WHO columns recording row creation.
• CONTEXT (VARCHAR2, 30) — Descriptive Flexfield context column.
• ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2, 150) — Descriptive Flexfield segments available for customer-specific extensions.

The surrogate primary key is IGC_CC_GROUP_USER_PK, defined on the composite of (CC_GROUP_ID, USER_ID). A unique index, IGC_CC_GROUP_USER_U1, also exists on the same (CC_GROUP_ID, USER_ID) pair — the index the user searched for. Because the business key and primary key columns coincide, IGC_CC_GROUP_USER_U1 effectively functions as both the uniqueness enforcement mechanism and the natural business key candidate for this link.

Common Use Cases and Queries

Typical scenarios include determining which users belong to an approval group, verifying whether a given user is authorized for a specific group, and generating access-review reports. A representative query to list members of a group is:

• SELECT g.user_id, u.user_name FROM igc.igc_cc_group_users g, fnd_user u WHERE g.cc_group_id = :group_id AND g.user_id = u.user_id;
• Identify all groups a user belongs to: SELECT cc_group_id FROM igc.igc_cc_group_users WHERE user_id = :user_id;
• Audit recently modified assignments using WHERE last_update_date > SYSDATE - 30.

Because the table links directly to FND_USER, joins to that view are routine for producing human-readable membership rosters used in segregation-of-duties and compliance reporting.

Related Objects

The most significant related objects, grounded in the documented foreign key relationships, include:

• IGC.IGC_CC_GROUPS — Parent approval group definition, joined via CC_GROUP_ID.
• FND_USER — Application user master, joined via USER_ID.
• FND_LOGINS — Referenced by LAST_UPDATE_LOGIN for login audit tracing.
• IGC_CC_GROUP_USER_PK — The primary key constraint enforcing unique (CC_GROUP_ID, USER_ID) pairs.
• IGC_CC_GROUP_USER_U1 — The unique index supporting fast membership lookups and business-key enforcement.

These relationships confirm the table's central role in approval-group membership resolution within the IGC approval framework.