Search Results sync_ip_im_index

Overview

INV_ITEM_EVENTS_PVT is a private PL/SQL package in the Oracle Inventory (INV) application, owned by APPS. It implements the internal event-raising engine that supports the Oracle Inventory item business event framework — commonly known as the Item Event API. Its principal responsibility is to detect changes made to inventory item master records and to publish the appropriate Oracle Workflow business events, so that subscribers (such as Oracle Advanced Product Catalog, Oracle Product Information Management, and other downstream applications) can synchronize their own item data with the changes occurring in MTL_SYSTEM_ITEMS and its related entities.

Because it is classified as a private (PVT) API, it is not documented for direct customer invocation. It exists to be called by the public item interfaces and by the internal DML triggers that fire when rows in the item tables are inserted, updated, or deleted. The source header identifies the API name as "Raise Business Event" and describes the package as private, confirming its role as an internal orchestration layer rather than a supported external interface.

Key Procedures and Functions

The package exposes six documented program units. Their purposes are as follows:

• RAISE_EVENTS — The core entry point. It accepts the identity of the affected item (inventory item, item number, organization, revision), the DML type (INSERT, UPDATE, DELETE, or BULK), and a broad set of optional context parameters covering categories, catalog groups, attribute groups, extensions, manufacturer and manufacturer part number, cross-references, customer items, related items and relationship types, and effective dates. It constructs and raises the corresponding Workflow business event.
• INVOKE_ICX_APIS — The routine that bridges Inventory item events to the ICX (Oracle iProcurement / Internet Commerce Exchange) API layer. This is the procedure most commonly associated with the search term "invoke_icx_apis": it exists to propagate item change information into the ICX-related structures so that catalog and procurement content remains consistent with the base item definition.
• INVOKE_ICX_WRAPPER — A wrapper around the ICX invocation. It provides the controlled calling context (error isolation and sequencing) in which INVOKE_ICX_APIS executes, so that a failure in the ICX propagation path does not abort the primary item transaction.
• SYNC_IP_IM_INDEX — Synchronizes the item index used by Inventory Planning and Inventory Management search/query functionality, ensuring indexed item attributes reflect the latest item master state after a change event.
• INVOKE_JAI_API — Invokes the JAI (Oracle Financials for India) integration API, supporting India-specific statutory attributes and localization requirements that must be kept aligned with item changes.
• INVOKE_JG_ZZ_API — Invokes the JG (Oracle Financials for Asia/Pacific regional/localization) API, propagating item changes required by regional localization modules.

Tables Accessed

The package operates against the core item definition and its supporting setup tables, all accessed through APPS synonyms:

• MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_SYSTEM_ITEMS_INTERFACE — the base item master, its key-flexfield view, and the open interface table used when item changes arrive through the interface rather than direct DML.
• MTL_ITEM_CATEGORIES_INTERFACE, MTL_CATEGORIES_KFV — category assignments and category descriptions used to populate category-related event context.
• MTL_ITEM_REVISIONS_INTERFACE — revision-level change data.
• HR_ORGANIZATION_INFORMATION — resolves the owning inventory organization and its classification, used to derive organization context such as organization code.
• MTL_PARAMETERS — organization-level Inventory setup, typically consulted to determine whether event publication is enabled for the organization.
• DUAL — used for single-row lookups and default-value evaluation.

Usage Notes

INV_ITEM_EVENTS_PVT is invoked indirectly. Item maintenance performed through the Master Item form, the Item Copy and Item Import concurrent programs, or the public item APIs ultimately routes through this package to publish the item business event. The metadata shows the package is referenced by 20 other packages, confirming its role as a shared internal service rather than a standalone entry point. Because the source header states that output parameters were deliberately removed ("we make this call inside a nested block and exceptions are not required to be handled there"), callers should not expect return values or propagated exceptions; error handling is the caller's responsibility. The p_commit parameter controls whether the raising transaction commits. Custom code should invoke the supported public item APIs rather than this private package, since its signature and behavior are subject to change between releases such as 12.1.1 and 12.2.2.