Search Results encumbred_amount

Overview

IGC_CBC_DR_V is a reporting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the IGC product family (Contract Commitment) and is documented in ETRM as "View based on interface for Displaying Result." Its status is VALID. The view consolidates contract commitment and funds-checking data sourced from the IGC_CC_INTERFACE_V interface view and enriches it with decodes and descriptive lookups drawn from General Ledger. Its primary role is to expose Budgetary Control (CBC) result information — commitment and obligation encumbrance amounts, funds-available amounts, budget versions, and funds-check results — in a form suitable for concurrent program output, Oracle Reports, OAF pages, or ad hoc SQL reporting. Because it resolves foreign-key codes into human-readable meanings, it is commonly the target of investigative queries against the status_code_meaning and related result columns.

Underlying Base Objects

The documented base objects referenced by IGC_CBC_DR_V are FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), GL_BUDGET_VERSIONS (SYNONYM), GL_ENCUMBRANCE_TYPES (SYNONYM), GL_LOOKUPS (VIEW), GL_PERIOD_STATUSES (SYNONYM), and IGC_CC_INTERFACE_V (VIEW). The driving object is IGC_CC_INTERFACE_V, aliased CCV, from which all transactional columns are projected. GL_LOOKUPS (aliases GL1 through GL4) supplies translated meanings for result codes, balance types, budget types, and status codes. GL_PERIOD_STATUSES (GPS) provides PERIOD_YEAR and PERIOD_NUM for the accounting period. GL_BUDGET_VERSIONS (GBV) supplies the BUDGET_NAME. GL_ENCUMBRANCE_TYPES (GET) provides the ENCUMBRANCE_TYPE description. FND_LOOKUPS is present for lookup-driven decoding, and FND_GLOBAL is referenced as a package, typically for session or responsibility context in related logic. The view therefore joins interface-level commitment data to the GL reference data necessary to render it intelligible.

Key Columns

The view projects identifying keys (ROW_ID, CC_HEADER_ID, CC_ACCT_LINE_ID, CODE_COMBINATION_ID, BATCH_LINE_NUM, SET_OF_BOOKS_ID) alongside transaction attributes such as CC_TRANSACTION_DATE, JE_SOURCE_NAME, JE_CATEGORY_NAME, PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, and ACTUAL_FLAG. Financial columns include CC_FUNC_DR_AMT, CC_FUNC_CR_AMT, a derived TRANSACTION_AMOUNT (NVL(DR) − NVL(CR)), BUDGET_AMT, COMMITMENT_ENCMBRNC_AMT, OBLIGATION_ENCMBRNC_AMT, a derived ENCUMBRED_AMOUNT (NVL(COMMITMENT) + NVL(OBLIGATION)), and FUNDS_AVAILABLE_AMT. Descriptive decodes include BALANCE_TYPE, BUDGET_TYPE, AMOUNT_TYPE (from REFERENCE_10/AMOUNT_TYPE_CODE), ENCUMBRANCE_TYPE, RESULT_CODE_MEANING, and STATUS_CODE_MEANING. The RESULT_CODE_MEANING column decodes CBC_RESULT_CODE via GL_LOOKUPS, substituting 'THIS ACCOUNT HAS NOT BEEN FUNDS CHECKED' when null. The STATUS_CODE_MEANING column — the object of the searched term — decodes STATUS_CODE via GL_LOOKUPS (GL3.MEANING), returning 'NOT FUNDS CHECKED' when STATUS_CODE is null. Together these two decodes communicate whether funds checking ran and, if so, its outcome.

Common Use Cases and Queries

Typical uses include auditing funds-check results for a period, reconciling commitment and obligation encumbrances against budgets, and diagnosing accounts that bypassed budgetary control.
SELECT cc_header_id, cc_acct_line_id, period_name, status_code, status_code_meaning,
       cbc_result_code, result_code_meaning, transaction_amount, funds_available_amt
 FROM apps.igc_cbc_dr_v
 WHERE status_code_meaning = 'NOT FUNDS CHECKED';
Reporting of encumbrance exposure by budget version:
SELECT budget_name, encumbrance_type, SUM(encumbred_amount) encumbred,
       SUM(funds_available_amt) available
 FROM apps.igc_cbc_dr_v
 WHERE period_name = :p_period
 GROUP BY budget_name, encumbrance_type;
Detail by accounting period and set of books:
SELECT set_of_books_id, period_year, period_num, period_name, actual_flag,
       balance_type, amount_type, commitment_encmbrnc_amt, obligation_encmbrnc_amt
 FROM apps.igc_cbc_dr_v
 WHERE set_of_books_id = :p_sob_id
 ORDER BY period_year, period_num;
Because the view reads from an interface source and GL lookups, it is best treated as read-only; all filtering by status or result should reference the decoded *_MEANING columns to avoid depending on lookup code values that may differ by configuration.