Search Results igc_cc_interface_n1

Overview

IGC.IGC_CC_INTERFACE is an interface staging table in the Oracle E-Business Suite Contract Commitment (IGC) module. Its documented purpose is to store information received from the Contract Commitment system that must be passed to the Commitment Budgetary Control submodule for funds checking and funds reservation. Both a funds check and a funds reservation request can be initiated from Contract Commitment; when the associated concurrent tasks are submitted, the system inserts the rows into this table, which functions as the interface to the submodule. Depending on whether budgetary control has been enabled, the funds check and reservation may be processed against the General Ledger standard budget or the commitment budget. The table therefore temporarily holds all data required to complete the tasks handled by the submodules.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is a link. The table resides in the APPS_TS_INTERFACE tablespace with PCT Free 10, is owned by the IGC schema, and is delivered with FND Design Data reference IGC.IGC_CC_INTERFACE. The documented physical schema contains 50 columns, and the object carries status VALID in ETRM 12.2.2 metadata, applying to both 12.1.1 and 12.2.2 environments.

Key Information Stored

The table records the financial and control context of each Contract Commitment line staged for budgetary control processing. The principal surrogate identifier is CC_HEADER_ID, the document identifier defining column. Business-key identification is provided by the unique index IGC_CC_INTERFACE_U1, which spans CC_HEADER_ID, DOCUMENT_TYPE, ACTUAL_FLAG, and BATCH_LINE_NUM.

• CC_HEADER_ID, CC_VERSION_NUM — contract commitment document identifier and version.
• CC_ACCT_LINE_ID, CC_DET_PF_LINE_ID — account line and detail payment forecast line defining columns.
• CODE_COMBINATION_ID — key flexfield account combination used for funds checking.
• BATCH_LINE_NUM, BATCH_ID — line number of the batch and batch grouping.
• CC_TRANSACTION_DATE — accounting date of the contract.
• CC_FUNC_DR_AMT, CC_FUNC_CR_AMT — transactional debit and credit amounts.
• JE_SOURCE_NAME, JE_CATEGORY_NAME — journal entry source and category.
• PERIOD_SET_NAME, PERIOD_NAME — accounting period context.
• ACTUAL_FLAG, BUDGET_DEST_FLAG, BUDGET_VERSION_ID — budgetary control destination and budget version.
• SET_OF_BOOKS_ID, ENCUMBRANCE_TYPE_ID — ledger and encumbrance type linkage.
• CBC_RESULT_CODE, RESULT_CODE_SOURCE — outcomes returned from Commitment Budgetary Control.
• STATUS_CODE, FUNDS_AVAILABLE_AMT, BUDGET_AMT — processing status and monetary results.

Common Use Cases and Queries

Primary usage centers on diagnosing failed or pending funds checks and funds reservations. The unique key is the natural access path, and the user search for IGC_CC_INTERFACE_U1 reflects this indexing pattern.

• Retrieve all staged rows for a contract: select by CC_HEADER_ID and status.
• Trace results by joining CBC_RESULT_CODE and RESULT_CODE_SOURCE to interpret funds check outcomes.
• Reconcile amounts by comparing BUDGET_AMT, COMMITMENT_ENCMBRNC_AMT, OBLIGATION_ENCMBRNC_AMT, and FUNDS_AVAILABLE_AMT.
• Report on the IGC_CC_INTERFACE_N1 (CC_HEADER_ID, ACTUAL_FLAG), N2 (CC_ACCT_LINE_ID), and N3 (CC_DET_PF_LINE_ID) access paths for line-level analysis.

A representative query filters by CC_HEADER_ID and ACTUAL_FLAG, ordering by BATCH_LINE_NUM to reconstruct the batch sequence.

Related Objects

The table references GL_ENCUMBRANCE_TYPES through ENCUMBRANCE_TYPE_ID, linking staged rows to the encumbrance type definition. The columns CC_DET_PF_LINE_ID, CC_ACCT_LINE_ID, and CC_HEADER_ID carry documented foreign-key relationships to their parent Contract Commitment entities. Commitment Budgetary Control processing consumes rows to perform funds checking and reservation, and the General Ledger standard or commitment budget is the downstream destination when budgetary control is enabled. Oracle General Ledger budget and encumbrance reporting objects are the principal consumers of the results written back into CBC_RESULT_CODE and related result columns.