Search Results igc_cc_bc_enable_u1

Overview

IGC.IGC_CC_BC_ENABLE is a configuration table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 IGC (Grants/Contracts) schema. It stores the flags that determine whether commitment budgetary control is enabled or disabled for a given set of books (ledger). Commitment budgetary control operates independently of standard budgetary control, and this table acts as the authoritative switchboard for that distinct control regime. The object is documented in the ETRM repository as VALID, with the internal FND Design Data reference IGC.IGC_CC_BC_ENABLE, and resides in the APPS_TS_TX_DATA tablespace.

From a Data Vault modeling perspective, the mined relationship data classifies this entity as satellite-leaning. Its structure is narrow, keyed on a single business identifier, and carries descriptive flags and audit columns rather than serving as a central hub or link — a configuration/attribute satellite around the set-of-books dimension. Treating it as a satellite in a warehouse design is a reasonable heuristic suggestion, not a mandatory EBS construct.

Key Information Stored

The table holds eight documented columns. The most significant are the following:

• SET_OF_BOOKS_ID (NUMBER, mandatory) — the accounting books defining column. This is both the primary key (IGC_CCBCE_PK) and the unique-indexed column via IGC_CC_BC_ENABLE_U1, making it the single business-key candidate. It foreign-keys to GL_SETS_OF_BOOKS.
• CC_BC_ENABLE_FLAG (VARCHAR2) — indicates whether commitment budgetary control is enabled at the broad level for the set of books.
• CBC_PO_ENABLE (VARCHAR2) — a granular flag; when set to Y, commitment budgetary control is enabled specifically for Purchase Orders, and when N, it is disabled for that document type.
• Standard Who audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY. These capture creation and last-modification metadata, with the user columns keyed to FND_USER.USER_ID and the login column to FND_LOGINS.LOGIN_ID.

The separation between CC_BC_ENABLE_FLAG and CBC_PO_ENABLE is notable: the former governs the general enablement state, while the latter controls the Purchase Order-specific dimension, allowing finer-grained administration.

Common Use Cases and Queries

The primary use case is validating, for a given ledger, whether commitment budgetary control is active before funds-checking logic executes. Administrators and support analysts query this table to diagnose why commitment checking behaves differently across sets of books.

• Checking enablement for a ledger: SELECT CC_BC_ENABLE_FLAG, CBC_PO_ENABLE FROM IGC.IGC_CC_BC_ENABLE WHERE SET_OF_BOOKS_ID = :sob_id;
• Reporting all ledgers with commitment control enabled: join to GL_SETS_OF_BOOKS to translate the ID into a readable ledger name.
• Purchase Order-specific audit: filter on CBC_PO_ENABLE = 'Y' to list ledgers where PO commitment control is on.
• Change tracking: use the Who columns to identify recent configuration changes, e.g. WHERE LAST_UPDATE_DATE >= :cutoff.

The query text documented in the metadata supports direct extraction of all columns for downstream reconciliation.

Related Objects

• GL_SETS_OF_BOOKS — referenced via IGC_CC_BC_ENABLE.SET_OF_BOOKS_ID = GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID; provides ledger context.
• FND_USER — referenced by LAST_UPDATED_BY and CREATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN.
• IGC_CC_BC_ENABLE# — the internal constraint/index object that references this table.
• Commitment budgetary control program and funds-checking logic — consumes the flag values stored here to govern runtime behavior for grants and contracts transactions.