Search Results get_object_tablespace

Overview

AD_TSPACE_UTIL is a utility package body owned by the APPS schema in Oracle E-Business Suite. Its purpose is to centralize the resolution of tablespace-related configuration metadata used throughout the EBS application tier. In a multi-product installation, each registered Oracle application (for example, General Ledger, Purchasing, or Inventory) can be associated with a default database tablespace and a set of object-specific tablespace overrides. AD_TSPACE_UTIL provides the programmatic interface through which other EBS packages, forms, and concurrent programs query this information without embedding direct SQL against the underlying FND tables.

The package is classified as a UTIL (utility) API, indicating that it is a supporting infrastructure component rather than a business-facing API. In the 12.1.1 and 12.2.2 releases its status is VALID, and it is referenced by 18 other database objects, confirming its role as a shared dependency across EBS product schemas.

Key Procedures and Functions

The documented metadata lists five procedures and functions, each addressing a distinct aspect of tablespace resolution:

• IS_NEW_TS_MODE — Determines whether the environment operates in the "new tablespace mode," the configuration introduced to control how EBS assigns tablespaces during installation and upgrade operations. This flag governs the behavior of the remaining routines.
• GET_OBJECT_TABLESPACE — Returns the tablespace designated for a specific database object, consulting the object-level tablespace assignment table before falling back to application or product-level defaults.
• GET_TABLESPACE_NAME — Resolves and returns the applicable tablespace name for a given context, serving as the primary lookup routine used by callers that need a single resolved value.
• GET_APPL_ID — Retrieves the application identifier associated with a product or context, allowing callers to map between product short names and numeric application IDs.
• GET_PRODUCT_SHORT_NAME — Returns the product short name (such as SQLGL or INV) corresponding to an application or installation context, complementing GET_APPL_ID.

These routines are deliberately narrow in scope: each encapsulates one lookup against the FND configuration tables so that consumers do not need to replicate the resolution logic or hard-code schema-qualified queries.

Tables Accessed

AD_TSPACE_UTIL reads from six tables, accessed through APPS synonyms:

• FND_APPLICATION — Provides the mapping between application IDs and application short names, supporting GET_APPL_ID and GET_PRODUCT_SHORT_NAME.
• FND_OBJECT_TABLESPACES — Stores object-level tablespace assignments, the primary source for GET_OBJECT_TABLESPACE.
• FND_PRODUCT_GROUPS — Supplies product group context used to scope tablespace resolution.
• FND_PRODUCT_INSTALLATIONS — Identifies which products are installed in the current EBS instance, ensuring that only valid applications are considered.
• FND_TABLESPACE — Holds the registered tablespace definitions and their application associations.
• DBA_TABLESPACES — The Oracle data dictionary view, used to validate that a resolved tablespace physically exists in the database.

Consistent with its UTIL classification, the package performs read-only lookups; no documented inserts, updates, or deletes are attributed to it.

Usage Notes

AD_TSPACE_UTIL is invoked internally by other EBS components rather than by end users directly. Its 18 dependent objects include installation, upgrade, and administration utilities that must determine correct tablespace targets when creating or migrating database segments. Typical invocation points include:

• AD Administration and AutoConfig-related utilities that build or validate tablespace assignments during patching and upgrades.
• Concurrent programs that generate database objects and require the correct target tablespace per product.
• Forms and OAF pages in the System Administrator responsibility that display tablespace configuration to administrators.
• Custom code and customer extensions that must honor the same resolution rules as standard EBS tooling, rather than querying FND_TABLESPACES directly.

Because the package is not referenced by any object outside this set and is marked VALID, customizations should treat it as a stable but internal interface. Callers should rely on the documented functions rather than on the underlying tables, since the resolution order (object-level, then product, then application default) is encapsulated within the package body and may be refined across EBS releases.