Search Results source_header_ref_id




Overview
Explore in AI Chat

Overview

CSI_SYSTEMS_TRANSACTIONS_V is a reporting and integration view owned by the APPS schema within the Oracle E-Business Suite Install Base (CSI) product family. It presents a denormalized, joined representation of system-level transactions recorded in the Install Base transaction repository. The view consolidates transaction header data with the associated system (item instance) descriptive and translation information, together with the name of the user who last updated the transaction record. Its status is VALID, and it is documented for both EBS 12.1.1 and 12.2.2.

The view is primarily consumed by reporting, diagnostics, and interface processes that need to reconcile system transactions against their originating source references—order management, inventory, or other feeder applications—without navigating multiple base tables directly. Because it joins translation and user tables internally, it eliminates much of the manual join logic typically required when querying CSI_TRANSACTIONS in isolation.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms:

  • CSI_TRANSACTIONS — the driving table (alias T) containing the transactional detail.
  • CSI_SYSTEMS_H — the transaction-to-system association table (alias H), joined on TRANSACTION_ID.
  • CSI_SYSTEMS_B — the base system (instance) table (alias B), joined on SYSTEM_ID.
  • CSI_SYSTEMS_TL — the translation table (alias TL), joined on SYSTEM_ID, supplying the system NAME and DESCRIPTION.
  • FND_USER — the user table (alias FND), joined on LAST_UPDATED_BY to resolve the transaction user name.

The join path is: CSI_TRANSACTIONS → CSI_SYSTEMS_H (on TRANSACTION_ID) → CSI_SYSTEMS_TL and CSI_SYSTEMS_B (on SYSTEM_ID) → FND_USER (on USER_ID = LAST_UPDATED_BY). A language predicate on the translation table (TL.LANG) restricts output to the appropriate language rows.

Key Columns

Common Use Cases and Queries

A frequent scenario is reporting transaction quantities broken down by unit of measure for a given system or date range. For example:

SELECT transaction_id, system_id, transaction_date,
       transaction_quantity, transaction_uom_code,
       transaction_status_code, txn_user_name
  FROM apps.csi_systems_transactions_v
 WHERE transaction_uom_code = 'EA'
   AND transaction_date >= SYSDATE - 30;

Another common use is tracing a system's transactional history with descriptive names resolved:

SELECT system_number, name, transaction_date,
       transaction_type_id, transaction_quantity, txn_user_name
  FROM apps.csi_systems_transactions_v
 WHERE system_id = :p_system_id
 ORDER BY transaction_date DESC;

Integration and reconciliation processes use the SOURCE_*_REF columns to match Install Base transactions to feeder-system documents, while diagnostics teams use TRANSACTION_STATUS_CODE and MESSAGE_ID to identify failed or pending transactions. Because the view performs all joins internally, it is well suited to ad hoc querying, custom concurrent programs, and BI Publisher reports where a flat, human-readable transaction record is required.