Results for “igc_cc_group_users_v”

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

Overview

IGC_CC_GROUP_USERS_V is a standard Oracle E-Business Suite view owned by the APPS schema and shipped with the IGC (Contract Commitment) product family. It exposes the association between Contract Commitment user groups and the Oracle EBS application users who belong to those groups. In other words, the view answers the question: "which FND users are members of which IGC Contract Commitment group?" Because it joins group membership data to the global FND_USER directory, it is the natural reporting and integration entry point whenever a query must reconcile group-level access with a full user profile rather than a raw USER_ID.

The view is delivered in a VALID status in both EBS 12.1.1 and 12.2.2, where it is most commonly consumed by Concurrent Program extracts, OBIEE / XML Publisher reports, and custom interfaces that need to enumerate authorized users for a Contract Commitment group before routing work items or applying security logic.

Underlying Base Objects

The view is defined over three objects, all resolved through APPS synonyms:

• IGC_CC_GROUP_USERS (ICGU) — the primary membership table; supplies the group-to-user link (CC_GROUP_ID, USER_ID) and the descriptive/flex columns.
• IGC_CC_GROUPS (ICG) — the group header; joined on CC_GROUP_ID to confirm and constrain the group.
• FND_USER (U) — the application user directory; joined on USER_ID to return USER_NAME and the user's START_DATE, END_DATE, and DESCRIPTION.

The join predicate is ICG.CC_GROUP_ID = ICGU.CC_GROUP_ID AND ICGU.USER_ID = U.USER_ID. Because it is a view, no independent storage exists; row-level DML against group members must be performed on the IGC_CC_GROUP_USERS base table, not on the view.

Key Columns

• ROW_ID — the base table ROWID of the IGC_CC_GROUP_USERS record; useful for isolated updates.
• CC_GROUP_ID — foreign key to IGC_CC_GROUPS, identifying the group.
• USER_ID / USER_NAME — the FND_USER identifier and the human-readable login name.
• START_DATE / END_DATE / DESCRIPTION — taken from FND_USER and reflecting the user record, not the membership period.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, following the standard WHO convention.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the DFF (descriptive flexfield) columns carried through from IGC_CC_GROUP_USERS for customer-defined extensions.

Common Use Cases and Queries

Typical scenarios include: building a group membership report, verifying that a departing employee is removed from all Contract Commitment groups, or filtering Contract Commitment notifications to active users only. A standard query follows:

SELECT g.cc_group_id,
       g.name            group_name,
       v.user_name,
       v.start_date,
       v.end_date
FROM   apps.igc_cc_group_users_v v,
       apps.igc_cc_groups g
WHERE  v.cc_group_id = g.cc_group_id
AND    v.end_date IS NULL
ORDER  BY g.cc_group_id, v.user_name;

Because the view already joins FND_USER, the END_DATE IS NULL predicate conveniently restricts output to currently active users. A second common pattern lists all groups a specific user belongs to:

SELECT cc_group_id
FROM   apps.igc_cc_group_users_v
WHERE  user_name = :p_user_name;

Note that the view does not expose the group name itself; join IGC_CC_GROUPS as shown above when the group description is required.