Search Results gl_recurring_batches




Overview
Explore in AI Chat

Overview

The GL_RECURRING_BATCHES table is a core data object within the Oracle E-Business Suite (EBS) General Ledger (GL) module. It serves as the master repository for recurring journal entry and budget formula batches. These batches are foundational for automating the creation of repetitive journal entries and budget calculations across accounting periods, thereby enforcing consistency and reducing manual effort. The table's role is to store the high-level definition and control information for a batch, which in turn contains one or more individual recurring journal or budget formulas. Its existence is critical for the period-end close and budgeting processes, ensuring standardized, repeatable postings are generated according to a defined schedule and template.

Key Information Stored

The table stores the defining attributes for a recurring batch. While the full column list is not detailed in the provided metadata, the documented primary and foreign keys reveal its critical data points. The primary identifier is RECURRING_BATCH_ID. The NAME column is also a unique key, enforcing uniqueness for batch names. The table links to the chart of books structure via the LEDGER_ID foreign key to GL_SETS_OF_BOOKS_11I, associating the batch with a specific ledger. It references the accounting calendar via PERIOD_TYPE to GL_PERIOD_TYPES. For budget-related batches, it tracks the LAST_EXEC_BUDGET_VERSION_ID, linking to GL_BUDGET_VERSIONS to record the last budget version used during execution. Other typical columns (implied by standard functionality) would include status, creation and last update dates, description, and control totals.

Common Use Cases and Queries

This table is central to managing and reporting on automated accounting processes. Common operational scenarios include auditing the inventory of all recurring batches, identifying batches for a specific ledger, and troubleshooting batch execution issues. For reporting, administrators often need to list batches alongside their execution history or child entries. A typical query would join to related header tables to assess the volume and value of transactions generated. A sample SQL pattern to list active recurring batches for a ledger would be:

  • SELECT name, description, creation_date FROM gl_recurring_batches WHERE ledger_id = :ledger_id AND status = 'A';

Another critical use case involves data migration or reconciliation, where scripts might reference this table to validate the setup of recurring processes before and after a system change.

Related Objects

The GL_RECURRING_BATCHES table has defined relationships with several other key GL tables, forming the backbone of the recurring transactions subsystem. As per the provided foreign key metadata:

  • Parent Tables (Foreign Key References):
    • GL_SETS_OF_BOOKS_11I (via LEDGER_ID)
    • GL_PERIOD_TYPES (via PERIOD_TYPE)
    • GL_BUDGET_VERSIONS (via LAST_EXEC_BUDGET_VERSION_ID)
  • Child Tables (Referenced by Foreign Keys):

These relationships illustrate that a single recurring batch in GL_RECURRING_BATCHES can parent multiple recurring journal headers (GL_RECURRING_HEADERS) and budget batches (GL_BUDGET_BATCHES).