Search Results gl_storage_parameters_v




Overview
Explore in AI Chat

Overview

GL_STORAGE_PARAMETERS_V is an APPS-owned database view in the General Ledger (GL) product family of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. The view is described in the source metadata with the notation "10SC ONLY," indicating that it is scoped to a specific deployment or configuration context rather than being a general-purpose GL object. Its status is VALID and its owner is the APPS schema.

Functionally, the view exposes storage-parameter definitions maintained in the General Ledger schema, enriching the raw stored attributes of each database object with a decoded, user-facing lookup meaning. It is therefore both a reporting convenience view and an integration surface: any concurrent program, form, or external interface that needs to present storage parameters in business language rather than as coded values can query this view directly instead of performing its own join to the lookup table.

Underlying Base Objects

The view text defines it over two referenced objects:

  • GL_STORAGE_PARAMETERS (SYNONYM) — the driving object, supplying the storage parameter rows. The view aliases this object as S. The synonym resolves to the underlying GL storage-parameter table in the APPS schema.
  • GL_LOOKUPS (VIEW) — the lookup source, aliased as L, supplying the translated meaning of the object type code.

The two objects are joined on a coded value: L.LOOKUP_TYPE = 'OBJECT_TYPE' AND L.LOOKUP_CODE = S.OBJECT_TYPE. This restricts the lookup side to the OBJECT_TYPE lookup type, so the decoded column always reflects the seeded or user-maintained meaning for that specific lookup code. Because GL_LOOKUPS is itself a view, the join is resolved against the lookup layer rather than a physical lookup table, which is consistent with standard Oracle EBS lookup usage.

Key Columns

The view exposes sixteen columns. The most significant are:

  • ROW_ID — the ROWID of the underlying GL_STORAGE_PARAMETERS row, providing a unique physical identifier for each returned record.
  • OBJECT_NAME — the name of the database object whose storage parameters are being described.
  • OBJECT_TYPE — the coded object type value stored on GL_STORAGE_PARAMETERS.
  • OBJECT_TYPE_MEANING — the decoded description of OBJECT_TYPE obtained from GL_LOOKUPS where LOOKUP_TYPE = 'OBJECT_TYPE'. This is the column that resolves the user's search term and is the primary reason to use the view rather than the base object.
  • TABLESPACE_NAME — the tablespace in which the object's storage is allocated.
  • INITIAL_EXTENT_SIZE_KB, NEXT_EXTENT_SIZE_KB, MAX_EXTENTS, PCT_INCREASE, PCT_FREE — the standard Oracle storage clause attributes, expressed in kilobytes where applicable.
  • DESCRIPTION — free-text description associated with the storage parameter definition.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO columns supporting audit and change tracking.

Common Use Cases and Queries

The most frequent use case is retrieving storage parameters with human-readable object type descriptions, either for a single object or across a set. A representative query is:

SELECT object_name, object_type, object_type_meaning, tablespace_name,
       initial_extent_size_kb, next_extent_size_kb, max_extents
  FROM apps.gl_storage_parameters_v
 WHERE object_name = :object_name;

To list all objects of a given decoded type, the meaning column can be filtered directly:

SELECT object_name, tablespace_name, initial_extent_size_kb
  FROM apps.gl_storage_parameters_v
 WHERE object_type_meaning = :meaning;

Because the view carries audit columns, it also supports change-tracking queries, for example identifying storage-parameter rows created or modified after a given date. Note that the view is documented as "10SC ONLY"; deployments that do not match that scope should confirm availability before relying on it in custom code. As with all APPS views, grants and synonyms determine accessibility for non-APPS schemas.