Search Results csi_bis_txn_dtls_v




Overview
Explore in AI Chat

Overview

The APPS.CSI_BIS_TXN_DTLS_V view is a reporting and integration object within the Oracle E-Business Suite Install Base (CSI) module. It is documented in ETRM as a business intelligence extract created specifically for the Oracle IT – GSI (Global Single Instance) initiative, exposing installation transaction details in a flattened structure suitable for downstream analytics, data warehousing, and cross-module reporting.

The view consolidates transaction header information (source transaction identifiers and types), transaction line details (item, quantity, serial, lot, and instance attributes), and system information (system name and number). By joining these related CSI entities into a single accessible row format, it spares report and integration developers from reconstructing the normalized relationship between transaction lines, sub-types and systems manually. This is particularly relevant in Oracle EBS 12.1.1 and 12.2.2, where Install Base transaction processing remains central to the lifecycle of tracked and non-tracked instances.

Underlying Base Objects

The view definition joins four documented objects, each of which is a view or synonym owned by APPS:

The ETRM metadata confirms all four referenced objects are valid in the APPS schema. Their combination defines the transactional grain of the view: one row per transaction line detail.

Key Columns

The most frequently referenced columns include:

This column set supports both transaction auditing and exception reporting.

Common Use Cases and Queries

Typical scenarios include extracting installation transactions for a specific system, reconciling failures in the Install Base interface, and feeding a data warehouse. A representative query restricted by system name is:

SELECT SOURCE_TRANSACTION_ID,
       SYSTEM_NAME,
       TRANSACTION_TYPE_NAME,
       SERIAL_NUMBER,
       QUANTITY,
       PROCESSING_STATUS,
       ERROR_EXPLANATION
FROM   APPS.CSI_BIS_TXN_DTLS_V
WHERE  SYSTEM_NAME = :p_system_name
AND    PROCESSING_STATUS = 'ERROR';

Aggregate-style reporting groups rows by transaction type and system:

SELECT SYSTEM_NAME, TRANSACTION_TYPE_NAME, COUNT(*)
FROM   APPS.CSI_BIS_TXN_DTLS_V
GROUP  BY SYSTEM_NAME, TRANSACTION_TYPE_NAME;

Because the view is read-only and defined over transactional base tables, longer-running queries should be bound by date or transaction identifiers where possible. It is intended for reporting and integration consumption rather than for direct DML.