Search Results create_temp_clob




Overview
Explore in AI Chat

Overview

FND_SEED_STAGE_UTIL is a utility package in the Oracle E-Business Suite Application Object Library (FND) schema that supports the seed data staging infrastructure. Seed data in EBS refers to the predefined configuration and reference data that Oracle ships with the product, such as messages, lookups, profiles, responsibilities and menus. During patching, cloning, and upgrade operations, this data passes through staging tables before being validated and applied to the target environment. FND_SEED_STAGE_UTIL provides the low-level primitives that other seed data processing packages use to write status messages, track processing status, retrieve accumulated messages, and upload staged content.

The package is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the defining user. This design allows it to be called from within the APPS schema context while honoring the caller's security profile, which is important for a utility that participates in privileged patching operations. The package header carries a version of 120.5, indicating it has been stable since early 2011 and is shared across the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

The package exposes a small, focused set of procedures. Several collection types are declared at the top of the specification, including character, numeric, date, and 4K character tables indexed by binary integer; these are used as bulk binding containers throughout the seed staging code.

  • INSERT_MSG — Accepts a message string and records it in the staging message store, providing the standard mechanism by which seed processing code reports progress and errors.
  • UPDATE_STATUS — Updates the processing status of a staged seed record. It accepts parameters for debug level, a sequence identifier, and the new status value, allowing callers to move records through the staging lifecycle.
  • GET_MESSAGES — The procedure the user searched for. It is overloaded three times: a variant returning all messages into an output 4K character table, a variant accepting a single message number to retrieve, and a variant accepting a from/to range to retrieve a bounded window of messages. This overloading lets callers retrieve anywhere from one message to the full message buffer.
  • UPLOAD — Processes a local staging file identified by file name and procedure identifier. It reports debug information and returns out parameters for abort status, warning status, error count, and an error message table, making it the primary entry point for loading staged seed content.
  • CREATE_TEMP_CLOB — Creates and returns a temporary CLOB locator, used when seed content exceeds the 4000-byte VARCHAR2 limit and must be handled as a large object.

Tables Accessed

The package references FND_SEED_STAGE_CONFIG, the configuration table that governs seed staging behavior, and PLITBLM, which provides PL/SQL table-to-database interoperability. It also depends on the DBMS_LOB and DBMS_SQL built-in packages for LOB handling and dynamic SQL operations. These dependencies confirm the package's role as a processing engine rather than a data owner: it reads configuration, manipulates staged content, and delegates bulk storage to the database.

Usage Notes

FND_SEED_STAGE_UTIL is not intended for direct end-user invocation. It is called by the seed data staging framework during patch application, rapid install, and upgrade processing, where concurrent programs and internal API layers drive the load sequence. Of particular relevance to users tracing the "get_messages" entry point, GET_MESSAGES is typically called by wrapper programs that need to surface staging errors to logs or to the patching console. Because the metadata records that the package is referenced by exactly one other package, its callers are tightly scoped, and custom code should treat it as an internal utility subject to change between release updates. Developers writing extensions against it should prefer documented wrappers over direct calls.