Search Results reference_4




Overview
Explore in AI Chat

Overview

The view APPS.IGCBV_CBC_JOURNAL_LINES is a read-only database object shipped within the Oracle E-Business Suite (EBS) Contract Commitment module, identified by the product code IGC. In EBS 12.1.1 and 12.2.2, the Contract Commitment module supports the generation and maintenance of commitment (encumbrance) accounting entries that are eventually transferred to General Ledger. The view exposes the journal lines produced by the Contract Commitment journal entry generation process, presenting each commitment journal line together with its associated batch context.

The IGCBV_ prefix denotes a Business View belonging to the IGC product, and the view is owned by the APPS schema with a documented status of VALID. Its role is primarily reporting and integration: it provides a denormalised, consumer-friendly projection of commitment journal lines joined to their parent batches, allowing concurrent programs, reports, and external interfaces to read commitment accounting data without navigating the underlying normalised tables directly. The view is defined WITH READ ONLY, so it may only be queried, never modified.

Underlying Base Objects

The view is defined over two synonyms that resolve to the base tables of the Contract Commitment journal architecture:

  • IGC_CBC_JE_LINES (aliased IGC_CBCJEL) — the commitment journal entry lines table, holding individual debit and credit lines, references, amount columns, and accounting attributes.
  • IGC_CBC_JE_BATCHES (aliased IGC_CBCJEB) — the commitment journal entry batches table, holding batch-level attributes such as the batch name.

The two objects are joined on the batch identifier: IGC_CBCJEL.CBC_JE_BATCH_ID = IGC_CBCJEB.CBC_JE_BATCH_ID. Because the view performs an inner join, only journal lines that have a valid parent batch are returned. The batch name from the header table is projected into the view as BATCH_NAME, giving each line its batch context.

Key Columns

The view exposes a broad set of columns spanning line identity, accounting classification, amounts, and audit attributes:

Common Use Cases and Queries

Typical uses include reconciliation of commitment journal lines to General Ledger, reporting on commitment activity by period or ledger, extraction of reference information for downstream interfaces, and troubleshooting of journal generation. A representative query retrieving lines for a specific reference follows:

  • SELECT journal_line_number, journal_source, journal_category, batch_name, period_name, entered_dr, entered_cref, reference_3 FROM apps.igcbv_cbc_journal_lines WHERE reference_3 = :reference_value;

Aggregation by period and ledger is equally common:

  • SELECT period_name, set_of_books_id, SUM(entered_dr) dr, SUM(entered_cr) cr FROM apps.igcbv_cbc_journal_lines GROUP BY period_name, set_of_books_id;

Because the view is read-only, it is safe for concurrent reporting and cannot be used for DML; all modifications must target the underlying IGC_CBC_JE_LINES and IGC_CBC_JE_BATCHES tables.