Search Results igc_cc_interface

Overview

IGC.IGC_CC_INTERFACE is the staging and interface table used by the Oracle E-Business Suite IGC – Contract Commitment module to pass transaction data into the budgetary control / commitment submodule for funds checking and fund reservation. It is the bridge between contract and commitment accounting events and the encumbrance engine that ultimately feeds General Ledger via the GL_ENCUMBRANCE_TYPES and GL interface constructs. The table is classified as VALID and contains 50 physical columns in the ETRM 12.2.2 schema.

Under a heuristic Data Vault modeling lens, this table is best understood as a link entity. Its foreign keys (CC_HEADER_ID, CC_ACCT_LINE_ID, CC_DET_PF_LINE_ID, and ENCUMBRANCE_TYPE_ID) reference associated contract-commitment lines and encumbrance type definitions rather than acting as an independent hub. This modeling suggestion reflects the fact that IGC_CC_INTERFACE represents the intersection of contract documents and budgetary control transactions.

Key Information Stored

The table carries both the contract-side identifiers and the budgetary-check results. The most significant columns include:

• CC_HEADER_ID – contract commitment header reference and part of the business key.
• CC_ACCT_LINE_ID and CC_DET_PF_LINE_ID – foreign keys to the associated contract commitment distribution / performance obligation lines.
• CODE_COMBINATION_ID – the GL accounting flexfield combination used for funds checking.
• BATCH_LINE_NUM, BATCH_ID, DOCUMENT_TYPE, and ACTUAL_FLAG – identify the batch, document class, and whether amounts are actual or budgetary.
• CC_FUNC_DR_AMT / CC_FUNC_CR_AMT – functional debit and credit amounts.
• ENCUMBRANCE_TYPE_ID – FK to GL_ENCUMBRANCE_TYPES, defining whether the entry is a commitment, obligation, or other encumbrance category.
• BUDGET_AMT, COMMITMENT_ENCMBRNC_AMT, OBLIGATION_ENCMBRNC_AMT, and FUNDS_AVAILABLE_AMT – the budgetary check outcome amounts.
• CBC_RESULT_CODE, STATUS_CODE, and RESULT_CODE_SOURCE – funds-check / reservation status feedback from budgetary control.
• SET_OF_BOOKS_ID, CURRENCY_CODE, PERIOD_NAME, and PERIOD_SET_NAME – accounting context.

The documented unique index IGC_CC_INTERFACE_U1 spans (CC_HEADER_ID, DOCUMENT_TYPE, ACTUAL_FLAG, BATCH_LINE_NUM), which serves as the business-key candidate for row uniqueness.

Common Use Cases and Queries

Typical activities include confirming which interface rows have been successfully funds-checked versus rejected, and reconciling contract commitments against GL encumbrance balances. For example, to identify rows failing budgetary control:

SELECT cc_header_id, code_combination_id, cbc_result_code, status_code FROM igc.igc_cc_interface WHERE status_code IS NOT NULL AND cbc_result_code <> 'S';

Reporting queries frequently join to GL_ENCUMBRANCE_TYPES via ENCUMBRANCE_TYPE_ID to summarize reserved commitment and obligation amounts by encumbrance category. Reconciliation extracts join by SET_OF_BOOKS_ID and PERIOD_NAME to compare BUDGET_AMT and FUNDS_AVAILABLE_AMT against posted GL balances. Because this is an interface table, purge routines typically remove rows after successful transfer to the commitment submodule.

Related Objects

• GL_ENCUMBRANCE_TYPES – joined via ENCUMBRANCE_TYPE_ID to define the encumbrance category.
• IGC_CC_INTERFACE self-referencing keys (CC_HEADER_ID, CC_ACCT_LINE_ID, CC_DET_PF_LINE_ID) that tie back to Contract Commitment header and line tables.
• General Ledger encumbrance and budgetary-control interface objects that consume the result codes and amounts populated here.
• Contract Commitment (IGC) header, account line, and performance-obligation tables referenced by the foreign keys above.