Search Results csd_product_txns_v




Overview
Explore in AI Chat

Overview

CSD_PRODUCT_TXNS_V is a valid APPS-owned view in the Oracle E-Business Suite Depot Repair (CSD) module, available in releases 12.1.1 and 12.2.2. Its documented purpose is to drive the Receive/Ship tab of the Repair Orders Workbench, presenting all charge lines and their related attributes for a repair order. The view consolidates data from repair headers, repair lines, estimate details, inventory items, and the product transaction records that represent the physical movement of goods through the depot repair flow.

For reporting and integration, the view functions as a denormalized read layer over the transactional core. It joins product transaction rows to repair order context so that functional users and downstream programs can query charge-line detail—quantities, statuses, subinventories, lot numbers, and sales order interface flags—without reconstructing the underlying joins themselves. The user search for "estimate_quantity" maps directly to a column in this view, where EDT.QUANTITY_REQUIRED is aliased as ESTIMATE_QUANTITY.

Underlying Base Objects

The documented ETRM metadata lists the objects referenced by the view definition. The principal transactional base is CSD_PRODUCT_TRANSACTIONS, accessed as a synonym, which supplies the row identity (PRODUCT_TRANSACTION_ID), action type and code, interface and sales order flags, product transaction status, subinventory, lot number, source and non-source instance identifiers, and the standard WHO columns plus descriptive flexfield context and attribute segments.

CSD_REPAIRS supplies repair order context such as repair number, repair mode, repair type, quantity, quantities in WIP, received and shipped, approval flags and status, status, date closed, and promise date. CS_ESTIMATE_DETAILS contributes the estimate detail identity, inventory item, quantity required, unit of measure, and item revision. The view also references MTL_SYSTEM_ITEMS_VL and MTL_UNITS_OF_MEASURE_VL for item concatenated segments, descriptions, and unit of measure translations, along with supporting objects spanning CSI_ITEM_INSTANCES, OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, WSH_PICKING_RULES, OKC_K_HEADERS_B, PO_HEADERS_ALL, QP_LIST_HEADERS_TL, HZ customer and location entities, CS_TRANSACTION_TYPES_VL, CS_TXN_BILLING_TYPES, MTL_PARAMETERS, and the CS_STD package. These objects support shipping, order capture, contracts, and pricing context used by the workbench.

Key Columns

Common Use Cases and Queries

Typical uses include Repair Orders Workbench receive/ship population, repair charge-line reporting, reconciliation of estimated versus received quantities, and integration extracts for Order Management. A representative query retrieving estimated quantities for a repair order follows:

  • SELECT REPAIR_NUMBER, PRODUCT, PRODUCT_DESCRIPTION, ESTIMATE_QUANTITY, REPAIR_QUANTITY, QUANTITY_RCVD, QUANTITY_SHIPPED, PROD_TXN_STATUS FROM CSD_PRODUCT_TXNS_V WHERE REPAIR_NUMBER = :p_repair_number;
  • SELECT REPAIR_NUMBER, ESTIMATE_QUANTITY, QUANTITY_IN_WIP FROM CSD_PRODUCT_TXNS_V WHERE ESTIMATE_QUANTITY > NVL(QUANTITY_RCVD, 0);
  • SELECT PRODUCT_TRANSACTION_ID, ACTION_CODE, INTERFACE_TO_OM_FLAG, SHIP_SALES_ORDER_FLAG FROM CSD_PRODUCT_TXNS_V WHERE PROD_TXN_STATUS = :p_status;

Because the view is a read-only projection, all access should be limited to SELECT statements, and consumers should account for the NVL defaults applied to QUANTITY_IN_WIP, QUANTITY_RCVD, and QUANTITY_SHIPPED when comparing estimated quantities against actual movement.