Results for “igi_bud_journal_batches”

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

Overview

The IGI.IGI_BUD_JOURNAL_BATCHES table is a core transactional object within the IGI — Public Sector Financials International product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the batch-level header information for budget journals, acting as the highest grouping construct for a set of related budget journal entries before they are validated, totaled, and posted. Each row represents one budget journal batch and carries the control information (batches, totals, completion status, and audit fields) that governs the journal lines and headers belonging to it.

Under the ETRM Data Vault heuristic classification, this table is hub-leaning. The primary key BE_BATCH_ID is a surrogate identifier generated by the system, and multiple downstream tables reference it as a foreign key. From a dimensional modeling perspective, this suggests treating IGI_BUD_JOURNAL_BATCHES as a hub in a Data Vault design, with the referencing tables (IGI_BUD_JOURNAL_HEADERS, IGI_BUD_JOURNAL_PERIODS, and IGI_BUD_JOURNAL_LINES) acting as links or satellites that carry their own descriptive and transactional detail.

Key Information Stored

The table comprises 16 documented columns. The most significant are:

• BE_BATCH_ID — The surrogate primary key (IGI_BUD_JOURNAL_BATCHES_PK), uniquely identifying each budget journal batch. This is the column referenced by all child tables.
• NAME — The user-facing batch name or description.
• FISCAL_YEAR and SET_OF_BOOKS_ID — The accounting context in which the batch is created; together these establish the period and ledger for the budget entries.
• RECORD_TYPE — Classifies the nature of the batch (for example, budget, encumbrance, or actual, depending on IGI configuration).
• COMPLETE_FLAG — Indicates whether the batch has been finalized and is ready for downstream processing.
• CONTROL_TOTAL — The expected total amount of the batch, used for reconciliation against the sum of journal lines.
• RUNNING_TOTAL_DR and RUNNING_TOTAL_CR — Accumulated debit and credit totals as lines are added, facilitating balance checks.
• DATE_COMPLETED — The date the batch was marked complete.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit and WHO columns tracking insert and modification history.
• REQUEST_ID — Links the batch to the concurrent request that created or processed it, aiding diagnostics and reconciliation.

The only documented unique index is the primary key on BE_BATCH_ID; no separate business-key unique index is recorded, so BE_BATCH_ID is both the surrogate and the operative identifier.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include verifying that batches balance, monitoring incomplete batches, and tracing budget journal activity by ledger and fiscal year. A representative query to find batches whose control total does not match the running totals might be:

• SELECT BE_BATCH_ID, NAME, CONTROL_TOTAL, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR FROM IGI.IGI_BUD_JOURNAL_BATCHES WHERE COMPLETE_FLAG = 'N';
• SELECT BE_BATCH_ID, NAME, FISCAL_YEAR, CONTROL_TOTAL FROM IGI.IGI_BUD_JOURNAL_BATCHES WHERE SET_OF_BOOKS_ID = :ledger_id AND FISCAL_YEAR = :year;
• SELECT b.BE_BATCH_ID, b.NAME, h.* FROM IGI.IGI_BUD_JOURNAL_BATCHES b JOIN IGI.IGI_BUD_JOURNAL_HEADERS h ON h.BE_BATCH_ID = b.BE_BATCH_ID WHERE b.COMPLETE_FLAG = 'Y';

These patterns support batch status dashboards, period-close reconciliation, and drill-down from batch to header and line level.

Related Objects

The following objects reference or are referenced by IGI_BUD_JOURNAL_BATCHES through the documented foreign key relationships:

• IGI_BUD_JOURNAL_HEADERS — References BE_BATCH_ID; holds batch header detail.
• IGI_BUD_JOURNAL_PERIODS — References BE_BATCH_ID; stores period-level batch information.
• IGI_BUD_JOURNAL_LINES — References BE_BATCH_ID; contains the individual budget journal lines belonging to the batch.

Together these tables form the budget journal batch hierarchy, with IGI_BUD_JOURNAL_BATCHES at the top of the relationship chain, and the dependent tables keyed back to it via BE_BATCH_ID.