Search Results gl_budget_batches




Overview
Explore in AI Chat

Overview

The GL_BUDGET_BATCHES table is a core data object within the Oracle E-Business Suite General Ledger (GL) module, specifically for releases 12.1.1 and 12.2.2. It functions as a junction or association table that manages the relationship between budget versions and recurring batch processes. Its primary role is to track which recurring formula batches are assigned to a specific budget version, thereby enabling the automated, periodic generation of budget data through defined formulas. This table is essential for organizations utilizing Oracle's budget formulation and mass allocation capabilities to streamline their financial planning cycles.

Key Information Stored

The table's structure is defined by its composite primary key, which consists of two critical foreign key columns. These columns store the identifiers that link the two main entities. The BUDGET_VERSION_ID column stores the unique identifier for a specific budget version, as defined in the GL_BUDGET_VERSIONS table. The RECURRING_BATCH_ID column stores the unique identifier for a recurring batch process, as defined in the GL_RECURRING_BATCHES table. Together, each record in this table represents a single, explicit assignment of a recurring batch to a budget version for execution.

Common Use Cases and Queries

A primary use case is auditing and reporting on the configuration of automated budget processes. System administrators and financial analysts query this table to verify which recurring batches are scheduled to populate a given budget version, ensuring setup accuracy before a planning cycle begins. A common diagnostic query involves joining to the related master tables to get descriptive information. For example:

  • To list all recurring batches linked to a specific budget version: SELECT gbb.*, gbv.NAME, grb.BATCH_NAME FROM GL.GL_BUDGET_BATCHES gbb JOIN GL.GL_BUDGET_VERSIONS gbv ON gbb.BUDGET_VERSION_ID = gbv.BUDGET_VERSION_ID JOIN GL.GL_RECURRING_BATCHES grb ON gbb.RECURRING_BATCH_ID = grb.RECURRING_BATCH_ID WHERE gbv.NAME = '<Budget_Version_Name>';
  • To identify budget versions that have no recurring batches assigned, which may indicate an incomplete setup: SELECT gbv.* FROM GL.GL_BUDGET_VERSIONS gbv WHERE NOT EXISTS (SELECT 1 FROM GL.GL_BUDGET_BATCHES gbb WHERE gbb.BUDGET_VERSION_ID = gbv.BUDGET_VERSION_ID);

Related Objects

The GL_BUDGET_BATCHES table has direct, documented foreign key relationships with two key parent tables in the General Ledger schema, as per the provided ETRM metadata. These relationships are fundamental to its purpose and data integrity.

  • GL_BUDGET_VERSIONS: This table is referenced via the BUDGET_VERSION_ID column. It stores the master definition of budget versions, including name, status, and associated ledger.
  • GL_RECURRING_BATCHES: This table is referenced via the RECURRING_BATCH_ID column. It stores the definition of recurring batches, which contain formulas for generating journal or budget entries on a scheduled basis.

These relationships enforce that a record in GL_BUDGET_BATCHES cannot exist without a valid corresponding record in both parent tables, ensuring configuration consistency.