Search Results ro_status

Overview

The CSD_PRODUCT_TXNS_IRO_V view is a Depot Repair (CSD) reporting object that exposes product transaction activity related to repair orders in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates material movement, repair-line, order, and item metadata so that shipping, receiving, and integration events tied to a repair order can be queried in a single denormalized record. The view is owned by the APPS schema and is documented as VALID in the ETRM metadata.

A distinguishing feature is its interaction with order management entities. The view joins to OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and OE_TRANSACTION_TYPES_TL, and exposes flags such as INTERFACE_TO_OM_FLAG, BOOK_SALES_ORDER_FLAG, RELEASE_SALES_ORDER_FLAG, and SHIP_SALES_ORDER_FLAG. These columns indicate whether a repair product transaction has been interfaced to Order Management, booked, released, or shipped, making the view particularly relevant to integrators searching for order-line related data (for example, users searching for OE_ORDER_LINES_V).

Underlying Base Objects

The view is defined over, or resolves references to, the following documented base objects:

• CSD_PRODUCT_TRANSACTIONS – primary driver of product transaction records (aliased PTXN); source of ACTION_TYPE, ACTION_CODE, PROD_TXN_STATUS, PROD_TXN_CODE, LOT_NUMBER, and the OM interface flags.
• CSD_REPAIRS – repair order line (aliased CR); supplies REPAIR_LINE_ID, REPAIR_NUMBER, QUANTITY, SERIAL_NUMBER, REPAIR_MODE, RO_STATUS, and approval attributes.
• OE_ORDER_LINES_ALL / OE_ORDER_HEADERS_ALL / OE_TRANSACTION_TYPES_TL – sales order context used to derive inventory item, UOM, and OM transaction type information.
• MTL_SYSTEM_ITEMS_KFV – item concatenated segments, description, lot control code, and serial number control code.
• CSI_ITEM_INSTANCES / CSD_REPAIR_TYPES_B – instance and repair type references.
• PO_REQUISITION_HEADERS_ALL / PO_REQUISITION_LINES_ALL – requisition context referenced by transaction rows.
• Supporting objects – CSD_PARTY_SITES_V, FND_LOOKUPS, FND_GLOBAL, HR_ALL_ORGANIZATION_UNITS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and WSH_PICKING_RULES.

Key Columns

• PRODUCT_TRANSACTION_ID / REPAIR_LINE_ID / REPAIR_NUMBER – primary transaction and repair line identifiers.
• INVENTORY_ITEM_ID / ITEM / ITEM_DESC / UNIT_OF_MEASURE – item identity and order quantity UOM (sourced from OE_ORDER_LINES_ALL).
• ACTION_TYPE / ACTION_CODE / PROD_TXN_CODE / PROD_TXN_STATUS – describes the product transaction action and its shipping/receiving status.
• INTERFACE_TO_OM_FLAG / BOOK_SALES_ORDER_FLAG / RELEASE_SALES_ORDER_FLAG / SHIP_SALES_ORDER_FLAG – order management integration state indicators.
• SUB_INVENTORY / SUB_INVENTORY_RCVD / LOT_NUMBER / LOT_NUMBER_RCVD – source and destination subinventory and lot tracking, using NVL against PRL.SOURCE_SUBINVENTORY, PRL.DESTINATION_SUBINVENTORY, and PTXN.SUB_INVENTORY_RCVD.
• LOT_CONTROL_CODE / SERIAL_NUMBER_CONTROL_CODE – item control attributes from MTL_SYSTEM_ITEMS_KFV.
• RO_QUANTITY / RO_QUANTITY_SHIPPED / RO_QUANTITY_RCVD / RO_SERIAL_NUMBER / RO_STATUS / REPAIR_MODE – repair order level quantities and status.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, SECURITY_GROUP_ID.

Common Use Cases and Queries

Typical scenarios include reviewing repair order shipment/receipt activity, tracking OM interfacing status for repair transactions, and reconciling lot/serial controlled item movements. A basic query follows:

• SELECT repair_number, item, item_desc, action_code, prod_txn_status, ship_sales_order_flag FROM csd_product_txns_iro_v WHERE repair_number = :p_repair_number;
• SELECT product_transaction_id, inventory_item_id, sub_inventory, sub_inventory_rcvd, lot_number, lot_number_rcvd FROM csd_product_txns_iro_v WHERE interface_to_om_flag = 'Y' AND book_sales_order_flag <> 'Y';
• SELECT r.repair_number, r.ro_status, r.ro_quantity_shipped, r.ro_quantity_rcvd, t.action_type FROM csd_product_txns_iro_v t, csd_repairs r WHERE t.repair_line_id = r.repair_line_id;

Because the view exposes both repair and order management context, it is frequently joined back to OE_ORDER_LINES_ALL or OE_ORDER_LINES_V on inventory item and order identifiers when full sales order line detail is required, since the view itself surfaces only the OM flags and item/UOM derivations.