Search Results source_line_ref




Overview
Explore in AI Chat

Overview

CSI_TXN_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the CSI (Install Base) product family. Its documented description is "Instance Transaction Details View." The view presents transaction detail records originating from the CSI_TRANSACTIONS table, joined to transaction type definitions and to the Oracle Application Object Library's FND_APPLICATION table so that application short names can be resolved alongside the raw transaction data.

The view plays a significant role in EBS reporting and integration scenarios involving Install Base. Because CSI_TRANSACTIONS stores many foreign-key and reference identifiers (transaction type, sub-type, group, header, line, and distribution references) without embedding descriptive text, CSI_TXN_DETAILS_V enriches each row with human-readable context. Specifically, it exposes SOURCE_TRANSACTION_TYPE and SOURCE_TXN_TYPE_NAME from the transaction type definition, which is precisely the attribute users search for when tracing a transaction back to its originating system transaction type. The view is documented as VALID and is defined in APPS, making it accessible to report authors and integrators with appropriate privileges.

Underlying Base Objects

The view is defined over three documented base objects, all referenced as synonyms:

  • CSI_TRANSACTIONS (CT) — the primary source of transaction records, supplying transaction ID, dates, type IDs, reference identifiers, quantities, status, action codes, and the standard WHO/attribute columns.
  • CSI_TXN_TYPES (CTT) — the transaction type definition table, joined on CT.TRANSACTION_TYPE_ID = CTT.TRANSACTION_TYPE_ID. This join contributes SOURCE_TRANSACTION_TYPE, SOURCE_TXN_TYPE_NAME, and DESCRIPTION.
  • FND_APPLICATION (FA) — joined via CTT.SOURCE_APPLICATION_ID = FA.APPLICATION_ID, contributing APPLICATION_SHORT_NAME so the owning application of the transaction type is identifiable.

The inner joins mean that only transactions whose transaction type resolves to a valid CSI_TXN_TYPES row (and whose source application resolves in FND_APPLICATION) appear in the view. Transactions with orphaned or unresolvable type references would be excluded.

Key Columns

Common Use Cases and Queries

The view is typically used to report or reconcile Install Base transactions, to trace a transaction to the originating application and transaction type, and to feed downstream integration extracts that require decoded type descriptions rather than raw IDs.

To find all transactions of a given originating transaction type, query on SOURCE_TRANSACTION_TYPE:

  • SELECT transaction_id, transaction_date, source_transaction_type, source_txn_type_name, application_short_name, transaction_quantity, transaction_status_code FROM csi_txn_details_v WHERE source_transaction_type = :p_type;
  • SELECT application_short_name, source_transaction_type, COUNT(*) FROM csi_txn_details_v GROUP BY application_short_name, source_transaction_type ORDER BY 1, 2;
  • SELECT transaction_id, source_header_ref, source_line_ref, transaction_quantity FROM csi_txn_details_v WHERE inv_material_transaction_id = :p_inv_txn_id;

Because the view is read-only and joins three base objects, it is suited to ad-hoc reporting and to definition of custom concurrent programs or BI Publisher data sets. As with any CSI-based query, filtering by application short name and transaction date ranges improves performance and narrows results to the relevant originating module.