Search Results detail_summary_code




Overview
Explore in AI Chat

Overview

APPS.IGCBV_CBC_ENCUMBRANCE_BALANCES is a read-only view in the Oracle E-Business Suite Contract Commitment (IGC) module. It presents period-to-date encumbrance balances drawn from the journal lines balance view IGC_CBC_JE_LINES_BAL_PTD_V, enriched with descriptive attributes sourced from the General Ledger (GL) schema. As its name suggests, the view is oriented toward encumbrance accounting balances—commitments and obligations recorded against budgetary resources—rather than actual expenditures. Because the view restricts its result set with the predicate ACTUAL_FLAG = 'E' and is defined WITH READ ONLY, it functions strictly as a reporting and inquiry construct. It exposes a queryable, denormalized projection of encumbrance data that downstream reports, concurrent programs, and integration routines can consume without directly navigating the more complex underlying balance structures.

Underlying Base Objects

The view is defined over four referenced objects: IGC_CBC_JE_LINES_BAL_PTD_V, GL_CODE_COMBINATIONS, GL_SETS_OF_BOOKS, and GL_ENCUMBRANCE_TYPES. The core balance data originates from IGC_CBC_JE_LINES_BAL_PTD_V, the driving table in the FROM clause. Joins to the GL objects are performed as follows:

  • GL_SETS_OF_BOOKS is joined via an outer join ((+)) on SET_OF_BOOKS_ID, supplying the ledger name and short name.
  • GL_CODE_COMBINATIONS is joined on CODE_COMBINATION_ID as an inner join, resolving the accounting flexfield.
  • GL_ENCUMBRANCE_TYPES is joined via an outer join ((+)) on ENCUMBRANCE_TYPE_ID, providing the encumbrance type name.

The ETRM metadata additionally lists IGC_CBC_INQUIRY_PKG among the referenced base objects, indicating that the inquiry package participates in the balance resolution chain behind IGC_CBC_JE_LINES_BAL_PTD_V. The view therefore sits atop a layered stack, inheriting its filtering, encumbrance-type, and key-flexfield semantics from that underlying balance view.

Key Columns

The view projects a substantial set of columns, the most significant of which include:

Common Use Cases and Queries

This view is typically used in encumbrance inquiry, budget-versus-commitment reporting, and reconciliation extracts. A representative query retrieving encumbrance balances for a ledger and period is:

  • SELECT DETAIL_SUMMARY_CODE, PERIOD_NAME, ENCUMBRANCE_TYPE_NAME, ENTERED_DR, ENTERED_CR, PERIOD_TO_DATE_BALANCE FROM APPS.IGCBV_CBC_ENCUMBRANCE_BALANCES WHERE SET_OF_BOOKS_ID = :ledger_id AND PERIOD_NAME = :period AND DETAIL_SUMMARY_CODE = 'D';

Other practical applications include filtering by ENCUMBRANCE_TYPE_NAME to isolate a specific commitment class, joining on CODE_COMBINATION_ID to attribute balances to accounting flexfield segments via GL_CODE_COMBINATIONS, and summarizing period-to-date balances by PERIOD_YEAR and QUARTER_NUMBER for trend reporting. Because the view is read-only, it is safe for ad hoc inquiry and warehouse-style extraction without risk of modifying base encumbrance data.