Results for “fnd_tablespace”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.FND_TABLESPACES_PUB is a public PL/SQL package within the Oracle E-Business Suite foundation (FND) product layer that exposes the customization interface for the Oracle Applications Tablespace Model (OATM). Its documented display name is "Customize Tablespace Model," and its business entity is registered as FND_TABLESPACE. The package provides the sanctioned API through which administrators register custom tablespace types that are not shipped by default with OATM and modify the tablespace names associated with either default OATM tablespace types or previously registered custom types.
Because the tablespace model governs where database segments for EBS objects are physically created, changes made through this package affect the mapping maintained in FND_TABLESPACES, which the AD utilities and AutoConfig consume when provisioning or migrating objects. The package therefore acts as the controlled entry point for extending and renaming the tablespace model without directly manipulating the underlying repository table. The package header carries the standard header revision marker and is annotated with @rep:scope public and @rep:lifecycle active, confirming it is a supported, current public API for release 12.1.1 and 12.2.2.
Key Procedures and Functions
The ETRM metadata documents three public procedures:
- CREATE_TABLESPACES — Registers a custom tablespace type that is not available by default with OATM. It accepts a tablespace type and a tablespace name and returns a standard API status plus message count and message data. It supports the standard API conventions for message list initialization and commit control.
- UPDATE_TABLESPACES — Modifies the tablespace name associated with any default OATM tablespace or any custom tablespace previously registered through CREATE_TABLESPACES. It likewise follows the standard API pattern with initialization, commit, and returned status/message parameters.
- VALIDATE_TABLESPACES — Performs validation associated with the tablespace model, allowing callers to verify inputs or existing registrations before changes are propagated.
The source comments state explicitly that all necessary validation should be performed before changes are propagated to FND_TABLESPACES, underscoring that callers must not bypass the validation path.
Tables Accessed
The package reads and writes a single documented table via its APPS synonym: FND_TABLESPACES. This table stores the mapping between tablespace types and their physical tablespace names that constitutes the OATM configuration. CREATE_TABLESPACES inserts new custom type-to-tablespace associations, UPDATE_TABLESPACES modifies existing rows, and VALIDATE_TABLESPACES queries the table to confirm that proposed values are consistent with existing registrations. No other tables are documented as referenced.
Usage Notes
FND_TABLESPACES_PUB is typically invoked from administrator-facing setup flows rather than from end-user forms, and is the recommended programmatic route for automating tablespace model customization in custom concurrent programs, deployment scripts, or installation tooling. The metadata records that the package is referenced by zero other packages, meaning it is a top-level public API with no internal FND callers — any integration must be initiated by external code or a setup UI. Callers should supply the API version number, initialize the message list, and decide commit behavior explicitly; because the API returns X_Return_Status, X_Msg_Count, and X_Msg_Data, calling code should check the status and surface returned messages rather than assuming success. Direct DML against FND_TABLESPACES should be avoided in favor of this package so that validation and the supported commit semantics are preserved.