Search Results gl_je_batches




Overview
Explore in AI Chat

Overview

The GL_JE_BATCHES table is a core data structure within the Oracle E-Business Suite General Ledger (GL) module. It serves as the primary repository for journal entry batch headers, which are logical groupings of individual journal entries. A batch provides a critical control and processing layer, allowing users to manage, post, and review multiple related journal entries as a single unit. Its role is fundamental to the financial accounting process, acting as the parent container for detailed journal lines stored in related tables like GL_JE_HEADERS and GL_JE_LINES. The integrity of the batch is enforced by its primary key and its relationships with key setup entities, such as the ledger (SET_OF_BOOKS_ID_11I).

Key Information Stored

The table stores essential control and descriptive attributes for each journal batch. The primary identifier is the system-generated JE_BATCH_ID. Key business columns include the user-defined NAME of the batch and the DEFAULT_PERIOD_NAME, which specifies the accounting period. The SET_OF_BOOKS_ID_11I column is a foreign key to GL_SETS_OF_BOOKS_11I, linking the batch to a specific ledger. Other significant columns track processing status (e.g., STATUS, POSTED_DATE), control totals (e.g., RUNNING_TOTAL_DR, RUNNING_TOTAL_CR), and system process information such as REQUEST_ID for concurrent requests and PARENT_JE_BATCH_ID for hierarchical batch structures.

Common Use Cases and Queries

This table is central to journal processing and financial reporting. Common operational scenarios include identifying unposted batches for a specific ledger, tracing the source of posted entries, and analyzing batch-level control totals. A typical query retrieves batch details along with status and ledger information:

  • SELECT je_batch_id, name, status, default_period_name, posted_date FROM gl_je_batches WHERE set_of_books_id_11i = :ledger_id AND status = 'U';

For audit and reconciliation purposes, analysts often join GL_JE_BATCHES with GL_JE_HEADERS and GL_JE_LINES to report on all entries within batches posted in a given period. Troubleshooting data integration from subledgers like Payables or Assets frequently involves querying this table using the batch name or request ID to locate specific journal imports.

Related Objects

GL_JE_BATCHES has extensive relationships within the E-Business Suite. It is the parent table for GL_JE_HEADERS, which in turn contains GL_JE_LINES. As indicated by the foreign key metadata, it references GL_SETS_OF_BOOKS_11I for the ledger and FND_CONCURRENT_REQUESTS for process tracking. Crucially, it is referenced by numerous transactional tables across other modules, establishing its role as a key integration point. Significant referencing objects include AP_CHECK_TRANSMISSIONS and AP_INVOICE_TRANSMISSIONS (Payables), and multiple batch ID columns in FA_DEPRN_PERIODS and FA_MC_DEPRN_PERIODS (Assets), which track journals generated for depreciation, additions, retirements, and other fixed asset transactions.