Search Results sync_index

Overview

The CTXSYS.ICX_POR_INDEX_REBUILD_PKG package body is a small Oracle Text (interMedia) utility wrapper delivered as part of the Oracle E-Business Suite iProcurement / Internet Procurement module. Its sole documented purpose is to expose a thin PL/SQL interface — SYNC_INDEX — that Oracle EBS application code can call to synchronize an Oracle Text (CONTEXT) index owned by a schema other than the calling session. Because Oracle Text's native CTX_DDL.SYNC_INDEX procedure resides in the CTXSYS schema, EBS application objects cannot invoke it directly without the appropriate privileges; this wrapper, compiled in CTXSYS, allows the indexed column's owner-prefixed name to be passed in and forwarded to the native Text API.

The package belongs to the Internet Procurement family of objects (prefix ICX) that support the iProcurement searchable catalog. In EBS releases 12.1.1 and 12.2.2, this catalog relies on Oracle Text indexes to provide keyword and attribute search across purchasable items, supplier content, and punchout data. The ICX_POR_INDEX_REBUILD_PKG contributes the synchronization step that pushes pending index changes into the Text index so that newly created or updated catalog rows become searchable.

Key Procedures and Functions

The package declares a single public procedure, as documented in the ETRM package metadata:

• SYNC_INDEX — Synchronizes the named Oracle Text index. The procedure accepts an index owner identifier and an index name as its inputs, concatenates them into a fully qualified owner.index_name string, and passes that string to CTX_DDL.SYNC_INDEX. No other procedures, functions, or package-level variables are declared; the body opens with the AS clause defining SYNC_INDEX and closes immediately after the procedure definition, confirming that the package is a pure delegation wrapper with no internal business logic, error handling, or logging.

Tables Accessed

The package body contains no SQL statements and therefore does not read from or write to any application tables directly. Its effect on data is indirect: by invoking CTX_DDL.SYNC_INDEX, it causes Oracle Text to merge pending DML entries held in the corresponding Text index's change-tracking tables (for example, the DR$…$I pending-row table and associated $N / $K tables) into the searchable index structures. The ETRM metadata lists no tables referenced via APPS synonyms, consistent with the source, which does no table access of its own. Consequently, no EBS product schema tables such as ICX_POR_… catalog or search staging tables are touched by this package.

Usage Notes

Because SYNC_INDEX simply forwards its arguments, it is invoked in contexts where index synchronization must be performed by code that does not own the index. Typical callers include concurrent programs and background jobs in iProcurement that refresh the searchable catalog, as well as custom or diagnostic scripts that need to force a Text index to catch up after bulk catalog load or update operations.

In practice, an administrator or scheduled process runs synchronization on a periodic basis rather than after every row insert, since Text index synchronization is a relatively expensive operation. The wrapper inherits all of the native CTX_DDL.SYNC_INDEX behavior, including the requirement that pending rows exist and that adequate privileges and Text index configuration are in place. It performs no commit, exception handling, or parameter validation, so callers are responsible for correct owner and index names and for committing any surrounding DML before synchronization. The package is not referenced by any other documented EBS packages, indicating it is a leaf utility rather than a shared framework component.