Search Results gl_das_massallocation_u

Overview

APPS.GL_ALLOC_BATCHES_LOV_V is a security-aware database view in Oracle E-Business Suite General Ledger. It exposes allocation batch definitions held in GL_ALLOC_BATCHES together with two derived privilege columns, VIEW_PRIVILEGE and USE_PRIVILEGE, that are computed at query time by the FND_DATA_SECURITY package. In 12.1.1 and 12.2.2 the view serves as the list-of-values (LOV) source for allocation batch selection in mass allocation, mass budget, and related allocation programs. Because access to allocation batches is controlled through Oracle data security, the view does not simply return every row in the base table; it evaluates the calling user's function security grants and returns 'Y' or 'N' indicators that a Forms LOV or program logic can use to filter or disable entries.

The name reflects its primary purpose: supplying the LOV that drives selection of an allocation batch. The user search term "gl_das_massbudget_u" appears directly in the view text as the function name passed to FND_DATA_SECURITY.CHECK_FUNCTION for the USE_PRIVILEGE column when the batch is a budget batch (ACTUAL_FLAG = 'B'). This confirms the view is the runtime enforcement point for the mass budget update privilege.

Underlying Base Objects

The documented base objects referenced by the view are:

• GL_ALLOC_BATCHES (referenced through a synonym) — the single physical source of rows returned by the view.
• FND_DATA_SECURITY (package) — supplies CHECK_FUNCTION, which evaluates whether a user holds a named function privilege against a specific data key.
• FND_GLOBAL (package) — supplies USER_NAME, used as the user identity passed to the security check.

The view is owned by APPS and defined as a single SELECT over GL_ALLOC_BATCHES with no joins, so its row cardinality matches the base table for users with unrestricted access. In practice, the security functions resolve the current user, the target function name, and the row's primary key to a grant result, returning 'T' when a grant exists. The DECODE chains translate that 'T' into the 'Y' exposed in VIEW_PRIVILEGE and USE_PRIVILEGE, and force 'N' whenever SECURITY_FLAG is not 'Y'.

Key Columns

• ALLOCATION_BATCH_ID — primary identifier of the allocation batch; passed as the data key into the security check.
• NAME — the batch name displayed in the LOV.
• DESCRIPTION — free-text description of the batch.
• CHART_OF_ACCOUNTS_ID — chart of accounts to which the batch belongs; governs which ledger context the batch is valid in.
• ACTUAL_FLAG — indicates batch type. 'B' denotes a budget batch; other values denote actual mass allocation batches. This flag selects which DAS function name is checked.
• VIEW_PRIVILEGE — 'Y' when the user may view the batch; resolved through GL_DAS_MASSBUDGET_V or GL_DAS_MASSALLOCATION_V.
• USE_PRIVILEGE — 'Y' when the user may execute or update the batch; resolved through GL_DAS_MASSBUDGET_U or GL_DAS_MASSALLOCATION_U.

Common Use Cases and Queries

The view supports LOV population, custom reports, and diagnostic checks of data security configuration. Typical usage filters to batches the user may act upon:

SELECT allocation_batch_id, name, description, actual_flag
FROM   apps.gl_alloc_batches_lov_v
WHERE  use_privilege = 'Y'
AND    actual_flag = 'B';

To audit why a specific user cannot reach a budget batch, query the same view while connected as that user and inspect both privilege columns; a 'Y' in VIEW_PRIVILEGE paired with 'N' in USE_PRIVILEGE indicates the user can see but not run the batch, which is the expected outcome when GL_DAS_MASSBUDGET is granted without GL_DAS_MASSBUDGET_U.