Results for “gl_budget_batches”

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

Overview

GL_BUDGET_BATCHES is a General Ledger (GL) table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model that stores budget formula batches. It holds the association between a budget version defined in GL_BUDGET_VERSIONS and a recurring batch defined in GL_RECURRING_BATCHES, effectively recording which recurring journal or budget batch processes are run against a given budget version. This table is central to the Budget Formula functionality, where formulas are uploaded and executed against budgetary data in batch mode rather than through online entry.

Under the heuristic Data Vault classification mined from the foreign key structure, GL_BUDGET_BATCHES is best modeled as a link table. Its primary key is composed entirely of two foreign keys — BUDGET_VERSION_ID and RECURRING_BATCH_ID — which is the defining characteristic of a link entity resolving a many-to-many relationship between budgets and recurring batches. A small number of descriptive attributes (status and execution timestamps) are carried in the same table rather than split into a separate satellite, which is common in EBS legacy schemas.

Key Information Stored

The table contains eight documented columns. The most significant are:

• BUDGET_VERSION_ID — Foreign key to GL_BUDGET_VERSIONS, identifying the budget version against which the batch executes. Part of the composite primary key.
• RECURRING_BATCH_ID — Foreign key to GL_RECURRING_BATCHES, identifying the recurring batch definition used to drive the budget formula. Part of the composite primary key.
• STATUS — Indicates the current state of the batch association (for example, active or inactive), governing whether the batch is eligible for execution.
• LAST_EXECUTED_DATE — Timestamp of the most recent execution of the batch for this budget version.
• LAST_EXECUTED_START_PERIOD — The beginning accounting period covered by the last execution.
• LAST_EXECUTED_END_PERIOD — The ending accounting period covered by the last execution.
• LAST_UPDATE_DATE — Standard EBS audit column recording when the row was last modified.
• LAST_UPDATED_BY — Standard EBS audit column recording the user who last modified the row.

The surrogate-style primary key is GL_BUDGET_BATCHES_PK, composed of BUDGET_VERSION_ID and RECURRING_BATCH_ID. A unique index, GL_BUDGET_BATCHES_U1, enforces the same column pair as the business-key candidate, confirming that a budget version may be linked to a given recurring batch only once. Because the primary key is entirely a composite of foreign keys, there is no independent surrogate identifier column in the documented schema.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include determining which recurring batches are attached to a budget version, identifying batches that have never executed, and analyzing execution history by period.

• List all batches for a budget version, joining to GL_BUDGET_VERSIONS to obtain the budget name and to GL_RECURRING_BATCHES for the batch name.
• Identify stale batches — rows where LAST_EXECUTED_DATE is null or older than a threshold — to support period-close troubleshooting.
• Report the last executed period range (LAST_EXECUTED_START_PERIOD through LAST_EXECUTED_END_PERIOD) for audit and reconciliation of budget loading.
• Filter by STATUS to isolate only active batch definitions used by the Budget Formula concurrent programs.

A representative query joins the parent tables on the foreign key columns, for example selecting b.BUDGET_VERSION_ID, r.BATCH_NAME, b.STATUS, and b.LAST_EXECUTED_DATE from GL_BUDGET_BATCHES b joining GL_RECURRING_BATCHES r on b.RECURRING_BATCH_ID = r.RECURRING_BATCH_ID, restricted by budget version.

Related Objects

The following objects are most significant in relation to GL_BUDGET_BATCHES, based on documented foreign key and primary key relationships:

• GL_BUDGET_VERSIONS — Parent table referenced by BUDGET_VERSION_ID; defines the budget version targeted by the batch.
• GL_RECURRING_BATCHES — Parent table referenced by RECURRING_BATCH_ID; defines the recurring batch that executes the formula.
• GL_BUDGET_BATCHES_PK — Primary key constraint on (BUDGET_VERSION_ID, RECURRING_BATCH_ID).
• GL_BUDGET_BATCHES_U1 — Unique index on the same column pair, serving as the business-key candidate.
• GL_BUDGET_ASSIGNMENTS / GL_BUDGET_ENTITIES — Related budget structures in the GL budget schema that participate in budget definition and validation.

Because the table is a link entity, all meaningful joins resolve through its two foreign key columns. Queries against GL_BUDGET_BATCHES should therefore always include the BUDGET_VERSION_ID and RECURRING_BATCH_ID predicates to maintain referential performance, particularly in large multi-org or multi-set-of-books environments.