Search Results get_item_text_varchar2

Overview

The CTXSYS.EGO_ITEM_TEXT_CTX_PKG package body is a thin wrapper within the Oracle E-Business Suite (EBS) Oracle Text (interMedia Text, or iMT) integration layer. It belongs to the EGO product family, which governs item master extensibility, item attributes, and item description frameworks. In EBS 12.1.1 and 12.2.2 the package is owned by APPS and is classified under the OTHER API classification in the E-Business Suite Technical Reference Manual (ETRM).

Its business function is to expose Item text (descriptions and related long-text attributes) to Oracle Text indexing services via a controlled interface. Because Oracle Text user datastores require a callback signature that returns stored document text on demand during index build and query time, EGO_ITEM_TEXT_CTX_PKG acts as the indirection point between the Oracle Text engine (running as CTXSYS) and the EBS business logic that actually resolves item text from the database. This decoupling is deliberate: it isolates the iMT datastore API from the underlying EBS retrieval logic and keeps the index-time contract stable across patch releases.

Key Procedures and Functions

ETRM documents exactly two procedures in this package body, and both are declarations of the Oracle Text user datastore callback signature:

• GET_ITEM_TEXT_CLOB — Returns item text as a CLOB. It accepts a row identifier and an output CLOB parameter, delegating all substantive work to APPS.EGO_ITEM_TEXT_UTIL.Get_Item_Text with an output type of 'CLOB'. The local character variable is initialized to NULL and passed through as an unused companion argument, reflecting the shared signature of the utility routine.
• GET_ITEM_TEXT_VARCHAR2 — Returns item text as a VARCHAR2, used when the item text value fits within the SQL VARCHAR2 limit. It declares a local CLOB initialized to NULL and invokes APPS.EGO_ITEM_TEXT_UTIL.Get_Item_Text with an output type of 'VARCHAR2', populating the output character parameter directly. Two DBMS_LOB temporary LOB calls are present in the source but commented out, indicating the temporary LOB lifecycle is handled internally by the utility procedure rather than by this wrapper.

Both procedures consist of a single delegating call; no business logic, validation, or exception handling is implemented locally.

Tables Accessed

The ETRM metadata for this package body records no directly referenced tables via APPS synonyms. This is consistent with its design: the package performs no SQL of its own. All data retrieval is delegated to APPS.EGO_ITEM_TEXT_UTIL.Get_Item_Text, which is the component that reads the relevant EGO item description and text storage structures. Consequently, any table access attributable to this package is indirect and flows through that utility package, not through the wrapper itself.

Usage Notes

EGO_ITEM_TEXT_CTX_PKG is not intended for direct invocation by application forms, concurrent programs, or ordinary custom code. It is registered as an Oracle Text user datastore callback, meaning the Oracle Text index engine invokes it automatically during index creation, synchronization, optimization, and query-time text retrieval for EGO item indexes. The P_ROWID it receives is the row identifier the index maps to the stored item record.

Because ETRM shows the package is referenced by zero other packages, its callers are external to the PL/SQL dependency graph — they are the Oracle Text indexing infrastructure and the datastore preference configuration that points at these procedures. Customizations should not call these routines directly; integration needs should instead target APPS.EGO_ITEM_TEXT_UTIL.Get_Item_Text. The package should be regarded as read-only infrastructure, and its procedure signatures must not be altered, since changes would invalidate the Oracle Text datastore preference and require index rebuilds.