Search Results view_privilege




Overview
Explore in AI Chat

Overview

GL_ALLOC_BATCHES_LOV_V is a view owned by the APPS schema in Oracle E-Business Suite, defined under the GL – General Ledger product. The ETRM documentation describes the object with the terse annotation "10SC ONLY," indicating that the view is intended for a restricted deployment context tied to the 10SC configuration rather than for general use across all EBS installations. Its name follows Oracle's LOV (List of Values) naming convention, meaning the view is designed to supply the selection list displayed when a user picks an allocation batch during a General Ledger transaction, such as launching MassAllocation or MassBudget processes.

Functionally, the view exposes allocation batch identifiers and descriptive attributes from GL_ALLOC_BATCHES while augmenting each row with two computed privilege columns, VIEW_PRIVILEGE and USE_PRIVILEGE. These columns are populated at query time by calling FND_DATA_SECURITY.CHECK_FUNCTION and FND_GLOBAL.USER_NAME, so that the LOV returns only those batches the connected user is authorized to view or use. In EBS 12.1.1 and 12.2.2 the view therefore acts as a security-filtered reporting and selection interface rather than as a plain mirror of the base table.

Underlying Base Objects

Per the documented metadata, the view references three base objects:

  • GL_ALLOC_BATCHES (SYNONYM) – the synonym resolving to the application table that stores allocation batch definitions (identifier, name, description, chart of accounts, and actual flag). All projected data columns originate here.
  • FND_DATA_SECURITY (PACKAGE) – invoked through CHECK_FUNCTION to evaluate the current user's data-access privileges for the relevant security function, returning a value that the DECODE logic converts into a Y/N privilege flag.
  • FND_GLOBAL (PACKAGE) – supplies USER_NAME, the identifier passed into CHECK_FUNCTION as part of the privilege evaluation context.

The security function names passed to CHECK_FUNCTION are chosen dynamically based on ACTUAL_FLAG: GL_DAS_MASSBUDGET_V and GL_DAS_MASSALLOCATION_V for viewing, and GL_DAS_MASSBUDGET_U and GL_DAS_MASSALLOCATION_U for use. A SECURITY_FLAG of 'T' short-circuits the check and returns 'Y', granting unconditional access.

Key Columns

  • ALLOCATION_BATCH_ID – primary identifier of the allocation batch; the LOV return value.
  • NAME – user-defined batch name displayed in the LOV.
  • DESCRIPTION – descriptive text for the batch.
  • CHART_OF_ACCOUNTS_ID – chart of accounts to which the batch belongs, used for context filtering.
  • ACTUAL_FLAG – distinguishes actual versus budget batches ('A' versus 'B'), and drives which security functions are evaluated.
  • VIEW_PRIVILEGE – computed Y/N flag indicating whether the user may view the batch.
  • USE_PRIVILEGE – computed Y/N flag indicating whether the user may run or apply the batch.

Common Use Cases and Queries

The principal use case is driving the allocation batch list of values in General Ledger forms and concurrent programs, where only authorized batches should appear. A typical query restricts output to batches the user may use:

SELECT allocation_batch_id, name, description
FROM gl_alloc_batches_lov_v
WHERE use_privilege = 'Y'
AND actual_flag = 'A';

For reporting, the view can enumerate batches with their privilege states, allowing administrators to audit effective access:

SELECT allocation_batch_id, name, actual_flag, view_privilege, use_privilege
FROM gl_alloc_batches_lov_v
WHERE chart_of_accounts_id = :coa_id;

Because privilege columns are derived from session-sensitive package calls, results vary by user and must not be cached or materialized. The documented "10SC ONLY" restriction should be respected when considering reuse of this view outside its intended deployment.