Search Results gl_das_budget_formula

Overview

APPS.GL_RECURRING_BATCHES_V is a security-aware reporting view in the Oracle E-Business Suite General Ledger module. It exposes recurring journal batch definitions together with calculated row-level privilege indicators, allowing Oracle Forms, OAF pages, and custom integrations to present only those recurring batches that the connected user is authorized to see, use, or modify. The view is a critical component of Oracle's data security architecture within General Ledger, since recurring journals can be generated automatically for expenses, allocations, and standard accruals. Rather than relying on the calling application to enforce access, the view embeds the FND_DATA_SECURITY.CHECK_FUNCTION evaluation directly into its SELECT list, producing VIEW_PRIVILEGE, USE_PRIVILEGE, and MODIFY_PRIVILEGE columns. This design allows a single query to return authorization results alongside the descriptive batch attributes, simplifying UI development and preventing privilege escalation in custom code.

Underlying Base Objects

The ETRM metadata lists five referenced objects. GL_RECURRING_BATCHES is the primary synonym and supplies the batch header attributes such as name, ledger, batch type, security flag, and last execution details. GL_LEDGERS provides the LEDGER_NAME column via a join on ledger_id. GL_BUDGET_VERSIONS supplies the associated budget name when a batch is budget-related, surfaced as AB_LE_BUDGET. FND_GLOBAL supplies the user_name passed into the security check function. FND_DATA_SECURITY is a PL/SQL package whose CHECK_FUNCTION procedure performs the actual access validation, returning 'T' for authorized and other values for denied access. The view joins these objects so that reporting and forms can consume pre-computed privileges without duplicating security logic.

Key Columns

• RECURRING_BATCH_ID — Primary key identifying the recurring batch; also the value passed to the security check function.
• AB_NAME — The recurring batch name.
• LEDGER_NAME — Descriptive ledger name from GL_LEDGERS.
• LEDGER_ID / CHART_OF_ACCOUNTS_ID — Ledger and chart of accounts identifiers.
• LE_PERIOD_NAME / LE_DATE — Last executed period name and last execution date.
• AB_LE_PERIOD_NAME / AB_LE_JE_DATE / AB_LE_CE_DATE — Last executed period, journal date, and calculation date.
• AB_LE_BUDGET — Budget name associated with the batch, sourced from GL_BUDGET_VERSIONS.
• SECURITY_FLAG / RECURRING_BATCH_TYPE — Control flags indicating whether security enforcement applies and the batch type.
• VIEW_PRIVILEGE, USE_PRIVILEGE, MODIFY_PRIVILEGE — Derived Y/N indicators evaluated through FND_DATA_SECURITY.CHECK_FUNCTION against GL_DAS_RECURRING_JOURNAL_V/U/M or GL_DAS_BUDGET_FORMULA_V/U/M, depending on the BUDGET_FLAG value.

Common Use Cases and Queries

Typical usage includes custom recurring journal reports, OAF-based maintenance pages, and migration scripts that must respect row-level security. A basic listing query follows:

• SELECT recurring_batch_id, ab_name, ledger_name, ab_le_budget, view_privilege, use_privilege, modify_privilege FROM apps.gl_recurring_batches_v WHERE view_privilege = 'Y';

Filtering by ledger and privilege for administrative review:

• SELECT ab_name, ledger_name, le_period_name, le_date FROM apps.gl_recurring_batches_v WHERE ledger_id = :p_ledger_id AND view_privilege = 'Y' ORDER BY ab_name;

Identifying budget-related batches where the user holds modification rights:

• SELECT ab_name, ab_le_budget, modify_privilege FROM apps.gl_recurring_batches_v WHERE ab_le_budget IS NOT NULL AND modify_privilege = 'Y';

Because privilege evaluation invokes FND_DATA_SECURITY for each row, queries against this view should be narrowly filtered on ledger_id or recurring_batch_id to avoid performance degradation. The view is also the recommended source when building custom recurring journal submission pages, since it guarantees consistent security outcomes with Oracle's standard General Ledger forms.