Results for “gl_je_batches”

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

Overview

GL_JE_BATCHES is the master table for journal entry batches in the Oracle E-Business Suite General Ledger module (schema GL). Every journal entry processed by Oracle General Ledger is grouped into a batch, and this table stores the batch header information that governs the grouping, control totals, posting status, and accounting context for the individual journal headers and lines that belong to it. In Oracle EBS 12.1.1 and 12.2.2, GL_JE_BATCHES acts as the entry point for the entire journal lifecycle: import from subledgers, manual creation, approval, posting, reversal, and archiving.

The batch record carries the Set of Books (11i) and Chart of Accounts / period set context that determines which ledger the journals belong to, the actual versus budget indicator, and the running control totals used to validate that the batch is balanced before posting. Because posted and unposted journals, subsidiary batches, and multi-period activity all reference batches, GL_JE_BATCHES is one of the most heavily referenced objects in the EBS financial data model.

From a data modeling perspective, the documented foreign key structure—with GL_JE_BATCHES referencing GL_SETS_OF_BOOKS_11I, FND_CONCURRENT_REQUESTS, and itself via PARENT_JE_BATCH_ID—supports classification of this table as a hub in a Data Vault model. The batch identity (JE_BATCH_ID) is the durable business key around which descriptive attributes and downstream relationships (headers, lines, imports, reversals) are organized.

Key Information Stored

GL_JE_BATCHES contains 73 documented columns. The most operationally significant are:

• JE_BATCH_ID — Surrogate primary key (GL_JE_BATCHES_PK) and unique index GL_JE_BATCHES_U1. Also the foreign key column referenced by GL_JE_HEADERS.JE_BATCH_ID.
• NAME — User-visible batch name. Part of the composite unique index GL_JE_BATCHES_U2 (NAME, DEFAULT_PERIOD_NAME, CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE).
• DEFAULT_PERIOD_NAME — Accounting period to which journals in the batch are assigned by default.
• STATUS and STATUS_VERIFIED — Batch posting status (e.g., U for unposted, P for posted) and a verification flag used by posting programs.
• ACTUAL_FLAG — Distinguishes actual, budget, or encumbrance journals.
• DEFAULT_EFFECTIVE_DATE — Default accounting date applied to journal lines in the batch.
• CONTROL_TOTAL — Expected total used to validate that debits equal credits prior to posting.
• RUNNING_TOTAL_DR, RUNNING_TOTAL_CR, RUNNING_TOTAL_ACCOUNTED_DR, RUNNING_TOTAL_ACCOUNTED_CR — Accumulated debit and credit amounts, entered and accounted, used to determine whether the batch is balanced.
• SET_OF_BOOKS_ID_11I — Foreign key to GL_SETS_OF_BOOKS_11I, identifying the ledger/set of books.
• PARENT_JE_BATCH_ID — Self-referencing FK identifying a parent batch, used for grouping subordinate batches and reversals.
• POSTED_DATE and POSTED_BY — Timestamp and user responsible for the posting action.
• REQUEST_ID — Foreign key to FND_CONCURRENT_REQUESTS, linking the batch to the concurrent request that created or processed it.
• CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE — Accounting context columns completing the business-key composite in GL_JE_BATCHES_U2.
• APPROVAL_STATUS_CODE and APPROVER_EMPLOYEE_ID — Journal approval workflow state and approver identity.

Common Use Cases and Queries

Typical scenarios include identifying unposted or unbalanced batches, tracing journal sources to concurrent requests, reporting posted activity by ledger and period, and reconciling subledger transfers. Representative query patterns:

• List all unposted batches for a ledger and period:
  SELECT b.je_batch_id, b.name, b.default_period_name, b.status
FROM gl_je_batches b
WHERE b.set_of_books_id_11i = :sob AND b.status = 'U';
• Detect unbalanced batches by comparing control totals to running totals:
  SELECT je_batch_id, name, control_total,
  running_total_dr, running_total_cr
FROM gl_je_batches
WHERE control_total <> (running_total_dr - running_total_cr);
• Trace batch activity to the concurrent request that generated it:
  SELECT b.je_batch_id, b.name, r.request_id, r.phase_code
FROM gl_je_batches b, fnd_concurrent_requests r
WHERE b.request_id = r.request_id;
• Report batch totals by period and ledger for financial close:
  SELECT set_of_books_id_11i, default_period_name,
  sum(running_total_accounted_dr), sum(running_total_accounted_cr)
FROM gl_je_batches
WHERE actual_flag = 'A'
GROUP BY set_of_books_id_11i, default_period_name;

These patterns support close-cycle monitoring, audit reporting, and interfaces that push balanced batches through the GL posting programs (e.g., Journal Posting, Journal Import, and the Journal Reversal processes).

Related Objects

GL_JE_BATCHES is referenced by a broad set of financial tables. The most significant relationships include:

• GL_JE_HEADERS — Child table containing the individual journals; joins on GL_JE_HEADERS.JE_BATCH_ID = GL_JE_BATCHES.JE_BATCH_ID. This is the primary reporting linkage.
• GL_SETS_OF_BOOKS_11I — Parent ledger definition, joined via SET_OF_BOOKS_ID_11I.
• FND_CONCURRENT_REQUESTS — Concurrent request audit trail, joined via REQUEST_ID.
• GL_JE_BATCHES (self) — Parent/child batch grouping via PARENT_JE_BATCH_ID.
• FA_DEPRN_PERIODS — Fixed Assets depreciation period table, referencing batches for depreciation, revaluation, reclass, retirement, addition, adjustment, transfer, and CIP batch IDs (e.g., DEPRECIATION_BATCH_ID, REVAL_BATCH_ID, CIP_TRANSFER_BATCH_ID).
• FA_MC_DEPRN_PERIODS — Corresponding multi-currency depreciation period batches, following the same batch-ID pattern.
• GL_INTERFACE — Journal import interface, linked via JE_BATCH_ID for batch identification during import.
• AP_CHECK_TRANSMISSIONS / AP_INVOICE_TRANSMISSIONS — Payables transmissions referencing the JE_BATCH_ID to tie payment activity to GL batches.
• GL_CONS_BATCHES, GL_AUTO_ALLOC_BATCH_HISTORY, GL_AUTO_ALLOC_REV_BATCHES, GL_ELIMINATION_HISTORY — Consolidation, allocation, and elimination processes that store references to generated and reversal batches.
• GL_ARCHIVE_BATCHES, GL_IMPORT_REFERENCES, GL_BC_PACKETS — Archive, import reference, and budgetary control packet tables linked through JE_BATCH_ID.