Search Results balancing_segment_value




Overview

The APPS.IGCFV_CBC_JOURNAL_LINES view is a reporting and integration object within the Oracle E-Business Suite IGC – Contract Commitment product family. It exposes the journal line records entered against contract commitment batches, presenting them in a denormalized, business-friendly form suitable for reporting, extract, and downstream integration. The view carries a VALID status in the APPS schema and is defined over the IGC Contract Commitment journal entry line table (IGC_CBC_JE_LINES) joined to its batch header (IGC_CBC_JE_BATCHES) and a set of General Ledger reference tables.

Because the view flattens accounting flexfield, currency, period, and encumbrance context alongside the raw journal amounts, it is commonly consumed by custom reports, Oracle Discoverer worksheets, and interfaces that must reconcile commitment journal activity back to the General Ledger. The inclusion of the BALANCING_SEGMENT_VALUE column makes the view particularly relevant to users searching on that term, since balancing segment analysis is a frequent requirement in commitment accounting and budgetary control reporting.

Underlying Base Objects

The view is documented as being defined over the following base objects:

The join pattern links each journal line to its batch, its code combination, and the relevant GL reference rows, producing a single denormalized row per commitment journal line.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciliation of commitment journal lines to GL, balancing segment analysis, and encumbrance reporting by set of books and period.

SELECT balancing_segment_value,
       period_name,
       SUM(entered_dr) dr,
       SUM(entered_credit) cr
FROM   apps.igcfv_cbc_journal_lines
WHERE  set_of_books_id = :p_sob
AND    period_name = :p_period
GROUP BY balancing_segment_value, period_name;
SELECT batch_name, journal_line_number, gl_account,
       entered_dr, entered_cr, encumbrance_type_name
FROM   apps.igcfv_cbc_journal_lines
WHERE  journal_source = :p_source
ORDER BY batch_name, journal_line_number;

The view should be queried with the APPS schema or a synonym, and filtered on SET_OF_BOOKS_ID and PERIOD_NAME to bound result sets.