Results for “last_exec_journal_date”

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

Overview

GL_RECURRING_BATCHES is a General Ledger table in the Oracle E-Business Suite (validated on 12.1.1 and 12.2.2) that stores the definition of recurring journal entry and budget formula batches. Each row represents a named batch that controls the periodic generation of recurring journals or budget formulas, grouping one or more recurring headers under a common execution schedule, ledger, and period type. The batch acts as the parent control record: executing it causes General Ledger to generate journals or budget entries for the child headers defined in GL_RECURRING_HEADERS.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This suggests GL_RECURRING_BATCHES is best modeled as a satellite attached to a ledger or chart-of-accounts hub, since it carries descriptive and state attributes (name, description, flags, last-executed dates) rather than acting as a pure junction. Modelers should treat the surrogate key as the satellite's primary key and resolve the ledger or chart-of-accounts reference for the hub linkage.

Key Information Stored

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

• RECURRING_BATCH_ID — surrogate primary key (GL_RECURRING_BATCHES_PK; unique index GL_RECURRING_BATCHES_U1). It is the value propagated to child tables.
• NAME — user-defined batch name; part of the business-key unique index GL_RECURRING_BATCHES_U2.
• CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE — complete the U2 business key, scoping the batch to a chart of accounts and accounting calendar.
• LEDGER_ID — foreign key to GL_SETS_OF_BOOKS_11I, identifying the ledger the batch posts to.
• PERIOD_TYPE — foreign key to GL_PERIOD_TYPES, defining the recurrence period.
• BUDGET_FLAG, ALLOCATION_FLAG, BUDGET_IN_FORMULA_FLAG — control whether the batch produces budget entries, allocations, or budget formulas.
• RECURRING_BATCH_TYPE — distinguishes the batch category.
• LAST_EXECUTED_PERIOD_NAME, LAST_EXECUTED_DATE, LAST_EXEC_JOURNAL_DATE, LAST_EXEC_CALCULATION_DATE — execution audit columns used to prevent duplicate generation and to report on run history.
• LAST_EXEC_BUDGET_VERSION_ID — foreign key to GL_BUDGET_VERSIONS, recording the budget version last executed.
• DESCRIPTION, SECURITY_FLAG, and ATTRIBUTE1–10 / CONTEXT — descriptive text, security designation, and the standard EBS flexfield/descriptive extension columns.

Common Use Cases and Queries

Typical uses include identifying all active recurring batches for a ledger, auditing last execution, and joining to child headers to review the recurring journal lines. Sample patterns:

• List batches by ledger and name:
  SELECT recurring_batch_id, name, ledger_id, period_type FROM gl_recurring_batches WHERE ledger_id = :ledger_id ORDER BY name;
• Find batches not yet executed in a period:
  SELECT name, last_executed_period_name, last_executed_date FROM gl_recurring_batches WHERE last_executed_period_name <> :period_name;
• Join to headers:
  SELECT b.name, h.recurring_header_id FROM gl_recurring_batches b, gl_recurring_headers h WHERE b.recurring_batch_id = h.recurring_batch_id;
• Budget-focused batches:
  SELECT name, budget_flag, last_exec_budget_version_id FROM gl_recurring_batches WHERE budget_flag = 'Y';

These queries support period-close reconciliation, recurring-entry auditing, and reporting on budget formula runs.

Related Objects

The most significant related objects, based on documented foreign keys, are:

• GL_RECURRING_HEADERS — child table referencing RECURRING_BATCH_ID; holds the recurring journal/budget header definitions within each batch.
• GL_BUDGET_BATCHES — references RECURRING_BATCH_ID; links budget batch processing back to the recurring batch.
• GL_SETS_OF_BOOKS_11I — referenced via LEDGER_ID; the ledger assigned to the batch.
• GL_PERIOD_TYPES — referenced via PERIOD_TYPE; defines the recurrence cadence.
• GL_BUDGET_VERSIONS — referenced via LAST_EXEC_BUDGET_VERSION_ID; the budget version last executed.
• GL_MGT_SEG_UPGRADE_H — referenced via CHART_OF_ACCOUNTS_ID in the documented FK list.

Together these objects form the recurring-entry and budget-formula subsystem within Oracle General Ledger.