Search Results config_inst_baseline_rev_num

Overview

The APPS.CSI_T_TXN_LINE_DETAILS_V view is a reporting and integration layer within the Oracle E-Business Suite Install Base (CSI) module. It is defined over the transaction line details table, exposing a horizontally projected set of attributes that describe individual item lines associated with Install Base transactions. In the context of Oracle EBS 12.1.1 and 12.2.2, this view provides a stable, read-oriented interface for downstream consumers such as concurrent programs, OBIEE/BIP reports, and custom integration interfaces that need to resolve transaction line detail records without directly querying the underlying transactional table.

The view is owned by the APPS schema and is documented as VALID. Its metadata entry in the ETRM repository describes it simply as a "View on top of Transaction Line Details CSI_T_TXN_LINE_DETAILS." Because it is a projection-only view, it does not introduce transformation, aggregation, or join logic of its own; it mirrors the column list of the base object in the same order.

Underlying Base Objects

The view is defined over a single documented base object: the synonym CSI_T_TXN_LINE_DETAILS. The synonym resolves at runtime to the corresponding APPS-owned table that stores the transaction line detail rows written by Install Base transaction processing. The base object holds the physical storage for transaction line detail data, while CSI_T_TXN_LINE_DETAILS_V serves as the queryable surface exposed to external consumers.

Because the view carries no WHERE clause, DISTINCT, or join in its documented text, each row in the view corresponds one-to-one with a row in the base object. No filtering on transaction status, organization, or reference status is applied. Callers must therefore apply their own filtering predicates, particularly around INVENTORY_ORGANIZATION_ID and the effective date columns.

Key Columns

• TXN_LINE_DETAIL_ID — Surrogate identifier for the transaction line detail record; the primary reference for the row.
• TRANSACTION_LINE_ID — Foreign reference to the parent transaction line, enabling rollup from detail to line and then to transaction header.
• INVENTORY_ITEM_ID — The inventory item affected by the transaction line.
• INV_ORGANIZATION_ID — The inventory organization in which the transaction line operates.
• INVENTORY_REVISION — The revision of the inventory item carried on the transaction line. This is the column most directly relevant to revision-controlled items and to lookup searches such as "inventory_revision."
• QUANTITY — Quantity associated with the transaction line detail.
• UNIT_OF_MEASURE — Unit of measure in which the quantity is expressed.
• LOCATION_TYPE_CODE / LOCATION_ID — Location classification and the specific location identifier for the line detail.
• INSTANCE_DESCRIPTION — Descriptive text for the instance created or impacted by the transaction.
• CONFIG_INST_HDR_ID, CONFIG_INST_REV_NUM, CONFIG_INST_ITEM_ID, CONFIG_INST_BASELINE_REV_NUM — Configuration instance header, revision number, item, and baseline revision identifying the configured instance structure relevant to the line.
• TARGET_COMMITMENT_DATE — Target commitment date for the transaction line detail.
• ACTIVE_START_DATE / ACTIVE_END_DATE — Effective date range governing the record's active period.
• OBJECT_VERSION_NUMBER — Optimistic locking token used by the framework to detect concurrent updates.

Common Use Cases and Queries

The view is commonly used to report transactional activity against revision-controlled items, to populate interface staging tables for Install Base transactions, and to join transaction line details to item and organization master data. It is frequently combined with CSI item instance tables to reconcile instance creation with transacted inventory revisions.

Sample query listing transaction line details for a specific organization and revision:

SELECT d.txn_line_detail_id,
       d.transaction_line_id,
       d.inventory_item_id,
       d.inv_organization_id,
       d.inventory_revision,
       d.quantity,
       d.unit_of_measure,
       d.target_commitment_date
  FROM apps.csi_t_txn_line_details_v d
 WHERE d.inv_organization_id = :p_org_id
   AND d.inventory_revision  = :p_revision
   AND TRUNC(SYSDATE) BETWEEN NVL(d.active_start_date, TRUNC(SYSDATE))
                          AND NVL(d.active_end_date,   TRUNC(SYSDATE));

A second pattern aggregates transacted quantities by item and revision for a given organization:

SELECT d.inventory_item_id,
       d.inventory_revision,
       SUM(d.quantity) total_qty
  FROM apps.csi_t_txn_line_details_v d
 WHERE d.inv_organization_id = :p_org_id
 GROUP BY d.inventory_item_id, d.inventory_revision;

Because the view applies no filtering, queries should always qualify by organization and effective dates where transaction currency matters, and use OBJECT_VERSION_NUMBER when the view is used as the source of an update path into the base table.