Search Results ego_item_text_pvt




Overview
Explore in AI Chat

Overview

EGO_ITEM_TEXT_PVT is a private PL/SQL package body in the APPS schema that underpins Oracle E-Business Suite's item master text search capability. Its core responsibility is the creation and management of an Oracle Text (interMedia) index over descriptive item attributes — most notably the long-description and other flexfield-based attributes attached to inventory items. Text-based item searching in Oracle EBS (for example, the "Item Search" or iSupplier-facing catalog lookup) relies on a database-side full-text index; this package encapsulates the DDL and maintenance operations required to build that index in a controlled, resumable fashion rather than forcing users to run raw CTX_DDL calls manually.

The package is classified as PVT, indicating it is an internal implementation package rather than a public API. It is not intended to be called directly by external applications; instead it is orchestrated by higher-level item text utility routines and concurrent programs.

Key Procedures and Functions

  • BUILD_ITEM_TEXT_INDEX — The principal driver. This routine constructs (or rebuilds) the Oracle Text index used for item descriptive text searching. It coordinates preference creation, section-group and stoplist handling, and the actual CTX_DDL index-creation call. Because index building is resource-intensive, this procedure is typically the long-running step invoked from a concurrent request.
  • SET_LOG_MODE — Controls the logging verbosity of the package. It toggles whether diagnostic messages are written during index build operations, allowing operators to run in quiet mode during routine rebuilds or in verbose mode for troubleshooting.
  • LOG_LINE — Writes an individual log entry using the FND_FILE/FND_MESSAGE utilities. It is called repeatedly by the build routine to record progress, warnings, and errors to the concurrent manager log file.
  • GET_MSG_TEXT — Retrieves the localized message text associated with a message name, providing consistent, NLS-aware error and status strings for logging and exception handling.

A fifth documented callable exists alongside these; the package exposes a small, focused surface deliberately limited to index construction and logging concerns.

Tables Accessed

The package touches a mixture of application and dictionary views. It reads FND_DESCRIPTIVE_FLEXS and FND_ID_FLEX_STRUCTURES to identify which descriptive flexfields (and therefore which segment columns) supply searchable item text. ALL_TABLES and ALL_INDEXES are queried to detect whether the text index and its supporting structures already exist, enabling idempotent rebuild logic. Oracle Text catalog views — CTX_PARAMETERS, plus CTX_PREFERENCES, CTX_SECTION_GROUPS, CTX_STOPLISTS and CTX_INDEXES via the CTXSYS schema — are inspected and manipulated to configure the index. DDL against these Oracle Text objects is issued through AD_CTX_DDL, CTX_DDL and CTX_OUTPUT. V$PARAMETER is consulted, likely to confirm the text_enabled database parameter before attempting index operations. PLITBLM is referenced for the PL/SQL item table type used in temporary collections.

Usage Notes

EGO_ITEM_TEXT_PVT is normally invoked indirectly. The standard entry point is the concurrent program that synchronizes the item text index, which calls EGO_ITEM_TEXT_UTIL routines that in turn delegate to this private package. Because the package is not referenced by any database object at the ETRM documentation level but is itself called by two other packages (EGO_ITEM_TEXT_UTIL and potentially the package of the same name interface), administrators should treat it as an internal helper. Custom code may call it for on-demand index rebuilds after bulk item imports, but because index creation is DDL-heavy and can lock or extend significant space, such calls should be scheduled through the concurrent manager rather than run interactively. Always confirm that the Oracle Text option is installed and that CTXSYS objects are accessible before invoking the build routine.