Results for “csd_product_transactions”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSD_PRODUCT_TRANSACTIONS is a child table of CSD_REPAIRS within the Oracle E-Business Suite Depot Repair (CSD) module. It stores all product-level inbound and outbound transactions associated with a repair order, capturing the movement of goods, serialized units, and inventory items through the repair lifecycle. Each row represents a discrete product transaction line linked to a specific repair line, providing the transactional backbone that connects Depot Repair activity to Oracle Inventory, Order Management, Purchasing, and Shipping execution.

Under a heuristic Data Vault classification mined from its foreign-key structure, this object is best modeled as a link table. It resolves relationships between CSD_REPAIRS (the repair order context), CS_ESTIMATE_DETAILS (the estimate line context), and the downstream material transaction tables in Oracle Inventory such as MTL_UNIT_TRANSACTIONS and MTL_TRANSACTION_LOT_NUMBERS. It is not a hub (it has no natural business key independent of its parents) nor a pure satellite (it carries FK references to multiple parents rather than describing a single hub).

Key Information Stored

The table contains 65 documented columns in release 12.2.2. The surrogate primary key is PRODUCT_TRANSACTION_ID, enforced by unique index CSD_PRODUCT_TRANSACTIONS_U1 and constraint CSD_PRODUCT_TXNS_PK. There is no separate business-key unique index documented beyond this single-column unique constraint.

• PRODUCT_TRANSACTION_ID — Surrogate primary key; referenced by Inventory interface and transaction tables.
• REPAIR_LINE_ID — FK to CSD_REPAIRS; associates the transaction with the parent repair order line.
• ESTIMATE_DETAIL_ID — FK to CS_ESTIMATE_DETAILS; ties the transaction to the estimate line that authorized it.
• ACTION_TYPE / ACTION_CODE / PROD_TXN_CODE / PROD_TXN_STATUS — Classify the nature and current state of the transaction (e.g., receipt, shipment, return).
• INVENTORY_ITEM_ID — Inventory item being transacted.
• SHIPPED_SERIAL_NUMBER, SOURCE_SERIAL_NUMBER, NON_SOURCE_SERIAL_NUMBER, UNIT_NUMBER — Serialized unit identifiers for the shipped and source/non-source units.
• SOURCE_INSTANCE_ID, NON_SOURCE_INSTANCE_ID — Instance identifiers for the source and non-source configurations.
• QUANTITY_RECEIVED, QUANTITY_SHIPPED, QUANTITY_PICKED, QUANTITY_AVAILABLE, EXP_QUANTITY — Quantity measures across the receipt, pick, ship and expected stages.
• ORDER_HEADER_ID, ORDER_LINE_ID, REQ_HEADER_ID, REQ_LINE_ID, INTERNAL_PO_HEADER_ID — References to sales order, requisition and internal purchase order documents generated from the transaction.
• SUB_INVENTORY, SUB_INVENTORY_RCVD, LOCATOR_ID, LOT_NUMBER, LOT_NUMBER_RCVD, SHIP_FROM_OU, SHIP_FROM_ORG, RCV_INTO_OU, RCV_INTO_ORG — Inventory organization, subinventory and locator context for ship-from and receive-into flows.
• INTERFACE_TO_OM_FLAG, BOOK_SALES_ORDER_FLAG, RELEASE_SALES_ORDER_FLAG, SHIP_SALES_ORDER_FLAG, UNPLANNED_RECEIPT_FLAG — Processing flags controlling OM interface and order lifecycle actions.
• PROJECT_ID, TASK_ID — Project and task attribution for project-driven repairs.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS for multi-org security.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — Standard who-columns and DFF attributes.

Common Use Cases and Queries

Typical uses include repair order status reporting, inbound/outbound product movement analysis, serialized unit tracking, sales order link reporting (AtoO / RMA flows), and reconciliation between Depot Repair transactions and Inventory transactions.

• List all product transactions for a repair order line:

  SELECT PRODUCT_TRANSACTION_ID, PROD_TXN_CODE, PROD_TXN_STATUS,
         QUANTITY_RECEIVED, QUANTITY_SHIPPED, SHIPPED_SERIAL_NUMBER
  FROM   CSD_PRODUCT_TRANSACTIONS
  WHERE  REPAIR_LINE_ID = :repair_line_id;

• Trace transactions that produced sales order documents:

  SELECT PRODUCT_TRANSACTION_ID, ORDER_HEADER_ID, ORDER_LINE_ID,
         BOOK_SALES_ORDER_FLAG, RELEASE_SALES_ORDER_FLAG
  FROM   CSD_PRODUCT_TRANSACTIONS
  WHERE  INTERFACE_TO_OM_FLAG = 'Y';

• Reconcile against inventory unit transactions using the shared PRODUCT_TRANSACTION_ID reference exposed by MTL_UNIT_TRANSACTIONS.
• Report quantities received versus shipped per subinventory and locator for warehouse throughput analysis.

Related Objects

The most significant related objects, based on documented FK relationships, are:

• CSD_REPAIRS — parent repair order; joined via REPAIR_LINE_ID.
• CS_ESTIMATE_DETAILS — estimate line authorization; joined via ESTIMATE_DETAIL_ID.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID.
• MTL_UNIT_TRANSACTIONS — Inventory serialized unit transaction detail; references CSD_PRODUCT_TRANSACTIONS.PRODUCT_TRANSACTION_ID.
• MTL_TRANSACTION_LOT_NUMBERS — Lot/serial transaction detail; references PRODUCT_TRANSACTION_ID.
• MTL_SERIAL_NUMBERS_INTERFACE, MTL_SERIAL_NUMBERS_TEMP — serial number staging/interface tables.
• MTL_TRANSACTION_LOTS_INTERFACE, MTL_TRANSACTION_LOTS_TEMP — lot transaction interface tables.

These dependencies establish CSD_PRODUCT_TRANSACTIONS as the integration link between Depot Repair and Oracle Inventory material transaction history.