Search Results igc_cbcjel




Overview
Explore in AI Chat

Overview

APPS.IGCFV_CBC_MC_JOURNAL_LINES is a read-only reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It is part of the Oracle Financials Common Modules and the Intercompany (IGC) consolidation infrastructure. The view is defined with the WITH READ ONLY clause, which prevents any DML against it and confirms its purpose as a denormalized query surface rather than a transactional object.

The view presents consolidated multi-currency (MC) journal line information for intercompany cross-charge batches, joining the transactional journal lines against batch headers and the chart of accounts ledger (set of books). It exposes human-readable identifiers such as the set-of-books name and the batch name alongside the numeric identifiers required for joins, making it suitable for ad-hoc reporting, reconciliation, diagnostic queries, and downstream integrations that need to extract journal line detail without navigating the base tables directly.

Underlying Base Objects

The view is defined over four referenced objects, as documented in the ETRM metadata:

  • IGC_CBC_MC_JE_LINES (SYNONYM) — the primary multi-currency journal line source, aliased as IGCMJL. This is the driving table for the line-level detail.
  • IGC_CBC_JE_BATCHES (SYNONYM) — the batch header, aliased as IGC_CBCJEB, supplying the batch name and batch identifier.
  • IGC_CBC_JE_LINES (SYNONYM) — the single-currency journal lines, aliased as IGC_CBCJEL, used in an equi-join on the journal line number.
  • GL_SETS_OF_BOOKS (VIEW) — the General Ledger ledger definitions, supplying the set-of-books name and short name; joined on the reporting set-of-books identifier.

The joins are performed on IGCMJL.CBC_JE_LINE_NUM = IGC_CBCJEL.CBC_JE_LINE_NUM, IGCMJL.CBC_JE_BATCH_ID = IGC_CBCJEB.CBC_JE_BATCH_ID, and IGCMJL.REPORTING_SET_OF_BOOKS_ID = GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID. The view therefore assembles batch, line, and ledger context in a single result set.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling intercompany multi-currency journal lines against their single-currency counterparts, auditing currency conversion rates and dates applied to a batch, and extracting line detail for reporting or data migration. Because the view is read-only, it is safe to query in production without transactional side effects.

Sample SQL:

  • Retrieve all lines for a given batch: SELECT * FROM APPS.IGCFV_CBC_MC_JOURNAL_LINES WHERE BATCH_NAME = :batch_name;
  • Filter by currency and ledger: SELECT BATCH_NAME, JOURNAL_LINE_NUMBER, ENTERED_DR, ENTERED_CR FROM APPS.IGCFV_CBC_MC_JOURNAL_LINES WHERE CURRENCY_CODE = 'USD' AND SETS_OF_BOOKS_SHORT_NAME = :ledger;
  • Audit conversion details: SELECT JOURNAL_LINE_NUMBER, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE FROM APPS.IGCFV_CBC_MC_JOURNAL_LINES WHERE BATCH_ID = :batch_id ORDER BY JOURNAL_LINE_NUMBER;

Note that the view inherits the row-level and ledger security enforced by the underlying IGC and GL objects; responsibility-level access to intercompany data should be verified before broad extraction.