Search Results gl_das_autopost_set_u

Overview

APPS.GL_AUTOMATIC_POSTING_SETS_V is a data-secured reporting and integration view over the General Ledger Automatic Posting Sets entity. In Oracle EBS 12.1.1 and 12.2.2, an automatic posting set defines the criteria used by the Automatic Posting program to select and post unposted journal entries based on priority options, effective date windows, and period attributes. This view presents the posting set definition together with dynamically computed privilege flags, allowing forms, concurrent programs, and external integrations to evaluate a user's authorized access to each posting set row.

The view is primarily consumed by the Oracle Forms-based posting set maintenance screen (the "GL_DAS_AUTOPOST_SET" object family) and by any custom code that must respect data security when listing or acting on posting sets. Because the privilege columns are derived at query time, the row set visible to a user varies according to their assigned data access set and function grants.

Underlying Base Objects

The view is defined over the following documented objects:

• GL_AUTOMATIC_POSTING_SETS (accessed as a SYNONYM) — the base table holding the posting set definition, including priority options, effective date offsets, and descriptive flexfield attributes.
• FND_DATA_SECURITY (PACKAGE) — supplies the CHECK_FUNCTION routine used to evaluate view, use, and modify privileges against the security setup for the posting set object.
• FND_GLOBAL (PACKAGE) — provides the current user context (USER_NAME) required by the security function calls.

The view owner is APPS. Because the base table is referenced through a synonym and the security package executes with the caller's session context, the view must be queried in a session where FND_GLOBAL has been initialized (for example, after an EBS sign-on) for the privilege columns to resolve meaningfully.

Key Columns

• AUTOPOST_SET_ID / AUTOPOST_SET_NAME — the primary key and user-visible name of the posting set.
• CHART_OF_ACCOUNTS_ID — the chart of accounts to which the posting set applies.
• PERIOD_SET_NAME / ACCOUNTED_PERIOD_TYPE — the accounting period calendar and period type used to evaluate the posting selection criteria.
• ENABLED_FLAG — indicates whether the posting set is active and available for selection.
• SECURITY_FLAG — when set to 'Y', the view applies FND_DATA_SECURITY checks; when 'N', privileges are returned as 'Y'.
• SUBMIT_ALL_PRIORITIES_FLAG — controls whether all priority options are submitted together.
• NUM_OF_PRIORITY_OPTIONS — the number of priority options defined; the view decodes this to a default of 1 when null and to NULL when all priorities are submitted.
• EFFECTIVE_DAYS_BEFORE / EFFECTIVE_DAYS_AFTER — the date window, relative to the period, within which journals become eligible.
• VIEW_PRIVILEGE, USE_PRIVILEGE, and the modify privilege — values of 'Y' or 'N' computed by decoding SECURITY_FLAG and the result of FND_DATA_SECURITY.CHECK_FUNCTION against the 'GL_DAS_AUTOPOST_SET', 'GL_DAS_AUTOPOST_SET_V', and 'GL_DAS_AUTOPOST_SET_U' / '_M' security object names.
• ROW_ID and the ATTRIBUTE1–15 / CONTEXT columns — the row identifier and descriptive flexfield segments carried through from the base table.

Common Use Cases and Queries

The most common requirement is to list enabled posting sets that the current user is permitted to use, filtering on the derived security column so that unauthorized rows are excluded:

• Retrieving enabled posting sets for a chart of accounts: SELECT autopost_set_id, autopost_set_name FROM apps.gl_automatic_posting_sets_v WHERE enabled_flag = 'Y' AND chart_of_accounts_id = :p_coa_id.
• Enforcing security in a custom concurrent program: SELECT autopost_set_name, use_privilege FROM apps.gl_automatic_posting_sets_v WHERE use_privilege = 'Y'.
• Inspecting priority configuration: SELECT autopost_set_name, submit_all_priorities_flag, num_of_priority_options, effective_days_before, effective_days_after FROM apps.gl_automatic_posting_sets_v WHERE autopost_set_name = :p_name.
• Integration extraction of full definitions, including flexfield attributes and the SECURITY_FLAG, for downstream systems that must replicate posting set logic.

Because the security package is invoked per row, queries against this view can be more expensive than direct queries on the base table; in batch contexts it is advisable to restrict the result set by chart of accounts and enabled flag, and to avoid this view when data security is not required.