Search Results igc_pk

Overview

IGC_CC_CONTROL_GROUPS is a reference and control table within the Oracle E-Business Suite IGC (Contract Commitment) module. It stores contract type authorization groups, which define the grouping construct used to control which contract types a given user, responsibility, or workflow is permitted to create, approve, or process. The table functions as the authorization backbone for commitment control, allowing organizations to partition contract types into logical control groups and then grant or restrict access to those groups independently of the underlying contract type definitions.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is modeled as a standalone table. That classification indicates that, in a Data Vault 2.0 style model, this object would most naturally be treated as a standalone hub or reference structure with no downstream link dependencies captured in the FK metadata. It does not participate in a parent-child link relationship documented in the source metadata, so any Data Vault modeling should treat it as an independent hub keyed on its business key.

The table is documented as "Not implemented in this database," meaning the physical structure is defined in the ETRM metadata but is not present in the current instance. This is common for optional or feature-dependent IGC objects; the table materializes only when the corresponding contract commitment functionality is enabled and configured.

Key Information Stored

The documented metadata identifies two primary key constraints, which is the most important structural fact about this table:

• CONTROL_GROUP_ID — the surrogate primary key, enforced by constraint IGC_PK. This is the system-generated, non-intelligent identifier used for internal joins and referential integrity.
• CONTROL_GROUP_NAME — the business-key candidate, enforced by the unique index ICG_UK. This is the human-readable name of the contract type authorization group, and the value most users recognize when assigning or reporting on control groups.

Because ICG_UK is a unique index on CONTROL_GROUP_NAME, that column is the natural business key for integration, data migration, and Data Vault hub construction. The surrogate CONTROL_GROUP_ID should be treated as an internal operational key rather than a cross-system identifier. The metadata does not enumerate additional descriptive columns, so the authoritative fact set is limited to these two key attributes plus the implied descriptive context (contract type authorization grouping) conveyed by the object description.

Common Use Cases and Queries

Typical usage centers on authorization setup, security reporting, and reconciling control group assignments across responsibilities and contract types.

• Listing all defined control groups: SELECT control_group_id, control_group_name FROM igc_cc_control_groups ORDER BY control_group_name;
• Resolving a group by its business key: SELECT control_group_id FROM igc_cc_control_groups WHERE control_group_name = :name;
• Validating uniqueness before data load or migration: SELECT COUNT(*), control_group_name FROM igc_cc_control_groups GROUP BY control_group_name HAVING COUNT(*) > 1;
• Security and audit reporting that maps control groups to responsibilities and users, supporting segregation-of-duties reviews.
• Data Vault ingestion: CONTROL_GROUP_NAME as the hub business key, with CONTROL_GROUP_ID retained as the operational/technical key.

Because the table may not be physically implemented, queries should first confirm existence via ALL_TABLES or ALL_OBJECTS before being embedded in reports or concurrent programs.

Related Objects

The metadata classifies this object as standalone, so no foreign key dependencies were mined. In practice, the following IGC objects are the most likely integration points:

• IGC contract type definition tables — reference control groups to scope contract types.
• IGC responsibility / user authorization tables — associate responsibilities with control groups.
• IGC commitment control and processing tables — consume control group membership during contract validation.
• IGC concurrent programs and APIs that enforce authorization at contract creation and approval.
• Oracle EBS security and menu / function tables — indirect consumers where control group access maps to application functions.

All of the above should be confirmed against the actual IGC data dictionary for the specific 12.1.1 or 12.2.2 instance, since the documented metadata for IGC_CC_CONTROL_GROUPS itself captures only the two key columns and the standalone classification.