Search Results igc_cc_groups




Overview
Explore in AI Chat

Overview

IGC_CC_GROUPS is a table in the IGC (Contract Commitment) product family of Oracle E-Business Suite, residing in the IGC schema. Its documented description is "Groups defining common users," indicating that it stores grouping definitions used to aggregate or categorize users for contract commitment processing and related workflows. The object is registered as a VALID table in the ETRM metadata spanning Oracle EBS 12.1.1 and 12.2.2.

Under the heuristic Data Vault classification mined from the foreign-key structure, IGC_CC_GROUPS is characterized as standalone. In modeling terms, this suggests treating the table as a self-contained hub-like entity rather than as a dependent satellite or link table, since no incoming or outgoing foreign-key relationships were identified in the documented metadata. The table is owned by IGC and carries a documented physical schema of 25 columns in the 12.2.2 ETRM reference.

Key Information Stored

The primary key of the table is the constraint IGC_CC_GROUP_PK, defined on the CC_GROUP_ID column. This surrogate identifier uniquely distinguishes each contract commitment group record and is the column most often referenced when consumers search on the term "igc_cc_group_pk."

Two unique indexes are documented, exposing the business-key candidates:

  • IGC_CC_GROUPS_U2 on (SET_OF_BOOKS_ID, CC_GROUP_NAME) — the composite business key. Group names are unique only within a given set of books, which confirms that IGC_CC_GROUPS is a multi-organization-aware setup entity.
  • IGC_CC_GROUP_U1 on (CC_GROUP_ID) — a single-column unique index that reinforces the surrogate primary key.

The most significant descriptive and operational columns include:

  • CC_GROUP_ID — surrogate primary key and the anchor of the IGC_CC_GROUP_PK constraint.
  • SET_OF_BOOKS_ID — the ledger context that scopes the group definition; part of the U2 business key.
  • CC_GROUP_NAME — user-facing group name, the second component of the U2 business key.
  • CC_GROUP_DESC — descriptive text for the group.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit trail columns capturing who changed the row and when.
  • CREATION_DATE, CREATED_BY — row creation audit metadata.
  • CONTEXT — the DFF context column.
  • ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle flexfield (DFF) segment columns, providing extensibility without schema changes.

Common Use Cases and Queries

Because the table defines groups of common users, the most frequent reporting scenario is resolving a group identifier to its ledger-scoped name and description. A typical query retrieves a group by its primary key:

  • SELECT cc_group_id, set_of_books_id, cc_group_name, cc_group_desc FROM igc.igc_cc_groups WHERE cc_group_id = :p_group_id;

A second common pattern is business-key lookup within a ledger, exploiting the U2 index:

  • SELECT cc_group_id FROM igc.igc_cc_groups WHERE set_of_books_id = :p_sob AND cc_group_name = :p_name;

Setup and validation reports typically enumerate all groups per set of books, sorted by name, to confirm the grouping configuration loaded during implementation. Integration and migration scripts use the business-key columns to perform upserts, matching on (SET_OF_BOOKS_ID, CC_GROUP_NAME) to avoid duplicate group definitions. Auditing reports select LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, and CREATION_DATE to determine when a group was introduced or modified.

Related Objects

The documented FK structure classifies IGC_CC_GROUPS as standalone, meaning no direct foreign-key parents or children were mined. The most relevant associated objects are therefore the constraints and indexes defined on the table itself, together with the ledger context that scopes it:

  • IGC_CC_GROUP_PK — the primary key constraint on CC_GROUP_ID.
  • IGC_CC_GROUP_U1 — unique index on CC_GROUP_ID.
  • IGC_CC_GROUPS_U2 — unique index on (SET_OF_BOOKS_ID, CC_GROUP_NAME).
  • GL_SETS_OF_BOOKS — the ledger definition referenced through SET_OF_BOOKS_ID.
  • FND_USER — the user directory implicitly referenced by audit columns CREATED_BY and LAST_UPDATED_BY.
  • IGC_CC_GROUP_MEMBERS (or an equivalent membership object) — the typical dependent table mapping users into each group, joined on CC_GROUP_ID.

Consumers should confirm membership objects directly in their instance, as the ETRM metadata excerpt for this object documents no outbound foreign keys.