Search Results posting_priority

Overview

GL_AUTOMATIC_POSTING_OPTIONS_V is an APPS-owned reporting view in Oracle General Ledger that exposes the configuration of automatic posting sets. An automatic posting set defines the rules by which Journal Import assigns journal entries to posting categories and priorities during the posting process. Each row in the view represents a single posting option line belonging to a posting set, combining a ledger, journal source, and journal category with a numeric posting priority.

The view is primarily used for inquiry and reporting against the GL_AUTOMATIC_POSTING_OPTIONS base table. Because the base table stores ledger, source, and category as internal identifiers and codes, the view resolves those values into user-facing names through outer joins to GL_LEDGERS, GL_JE_SOURCES, and GL_JE_CATEGORIES. It further substitutes the literal meaning 'ALL' for wildcard rows via a lookup join to GL_LOOKUPS. This makes the view suitable for administrative review, setup auditing, and integration extracts where readable posting priority definitions are required. The POSTING_PRIORITY column is the most commonly queried attribute, as it drives the sequencing applied when multiple posting options match a given journal entry. The object is valid in both 12.1.1 and 12.2.2 and is referenced throughout the journals and posting code paths.

Underlying Base Objects

The view is defined over six documented base objects, all referenced as APPS synonyms:

• GL_AUTOMATIC_POSTING_OPTIONS — the driving table supplying all option-level columns, including POSTING_PRIORITY, ACTUAL_FLAG, PERIOD_NAME, and the descriptive flexfield CONTEXT and ATTRIBUTE1–15 columns.
• GL_AUTOMATIC_POSTING_SETS — joined on AUTOPOST_SET_ID to identify the parent set to which each option belongs.
• GL_LEDGERS — outer-joined on LEDGER_ID to return the ledger name, except where LEDGER_ID equals the reserved sentinel value -1234567890, in which case the lookup meaning is returned instead.
• GL_JE_SOURCES — outer-joined on JE_SOURCE_NAME, replaced by the lookup meaning when the stored value is 'ALL'.
• GL_JE_CATEGORIES — outer-joined on JE_CATEGORY_NAME, likewise replaced by the lookup meaning when the value is 'ALL'.
• GL_LOOKUPS — filtered to LOOKUP_TYPE = 'LITERAL' and LOOKUP_CODE = 'ALL' to supply the wildcard meaning text.

All joins to the descriptive tables are outer joins, ensuring that wildcard options still appear in the result set. The ROWID of the base option row is exposed as ROW_ID for row identification.

Key Columns

• AUTOPOST_SET_ID — identifier of the parent automatic posting set.
• ACTUAL_FLAG — indicates the balance type (Actual, Budget, or Encumbrance) covered by the option.
• PERIOD_NAME — the accounting period to which the option applies.
• LEDGER_ID / LEDGER_NAME — the target ledger and its resolved display name.
• JE_SOURCE_NAME / USER_JE_SOURCE_NAME — the internal source code and its user-facing name, or the 'ALL' literal meaning.
• JE_CATEGORY_NAME / USER_JE_CATEGORY_NAME — the internal category code and its user-facing name, or the 'ALL' literal meaning.
• POSTING_PRIORITY — the numeric priority assigned to the option, used to sequence posting when multiple options qualify.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• CONTEXT and ATTRIBUTE1–15 — descriptive flexfield segments for the option.

Common Use Cases and Queries

The most frequent requirement is to list the posting priorities configured for a given set, ledger, or source. For example:

• Reviewing all options for a posting set: SELECT autopost_set_id, ledger_name, user_je_source_name, user_je_category_name, posting_priority FROM gl_automatic_posting_options_v ORDER BY autopost_set_id, posting_priority;
• Identifying priority conflicts where the same ledger/source/category combination returns more than one priority.
• Auditing which options use the 'ALL' wildcard for source or category.
• Extracting the flexfield attributes for configuration migration between environments.

Because the view resolves codes and names, it is preferred over direct queries on GL_AUTOMATIC_POSTING_OPTIONS for reporting and support diagnostics. For 12.1.1 and 12.2.2, the structure and behavior are consistent, and no version-specific differences affect the columns or joins described.