Search Results gl_storage_parameters_u1

Overview

GL.GL_STORAGE_PARAMETERS is a General Ledger configuration table that stores the default storage parameters used when Oracle EBS creates interim tables in the Oracle General Ledger application. Interim tables are transient working structures populated during journal entry, consolidation, translation, and financial reporting processes; the values held in this table determine how much space Oracle allocates for each such table at creation time. A separate row exists for every interim table in the application, and no foreign keys are defined, making this a self-contained configuration repository. Administrators maintain the rows through the Storage Parameters form rather than through direct DML.

From a dimensional modeling perspective, the metadata classifies this object heuristically as standalone. This suggests it is best modeled as an independent reference or satellite-style dimension rather than as a hub or link within a Data Vault construct, since it has no parent or child dependencies and its rows represent descriptive configuration attributes rather than transactional relationships.

Key Information Stored

The table is keyed at the business level by OBJECT_NAME, carrying a VARCHAR2(30) value that holds the table or index name of the interim object. Uniqueness is enforced by the index GL_STORAGE_PARAMETERS_U1, whose documented columns are OBJECT_NAME and ZD_EDITION_NAME; the edition column participates in the unique constraint to support multi-tenant editioning in EBS 12.2.x while the column list remains functionally the same in 12.1.1 at the OBJECT_NAME level. The primary key constraint GL_STORAGE_PARAMETERS_PK is defined on OBJECT_NAME. There is no separately generated surrogate identifier; OBJECT_NAME serves simultaneously as the natural key and the join column.

The most significant descriptive columns include:

• OBJECT_NAME — name of the interim table or index whose storage is being configured.
• OBJECT_TYPE — identifies whether the row describes a table or an index.
• TABLESPACE_NAME — target tablespace for the interim object.
• INITIAL_EXTENT_SIZE_KB and NEXT_EXTENT_SIZE_KB — the initial and subsequent extent sizes in kilobytes.
• MAX_EXTENTS — upper limit on the number of extents allocated.
• PCT_INCREASE — percentage growth applied to each successive extent.
• PCT_FREE — reserved free space percentage retained within each block.
• DESCRIPTION — free-form text describing the purpose of the row.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — provide audit lineage.

Common Use Cases and Queries

Typical usage centers on auditing allocation settings, verifying that storage parameters match DBA standards, and preparing for period-end processing when interim tables are heavily populated. A DBA might compare configured values against actual segment sizes in DBA_TABLES or DBA_INDEXES to detect drift.

• List all interim objects configured for a specific tablespace: SELECT OBJECT_NAME, OBJECT_TYPE, INITIAL_EXTENT_SIZE_KB, NEXT_EXTENT_SIZE_KB FROM GL.GL_STORAGE_PARAMETERS WHERE TABLESPACE_NAME = :ts;
• Identify rows modified by a specific user for change-control reporting: SELECT OBJECT_NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM GL.GL_STORAGE_PARAMETERS WHERE LAST_UPDATED_BY = :user_id;
• Report objects with an unusually high PCT_INCREASE or low MAX_EXTENTS ahead of a bulk journal import cycle.

Confirmation of the unique key is available via a direct query on the index: SELECT OBJECT_NAME, ZD_EDITION_NAME FROM GL.GL_STORAGE_PARAMETERS; joined against USER_INDEXES on the GL_STORAGE_PARAMETERS_U1 index name.

Related Objects

Because GL_STORAGE_PARAMETERS declares no foreign keys, relationships are logical rather than enforced. Practitioners typically correlate it with the following objects:

• DBA_TABLES / DBA_INDEXES — compared by OBJECT_NAME to validate current segment allocation.
• DBA_TABLESPACES — joined on TABLESPACE_NAME to confirm space availability.
• FND_APPLICATION — used to relate the SQLGL design-data registration to the General Ledger application.
• FND_USER — joined on LAST_UPDATED_BY and CREATED_BY for audit attribution.
• GL_INTERFACE and its auxiliary interim structures — the runtime consumers of the configured storage values.
• GL_JE_BATCHES and GL_JE_HEADERS — context for the periods in which interim tables are populated.

There is no documented dependent view or API specifically referencing this table, reinforcing its role as a standalone configuration seed object owned by the GL schema within the APPS_TS_SEED tablespace.