Search Results csi_txn_errors_pkg




Overview
Explore in AI Chat

Overview

CSI_TXN_ERRORS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, declared with AUTHID CURRENT_USER so that its SQL executes under the privileges of the calling user. Its name and signature place it squarely within the CSI (Customer Items / Supply Chain Intelligence) product family, which manages item instance and transaction data across receiving, inventory, and order management flows. The package serves as the repository-level API for persisting transaction error records into the CSI_TXN_ERRORS entity. When a supply chain transaction fails validation or interface processing — for example an item instance transaction that cannot be resolved to a valid serial, lot, or location control combination — the failure is captured as a structured error row containing the source transaction identifiers, error text, staging context, and item attributes. CSI_TXN_ERRORS_PKG provides the single, controlled entry point for inserting such rows, thereby insulating calling code from the physical table structure and enforcing consistency across the many transaction interfaces that populate error information.

Key Procedures and Functions

The package exposes one documented public procedure:

  • INSERT_ROW — Inserts a single error record into the CSI transaction errors table. Because the source header comment block is empty in the shipped file, the procedure's intent must be inferred from its parameter surface, which is comprehensive: it accepts the transaction and message identifiers, error text, source type and source identifiers, a processed flag, standard WHO audit columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login), and OBJECT_VERSION_NUMBER for optimistic locking. Beyond the header-level fields, the signature carries source group, source header, source line, and distribution reference columns, the inventory material transaction identifier, an error stage indicator, message string, instance and inventory item identifiers, serial and lot numbers, transaction error date, and a full set of source and destination control codes (serial number, location, lot, revision/quantity) plus a communications trackable flag. The transaction_error_id is passed IN OUT NOCOPY, allowing the procedure to assign and return the generated primary key to the caller without a copy. No other procedures or functions are documented in the ETRM 12.2.2 metadata, which records one total.

Tables Accessed

The package operates against two documented tables, reached through APPS synonyms:

  • CSI_TXN_ERRORS — the base error table holding one row per failed transaction, keyed by transaction_error_id and storing the source references, item identifiers, control codes, and error narrative described above.
  • CSI_TXN_ERRORS_S — the corresponding DDL sequence used by the insert logic to generate the primary key value returned through the IN OUT transaction_error_id parameter.

The metadata does not enumerate query statements, so INSERT_ROW is understood to perform the primary key derivation against CSI_TXN_ERRORS_S and the row insert into CSI_TXN_ERRORS.

Usage Notes

CSI_TXN_ERRORS_PKG is an internal API rather than a user-facing program. It is invoked programmatically by other CSI processing units whenever a transaction fails to complete and must be logged for later diagnosis and reprocessing; the ETRM metadata confirms that at least two other packages reference it. Typical callers include the item instance transaction interfaces, receiving and inventory transaction processors, and any concurrent program that stages supply chain transactions for validation. In the 12.1.1 and 12.2.2 releases the package appears unchanged in behavior, consistent with its last source revision dated 2003. Custom code should call CSI_TXN_ERRORS_PKG.INSERT_ROW rather than inserting into CSI_TXN_ERRORS directly, because the procedure owns key generation and audit column handling. Because the package is compiled with AUTHID CURRENT_USER, callers must possess the necessary object privileges on the underlying tables and sequence. Error rows written here are subsequently surfaced through CSI error inquiry and correction functionality, where users review the message text and stage information before resubmitting the failed transaction.