Search Results gl_system_setup_u1

Overview

GL.GL_SYSTEM_SETUP_11I is a General Ledger configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores per-ledger (per set of books) processing parameters used by Oracle's standard GL programs. Each row corresponds to one ledger defined in GL_SETS_OF_BOOKS_11I and governs runtime behaviour such as batch sizing, memory buffering and journal import archiving. The table is owned by the GL schema, carries FND Design Data reference SQLGL.GL_SYSTEM_SETUP_11I, resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and is flagged Oracle Internal Use Only: it should not be accessed directly except through standard Oracle Applications programs.

Under the supplied heuristic Data Vault classification this object is satellite-leaning. In practice it may be modelled as a satellite attached to the ledger hub GL_SETS_OF_BOOKS_11I, since it holds descriptive, configuration-level attributes keyed by the ledger defining column rather than transaction relationships.

Key Information Stored

There are nine documented columns. The most significant are:

• SET_OF_BOOKS_ID (NUMBER 15) — the ledger defining column, mandatory, and both the primary key GL_SYSTEM_SETUP_PK and the unique index GL_SYSTEM_SETUP_U1. It is the foreign key to GL.GL_SETS_OF_BOOKS_11I.
• INDEXED_SEGMENT (VARCHAR2 10) — the key flexfield segment used for indexed access into GL_CODE_COMBINATIONS.
• RECORDS_TO_PROCESS (NUMBER 15) — maximum number of records processed per pass by GL programs.
• FLEX_CACHE_SIZE (NUMBER 15) — number of records buffered in memory from GL_CODE_COMBINATIONS.
• ARCHIVE_EASYLINK_FLAG (VARCHAR2) — controls whether Journal Import archives its output.
• ROLLBACK_SEGMENT (VARCHAR2 30) — rollback segment used by programs maintaining large data volumes (legacy name retained for compatibility).
• CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

The surrogate/technical primary key and the business-key candidate coincide here: SET_OF_BOOKS_ID is simultaneously the PK column and the sole unique index column, so no separate surrogate identifier exists.

Common Use Cases and Queries

Primary use cases include tuning GL performance (adjusting RECORDS_TO_PROCESS and FLEX_CACHE_SIZE), investigating Journal Import archiving behaviour via ARCHIVE_EASYLINK_FLAG, and supporting migration or ledger-copy exercises. A representative query joins the setup row to its ledger:

• SELECT s.SET_OF_BOOKS_ID, s.INDEXED_SEGMENT, s.RECORDS_TO_PROCESS, s.FLEX_CACHE_SIZE, s.ARCHIVE_EASYLINK_FLAG, b.NAME FROM GL.GL_SYSTEM_SETUP_11I s, GL.GL_SETS_OF_BOOKS_11I b WHERE s.SET_OF_BOOKS_ID = b.SET_OF_BOOKS_ID;
• SELECT SET_OF_BOOKS_ID, RECORDS_TO_PROCESS, FLEX_CACHE_SIZE FROM GL.GL_SYSTEM_SETUP_11I WHERE SET_OF_BOOKS_ID = :ledger_id;

Reporting typically focuses on configuration audits across all ledgers, since the table is small (one row per ledger). Because Oracle does not support direct modification, changes are normally made through the standard GL setup forms, and read-only queries should be confined to diagnostics or reconciliation.

Related Objects

The object is referenced by the APPS synonym GL_SYSTEM_SETUP_11I, which is the supported access path for application code. Its principal relationships are:

• GL.GL_SETS_OF_BOOKS_11I — parent ledger table; joined on SET_OF_BOOKS_ID.
• APPS.GL_SYSTEM_SETUP_11I — APPS-layer synonym/view used by concurrent programs and forms.
• GL.GL_CODE_COMBINATIONS — target of the FLEX_CACHE_SIZE and INDEXED_SEGMENT settings.
• GL.GL_JE_BATCHES / GL.GL_JE_HEADERS / GL.GL_JE_LINES — Journal Import/Sweep tables whose processing honours these setup values.
• GL.GL_INTERFACE_CONTROLS — companion setup table governing Journal Import behaviour alongside ARCHIVE_EASYLINK_FLAG.

The table is documented as referencing no other database object besides the ledger FK, and its dependent set is limited to the APPS synonym and the GL programs that read it.