Search Results get_product_short_name




Overview
Explore in AI Chat

Overview

AD_TSPACE_UTIL is a utility package owned by the APPS schema in Oracle E-Business Suite, classified as a UTIL API. Its purpose is to centralize tablespace resolution logic for database objects registered within EBS applications. The package abstracts the mapping between an application object (table, materialized view, advanced queue table, index-organized table, or materialized view log) and the tablespace in which it should reside. This resolution is critical during Oracle Applications installation, upgrade, patching, and cloning operations, where the framework must determine correct storage placements automatically rather than relying on hard-coded tablespace names.

The package supports the tablespace management model introduced in the Applications Release, distinguishing between "new" and "old" tablespace management modes. Under the new model, object-to-tablespace assignments are maintained declaratively in the FND_OBJECT_TABLESPACES repository, allowing the AD utilities and the AutoConfig/adpatch tooling to honor product-specific storage decisions. The package is heavily reused across the application tier — 18 other packages reference it — making it a foundational component of the storage resolution chain rather than an end-user-facing API.

Key Procedures and Functions

  • IS_NEW_TS_MODE — An out-parameter procedure that reports whether the database operates in the new tablespace management mode. A return of 'Y' indicates the new model; 'N' indicates the legacy model. This switch governs whether the remaining lookup routines consult FND_OBJECT_TABLESPACES or fall back to legacy behavior.
  • GET_OBJECT_TABLESPACE — Returns the tablespace for a given product short name, object name, object type, and index lookup flag. It also reports whether the object is registered in FND_OBJECT_TABLESPACES and, when validation is requested, whether the resolved tablespace actually exists in the database. Valid object types include TABLE, MVIEW, AQ_TABLE, IOT_TABLE, and MV_LOG. The index lookup flag allows callers to resolve the tablespace of an index by passing the underlying table name.
  • GET_TABLESPACE_NAME — Resolves a tablespace name for a supplied object or context, complementing GET_OBJECT_TABLESPACE for callers that require the name only.
  • GET_APPL_ID — Retrieves the application_id associated with a given application, supporting the application-scoped lookups required by the object tablespace repository.
  • GET_PRODUCT_SHORT_NAME — Returns the product short name for an application, enabling callers to work with the human-readable product identifier rather than the numeric application_id.

Tables Accessed

The package reads from several EBS foundation and dictionary views through APPS synonyms. FND_APPLICATION supplies application identifiers and short names used by the GET_APPL_ID and GET_PRODUCT_SHORT_NAME routines. FND_PRODUCT_GROUPS and FND_PRODUCT_INSTALLATIONS provide product installation context. FND_OBJECT_TABLESPACES is the central repository mapping registered objects to their assigned tablespaces. FND_TABLESPACES lists tablespaces known to the application schema. DBA_TABLESPACES provides the physical database-level existence check used when validating a resolved tablespace. No writes are documented; the package is read-only with respect to these objects.

Usage Notes

AD_TSPACE_UTIL is invoked by other EBS product packages, AD utilities, patching infrastructure, and upgrade drivers that must place or validate database objects without embedded tablespace literals. Custom code should call GET_OBJECT_TABLESPACE rather than reading FND_OBJECT_TABLESPACES directly, since the routine encapsulates registration checks and optional existence validation. Callers should first check IS_NEW_TS_MODE to determine whether tablespace resolution should be applied at all. Because the package depends on DBA_TABLESPACES, execution under a role with dictionary access (typically APPS) is required. The package is not intended for direct end-user invocation from forms or concurrent programs, but it may appear in custom concurrent programs that generate or relocate database objects.