Search Results config_inst_baseline_rev_num




Overview
Explore in AI Chat

Overview

APPS.CSI_T_TXN_LINE_DETAILS_V is a database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema and defined within the CSI (Complex Maintenance, Repair, and Overhaul / Install Base) application family. The view projects transaction line detail records that describe the individual inventory and configuration instance attributes associated with a transaction line. Its principal role is to provide a stable, report- and interface-friendly projection of the CSI_T_TXN_LINE_DETAILS table, exposing columns such as INSTANCE_DESCRIPTION, CONFIG_INST_HDR_ID, and QUANTITY for consumption by Concurrent Programs, Oracle Reports, BI Publisher data templates, and inbound/outbound integration interfaces. Because the view is a straight column projection of the base table, it carries no additional filtering or join logic, making it the recommended access path when only the transaction line detail attributes are required.

Underlying Base Objects

The view is defined exclusively over a single documented base object: the synonym CSI_T_TXN_LINE_DETAILS, which resolves to the corresponding CSI transaction line details table owned by the CSI schema. The ETRM metadata identifies this object as the only referenced base object, and no joins, unions, or sub-queries appear in the view text. Consequently, the view inherits the primary key TXN_LINE_DETAIL_ID, the foreign key linkage to the transaction line header via TRANSACTION_LINE_ID, and the standard EBS audit and concurrency columns including ACTIVE_START_DATE, ACTIVE_END_DATE, and OBJECT_VERSION_NUMBER. Any DML privileges granted to the view are, in practice, governed by the base table, and the view reflects the base table's transactional and historical data model without transformation.

Key Columns

  • TXN_LINE_DETAIL_ID — Primary key identifying the transaction line detail record.
  • TRANSACTION_LINE_ID — Foreign key to the parent transaction line, used to associate details with a specific transaction event.
  • INVENTORY_ITEM_ID and INV_ORGANIZATION_ID — Identify the item and the inventory organization for which the transaction applies.
  • INVENTORY_REVISION — The inventory revision of the item involved in the transaction line.
  • QUANTITY and UNIT_OF_MEASURE — The transacted quantity and its unit of measure.
  • LOCATION_TYPE_CODE and LOCATION_ID — Define the location context (for example, inventory or internal location) associated with the line detail.
  • INSTANCE_DESCRIPTION — The descriptive text for the instance; this is the column most commonly targeted by users searching on this view.
  • CONFIG_INST_HDR_ID, CONFIG_INST_REV_NUM, CONFIG_INST_ITEM_ID, and CONFIG_INST_BASELINE_REV_NUM — Identify the configuration instance header, revision, item, and baseline revision involved in the transaction.
  • TARGET_COMMITMENT_DATE — The target commitment date for the transaction line detail.
  • ACTIVE_START_DATE, ACTIVE_END_DATE, and OBJECT_VERSION_NUMBER — Standard EBS date-effective and optimistic locking columns.

Common Use Cases and Queries

The view is typically queried to retrieve instance descriptions and configuration details tied to a transaction line, either for reporting or for validating integration payloads. A representative query that retrieves instance descriptions for a given transaction line is:

  • SELECT txn_line_detail_id, transaction_line_id, inventory_item_id, instance_description, quantity, unit_of_measure FROM apps.csi_t_txn_line_details_v WHERE transaction_line_id = :p_transaction_line_id;
  • SELECT transaction_line_id, instance_description, config_inst_hdr_id, config_inst_rev_num FROM apps.csi_t_txn_line_details_v WHERE inventory_item_id = :p_item_id AND inv_organization_id = :p_org_id;
  • SELECT txn_line_detail_id, instance_description, location_type_code, location_id, target_commitment_date FROM apps.csi_t_txn_line_details_v WHERE active_end_date IS NULL;

These queries are commonly embedded in Install Base reconciliation reports, service transaction extracts, and configuration instance audits. When additional attributes from related CSI tables are required, the view can be joined to its parent transaction line table on TRANSACTION_LINE_ID.