Results for “create_tablespaces_pub”

2 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_TABLESPACES_PUB is a public (PUB) PL/SQL API package in the Oracle E-Business Suite APPS schema that manages the registration and maintenance of Oracle database tablespaces within the EBS application data model. Its primary business function is to create and update records in the FND_TABLESPACES repository, which stores metadata describing the tablespaces available to the EBS environment. This repository supports administrative functions such as tablespace selection, capacity planning, and database object management performed through the Oracle Applications Manager (OAM) and related administrative interfaces.

The package body header identifies the source file as fndptblb.pls, version 115.3, dated 2004-04-16, confirming this object has been stable across the 11i and R12 release families, including 12.1.1 and 12.2.2. As a PUB package, the procedures are intended for consumption by other modules and, where supported, by customer extensions.

Key Procedures and Functions

  • CREATE_TABLESPACES — Registers a new tablespace entry. The procedure performs standard API initialization steps: it establishes a savepoint (CREATE_TABLESPACES_PUB), validates the caller's API version through FND_API.Compatible_API_Call, optionally initializes the message list via FND_MSG_PUB.initialize, and sets the return status to success. It then invokes VALIDATE_TABLESPACES in create mode (passing AS_UTILITY_PVT.G_CREATE as the validation mode) before delegating the physical insert to FND_TABLESPACES_PKG.INSERT_ROW, which stamps the row with a custom flag of 'C'.
  • UPDATE_TABLESPACES — Modifies an existing tablespace registration. It follows the same API conventions (savepoint, compatibility check, message initialization, return status initialization) and applies validation before persisting changes to the FND_TABLESPACES record.
  • VALIDATE_TABLESPACES — Provides reusable validation logic for tablespace attributes. CREATE_TABLESPACES and UPDATE_TABLESPACES both call it, passing the appropriate validation mode, so that data integrity checks remain consistent regardless of the operation being performed.

All procedures conform to the FND_API return-status convention, returning X_Return_Status, X_Msg_Count, and X_Msg_Data to the caller rather than raising unhandled exceptions.

Tables Accessed

The only documented table is FND_TABLESPACES, accessed through its APPS synonym. The package reads this table during validation and writes to it via FND_TABLESPACES_PKG.INSERT_ROW. Each row captures identifying information about a tablespace, including its type, name, and creation date, along with a custom flag indicating whether the entry was created through the standard API.

Usage Notes

FND_TABLESPACES_PUB is not referenced by any other documented package, so it is typically invoked directly by administrative forms, concurrent programs, or custom code performing tablespace registration. Because it is a public API, customizations should call these procedures rather than inserting into FND_TABLESPACES directly, ensuring that all validation and auditing conventions are honored. Callers must supply a valid API version number and can control transaction behavior through the P_Commit parameter, allowing multiple registration operations to be grouped into a single transaction. Errors are surfaced through the standard message stack, so invoking code should check X_Return_Status and, when the message count exceeds one, call FND_MSG_PUB.Get for the complete list of messages. This behavior is identical in 12.1.1 and 12.2.2, since the package body is unchanged across the R12 release line.