Search Results csi_inv_txn_hook_pkg




Overview
Explore in AI Chat

Overview

The APPS.CSI_INV_TXN_HOOK_PKG package is a specialized hook package within the Oracle E-Business Suite Inventory (CSI) module. Its primary business function is to serve as an integration point between Oracle Inventory transaction processing and the CSI (Customer Intelligence / Installed Base) module. Specifically, this package enables the creation and updating of Install Base records based on Inventory material transactions, such as issuances, receipts, and transfers.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the package owner. This is a common pattern for hook and extension packages in EBS, allowing the package to be called from various contexts while respecting the caller's security context. The single documented procedure, POSTTRANSACTION, acts as a transactional hook that is triggered during Inventory transaction processing to synchronize Installed Base data with the physical movement of items.

Key Procedures and Functions

The package exposes one documented procedure:

  • POSTTRANSACTION — This is the core hook procedure invoked after an Inventory transaction has been processed. Based on the documented signature, it accepts a header identifier, a transaction identifier, and returns a status indicator. Its purpose is to evaluate the completed Inventory transaction and determine whether corresponding Installed Base (CSI) transaction records need to be created or updated. This allows the Installed Base to remain synchronized with material movements recorded in Oracle Inventory. The procedure is designed to be called programmatically as part of the Inventory transaction post-processing flow, and it communicates its outcome through the return status parameter.

No additional procedures or functions are documented in the ETRM metadata for this package, indicating that its scope is deliberately narrow and focused on the transaction hook integration.

Tables Accessed

The package references several tables through APPS synonyms, reflecting its role in bridging Inventory and CSI data:

  • MTL_MATERIAL_TRANSACTIONS — The primary Inventory transaction table. The package reads transaction details to identify the item, quantity, and nature of the movement that may affect installed base records.
  • MTL_PARAMETERS — Provides organization-level Inventory parameters, used to determine whether transaction processing and CSI integration are enabled for the current organization.
  • CSI_TXN_TYPES — Contains the definitions of CSI transaction types, allowing the package to map Inventory movements to the appropriate Installed Base transaction classifications.
  • WIP_ENTITIES — Referenced to resolve Work in Process entity information, which is relevant when transactions relate to WIP-related material movements.
  • PLITBLM — A PL/SQL internal table (index-by table) construct referenced in the package body for handling collections of data during processing.

These tables confirm that the package reads Inventory transaction and organization setup data, resolves CSI transaction types, and processes the results to maintain Installed Base integrity.

Usage Notes

CSI_INV_TXN_HOOK_PKG is not typically invoked directly by end users through a form or concurrent program. Instead, it is designed as a hook — a programmatic extension point — that is called by Oracle Inventory's transaction processing framework after a material transaction is committed. Its invocation is controlled by setup and profile options that enable Installed Base integration with Inventory.

In practice, administrators and developers encounter this package when troubleshooting Installed Base synchronization issues, when customizing transaction flows, or when extending CSI integration logic. Because the package is referenced by one other package (as documented in the ETRM metadata), it participates in a dependency chain where the calling package supplies the header and transaction identifiers. Custom code should avoid calling this package directly unless replicating Oracle's standard integration flow, as improper invocation could result in duplicate or inconsistent Installed Base transactions. When extending or debugging CSI-Inventory integration in EBS 12.1.1 or 12.2.2, this package should be treated as a controlled hook rather than a general-purpose API.