Search Results igcfv_cbc_mc_journal_lines




Overview
Explore in AI Chat

Overview

The view APPS.IGCFV_CBC_MC_JOURNAL_LINES is a reporting object within the Oracle E-Business Suite (EBS) IGC — Contract Commitment product. It is defined in the APPS schema with a documented status of VALID and is available in EBS releases 12.1.1 and 12.2.2. The view presents journal line information associated with contract commitment batch processing, joining multi-currency journal entry lines to their parent batch and the corresponding general ledger set of books. The "MC" component of the object name indicates that the view is oriented toward multi-currency journal data, exposing conversion type, conversion date, and conversion rate attributes alongside entered debit and credit amounts.

Functionally, the view serves as a flattened, read-only reporting interface that shields consumers from the underlying IGC contract commitment journal schema. It is defined with the WITH READ ONLY clause, meaning no DML operations can be performed against it; its sole purpose is query and reporting access. Because it resolves the set of books name and short name through a join to GL_SETS_OF_BOOKS, the view is well suited to building ad hoc reports, reconciliation queries, and integration extracts that require human-readable accounting context rather than raw identifiers.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over four referenced base objects:

  • IGC_CBC_MC_JE_LINES (SYNONYM) — aliased as IGCMJL, this is the primary source of journal line detail, supplying line number, entered debit and credit, reporting currency code, conversion attributes, reporting set of books identifier, and batch identifier.
  • IGC_CBC_JE_LINES (SYNONYM) — aliased as IGC_CBCJEL, joined on CBC_JE_LINE_NUM to link the multi-currency line to its base journal line record.
  • IGC_CBC_JE_BATCHES (SYNONYM) — aliased as IGC_CBCJEB, joined on CBC_JE_BATCH_ID to supply the batch name.
  • GL_SETS_OF_BOOKS (VIEW) — joined on SET_OF_BOOKS_ID to supply the set of books name and short name.

The join conditions correlate each multi-currency journal line to its batch and to the reporting set of books, producing one row per journal line enriched with batch and ledger descriptors.

Key Columns

  • SETS_OF_BOOKS_NAME / SETS_OF_BOOKS_SHORT_NAME — the full and abbreviated names of the general ledger set of books, sourced from GL_SETS_OF_BOOKS.
  • BATCH_NAME — the descriptive name of the contract commitment journal entry batch (IGC_CBCJEB.NAME).
  • JOURNAL_LINE_NUMBER — the line sequence number within the batch (CBC_JE_LINE_NUM).
  • ENTERED_DR / ENTERED_CR — the entered debit and credit amounts for the line in the entered (transaction) currency.
  • CURRENCY_CODE — the reporting currency code for the line.
  • CURRENCY_CONVERSION_TYPE — the conversion rate type applied (for example, Spot or Corporate).
  • CURRENCY_CONVERSION_DATE — the date governing the currency conversion.
  • CURRENCY_CONVERSION_RATE — the rate used to convert entered amounts to the reporting currency.
  • SET_OF_BOOKS_ID / BATCH_ID — the reporting set of books identifier and the parent batch identifier, useful as join keys in downstream queries.

Common Use Cases and Queries

Typical scenarios include reconciling contract commitment journal lines to the general ledger, auditing currency conversion rates applied across batches, and extracting line-level detail for subledger reporting. A representative query listing journal lines for a specific batch follows:

  • SELECT batch_name, journal_line_number, entered_dr, entered_cre, currency_code, currency_conversion_type, currency_conversion_rate FROM apps.igcfv_cbc_mc_journal_lines WHERE batch_id = :p_batch_id ORDER BY journal_line_number;
  • SELECT sets_of_books_short_name, batch_name, SUM(entered_dr), SUM(entered_cr) FROM apps.igcfv_cbc_mc_journal_lines GROUP BY sets_of_books_short_name, batch_name;
  • SELECT * FROM apps.igcfv_cbc_mc_journal_lines WHERE currency_code <> 'USD' AND currency_conversion_rate IS NOT NULL;

Because the view is read-only, it can be safely exposed to reporting users and BI tools without risk of data modification.