Search Results rcv_transactions_pk

Overview

RCV_TRANSACTIONS is the core receiving transactions table in Oracle E-Business Suite, owned by the PO (Purchasing) schema and validated across release 12.1.1 and 12.2.2. Each row represents a single discrete receiving event performed in the Receiving module, whether a receipt, inspection, delivery, return to vendor, transfer, or correction. Because every quantity movement associated with inbound goods and services passes through this table, it functions as the authoritative record of material receipts and the pivot point between Procurement, Inventory, Payables, Cost Management, and WIP.

The table is classified heuristically as hub-leaning under a Data Vault modeling approach. With 134 documented columns, a stable unique surrogate key (TRANSACTION_ID), and an extensive web of foreign keys to purchasing, inventory, vendor, routing, and job definition objects, it behaves as a central transactional hub surrounded by numerous dependent link and satellite structures.

Key Information Stored

The primary key is RCV_TRANSACTIONS_PK, defined on the TRANSACTION_ID column, which is also documented as the single-business-key unique index (RCV_TRANSACTIONS_U1). TRANSACTION_ID is the surrogate identifier used by all downstream dependent tables.

• TRANSACTION_TYPE and TRANSACTION_DATE – the nature of the receipt event and when it occurred.
• QUANTITY, UNIT_OF_MEASURE, PRIMARY_QUANTITY, PRIMARY_UNIT_OF_MEASURE, and UOM_CODE – the received quantity expressed in transaction, primary, and item UOMs.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID, PO_RELEASE_ID, and PO_REVISION_NUM – the purchasing document context.
• VENDOR_ID and VENDOR_SITE_ID – the supplier and supplier site delivering the goods.
• ORGANIZATION_ID, SUBINVENTORY, and LOCATOR_ID – the inventory destination of the receipt.
• SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID – the advance shipment notice linkage.
• INV_TRANSACTION_ID – the corresponding Inventory material transaction generated by the receipt.
• PARENT_TRANSACTION_ID – self-referencing pointer establishing receipt lineage for corrections and adjustments.
• INSPECTION_STATUS_CODE, ACCRUAL_STATUS_CODE, and RECEIPT_EXCEPTION_FLAG – receiving lifecycle state indicators.
• SOURCE_DOCUMENT_CODE, DESTINATION_TYPE_CODE, and INTERFACE_SOURCE_CODE – classification of the receipt origin and destination.

Common Use Cases and Queries

Receiving analysts, buyers, and cost accountants query RCV_TRANSACTIONS to reconcile receipts against purchase orders, confirm accrual postings, trace returns, and validate the receipt-to-invoice match. A typical pattern retrieves receipts for a purchase order line:

SELECT transaction_id, transaction_type, transaction_date, quantity,
       unit_of_measure, inspection_status_code
FROM   rcv_transactions
WHERE  po_line_id = :po_line_id
AND    transaction_type IN ('RECEIVE','DELIVER','RETURN TO VENDOR');

Returns and corrections are located through the self-join on PARENT_TRANSACTION_ID, while reconciliation reporting frequently joins RCV_TRANSACTIONS to MTL_MATERIAL_TRANSACTIONS on INV_TRANSACTION_ID to confirm that each receipt generated a valid inventory movement. Subscription and period-end reporting often aggregate quantities by VENDOR_ID, ORGANIZATION_ID, or TRANSACTION_DATE.

Related Objects

• PO_LINES_ALL and PO_LINE_LOCATIONS_ALL – joined on PO_LINE_ID and PO_LINE_LOCATION_ID; define the ordered line and shipment.
• PO_HEADERS_ALL, PO_RELEASES_ALL, and PO_DISTRIBUTIONS_ALL – provide header, release, and accounting distribution context.
• MTL_MATERIAL_TRANSACTIONS – linked through INV_TRANSACTION_ID; the inventory-side counterpart of each receipt.
• RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES – the ASN documents that originated the receipt.
• AP_INVOICE_DISTRIBUTIONS_ALL and AP_HOLDS_ALL – reference RCV_TRANSACTION_ID to support invoice matching and holds.
• RCV_ACCOUNTING_EVENTS – captures the accounting events raised for each receipt transaction.
• RCV_LOT_TRANSACTIONS and RCV_SERIAL_TRANSACTIONS – track lot and serial detail tied to the receipt.
• PO_VENDORS and PO_VENDOR_SITES_ALL – supply supplier and supplier site information via VENDOR_ID and VENDOR_SITE_ID.