Search Results csi_transactions_pvt




Overview
Explore in AI Chat

Overview

CSI_TRANSACTIONS_PVT is the private implementation package body for the Oracle Enterprise Business Suite (EBS) Install Base transaction API, owned by the APPS schema in release 12.1.1 and 12.2.2. Where its companion public package, CSI_TRANSACTIONS_PUB, exposes the documented, versioned interface that external callers are expected to use, CSI_TRANSACTIONS_PVT contains the internal logic that performs the actual validation, defaulting, and persistence of Install Base transactions against the underlying CSI tables. The package is classified as a PVT (private) API in the ETRM inventory, meaning it is intended for internal consumption by Oracle's own Install Base code rather than for direct invocation by customers or third-party integrations.

Functionally, the package underpins the lifecycle of an Install Base transaction: retrieving existing transaction records, creating new ones, applying updates across one or more transactions, and recording errors encountered during processing. It is a core building block of the Install Base transaction engine and is referenced by 28 other database objects, confirming its central role in the CSI module.

Key Procedures and Functions

  • GET_TRANSACTIONS — Retrieves Install Base transaction data for consumption by calling code. It typically returns transaction rows and associated header or detail attributes that a caller then validates or renders. No parameter list should be assumed; consult the ETRM signature report for exact arguments.
  • CREATE_TRANSACTION — Creates a new transaction record in the Install Base transaction tables. This is the entry point through which new transaction headers are instantiated prior to line-level or item-level processing.
  • UPDATE_TRANSACTIONS — Applies updates to one or more existing transactions, supporting bulk transactional modifications rather than single-record edits.
  • CREATE_TXN_ERROR — Records an error condition against a transaction, typically populating an error staging or error message table so that a processing program can surface the failure to the user.

All four documented procedures are internal implementation routines; their semantic contract is defined by the calling public API rather than by an independently published signature.

Tables Accessed

  • CSI_TRANSACTIONS — The principal Install Base transaction table, read and written by GET_TRANSACTIONS, CREATE_TRANSACTION, and UPDATE_TRANSACTIONS.
  • CSI_TXN_TYPES — Provides transaction type definitions used to validate and classify transactions.
  • FND_USER — Supplies the application user identity used for auditing and for the "created by"/"updated by" context.
  • JTF_OBJECT_USAGES — Used to resolve object usage/context information associated with the transaction.
  • DBMS_SQL and DUAL — DBMS_SQL indicates dynamic SQL construction, typically for flexible lookups or context-driven queries; DUAL is used for scalar lookups and set-based construction.

Supporting packages referenced by this body include CSI_DATASTRUCTURES_PUB, CSI_GEN_UTILITY_PVT, CSI_TRANSACTIONS_PKG, CSI_TXN_ERRORS_PKG, FND_API, FND_MSG_PUB, FND_MESSAGE, FND_PROFILE, and FND_GLOBAL, which together provide the API framework, error handling, message resolution, profile option access, and session context required by the transaction engine.

Usage Notes

CSI_TRANSACTIONS_PVT should not be called directly by custom code. It is invoked indirectly by the Install Base public API layer (CSI_TRANSACTIONS_PUB) and by the 28 database objects that depend on it, including Install Base forms, the transaction processing concurrent programs, and the Install Base Integrator. In a typical flow, a form or interface program calls the public wrapper, which validates the request and delegates to the PVT routines here for retrieval, creation, update, and error-recording operations.

Because the package is classified PVT and is not referenced by any database object in a public sense, Oracle reserves the right to change its internals between releases. Customizations should always target the public package. When debugging Install Base transaction failures, however, tracing into this package is often necessary, since transaction errors generated during create or update processing are recorded through CREATE_TXN_ERROR and routed into the error tables read by CSI_TXN_ERRORS_PKG.