Search Results source_transaction_table




Overview
Explore in AI Chat

Overview

CSI_T_TXN_LINES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the CSI — Install Base product. It is documented as VALID in both EBS 12.1.1 and 12.2.2. The view is a thin projection over the transaction-line staging table CSI_T_TRANSACTION_LINES, exposing the set of columns required for configuration and install-base processing without requiring consumers to query the base table directly. Because CSI_T_TRANSACTION_LINES is a transaction interface/staging structure rather than a master data table, the view is typically used to inspect inbound transaction lines, determine their configuration validation outcome, and correlate a line to the configuration session and session item that produced it. The column CONFIG_SESSION_ITEM_ID, which is the term users most often search against this object, is exposed directly by the view and identifies the specific configuration item within a configuration session revision.

Underlying Base Objects

The documented base object is CSI_T_TRANSACTION_LINES, referenced through a SYNONYM. The view definition is a straightforward projection with no joins, filters, or aggregations:

Because the view carries no predicate, row counts and cardinality match the base table exactly. It therefore inherits the base table's performance characteristics; heavy reads against CSI_T_TRANSACTION_LINES translate directly into heavy reads against the view, and the view cannot be used to reduce processing volume. Its principal value is interface stability: the column list is fixed and documented, so integrations can depend on it even where the base table's physical definition may evolve.

Key Columns

  • TRANSACTION_LINE_ID — Primary identifier of the transaction line; the join key back to the base table and to related transaction-line detail.
  • SOURCE_TRANSACTION_TABLE / SOURCE_TRANSACTION_ID — Identify the originating record that generated the line, enabling traceability to the source application entity.
  • SOURCE_TRANSACTION_TYPE_ID — Classifies the source transaction type, used to distinguish install, update, and similar line categories.
  • CONFIG_SESSION_HDR_ID — Header identifier of the configuration session associated with the line.
  • CONFIG_SESSION_REV_NUM — Revision number of that configuration session, distinguishing successive configurations of the same instance.
  • CONFIG_SESSION_ITEM_ID — Identifier of the configuration session item; the column most frequently searched. It links a transaction line to the specific item instance created or validated within the session.
  • CONFIG_VALID_STATUS — Indicates whether the configuration was validated successfully or failed validation.
  • SOURCE_TRANSACTION_STATUS — Processing status of the source transaction line.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the concurrent/API layer to detect concurrent updates.

Common Use Cases and Queries

Typical scenarios include diagnosing why a configuration failed to process, tracing a transaction line back to its source record, and reconciling configuration session activity. A search for CONFIG_SESSION_ITEM_ID commonly reflects an attempt to find all lines belonging to one configuration item:

  • SELECT transaction_line_id, config_session_hdr_id, config_session_rev_num, config_valid_status, source_transaction_status FROM csi_t_txn_lines_v WHERE config_session_item_id = :item_id;
  • SELECT transaction_line_id, source_transaction_table, source_transaction_id, config_valid_status FROM csi_t_txn_lines_v WHERE config_valid_status = 'FAILED';
  • SELECT config_session_hdr_id, config_session_rev_num, COUNT(*) FROM csi_t_txn_lines_v GROUP BY config_session_hdr_id, config_session_rev_num;

When querying large volumes, restrict by TRANSACTION_LINE_ID, SOURCE_TRANSACTION_ID, or CONFIG_SESSION_HDR_ID, and consider querying CSI_T_TRANSACTION_LINES directly where an index on the base table better serves the predicate.