Search Results expected_installation_date

Overview

CSI_LINE_INST_DETAILS_V is an APPS-owned backward-compatibility view in the Oracle E-Business Suite CSI (Install Base / Enterprise Territory and Resource Management) module. It exposes installation detail records that were originally stored in the legacy table CS_LINE_INST_DETAILS, allowing older customizations, reports, and integrations written against that base table to continue functioning after the schema was refactored into the CSI_T_* transaction table family. In Oracle EBS 12.1.1 and 12.2.2 the view remains VALID and is delivered as a read-mostly compatibility layer rather than as a transaction-entry object.

The view is significant because the CSI install-base transaction model captures installation, return, and RMA activity through a normalized set of transaction tables. CSI_LINE_INST_DETAILS_V flattens the line-level detail of those transactions into the historical column layout, including the SOURCE_LINE_INST_DETAIL_ID and related columns that users commonly search for when tracing installation detail lineage. It is therefore used primarily for reporting, data extraction, and migration lookups, not for DML.

Underlying Base Objects

Per the documented view text, CSI_LINE_INST_DETAILS_V is defined over four base objects resolved through APPS synonyms:

• CSI_T_TXN_LINE_DETAILS (CTTLD) — the primary transaction line detail table, supplying TXN_LINE_DETAIL_ID (aliased to LINE_INST_DETAIL_ID), CSI_SYSTEM_ID, INSTANCE_ID, INSTANCE_TYPE_CODE, QUANTITY, INSTALLATION_DATE, the CONTEXT/ATTRIBUTE flex columns, OBJECT_VERSION_NUMBER, and the ACTIVE_START_DATE/ACTIVE_END_DATE pair. It is the driver table in the join.
• CSI_T_TRANSACTION_LINES (CTTL) — joined by TRANSACTION_LINE_ID = CTTLD.TRANSACTION_LINE_ID (outer join), providing SOURCE_TRANSACTION_TABLE and SOURCE_TRANSACTION_ID used in the DECODE clauses that populate ORDER_LINE_ID and QUOTE_LINE_SHIPMENT_ID.
• CSI_T_PARTY_DETAILS (CTPD) — joined by TXN_LINE_DETAIL_ID, supplying PARTY_SOURCE_ID, which maps to INSTALLED_AT_PARTY_SITE_ID.
• CSI_TRANSACTIONS (CT) — joined by CTTLD.CSI_TRANSACTION_ID = CT.TRANSACTION_ID, supplying TRANSACTION_TYPE_ID.

Because CTPD is joined with an equi-join while CTTL uses an outer join, party detail rows are required for a line detail to appear; transaction line data is optional. This affects row returns and should be considered when tuning queries.

Key Columns

• LINE_INST_DETAIL_ID — the primary identifier, sourced from CSI_T_TXN_LINE_DETAILS.TXN_LINE_DETAIL_ID. This is the modern equivalent of the legacy line-installation-detail ID.
• SOURCE_LINE_INST_DETAIL_ID — a lineage column preserved for backward compatibility, used to relate a detail to its originating detail record. Note that the documented view text maps this position to a literal NULL, so consumers should verify population before relying on it in 12.1.1/12.2.2.
• ORDER_LINE_ID — populated via DECODE when SOURCE_TRANSACTION_TABLE = 'OE_ORDER_LINES_ALL', capturing the order line that drove the installation.
• QUOTE_LINE_SHIPMENT_ID — populated via DECODE when SOURCE_TRANSACTION_TABLE = 'WSH_DELIVERY_DETAILS', capturing the delivery detail.
• TRANSACTION_TYPE_ID — the CSI transaction type classifying the installation event.
• CUSTOMER_PRODUCT_ID / CUSTOMER_PRODUCT_TYPE_CODE / CUSTOMER_PRODUCT_QUANTITY — the instance and quantity context for the installation detail.
• INSTALLED_AT_PARTY_SITE_ID — the party site where the customer product was installed.
• EXPECTED_INSTALLATION_DATE — the planned installation date.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT, ACTIVE_START_DATE, ACTIVE_END_DATE — descriptive flexfield and effective-dating columns.

Common Use Cases and Queries

Typical uses include tracing installation details back to originating order or delivery transactions, extracting install-base history for data warehousing, and validating migrated records against the legacy CS_LINE_INST_DETAILS layout.

• Retrieving a specific installation detail by its legacy identifier.
• Reporting installation activity by transaction type and party site.
• Reconciling order lines and delivery details against installation records.

Sample query retrieving detail, order, and delivery lineage:

SELECT line_inst_detail_id, source_line_inst_detail_id, order_line_id, quote_line_shipment_id, transaction_type_id, customer_product_id, installed_at_party_site_id, expected_installation_date FROM apps.csi_line_inst_details_v WHERE line_inst_detail_id = :p_detail_id;

Sample query listing installation activity for a party site:

SELECT line_inst_detail_id, transaction_type_id, customer_product_quantity, installation_date FROM apps.csi_line_inst_details_v WHERE installed_at_party_site_id = :p_party_site_id AND installation_date >= :p_from_date ORDER BY installation_date;