Search Results igc_cc_control_functions

Overview

IGC_CC_CONTROL_FUNCTIONS is a configuration table within the Oracle E-Business Suite Contract Commitment (IGC) module. Its documented purpose is to define "contract type control functions" — the discrete control behaviors applied to a contract type in the Contract Commitment schema. In Oracle EBS, the IGC module governs commitment accounting for contracts (obligations, funds checking, and downstream commitments to General Ledger). Control functions act as a rule layer that determines how a given contract type behaves operationally: which controls are active, permitted, or enforced when commitments are created, validated, and posted.

The ETRM metadata explicitly states that the table is not implemented in this database. This is a significant implementation caveat: not every EBS instance ships or enables every IGC object, so the table may only exist in installations where the Contract Commitment control-function capability has been configured or licensed. Confirming presence via DBA_TABLES or ALL_TAB_COLUMNS is therefore a prerequisite before writing dependent queries.

From a data-modeling standpoint, the metadata's heuristic Data Vault classification is satellite-leaning. This suggests the table is best understood as a descriptive/attribute satellite attached to a parent grouping entity, rather than as a standalone hub or relationship link. The classification is a modeling suggestion derived from foreign-key structure, not a documented EBS fact.

Key Information Stored

The documented primary key is ICF_PK, defined on the column CONTROL_FUNCTION_ID. This is the surrogate key — a system-generated identifier with no inherent business meaning, used to enforce row-level uniqueness.

The metadata documents a single named foreign key relationship: CONTROL_GROUP_ID in IGC_CC_CONTROL_FUNCTIONS. This column links each control function row to a parent control group, establishing the grouping that the satellite-leaning classification reflects. The FK note lists the column as referencing a table represented only as "%" in the excerpt — that is, the referenced table name was not captured in the ETRM extract and must be resolved against the live data dictionary.

The excerpt does not enumerate additional columns. In comparable IGC control tables the retained attributes typically include the control-function name or code, an enabled/active flag, a sequence or ordering value, a description, and the standard Oracle WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY). Because these are not documented here, they should be treated as probable rather than certain, and verified against ALL_TAB_COLUMNS. No unique business-key index is documented, so CONTROL_GROUP_ID plus a control-function identifier would be the likely natural business key candidate, contingent on confirmation.

Common Use Cases and Queries

Typical scenarios include auditing which control functions apply to a contract type group, validating that required controls exist before enabling commitment processing, and extracting control configuration for compliance or migration reporting.

• List control functions for a given control group, joining on the documented FK:
  SELECT * FROM igc_cc_control_functions WHERE control_group_id = :p_group_id;
• Enumerate distinct control groups referenced, to map the parent grouping table:
  SELECT DISTINCT control_group_id FROM igc_cc_control_functions ORDER BY 1;
• Confirm the object exists in the instance before querying:
  SELECT table_name FROM all_tables WHERE table_name = 'IGC_CC_CONTROL_FUNCTIONS';
• Confirm the primary key and any unique indexes:
  SELECT * FROM all_constraints WHERE table_name = 'IGC_CC_CONTROL_FUNCTIONS' AND constraint_type IN ('P','U');

Reporting use cases center on configuration drift: comparing control functions across environments (DEV vs. PROD), and producing a control-function inventory for a given contract type hierarchy.

Related Objects

The documented relationships are limited but provide the anchoring join:

• IGC_CC_CONTROL_FUNCTIONS.CONTROL_FUNCTION_ID — primary key (ICF_PK); the surrogate join target for child satellite tables.
• IGC_CC_CONTROL_FUNCTIONS.CONTROL_GROUP_ID — foreign key to the parent control-group table (name unresolved in the metadata extract); the principal parent join.
• Parent control-group table (referenced via CONTROL_GROUP_ID) — supplies the grouping context; identify it via ALL_CONSTRAINTS / ALL_CONS_COLUMNS on this table's R constraint.

Other IGC Contract Commitment configuration and commitment-processing tables — such as contract type and commitment definition objects — are functionally adjacent and are the likely consumers of control-function definitions, but they are not documented in the supplied metadata and should be confirmed against the live dictionary before being used in production joins.