Search Results security_flag




Overview
Explore in AI Chat

Overview

GL_AUTOMATIC_POSTING_SETS_V is an APPS-owned security-enabled view in the General Ledger (GL) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It exposes the configuration of automatic posting sets — the named groups that determine how journal batches are automatically posted, including which priorities are submitted, the effective date window, and the period/accounting context. Automatic posting sets are consumed by the AutoPost concurrent program and by the GL period-close process.

The view is more than a simple projection of the underlying table. It wraps GL_AUTOMATIC_POSTING_SETS and decorates each row with two computed privilege columns, VIEW_PRIVILEGE and USE_PRIVILEGE, derived from the SECURITY_FLAG column and Oracle's Data Access Security (DAS) framework. When SECURITY_FLAG is 'Y', the view calls FND_DATA_SECURITY.CHECK_FUNCTION against the GL_DAS_AUTOPOST_SET_V and GL_DAS_AUTOPOST_SET (and related _U/_M) security objects; the return value 'T' is normalized to 'Y', otherwise 'N'. When SECURITY_FLAG is not 'Y', the DECODE defaults to 'Y', meaning no row-level restriction applies. This makes the view the security-aware interface for reporting and integration rather than a raw data access path.

Underlying Base Objects

The view is defined over a synonym that resolves to the base table:

  • GL_AUTOMATIC_POSTING_SETS (SYNONYM) — the transactional/configuration table holding posting set definitions per chart of accounts.
  • FND_DATA_SECURITY (PACKAGE) — supplies CHECK_FUNCTION, evaluated at query time to resolve the current user's privileges.
  • FND_GLOBAL (PACKAGE) — supplies USER_NAME (and implicitly the runtime user/application context) passed into the security check.

Because the security checks execute as PL/SQL calls within the view's SELECT list, performance depends on the session's FND context and on the grant definitions for the DAS objects. The view does not itself persist data; all writes must target the base table through the supported forms or APIs.

Key Columns

Common Use Cases and Queries

Typical use cases include auditing which posting sets are enabled per ledger, diagnosing why a user cannot see or apply a set (security investigated via SECURITY_FLAG and the privilege columns), and feeding downstream reporting or integration that must respect DAS.

List enabled sets and their effective windows:

  • SELECT autopost_set_id, autopost_set_name, chart_of_accounts_id, effective_days_before, effective_days_after, enabled_flag FROM gl_automatic_posting_sets_v WHERE enabled_flag = 'Y' ORDER BY autopost_set_name;

Inspect security posture for the current user:

  • SELECT autopost_set_id, autopost_set_name, security_flag, view_privilege, use_privilege FROM gl_automatic_posting_sets_v WHERE security_flag = 'Y';

Identify sets that submit all priorities versus a fixed count:

  • SELECT autopost_set_name, submit_all_priorities_flag, num_of_priority_options FROM gl_automatic_posting_sets_v WHERE submit_all_priorities_flag = 'Y';

Because privilege evaluation occurs per row, queries should filter by chart of accounts or set name where possible to limit the number of DAS invocations and avoid unnecessary overhead on large result sets.