Search Results csi_process_txn_pvt




Overview
Explore in AI Chat

Overview

CSI_PROCESS_TXN_GRP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as a Group (GRP) layer API. It sits within the Oracle Installed Base (CSI) product family and provides the public entry point for processing Installed Base transactions. The package acts as a thin group-layer wrapper that delegates the substantive transaction logic to the private implementation package CSI_PROCESS_TXN_PVT. This public/private split is the standard Oracle EBS API idiom: the _GRP package exposes a stable, supported interface, while the _PVT package holds the procedural business logic that Oracle may revise between releases.

The business function of the package is to accept a transaction payload describing an Installed Base event — such as an item instance creation, update, move, or termination — and route it through the validation, defaulting, and persistence logic owned by the private layer. Because it validates the incoming transaction group against Installed Base data structures before writing, it is a gating point for data integrity in the CSI transaction pipeline.

Key Procedures and Functions

The documented interface exposes a single public procedure, PROCESS_TRANSACTION. Its purpose is to receive a caller-supplied transaction group and drive it through the Installed Base transaction processing sequence. Parameter lists are not documented here and should be confirmed against the deployed package specification for the target release; the recommended practice is to reference the source in the database rather than rely on secondary descriptions.

Internally, PROCESS_TRANSACTION relies on CSI_PROCESS_TXN_PVT for the working implementation and on FND_API for the standard EBS API return-status conventions (success, expected error, unexpected error). The dependence on FND_GLOBAL indicates that the procedure reads application context such as the current user, responsibility, and login, so transaction audit columns are populated consistently with the calling session.

Tables Accessed

Two tables are documented as referenced through APPS synonyms:

  • CSI_ITEM_INSTANCES — the core Installed Base table of item instance records. The package reads and writes this table as transactions create, amend, or close item instances.
  • PLITBLM — the standard EBS PL/SQL table used for bulk/temporary collection handling during set-based processing.

Dependency metadata confirms the package also references CSI_DATASTRUCTURES_PUB, the public structures package that defines the transaction record types passed between the group and private layers. This confirms that the transaction payload is a typed PL/SQL record structure rather than a loose scalar argument list.

Usage Notes

CSI_PROCESS_TXN_GRP is the public API that should be called by external and Oracle-internal code; direct invocation of CSI_PROCESS_TXN_PVT is not supported. Documented callers include CSE_DEPLOYMENT_GRP, CSF_IB, CSI_RMA_FULFILL_PUB, CSI_RMA_RECEIPT_PUB, CSI_WIP_TRXS_PKG, CSI_T_GEN_UTILITY_PVT, and the _PVT package itself. This caller set shows the package is invoked from deployment, RMA fulfillment and receipt, WIP transaction, and generic Installed Base utility flows.

Typical invocation occurs from concurrent programs, Oracle Forms business logic, and custom PL/SQL that must record Installed Base movements arising from order, shipping, RMA, or manufacturing activity. Callers are expected to initialise the FND global context, populate a CSI_DATASTRUCTURES_PUB record, invoke PROCESS_TRANSACTION, then inspect the FND_API return status before committing. Because the package participates in the caller's transaction, commit and rollback control remain with the invoking program.