Results for “igc_cbc_det_balances_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGC_CBC_DET_BALANCES_V view is an APPS-owned database object within the Contract Commitment (IGC) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents detailed commitment and budget control balances at the level of a set of books and a code combination, aggregating journal line activity by accounting period. Its primary purpose is to expose budget, commitment, actual, obligation, and funds-available balances used by the Contract Commitment inquiry and reporting layer. The view is read-only and derives all data dynamically from the general ledger interface lines maintained for commitment control, rather than storing balances itself. The inclusion of the single-row pseudo columns LAST_UPDATE_DATE and LAST_UPDATED_BY (fixed to SYSDATE and -1 respectively) indicates the view is designed primarily for display and inquiry rather than for persistence or form-based update. The search term "cc_conf_encmbrnc_type_id" corresponds to the encumbrance type identifier used internally to classify confirmed commitments, referenced in the view definition through the CC_CONF_ENCMBRNC_TYPE_ID token in the DECODE logic.

Underlying Base Objects

The view is defined over three documented base objects:

• IGC_CBC_JE_LINES (synonym) — the journal entry lines holding entered debit and credit amounts, actual flag ('B' for budget, 'E' for encumbrance), encumbrance type, period name, period year, quarter, and period number. This is the principal driving table for all amount calculations.
• IGC_CC_ENCMBRNC_ORG_V (view) — supplies the organizational encumbrance type context, including the referenced CC_PROV_ENCMBRNC_TYPE_ID and CC_CONF_ENCMBRNC_TYPE_ID values that drive the classification of provisional and confirmed commitment amounts.
• IGC_CBC_INQUIRY_PKG (package) — provides the CHECK_AMOUNT_TYPE function used to filter which period/amount-type combinations are included, and the GET_AMOUNT_TYPE and GET_PERIOD_NAME functions used to populate the AMOUNT_TYPE and PERIOD_NAME columns in the outer query.

Key Columns

• SET_OF_BOOKS_ID — the ledger or set of books to which the balance belongs.
• CODE_COMBINATION_ID — the accounting flexfield combination feeding the balance.
• BUDGET_VERSION_ID — highest budget version identifier applied to the combination.
• BUDGET_AMOUNT — sum of lines flagged 'B', representing the budgeted amount for the combination.
• COMM_AMOUNT — sum of encumbrance lines matching the provisional encumbrance type, representing committed (provisional) amounts.
• ACT_AMOUNT — sum of encumbrance lines matching the confirmed encumbrance type (tied to cc_conf_encmbrnc_type_id).
• OTH_AMOUNT — sum of encumbrance lines that match neither provisional nor confirmed types.
• TOT_AMOUNT — COMM_AMOUNT + ACT_AMOUNT + OTH_AMOUNT, the total obligated amount.
• FA_AMOUNT — BUDGET_AMOUNT minus COMM_AMOUNT minus ACT_AMOUNT, the funds-available balance.
• AMOUNT_TYPE — the amount type description returned by IGC_CBC_INQUIRY_PKG.GET_AMOUNT_TYPE, truncated to 4 characters.
• PERIOD_NAME — accounting period description from GET_PERIOD_NAME, truncated to 20 characters.

Common Use Cases and Queries

The view supports commitment control inquiries such as balance enquiry screens, funds-availability checks, and custom reports. A typical query retrieves unfunded or over-committed combinations by filtering on FA_AMOUNT:

• SELECT set_of_books_id, code_combination_id, budget_amount, comm_amount, act_amount, tot_amount, fa_amount FROM apps.igc_cbc_det_balances_v WHERE set_of_books_id = :p_sob AND fa_amount < 0;
• SELECT code_combination_id, tot_amount FROM apps.igc_cbc_det_balances_v WHERE code_combination_id = :p_ccid ORDER BY period_name;
• SELECT period_name, comm_amount, act_amount, fa_amount FROM apps.igc_cbc_det_balances_v WHERE set_of_books_id = :p_sob AND period_name LIKE :p_period;

Because all columns are derived at runtime and the view exposes no upward dependencies, it is safe for ad-hoc reporting and integration extracts. Joins should typically target GL_CODE_COMBINATIONS on CODE_COMBINATION_ID for descriptive flexfield or account segment reporting.