Search Results recurring_batch_id




Overview
Explore in AI Chat

Overview

APPS.GL_REC_BATCHES_LOV_V is a reporting and list-of-values (LOV) view in the Oracle E-Business Suite General Ledger module. It exposes a filtered, security-aware projection of recurring journal batch definitions, drawn from the GL_RECURRING_BATCHES synonym that resolves to the underlying GL_RECURRING_BATCHES base table. The view is designed to populate LOV windows in the recurring journal and budget formula forms, and to serve as a query surface for reporting and integration routines that must honor Oracle data security.

The name itself signals its purpose: the "_LOV_" infix indicates that the view is tuned for list-of-values population, while the suffix "_V" denotes a view. Because LOV windows typically need to display a user-friendly name and description while retaining the technical key, the view selects NAME, DESCRIPTION, and RECURRING_BATCH_ID alongside configuration columns such as the chart of accounts, period set, and accounting period type. Critically, the view computes a derived USE_PRIVILEGE column, so the LOV can render only those batches to which the current user has been granted access.

The user search term "accounted_period_type" maps directly to the ACCOUNTED_PERIOD_TYPE column. In the context of recurring journal batches, this attribute determines the period type against which the batch entries are accounted, and it is one of the configuration values that drives how and when the recurring journal is generated. Its presence in this LOV view allows form and report consumers to filter or display batches by the period type under which their accounting entries are recorded.

As with most APPS-owned views, it is advisable to treat GL_REC_BATCHES_LOV_V as a read-only interface. Direct DML against it is not supported; changes to recurring batches must be performed through the supported GL forms or the recurring journal APIs.

Underlying Base Objects

The view is defined over a single data source, GL_RECURRING_BATCHES, which is referenced in the view text as a synonym owned in the APPS schema. All columns exposed by the view are sourced from that object, with no joins to additional tables. This keeps the view lightweight and predictable, an important characteristic for an LOV surface that may be invoked interactively many times during a form session.

  • GL_RECURRING_BATCHES (SYNONYM) — The sole row source. It supplies NAME, DESCRIPTION, RECURRING_BATCH_ID, CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE, BUDGET_FLAG, and SECURITY_FLAG.
  • FND_DATA_SECURITY (PACKAGE) — Invoked through the CHECK_FUNCTION procedure to evaluate whether the current user holds the relevant data-access privilege for each recurring batch row.
  • FND_GLOBAL (PACKAGE) — Supplies the current user context through FND_GLOBAL.USER_NAME, which is passed into CHECK_FUNCTION so that security is evaluated for the logged-in user.

Because SECURITY_FLAG is a column on the base object, the view only performs the security lookup when that flag is set to 'Y'; otherwise the decode short-circuits and USE_PRIVILEGE is returned as 'Y'. This design avoids unnecessary package calls for batches that are not security-enabled.

Key Columns

  • NAME / DESCRIPTION — The user-facing batch name and description, presented as the LOV display values.
  • RECURRING_BATCH_ID — The primary key of the underlying recurring batch record, returned as the hidden LOV identifier.
  • CHART_OF_ACCOUNTS_ID — Identifies the chart of accounts to which the batch belongs; useful for restricting an LOV to the current ledger's chart.
  • PERIOD_SET_NAME — The accounting period set associated with the batch.
  • ACCOUNTED_PERIOD_TYPE — The period type under which the recurring batch is accounted, e.g. a monthly or other defined period type. This matches the searched term and is a primary filter or display attribute.
  • BUDGET_FLAG — Indicates whether the batch is a budget formula batch. The value drives which data-security function is evaluated inside the decode.
  • USE_PRIVILEGE — A derived column returning 'Y' or 'N', computed by combining SECURITY_FLAG, BUDGET_FLAG, and the appropriate CHECK_FUNCTION result. For non-budget batches the view checks the GL_DAS_RECURRING_JOURNAL_U/GL_DAS_RECURRING_JOURNAL function; for budget batches it checks GL_DAS_BUDGET_FORMULA_U/GL_DAS_BUDGET_FORMULA.

Common Use Cases and Queries

The most frequent use of this view is populating a recurring batch LOV, where the form or report needs the batch name, description, and identifier only for batches the user is permitted to see. A typical query filters on the current chart of accounts and the privilege flag:

  • LOV population: SELECT name, description, recurring_batch_id FROM apps.gl_re_batches_lov_v WHERE use_privilege = 'Y' AND chart_of_accounts_id = :p_coa_id ORDER BY name. (Referenced as apps.gl_rec_batches_lov_v in practice.)
  • Filtering by accounted period type: SELECT name, recurring_batch_id, accounted_period_type FROM apps.gl_rec_batches_lov_v WHERE accounted_period_type = 'M' AND use_privilege = 'Y'.
  • Separating budget formulas: SELECT name, budget_flag, use_privilege FROM apps.gl_rec_batches_lov_v WHERE budget_flag = 'Y'.
  • Integration validation: Joining the view to GL_RECURRING_BATCHES on recurring_batch_id to reconcile the LOV-visible batches against the full set for audit purposes.

Because USE_PRIVILEGE is resolved at query time using FND_GLOBAL session context, the view produces different results depending on the active user, which is the intended behavior for security-enabled LOVs. Reporting jobs run outside a form session should set FND_GLOBAL context explicitly or anticipate the returned privilege values accordingly.