Search Results RCV_TRANSACTIONS

Overview

The RCV_TRANSACTIONS table is the central transactional repository for all receiving activities within Oracle E-Business Suite Purchasing (PO) module. It records every material movement event associated with purchase orders, from initial receipt at the dock to final delivery, inspection, rejection, or return to a supplier. Its role is critical for maintaining the integrity of the procure-to-pay cycle, providing a detailed audit trail for inventory, cost accounting, and supplier performance analysis. The table's extensive foreign key relationships underscore its position as a nexus connecting procurement documents, inventory structures, and financial transactions.

Key Information Stored

The table's primary key is TRANSACTION_ID, which uniquely identifies each receiving event. Key columns and their significance include SHIPMENT_LINE_ID, linking to the specific received line; TRANSACTION_TYPE (e.g., RECEIVE, DELIVER, REJECT, RETURN); and QUANTITY. It stores critical references to source documents via PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, and PO_DISTRIBUTION_ID. For inventory accounting, it holds ORGANIZATION_ID, SUBINVENTORY, and LOCATOR_ID. The PARENT_TRANSACTION_ID supports transaction lineage for corrections and returns, while INV_TRANSACTION_ID creates a direct link to the corresponding material transaction in inventory. Other vital columns track UNIT_OF_MEASURE, TRANSACTION_DATE, CREATED_BY, and LAST_UPDATE_DATE.

Common Use Cases and Queries

This table is fundamental for operational reporting and reconciliation. Common analytical queries include tracing the receipt history for a specific purchase order line, calculating total received and outstanding quantities, and analyzing receipt-to-invoice matching discrepancies. Technical consultants often query it to debug receiving issues or generate custom reports. A foundational query pattern is:

• SELECT rt.transaction_id, rt.transaction_type, rt.quantity, rt.transaction_date, rsh.shipment_num, pl.line_num FROM rcv_transactions rt JOIN rcv_shipment_headers rsh ON rt.shipment_header_id = rsh.shipment_header_id JOIN po_lines_all pl ON rt.po_line_id = pl.po_line_id WHERE rt.po_header_id = <PO_ID> ORDER BY rt.transaction_date;

Another critical use case is identifying transactions pending delivery to inventory (TRANSACTION_TYPE = 'RECEIVE') or those linked to specific inventory transactions via INV_TRANSACTION_ID for cost flow analysis.

Related Objects

As indicated by its foreign keys, RCV_TRANSACTIONS is deeply integrated with the application's data model. Primary related objects include:

• RCV_SHIPMENT_HEADERS / RCV_SHIPMENT_LINES: The parent shipment records.
• PO_HEADERS_ALL, PO_LINES_ALL, PO_DISTRIBUTIONS_ALL: The source purchasing documents.
• MTL_MATERIAL_TRANSACTIONS: The corresponding inventory transaction (via INV_TRANSACTION_ID).
• RCV_TRANSACTIONS (self-referencing): For parent-child transaction relationships.
• MTL_SECONDARY_INVENTORIES, MTL_ITEM_LOCATIONS: For subinventory and locator details.
• Key APIs: Procedures within packages like RCV_TRANSACTION_PROCESSOR and RCV_ROUTING_PROCESSOR create and update records in this table.