Search Results recurring_batch_id




Overview

GL_REC_BATCHES_LOV_V is a security-enabled Oracle EBS General Ledger view owned by the APPS schema. It exposes a filtered list of recurring journal batch definitions from GL_RECURRING_BATCHES, formatted specifically for use as a List of Values (LOV) source in Oracle Forms and OAF-based GL pages. Rather than presenting the full recurring batch record, the view projects a narrow set of descriptive and control attributes (name, description, batch identifier, chart of accounts, period set, accounted period type, and budget flag) alongside a derived USE_PRIVILEGE column. That final column applies Oracle's data security model at query time, letting the calling form display only those recurring batches the current user is authorized to select.

The view's role in reporting and integration is primarily operational rather than analytical. It is not intended as a general-purpose reporting view; it exists to drive LOV pickers on GL recurring journal and budget formula entry forms. However, because it is a standard APPS view, it is frequently queried directly in custom reports, SQL*Plus diagnostics, and data-extraction scripts that need a security-aware list of recurring batches without replicating the FND_DATA_SECURITY logic manually. The accounted_period_type attribute carried through the view is of particular interest to users searching for period-type semantics, since it reflects the accounting period type associated with the recurring batch definition and its period set.

Underlying Base Objects

The view is defined over the synonym GL_RECURRING_BATCHES and invokes two PL/SQL packages at runtime:

The DECODE nesting on SECURITY_FLAG determines which data security function applies: GL_DAS_RECURRING_JOURNAL_U / GL_DAS_RECURRING_JOURNAL for non-budget batches, and GL_DAS_BUDGET_FORMULA_U / GL_DAS_BUDGET_FORMULA for budget formula batches (BUDGET_FLAG = 'Y').

Key Columns

  • NAME — Recurring batch name; primary LOV display value.
  • DESCRIPTION — Free-text description of the batch.
  • RECURRING_BATCH_ID — Primary key of the recurring batch; the LOV return value.
  • CHART_OF_ACCOUNTS_ID — Chart of accounts the batch belongs to, scoping batch selection to the active ledger's COA.
  • PERIOD_SET_NAME — Accounting period set (e.g., Accounting, or a custom calendar name) associated with the batch.
  • ACCOUNTED_PERIOD_TYPE — The accounted period type (typically 'Month', 'Quarter', 'Year', or 'Week') used to interpret the batch's period set; this column is central to the period-type filtering that users commonly request.
  • BUDGET_FLAG — Indicates whether the batch is a budget formula batch ('Y') or a standard recurring journal batch ('N'), which also drives the applicable security function.
  • USE_PRIVILEGE — Derived 'Y'/'N' flag indicating whether the current user has data security privilege over the batch.

Common Use Cases and Queries

Typical usage is on recurring journal entry and budget formula forms, but the view is also queried directly in diagnostics and custom LOVs. To list only batches to which the user has access:

  • SELECT recurring_batch_id, name, period_set_name, accounted_period_type FROM gl_rec_batches_lov_v WHERE use_privilege = 'Y' ORDER BY name;

To isolate batches by accounting period type or filter budget formulas from standard journals:

  • SELECT name, period_set_name, accounted_period_type, budget_flag FROM gl_rec_batches_lov_v WHERE accounted_period_type = 'Month' AND use_privilege = 'Y';
  • SELECT name, recurring_batch_id FROM gl_rec_batches_lov_v WHERE budget_flag = 'N' AND use_privilege = 'Y';

Because USE_PRIVILEGE relies on FND_GLOBAL.USER_NAME, the result set varies by session and cannot be meaningfully cached across users; any tool invoking these queries should run under an authenticated EBS session.