Search Results result_code_source

Overview

IGC_CC_INTERFACE_V is an APPS-owned database view within the Oracle E-Business Suite IGC (Contract Commitment) product family. It exposes the staging and interface data used to move contract commitment and budgetary control transactions into Oracle General Ledger and, where applicable, into encumbrance and funds-availability processing. The view is a thin projection over a single underlying interface table, IGC_CC_INTERFACE, and presents one row per commitment or accounting interface line together with its associated distribution, budgetary control, and descriptive reference attributes.

In 12.1.1 and 12.2.2 environments the view carries a VALID status and is registered in the APPS schema, making it accessible to concurrent programs, Oracle Reports, Oracle Forms, and custom SQL executed by application users with appropriate grants. Because it is a view rather than a table, it introduces no storage of its own; it is a read interface for the columns documented as part of the Contract Commitment interface, which supports the flow of commitments, obligations, and fund reservation results into the financials ledger. It is a common reference point for reporting on unaudited interface balances, budgetary control outcomes, and encumbrance amounts before or after the commitment interface process moves them downstream.

Underlying Base Objects

The documented underlying base object is IGC_CC_INTERFACE, referenced as a SYNONYM in the ETRM metadata. The view selects its column set directly from that table without joins, unions, aggregation, or filtering, so there is a strict one-to-one correspondence between view rows and base interface table rows. Every column documented for the view — from CC_HEADER_ID through CC_ENCMBRNC_DATE — maps one-to-one to a column on IGC_CC_INTERFACE.

• Owner/Schema: APPS.
• Base object: IGC_CC_INTERFACE (SYNONYM).
• Relationship: unqualified SELECT projection; no transformation or row filtering is applied by the view definition.
• Status: VALID in the documented 12.2.2 environment.

Because the view performs no joins, its correctness depends entirely on the interface table's integrity and on the concurrent processes that populate and purge that table. Reporting directly against the view is therefore equivalent to reporting against the base table, but the view is the documented, supported access path.

Key Columns

The view exposes identifiers, accounting keys, amounts, and status information. Key columns include:

• CC_HEADER_ID, CC_ACCT_LINE_ID, CC_DET_PF_LINE_ID — identifiers linking each interface row to its commitment header, accounting line, and detail performance line.
• CODE_COMBINATION_ID — the accounting flexfield combination receiving the transaction.
• BATCH_ID, BATCH_LINE_NUM — grouping and sequencing for the interface batch.
• CC_TRANSACTION_DATE, PERIOD_NAME, PERIOD_SET_NAME — the accounting date and period context.
• CC_FUNC_DR_AMT, CC_FUNC_CR_AMT — functional debit and credit amounts.
• JE_SOURCE_NAME, JE_CATEGORY_NAME, ACTUAL_FLAG — journal source, category, and actual/encumbrance indicator.
• SET_OF_BOOKS_ID — the ledger (set of books) for the transaction.
• ENCUMBRANCE_TYPE_ID, COMMITMENT_ENCMBRNC_AMT, OBLIGATION_ENCMBRNC_AMT — encumbrance classification and amounts.
• BUDGET_AMT, FUNDS_AVAILABLE_AMT, BUDGET_VERSION_ID, BUDGET_DEST_FLAG — budgetary control and funds-availability output.
• CBC_RESULT_CODE, RESULT_CODE_SOURCE, STATUS_CODE — budgetary control result and processing status.
• REFERENCE_1 through REFERENCE_10 — descriptive flexfield-style reference attributes for source-system traceability.
• CURRENCY_CODE, DOCUMENT_TYPE, TRANSACTION_DESCRIPTION, PA_FLAG — transaction context and Project Accounting indicator.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus CC_VERSION_NUM and CC_ENCMBRNC_DATE.

Common Use Cases and Queries

Typical uses include auditing unposted commitment interface lines, reconciling encumbrance balances to General Ledger, diagnosing budgetary control failures, and driving custom extracts. Because REFERENCE_1 through REFERENCE_10 are exposed, this view is commonly queried when supporting the exact search term "reference_1," for example to trace a contract back to an external source document.

Sample query listing failed budgetary control lines for a ledger:

SELECT cc_header_id, cc_acct_line_id, code_combination_id, period_name, reference_1, reference_2, cbc_result_code, status_code, commitment_encmbrnc_amt FROM igc_cc_interface_v WHERE set_of_books_id = :p_sob_id AND cbc_result_code IS NOT NULL ORDER BY cc_transaction_date, batch_id, batch_line_num;

Sample query reconciling debits and credits by period and encumbrance type:

SELECT period_name, encumbrance_type_id, je_source_name, SUM(cc_func_dr_amt) dr, SUM(cc_func_cr_amt) cr FROM igc_cc_interface_v WHERE actual_flag = 'E' GROUP BY period_name, encumbrance_type_id, je_source_name ORDER BY period_name;

Sample query searching by reference for support and reconciliation:

SELECT * FROM igc_cc_interface_v WHERE reference_1 = :p_reference;

Queries should generally restrict by SET_OF_BOOKS_ID, PERIOD_NAME, or BATCH_ID to limit result sets, and should avoid reliance on the view for real-time transactional posting logic.