Search Results icx_por_index_rebuild_pkg

Overview

The CTXSYS.ICX_POR_INDEX_REBUILD_PKG package is an Oracle E-Business Suite component that supports the maintenance of Oracle Text (interMedia) indexes used by the Procurement and iProcurement search infrastructure. In Oracle EBS 12.1.1 and 12.2.2, the "POR" naming convention within the ICX (Oracle iProcurement / Internet Commerce Exchange) schema refers to Purchase Order Requisition text search capabilities. This package provides a programmatic mechanism to synchronize a specified Oracle Text index owned by a given schema, ensuring that the full-text search index remains consistent with the underlying base tables after bulk data changes, structural modifications, or index invalidation events.

Although the package header records an owner of CTXSYS, the header comment ($Header: ICXINBLS.sql ...) and the ICX prefix indicate it originated within the Internet Commerce Exchange module and was catalogued under the CTXSYS context because its sole function is to invoke Oracle Text index operations. Under the ETRM classification it is registered as API type OTHER, meaning it is a utility wrapper rather than a business entity API. It is not referenced by any other packages, which confirms its role as a leaf-level utility invoked directly by callers.

Key Procedures and Functions

The documented package specification exposes a single procedure:

• SYNC_INDEX — The procedure accepts an index owner and an index name (as declared, index_owner IN VARCHAR2 and index_name IN VARCHAR2) and performs a synchronization of the named Oracle Text index. Its purpose is to bring the text index into a consistent state relative to its associated table data, typically by invoking the appropriate CTX_DDL synchronization routine. Because the procedure accepts the owner and index name as arguments, it is generic: it can be pointed at any qualifying Oracle Text index, not only those with ICX-prefixed names. No return value is defined; the procedure is a pure side-effect utility.

Tables Accessed

The ETRM metadata does not enumerate any base tables referenced through APPS synonyms, which is consistent with the nature of the package. As a wrapper that delegates to Oracle Text DDL and DML operations, the objects it touches are the Oracle Text internal tables (such as DR$<index>$I, DR$<index>$K, and the pending-queue tables) belonging to the index named in the call. It does not read or write application tables in the ICX or APPS schemas directly; instead, its effects manifest through the index metadata that Oracle Text maintains. Any table the target index is built upon is affected only indirectly, through index rebuild/sync processing.

Usage Notes

This package is most commonly invoked in scenarios where an iProcurement or purchasing-related Oracle Text index has become stale or invalid. Typical invocation paths include:

• Ad hoc DBA execution from SQL*Plus or a similar client, passing the index owner and index name as literals or bind variables.
• Custom concurrent programs or batch scripts created to automate index synchronization after bulk imports, data patches, or period-end activities.
• Diagnostic and recovery procedures when full-text search results in iProcurement return incomplete or outdated data.

Because the procedure signature permits arbitrary owner and index name values, callers must ensure the invoking schema holds sufficient privileges to perform DDL operations on the Oracle Text index. In EBS 12.1.1 and 12.2.2, execution is normally restricted to privileged accounts (such as APPS or a DBA account) rather than being exposed to end users. Administrators should schedule synchronization during low-activity windows, since a full index sync on large purchasing document volumes can be resource-intensive. When troubleshooting, verifying that the index owner and index name resolve to a valid Oracle Text index is the first diagnostic step, as an invalid identifier will cause the underlying synchronization call to fail.