Results for “gl_recurring_batches_v”

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

Overview

The APPS.GL_RECURRING_BATCHES_V view is a General Ledger (GL) security-based presentation object within Oracle E-Business Suite. Per the documented ETRM metadata, the object is a VALID VIEW owned by the APPS schema, and its description is recorded as "10SC ONLY," indicating that its intended exposure is limited to specific certified or localized configurations rather than a broadly distributed feature. The view surfaces recurring journal batch definitions alongside the ledger to which each batch belongs, and — most significantly — it computes per-row data-security privileges for the current user.

Rather than presenting raw recurring batch data alone, the view acts as a security envelope. It derives VIEW_PRIVILEGE, USE_PRIVILEGE, and MODIFY_PRIVILEGE columns dynamically through calls to FND_DATA_SECURITY.CHECK_FUNCTION, evaluated against the connected user returned by FND_GLOBAL.USER_NAME. This makes the view suitable for reporting and integration scenarios where both batch metadata and the calling user's authorization level must be returned in a single query, avoiding the need for downstream code to re-implement GL data-security logic. The view is available in the 12.1.1 and 12.2.2 codelines, with the documented metadata set aligned to 12.2.2.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects: FND_DATA_SECURITY (PACKAGE), FND_GLOBAL (PACKAGE), GL_BUDGET_VERSIONS (SYNONYM), GL_LEDGERS (SYNONYM), and GL_RECURRING_BATCHES (SYNONYM).

• GL_RECURRING_BATCHES — the primary driver, aliased as B in the view text. It supplies the batch name (B.NAME AB_NAME), last execution attributes, ledger identifier (LEDGER_ID), SECURITY_FLAG, BUDGET_FLAG, RECURRING_BATCH_TYPE, and audit columns.
• GL_LEDGERS — joined to resolve LEDGER_NAME via L.NAME, giving each row a human-readable ledger label rather than just an identifier.
• GL_BUDGET_VERSIONS — supplies the AB_LE_BUDGET value (V.BUDGET_NAME), reconciling the batch to its associated budget version where applicable.
• FND_DATA_SECURITY — invoked four times per row, once each for the view, use, and modify privilege checks against either the 'GL_DAS_RECURRING_JOURNAL' or 'GL_DAS_BUDGET_FORMULA' data-security object, dependent on the BUDGET_FLAG.
• FND_GLOBAL — provides USER_NAME, used as the identity argument passed into each CHECK_FUNCTION call.

The synonyms resolve to the corresponding GL application tables and are owned under APPS.

Key Columns

• AB_NAME — recurring batch name, sourced from GL_RECURRING_BATCHES.NAME.
• LEDGER_NAME / LEDGER_ID — the ledger and its descriptive name for each batch.
• LE_PERIOD_NAME / LE_DATE — the ledger execution period name and last executed date.
• AB_LE_PERIOD_NAME, AB_LE_JE_DATE, AB_LE_CE_DATE, AB_LE_BUDGET — batch-level last-executed period, journal date, calculation date, and budget name.
• SECURITY_FLAG, RECURRING_BATCH_TYPE — control flags passed from the base table governing which data-security object applies.
• VIEW_PRIVILEGE, USE_PRIVILEGE, MODIFY_PRIVILEGE — computed values ('Y' or 'N') returned by FND_DATA_SECURITY.CHECK_FUNCTION. When SECURITY_FLAG is 'Y', the view selects either the recurring journal or budget formula security object based on BUDGET_FLAG; otherwise the privilege defaults to 'Y'.
• ROW_ID, RECURRING_BATCH_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY — identification and audit columns.

Common Use Cases and Queries

Because the view encodes user-level privilege resolution, it is typically used by custom concurrent programs, forms personalizations, or integration extracts that must expose only the recurring batches a given user is authorized to see. A representative query returns the batch name, ledger, last execution period, and the three computed privileges:

• SELECT AB_NAME, LEDGER_NAME, LE_PERIOD_NAME, VIEW_PRIVILEGE, USE_PRIVILEGE, MODIFY_PRIVILEGE FROM APPS.GL_RECURRING_BATCHES_V WHERE VIEW_PRIVILEGE = 'Y';
• Filtering by LEDGER_ID to scope results to a single ledger for reconciliation or a period-close checklist.
• Joining RECURRING_BATCH_ID to GL_RECURRING_BATCHES or journal-generation tables to build a batch inventory report.
• Auditing MODIFY_PRIVILEGE = 'N' rows to confirm that segregation-of-duties controls are properly enforced before a user attempts maintenance.

Note that privilege evaluation depends on the runtime session identity (FND_GLOBAL.USER_NAME); results therefore vary by the connected user and should be tested under the target user's session before relying on them in automated logic. Given the "10SC ONLY" designation, deployments should confirm the view's availability in their specific environment.