Search Results search_move_data

Overview

IBE_SEARCH_SETUP_PVT is a private (PVT-classified) PL/SQL package in the APPS schema that supports search configuration and index maintenance for the Oracle iStore (IBE) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business role is to manage the underlying Oracle Text infrastructure used by iStore's catalog and content search capabilities. This includes the creation and population of search-related LOB segments, the initialization of Oracle Text preference and DDL structures (via CTX_DDL and CTX_PREFERENCES), and the movement of data between search staging and indexed tables, such as IBE_CT_IMEDIA_SEARCH and its companion table IBE_CT_IMEDIA_SEARCH_S1. Because the package is classified as PVT, it is not intended as a public integration API; rather, it is a building-block layer consumed internally by higher-level iStore search packages such as IBE_SEARCH_PVT and IBE_SEARCHUPDATE_PVT, both of which reference it. It also references itself, indicating internal recursion or shared helper logic across its own procedures.

Key Procedures and Functions

The ETRM metadata documents three procedures/functions within IBE_SEARCH_SETUP_PVT. Parameter signatures are not published in the metadata and should be derived from the deployed package specification when customization is required.

• WRITETOLOB — Writes content into a LOB (large object) column, typically associated with Oracle Text index storage such as the search table IBE_CT_IMEDIA_SEARCH. It leverages DBMS_LOB and likely CTX_DDL to persist searchable text chunks. This supports the indexing pipeline by ensuring document or media content is materialized into the appropriate CLOB/BLOB segment.
• SEARCH_MOVE_DATA — Performs the movement of data into or between search infrastructure tables (for example, staging data into IBE_CT_IMEDIA_SEARCH and IBE_CT_IMEDIA_SEARCH_S1). This is a core setup routine that prepares indexed content so that Oracle Text queries issued by the iStore storefront return current results.
• TEST_SEARCH_MOVE_DATA — A diagnostic or validation counterpart to SEARCH_MOVE_DATA. It exercises the data-movement logic to verify correctness without necessarily committing the production move, which is useful during implementation, patching, or troubleshooting of the search index setup.

Tables Accessed

The package reads and writes several documented objects, chiefly through APPS synonyms:

• IBE_CT_IMEDIA_SEARCH and IBE_CT_IMEDIA_SEARCH_S1 — The primary Oracle Text-indexed search table and its secondary segment; these hold the searchable content manipulated by WRITETOLOB and SEARCH_MOVE_DATA.
• MTL_ITEM_CATEGORIES and MTL_SYSTEM_ITEMS_TL — Inventory item and category data used to resolve catalog content that must be indexed for iStore search.
• OE_SYSTEM_PARAMETERS_ALL — Order-management system parameters consulted to align search behavior with the operating unit's configured sales/order context.
• FND_APPLICATION and FND_ORACLE_USERID — EBS application and database-user metadata, used to identify the owning application and schema for Oracle Text preference setup.
• USER_INDEXES — Data dictionary access to confirm existence/status of indexes before re-creation or population.
• CTX_DDL, CTX_PREFERENCES, DBMS_LOB, DBMS_UTILITY, STANDARD — Oracle Text and PL/SQL-supplied packages invoked to build preferences, perform DDL, and handle LOB and utility operations.

Usage Notes

IBE_SEARCH_SETUP_PVT is an internal setup utility rather than a user-facing API. It is most commonly invoked during iStore search configuration and index (re)build activities, including initial implementation, patch application, and troubleshooting when catalog search results become stale or the Oracle Text index requires re-population. It is referenced by IBE_SEARCH_PVT and IBE_SEARCHUPDATE_PVT, which drive runtime search and index-update flows; administrators typically trigger these higher-level packages through concurrent programs or iStore administrative screens rather than calling IBE_SEARCH_SETUP_PVT directly. Custom code should avoid depending on this PVT package because its specification is subject to change across EBS releases; where programmatic index maintenance is required, the supported public iStore search APIs should be used instead.