Search Results csi_transactions_pkg




Overview
Explore in AI Chat

Overview

CSI_TRANSACTIONS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that serves as a low-level data access layer for installation transaction records within the Enterprise Asset Management (EAM) and Install Base (CSI) product family. It anchors the persistence operations for the CSI_TRANSACTIONS entity, which stores individual transaction events associated with assets, inventory items, and installed base instances across their lifecycle. In Oracle EBS 12.1.1 and 12.2.2, this package is classified as a non-public ("OTHER") API, meaning it is intended primarily for internal consumption by higher-level private APIs rather than as a supported external integration interface. The package encapsulates the base table DML operations — insert, update, and row locking — that higher-level business logic packages rely on to maintain transactional consistency. By centralizing these operations, CSI_TRANSACTIONS_PKG enforces a consistent write path for transaction data and shields callers from the physical schema details of the underlying tables.

Key Procedures and Functions

The documented program units within this package are three procedures, each corresponding to a standard table-maintenance operation:

  • INSERT_ROW — Creates a new record in the transactions table. This procedure is the primary entry point for persisting a newly captured transaction event, populating the base table and its associated translated or descriptive columns.
  • UPDATE_ROW — Modifies an existing transaction record. It is used to amend attributes of a previously created transaction row, supporting corrections and status transitions during transaction processing.
  • LOCK_ROW — Acquires a row-level lock on a transaction record prior to modification. This procedure implements the standard EBS concurrency pattern of locking a row before update to prevent conflicting concurrent writes.

The metadata does not document explicit parameter lists, and these should not be assumed; callers should obtain signatures from the package specification directly. The three procedures reflect a conventional EBS low-level DML triad rather than a set of business-rule-enforcing APIs.

Tables Accessed

The package operates against two documented objects, referenced through APPS synonyms:

  • CSI_TRANSACTIONS — The primary transaction table holding the core transaction records manipulated by INSERT_ROW, UPDATE_ROW, and LOCK_ROW.
  • CSI_TRANSACTIONS_S — The companion table storing translated (language-specific) descriptive columns for the base table. The "_S" suffix denotes the multilingual shadow table used by EBS for translatable attributes.

Insert and update operations write to both the base and translation tables, while lock operations target the base row. Read access is implicit in the locking and update logic.

Usage Notes

CSI_TRANSACTIONS_PKG depends on the standard FND_API utility package (and by extension SYS.STANDARD) for its error-handling and API conventions. It is referenced directly by three components: CSI_TRANSACTIONS_PVT, CSI_COUNTER_READINGS_PVT, and itself. The private API packages CSI_TRANSACTIONS_PVT and CSI_COUNTER_READINGS_PVT are the principal consumers, indicating that transaction persistence is driven through the Install Base private API layer rather than invoked directly by forms or concurrent programs. Typical invocation therefore occurs when install base transactions are created or amended programmatically — for example, during asset instance setup, counter reading capture, or transaction processing routines layered above the private APIs. Custom code should avoid calling this package directly and instead use the documented PVT-layer APIs, since this package exposes raw table DML without business validation. No standalone concurrent program or form is associated with the package itself.