Search Results gl_automatic_posting_op_u1
Overview
GL_AUTOMATIC_POSTING_OPTIONS is a General Ledger (GL) transaction table in the Oracle E-Business Suite that stores the individual selection criteria used by the AutoPost program to identify journal entries eligible for posting. Each row represents a single criterion line within an AutoPost Criteria Set, capturing the balance type, accounting period, journal source, and journal category that together define which journal batches the posting process should pick up, along with a posting priority that governs the order in which criteria are evaluated.
The table sits at the heart of the AutoPost configuration model. AutoPost Criteria Sets, defined in the parent GL_AUTOMATIC_POSTING_SETS table, act as the top-level container, while each option row in this table supplies one filter combination within that set. This one-to-many relationship allows a single criteria set to combine multiple source/category/period permutations, which the posting engine then applies in priority order.
In Data Vault modeling terms, the mined foreign key structure suggests classifying this table as a link. It resolves the association between an AutoPost Criteria Set and the ledger, source, category, and period dimensions that make up each criterion, rather than functioning as an independent hub or a descriptive satellite.
Key Information Stored
The table contains 28 documented columns. The most operationally significant are:
- AUTOPOST_SET_ID — Foreign key identifying the AutoPost Criteria Set to which this criterion belongs.
- LEDGER_ID — Identifies the ledger against which the posting criterion is applied.
- ACTUAL_FLAG — The balance type criterion, permitted values 'A' (actual), 'B' (budget), or 'E' (encumbrance).
- PERIOD_NAME — The journal batch posting period the criterion targets.
- JE_SOURCE_NAME — The journal source name filter for candidate entries.
- JE_CATEGORY_NAME — The journal category name filter for candidate entries.
- POSTING_PRIORITY — Numeric priority governing the order in which criteria are processed.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns.
- ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — Descriptive flexfield segments available for client-specific extension.
The declared primary key, GL_AUTO_POSTING_OPTIONS_PK, is composite, comprising AUTOPOST_SET_ID, ACTUAL_FLAG, PERIOD_NAME, JE_SOURCE_NAME, and JE_CATEGORY_NAME. A separate unique index, GL_AUTOMATIC_POSTING_OP_U1, is defined over AUTOPOST_SET_ID, LEDGER_ID, JE_SOURCE_NAME, JE_CATEGORY_NAME, PERIOD_NAME, and ACTUAL_FLAG, and functions as the principal business-key candidate. The inclusion of LEDGER_ID in the unique index but not in the declared PK reflects the multi-ledger scope of the criteria set.
Common Use Cases and Queries
Administrators and technical consultants query this table to audit, troubleshoot, and report on AutoPost configuration. A common pattern retrieves all criteria for a given set, ordered by processing priority:
- Configuration review: SELECT AUTOPOST_SET_ID, ACTUAL_FLAG, PERIOD_NAME, JE_SOURCE_NAME, JE_CATEGORY_NAME, POSTING_PRIORITY FROM GL_AUTOMATIC_POSTING_OPTIONS WHERE AUTOPOST_SET_ID = :set_id ORDER BY POSTING_PRIORITY.
- Coverage analysis: Group criteria by JE_SOURCE_NAME and JE_CATEGORY_NAME to determine which source/category combinations are being auto-posted versus deliberately excluded.
- Ledger scoping: Filter on LEDGER_ID to confirm which ledgers a criteria set impacts, especially in multi-ledger environments.
- Period auditing: Identify criteria still referencing closed or future periods by joining PERIOD_NAME against GL_PERIODS.
Because AutoPost runs as a concurrent program, reconciliation reports frequently join this table to the posting execution history to explain why certain journal batches were or were not selected.
Related Objects
The following objects are most significant to the function and integrity of GL_AUTOMATIC_POSTING_OPTIONS:
- GL_AUTOMATIC_POSTING_SETS — Parent table; joined on AUTOPOST_SET_ID. Defines the criteria set header.
- GL_JE_SOURCES — Reference for JE_SOURCE_NAME values.
- GL_JE_CATEGORIES — Reference for JE_CATEGORY_NAME values.
- GL_PERIODS — Reference for PERIOD_NAME and period status.
- GL_LEDGERS — Resolves LEDGER_ID to ledger name and configuration.
- GL_JE_BATCHES / GL_JE_HEADERS — Candidate journal data evaluated against these criteria during AutoPost.
- GL_AUTOPOST — The concurrent program and associated posting logic that consumes these criteria.
Together these relationships position GL_AUTOMATIC_POSTING_OPTIONS as the configurable bridge between administrative posting setup and the journal batches that flow through the GL posting engine.
-
INDEX: GL.GL_AUTOMATIC_POSTING_OP_U1
12.1.1
owner:GL, object_type:INDEX, object_name:GL_AUTOMATIC_POSTING_OP_U1, status:VALID,
-
INDEX: GL.GL_AUTOMATIC_POSTING_OP_U1
12.2.2
owner:GL, object_type:INDEX, object_name:GL_AUTOMATIC_POSTING_OP_U1, status:VALID,
-
TABLE: GL.GL_AUTOMATIC_POSTING_OPTIONS
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_AUTOMATIC_POSTING_OPTIONS, object_name:GL_AUTOMATIC_POSTING_OPTIONS, status:VALID,
-
TABLE: GL.GL_AUTOMATIC_POSTING_OPTIONS
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_AUTOMATIC_POSTING_OPTIONS, object_name:GL_AUTOMATIC_POSTING_OPTIONS, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
eTRM - SQLGL Tables and Views
12.2.2
description: This table contains the tracking information that Golden Gate will use to launch Journal Import. ,
-
eTRM - SQLGL Tables and Views
12.1.1
description: USSGL transaction codes ,