Search Results gl_automatic_posting_options




Overview
Explore in AI Chat

Overview

GL_AUTOMATIC_POSTING_OPTIONS is a General Ledger configuration table in Oracle E-Business Suite (validated on 12.1.1 and 12.2.2) that stores the individual posting criteria belonging to an Automatic Posting Set. Where GL_AUTOMATIC_POSTING_SETS defines a named parent set, GL_AUTOMATIC_POSTING_OPTIONS records the granular rules that determine which journal entries are eligible for automatic posting. Each row associates a posting set with a specific combination of ledger, journal source, journal category, accounting period, and actual/encumbrance indicator, together with a posting priority that controls processing sequence.

The table resides in the GL schema and is owned by the General Ledger product. Its documented physical schema in ETRM 12.2.2 defines 28 columns, with the primary key constraint GL_AUTO_POSTING_OPTIONS_PK defined over AUTOPOST_SET_ID, ACTUAL_FLAG, PERIOD_NAME, JE_SOURCE_NAME, and JE_CATEGORY_NAME. A separate unique index, GL_AUTOMATIC_POSTING_OP_U1, covers AUTOPOST_SET_ID, LEDGER_ID, JE_SOURCE_NAME, JE_CATEGORY_NAME, PERIOD_NAME, and ACTUAL_FLAG, providing the business-key candidate that also incorporates LEDGER_ID. From a Data Vault modeling perspective, the mined FK structure classifies this object heuristically as a link, since its identity is anchored on the AUTOPOST_SET_ID relationship to the parent posting set rather than on an isolated business entity.

Key Information Stored

The most significant columns are:

  • AUTOPOST_SET_ID — Surrogate identifier of the parent automatic posting set; part of both the primary key and the unique index, and the FK to GL_AUTOMATIC_POSTING_SETS.
  • ACTUAL_FLAG — Indicates whether the rule applies to actual balances (A), encumbrances (E), or budget (B) journal entries.
  • PERIOD_NAME — The accounting period the posting rule applies to.
  • JE_SOURCE_NAME — The journal source (e.g., Payables, Manual) qualifying the entries.
  • JE_CATEGORY_NAME — The journal category qualifying the entries.
  • LEDGER_ID — The ledger context for the rule; present in the unique index but not in the surrogate primary key.
  • POSTING_PRIORITY — Numeric precedence that determines the order in which competing criteria are evaluated during posting.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
  • ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — The standard descriptive flexfield (DFF) columns used for client-specific extensibility.

Common Use Cases and Queries

Typical scenarios include auditing which journals a posting set will capture, reviewing priority conflicts between overlapping rules, and reporting posting configuration by ledger. The following pattern lists all criteria for a given posting set:

SELECT p.autopost_set_id, p.ledger_id, p.je_source_name,
       p.je_category_name, p.period_name, p.actual_flag,
       p.posting_priority
FROM   gl_automatic_posting_options p
WHERE  p.autopost_set_id = :p_set_id
ORDER BY p.posting_priority;

To detect overlapping or competing criteria within one ledger and period, group by the unique-index business key and count rows. Reports for period-close readiness commonly join this table to GL_AUTOMATIC_POSTING_SETS to present the set name alongside its rules.

Related Objects

The following objects are most significant in relation to this table:

  • GL_AUTOMATIC_POSTING_SETS — Parent table joined on AUTOPOST_SET_ID; holds the set name and header attributes.
  • GL_JE_SOURCES — Validates JE_SOURCE_NAME values.
  • GL_JE_CATEGORIES — Validates JE_CATEGORY_NAME values.
  • GL_LEDGERS — Resolves LEDGER_ID to the owning ledger.
  • GL_PERIODS / GL_PERIOD_SETS — Supply period validation for PERIOD_NAME.
  • GL_JE_HEADERS and GL_JE_BATCHES — Represent the journal entries ultimately selected by these posting criteria.

Because posting options are maintained through the General Ledger posting-set setup forms, direct DML on this table is generally discouraged; configuration changes should be applied through the standard GL setup interface to preserve referential and validation integrity.