Search Results get_guid

Overview

BISM_EXPORT_WRITER is an Oracle EBS database package owned by the APPS schema and classified as an "OTHER" API within the ETRM repository. Its name and structure indicate that it serves as the low-level persistence layer for the Business Intelligence Schema Management (BISM) export framework, which extracts and stores EBS metadata artifacts for use by external BI tooling, warehouse generation, and reporting layers. The package manages the storage, retrieval, and cleanup of binary and character large objects (BLOBs and NCLOBs) keyed by a globally unique identifier (GUID) and a file name, providing a uniform access contract for export content that may include XML templates, schema definitions, or generated report payloads.

The package header carries a header revision tag of $Header: bibexpws.pls 120.2 2006/04/03 05:23:34 akbansal noship $, which indicates the source was last revised in 2006 and is marked "noship" — meaning it is not shipped as a supported, customer-facing API. This is consistent with an internal utility used by other BISM components rather than a public interface.

Key Procedures and Functions

• GET_GUID — A function that returns a RAW value representing a newly generated globally unique identifier. It supplies the key value used to tag exported objects so that they can be uniquely referenced across INSERT_OBJECT, GET_OBJECT, and DELETE_OBJECT calls.
• DELETE_OBJECTS — A procedure that removes objects based on an age threshold expressed in seconds. It supports bulk purging of stale export content, and is typically called by scheduled housekeeping routines to prevent unbounded growth of the export repository.
• INSERT_OBJECT — A function that persists an export artifact. It accepts a group name, a GUID, a file name, character data (NCLOB), and binary data (BLOB), and returns a timestamp. This is the primary write path for export content and is the routine users search for under the term "insert_object."
• DELETE_OBJECT — A procedure that deletes a single, precisely identified object using group name, GUID, and file name. It complements DELETE_OBJECTS by providing targeted removal rather than time-based bulk cleanup.
• GET_OBJECT — A function that returns a REF CURSOR (SchemaCurType) for reading a stored object. The GUID parameter is declared IN OUT NOCOPY, which allows the routine to return or resolve a generated identifier back to the caller while avoiding unnecessary parameter copying.

Tables Accessed

The package operates against the BISM_EXPORT table through APPS synonyms, which is the primary repository for export objects. Character and binary content is manipulated with DBMS_LOB, reflecting the NCLOB and BLOB parameters in the interface. DUAL is referenced for scalar and sequence-style lookups such as GUID or timestamp generation. No other base tables are documented as direct dependencies, confirming the package's narrow, single-table persistence role.

Usage Notes

Because the package is classified as OTHER and marked noship, it is not intended for direct invocation by end users or via standard EBS forms. It is most commonly called from other PL/SQL components within the BISM export framework, or from custom concurrent programs and batch scripts that generate and store BI export artifacts. Typical invocation follows a GET_GUID call to obtain an identifier, one or more INSERT_OBJECT calls to write content, and later GET_OBJECT calls to stream data back to a consumer. DELETE_OBJECT and DELETE_OBJECTS are used for cleanup. Developers extending this area should treat the GUID and file name pair as the effective composite key and should not assume any commit semantics beyond the normal transactional behavior of the calling session. Referenced by zero other documented packages, it functions as a leaf utility whose stability is governed by its header revision rather than formal API versioning.