Search Results allocation_code

Overview

The GL_AUTO_ALLOC_SETS_V view is a General Ledger (GL) security-enabled reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents allocation set definitions stored in the AutoAllocation feature of Oracle General Ledger, exposing the allocation set header data alongside derived display and privilege columns. Allocation sets group recurring allocation rules and formulas that distribute balances across accounts based on user-defined bases such as statistical amounts, period-to-date balances, or constant values.

The view is not a simple projection of the base table. It is a data-security-aware view: it calls FND_DATA_SECURITY.CHECK_FUNCTION to evaluate whether the current user holds the view, use, or modify privilege on each allocation set. This makes it the appropriate access point for forms, concurrent programs, and reporting tools that must respect General Ledger data access set (DAS) security. The VIEW_PRIVILEGE, USE_PRIVILEGE, and MODIFY_PRIVILEGE columns return Y or N based on the user's authority, eliminating the need for downstream code to replicate security logic. Applications querying this view therefore see only the allocation sets they are entitled to reference or maintain.

Underlying Base Objects

The view is defined over the GL_AUTO_ALLOC_SETS table, referenced in the view text through an APPS synonym. It additionally depends on four documented objects:

• GL_AUTO_ALLOC_SETS (SYNONYM) — the base table holding allocation set definitions.
• FND_DATA_SECURITY (PACKAGE) — supplies CHECK_FUNCTION, used to evaluate the three privilege levels.
• FND_GLOBAL (PACKAGE) — supplies USER_NAME, identifying the executing user for security checks.
• GL_AUTO_ALLOC_VW_PKG (PACKAGE) — supplies GET_OWNER_DSP, which resolves the raw OWNER value into the display value in OWNER_DSP.

The view's SELECT projects every column of the base table, then appends four derived columns. Row identity is preserved via ROWID, aliased as ROW_ID, allowing the view to participate in Oracle Forms block-based updates where the row identifier is needed.

Key Columns

• ALLOCATION_SET_ID — primary identifier for the allocation set; used as the key passed to CHECK_FUNCTION and the value in the DAS object name.
• ALLOCATION_SET_NAME and ALLOCATION_SET_TYPE_CODE — the user-visible name and the type classification of the set.
• ALLOCATION_CODE — the allocation identifier associated with the set.
• CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE — define the accounting context in which the set operates.
• OWNER and OWNER_DSP — the raw owner value and its display form, truncated to 240 characters by SUBSTR.
• SECURITY_FLAG — controls whether security evaluation applies; when not Y, the privilege columns default to Y.
• VIEW_PRIVILEGE, USE_PRIVILEGE, MODIFY_PRIVILEGE — security-derived flags for the current user.
• ORG_ID — the operating unit context for multi-org installations.
• DESCRIPTION and ATTRIBUTE1–ATTRIBUTE15 plus CONTEXT — descriptive and descriptive-flexfield columns available for reporting.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include listing allocation sets available to the signed-in user, extracting allocation set definitions for migration or audit purposes, and driving custom reports that must observe DAS security.

To list allocation sets the user may modify:

• SELECT ALLOCATION_SET_NAME, OWNER_DSP, DESCRIPTION FROM GL_AUTO_ALLOC_SETS_V WHERE MODIFY_PRIVILEGE = 'Y';

To review sets in a specific chart of accounts:

• SELECT ALLOCATION_SET_ID, ALLOCATION_SET_NAME, ALLOCATION_SET_TYPE_CODE FROM GL_AUTO_ALLOC_SETS_V WHERE CHART_OF_ACCOUNTS_ID = :p_coa_id;

To confirm security configuration and privilege outcomes for troubleshooting:

• SELECT ALLOCATION_SET_ID, SECURITY_FLAG, VIEW_PRIVILEGE, USE_PRIVILEGE, MODIFY_PRIVILEGE FROM GL_AUTO_ALLOC_SETS_V ORDER BY ALLOCATION_SET_ID;

Because the view invokes FND_DATA_SECURITY.CHECK_FUNCTION per row, queries against large data volumes incur security-evaluation overhead; filtering by ALLOCATION_SET_ID, CHART_OF_ACCOUNTS_ID, or ORG_ID where possible improves performance. Direct DML should be directed to the base table through supported APIs rather than through this view.