Results for “igc_cbc_je_batches”

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

Overview

IGC_CBC_JE_BATCHES is a transactional table within the IGC (Contract Commitment) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores commitment budgetary control journal entry batches, which group the accounting entries generated when contract commitments are subjected to budgetary control processing. In the Oracle EBS architecture, this table acts as the batch-level header for commitment journal entries, providing the control and reconciliation point between the subledger commitment activity and the General Ledger sets of books. Each row represents one budgetary control batch, identified by the surrogate primary key CBC_JE_BATCH_ID, and serves as the parent for the individual journal lines and multi-currency detail records that make up the batch.

From a Data Vault modeling perspective, the heuristic classification of this table is hub-leaning. The CBC_JE_BATCH_ID surrogate key functions as the hub key, with the batch as the central business entity around which lines, multi-currency records, and archive records are organized. Modelers should treat it as a hub-style anchor rather than a pure satellite, given the volume of dependent child relationships.

Key Information Stored

The table contains 33 documented columns. The most significant are:

• CBC_JE_BATCH_ID — Surrogate primary key (IGC_CBC_JE_BATCHES_PK) and the unique business key candidate (IGC_CBC_JE_BATCHES_U1).
• SET_OF_BOOKS_ID — Foreign key to GL_SETS_OF_BOOKS, identifying the ledger to which the batch posts.
• CC_HEADER_ID — Reference linking the batch back to the originating commitment header.
• NAME — Descriptive batch name; DESCRIPTION — free-text explanation.
• BATCH_STATUS, BUDGETARY_CONTROL_STATUS, APPROVAL_STATUS_CODE — Lifecycle and control state indicators.
• ACTUAL_FLAG — Distinguishes actual versus budgetary amounts.
• EFFECTIVE_DATE — Accounting date of the batch.
• RUNNING_TOTAL_DR and RUNNING_TOTAL_CR — Aggregate debit and credit totals for the batch.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard audit columns.
• ATTRIBUTE1 through ATTRIBUTE15 — Flexfield-style descriptive attributes for extensibility.

Common Use Cases and Queries

Typical uses include reconciling budgetary control batches prior to GL posting, auditing commitment-to-budget flows, and reporting on approval and posting status. A representative query joins the batch to its ledger and lines:

• SELECT b.cbc_je_batch_id, b.name, b.batch_status, b.budgetary_control_status, l.amount FROM igc_cbc_je_batches b, igc_cbc_je_lines l WHERE b.cbc_je_batch_id = l.cbc_je_batch_id AND b.set_of_books_id = :ledger_id;
• Balance inspection: SELECT running_total_dr, running_total_cr FROM igc_cbc_je_batches WHERE cbc_je_batch_id = :id;
• Status reporting filtering on ACTUAL_FLAG and BUDGETARY_CONTROL_STATUS to identify unapproved or unposted batches.

Related Objects

The table participates in a well-defined referential network:

• GL_SETS_OF_BOOKS — referenced via SET_OF_BOOKS_ID.
• IGC_CBC_JE_LINES — child lines via CBC_JE_BATCH_ID.
• IGC_CBC_MC_JE_BATCHES — multi-currency batch records via CBC_JE_BATCH_ID.
• IGC_CBC_INTERFACE_EXCEPTIONS — captures processing exceptions for a batch.
• Archive counterparts — IGC_CBC_ARCHIVE_JE_BATCHES, IGC_CBC_ARCHIVE_JE_LINES, IGC_CBC_ARCHIVE_MC_JE_BATCHES, and IGC_CBC_ARCHIVE_MC_JE_LINES — all linked through CBC_JE_BATCH_ID for historical retention.