Search Results journal_batch_id

Overview

The IGCFV_CBC_JOURNAL_BATCHES view is a read-only reporting object in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It belongs to the IGC (Contract Commitment) product family and presents journal batch header information generated by the Contract Commitment feature. Within EBS, contract commitments produce budgetary accounting entries that must be transferred to General Ledger as journal batches. This view consolidates the descriptive attributes of those batches — name, status, balance type, approval and funds-check states, running debit/credit totals, effective date, and set of books — into a single denormalized layer intended for reports, integrations, and inquiry screens.

The view carries a WITH READ ONLY clause, confirming it is strictly a query surface with no DML capability. Client-extension views such as this one (signaled by the internal name mapping in the "_LA:" aliases) expose lookup descriptions rather than raw codes, simplifying downstream consumption. The column JOURNAL_BATCH_ID, derived from IGC_CBCJEB.CBC_JE_BATCH_ID, is the primary identifier users search for when retrieving a specific contract commitment journal batch.

Underlying Base Objects

The view is defined over three documented objects:

• IGC_CBC_JE_BATCHES (SYNONYM) — the driving table, aliased IGC_CBCJEB. It supplies batch identity, running totals, effective date, description, accounting context (SET_OF_BOOKS_ID), commitment linkage (CC_HEADER_ID), and audit columns.
• IGC_CC_HEADERS (SYNONYM) — aliased IGC_CCH, joined with an outer-join ((+)) on CC_HEADER_ID. It supplies the human-readable contract commitment number (CC_NUM). Because the join is optional, batches without an associated header still appear.
• GL_SETS_OF_BOOKS (VIEW) — joined on SET_OF_BOOKS_ID. It provides the set of books name and short name for accounting-context identification.

Notably, the join to GL_SETS_OF_BOOKS is inner, so a batch with no matching set of books will be excluded from the result set.

Key Columns

• JOURNAL_BATCH_ID — the batch's unique internal identifier (source CBC_JE_BATCH_ID); the principal lookup key.
• BATCH_NAME — the batch's user-defined name.
• "_LA:BATCH_STATUS", "_LA:BALANCE_TYPE", "_LA:APPROVAL_STATUS", "_LA:FUNDS_CHECK_STATUS" — lookup-derived descriptions exposing batch status, balance (actual vs. budgetary) type, approval state, and budgetary-control funds-check result.
• RUNNING_TOTAL_DR / RUNNING_TOTAL_CR — accumulated debit and credit amounts for the batch.
• EFFECTIVE_DATE, DESCRIPTION — the accounting effective date and free-text description.
• CONTRACT_COMMITMENT_NUMBER and CONTRACT_COMMITMENT_ID — the associated commitment header number and its key.
• SETS_OF_BOOKS_NAME, SETS_OF_BOOKS_SHORT_NAME, SET_OF_BOOKS_ID — accounting-context identification.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns.

Common Use Cases and Queries

Typical uses include reconciling contract commitment batches to GL, reporting approval/funds-check status, and supporting integration extracts. A representative query retrieving a specific batch by ID is:

SELECT journal_batch_id, batch_name, contract_commitment_number, sets_of_books_name, effective_date, running_total_dr, running_total_cr, "_LA:APPROVAL_STATUS", "_LA:FUNDS_CHECK_STATUS" FROM apps.igcfv_cbc_journal_batches WHERE journal_batch_id = :p_batch_id;

To list all batches for a commitment or set of books, filter on CONTRACT_COMMITMENT_ID or SET_OF_BOOKS_ID. Because the lookup columns are quoted mixed-case aliases, they must be referenced exactly as shown. All queries should target the APPS synonym and be executed against the appropriate EBS environment.