Results for “igc_cbc_mc_je_batches”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGC_CBC_MC_JE_BATCHES is a table owned by the IGC schema within the IGC - Contract Commitment module of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. It is described as the multiple reporting currency table for commitment budgetary control journal entry batches. Its purpose is to store the reporting-currency-denominated balances and conversion attributes associated with a commitment budgetary control batch, allowing a single batch to be carried in more than one reporting set of books.

In the standard EBS architecture, the primary batch record lives in IGC_CBC_JE_BATCHES, and this table extends that record into the multiple reporting currency (MRC) dimension, one row per reporting set of books per batch. From a Data Vault modeling perspective, the mined FK structure suggests a link classification: the table resolves a many-to-many style relationship between budgetary control batches and reporting sets of books, carrying descriptive conversion attributes alongside the relationship.

Key Information Stored

The physical schema contains ten documented columns. CBC_JE_BATCH_ID identifies the parent commitment budgetary control batch, while REPORTING_SET_OF_BOOKS_ID identifies the reporting ledger (set of books) under which the amounts are expressed. Together these two columns form the primary key IGCMJB_PK and also form the unique index IGC_CBC_MC_JE_BATCHES_U1, making them the composite business-key candidate for the table. Because the primary key is composite, there is no single-column surrogate key; the FK columns themselves serve as the unique identifier.

• Reporting currency context: REPORTING_CURRENCY_CODE holds the currency of the reporting ledger, and CONVERSION_TYPE, CONVERSION_DATE and CONVERSION_RATE capture how the functional amounts were converted.
• Batch balances: RUNNING_TOTAL_DR and RUNNING_TOTAL_CR hold the accumulated debit and credit totals for the batch within the reporting currency.
• Audit columns: CREATION_DATE and CREATED_BY capture standard row audit information.

Common Use Cases and Queries

A frequent requirement is to determine, for a given reporting set of books, all commitment budgetary control batches and their accumulated balances. The composite key makes this a direct lookup:

SELECT b.CBC_JE_BATCH_ID, b.REPORTING_SET_OF_BOOKS_ID,
       b.REPORTING_CURRENCY_CODE, b.RUNNING_TOTAL_DR, b.RUNNING_TOTAL_CR,
       b.CONVERSION_TYPE, b.CONVERSION_DATE, b.CONVERSION_RATE
FROM   IGC.IGC_CBC_MC_JE_BATCHES b
WHERE  b.REPORTING_SET_OF_BOOKS_ID = :reporting_so_id;

Because REPORTING_SET_OF_BOOKS_ID is the second column of the unique index and not the leading column, queries filtered on this column alone may not use the index efficiently; joining from the parent batch table is often preferred. A typical reporting query joins to GL_SETS_OF_BOOKS to obtain the ledger name, and to the parent batch for header context. Reconciliation reports compare RUNNING_TOTAL_DR minus RUNNING_TOTAL_CR per reporting set of books, and MRC translation audit reports examine CONVERSION_RATE, CONVERSION_TYPE and CONVERSION_DATE to verify that currency conversion was performed correctly.

Related Objects

• IGC_CBC_JE_BATCHES — parent batch table; joined on CBC_JE_BATCH_ID. Every reporting-currency row references exactly one base batch.
• GL_SETS_OF_BOOKS — reporting ledger definition; joined on REPORTING_SET_OF_BOOKS_ID to retrieve ledger name and functional currency.
• GL_CURRENCIES — referenced through REPORTING_CURRENCY_CODE for currency descriptions and precision.
• GL_DAILY_CONVERSION_TYPES — referenced through CONVERSION_TYPE to identify the translation rate type used.
• FND_USER — referenced through CREATED_BY for audit traceability.
• IGC_CBC_JE_LINES — line-level detail for the parent batch, used with this table to reconcile batch totals.

The table is populated as part of the budgetary control commitment processing flow and is normally accessed through the application rather than maintained manually.