Search Results rcv_transactions_n16

Overview

RCV_TRANSACTIONS is the core historical transaction table in the Oracle E-Business Suite Receiving (RCV) module, owned by the PO schema. It stores an immutable record of every receiving transaction processed by the Receiving Transaction Processor, including receipts, deliveries, inspections, returns, corrections, and transfers. Once a row is inserted, it is never updated; corrections are reflected through the net transaction quantity maintained in RCV_SUPPLY rather than by modifying the original row. Deletion is restricted to the Purge feature of Oracle Purchasing. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and in EBS 12.1.1 and 12.2.2 the physical schema documents 134 columns. From a Data Vault modeling perspective, the FK density (with dependencies on PO_LINES_ALL, PO_HEADERS_ALL, RCV_SHIPMENT_HEADERS, MTL_ITEM_LOCATIONS, and many others) suggests a hub-leaning classification, though the table realistically functions as a transactional fact with satellite attributes.

Key Information Stored

The surrogate primary key is TRANSACTION_ID, enforced by unique index RCV_TRANSACTIONS_U1 on TRANSACTION_ID — the very index referenced in the search "rcv_transactions_u1". Because it is the only unique index documented, TRANSACTION_ID is the sole business-key candidate. Other important columns include:

• TRANSACTION_TYPE and TRANSACTION_DATE – the nature and timestamp of the receiving event; TRANSACTION_DATE is indexed by RCV_TRANSACTIONS_N15 (with LPN_GROUP_ID).
• QUANTITY, UNIT_OF_MEASURE, PRIMARY_QUANTITY, and PRIMARY_UNIT_OF_MEASURE – transaction quantities in both transaction and primary UOMs.
• PARENT_TRANSACTION_ID – self-referencing link to the originating transaction; indexed by RCV_TRANSACTIONS_N1.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID, and PO_RELEASE_ID – the full purchasing document context.
• SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID – logistic shipment linkage (N2, N9).
• ITEM/INVENTORY DESTINATION: ORGANIZATION_ID, SUBINVENTORY, LOCATOR_ID.
• INVOICE_STATUS_CODE – indexed via function-based RCV_TRANSACTIONS_N16 using NVL('NA').
• EMPLOYEE_ID, DELIVER_TO_PERSON_ID, and VENDOR_ID/VENDOR_SITE_ID – receiver, deliver-to, and supplier attribution.
• INV_TRANSACTION_ID and MOVEMENT_ID – integration keys to inventory and movement statistics.

Common Use Cases and Queries

Typical reporting includes receipt history, three-way match support, and landed-cost or accrual reconciliation. A common pattern joins the header, lines, and items:

• Receipt history: select TRANSACTION_ID, TRANSACTION_TYPE, TRANSACTION_DATE, QUANTITY from RCV_TRANSACTIONS where PO_LINE_LOCATION_ID = :p.
• Correction chains: self-join on PARENT_TRANSACTION_ID to trace superseded transactions.
• Invoice matching: join to AP_INVOICE_DISTRIBUTIONS_ALL on RCV_TRANSACTION_ID to verify matched receipts.
• Inspection backlog: filter on INSPECTION_STATUS_CODE and TRANSACTION_TYPE = 'INSPECT'.
• Accrual reconciliation: join PO_ACCRUAL_RECONCILE_TEMP_ALL via PO_TRANSACTION_ID.

Related Objects

The table participates in extensive referential relationships. The most significant downstream objects referencing RCV_TRANSACTION_ID include AP_INVOICE_DISTRIBUTIONS_ALL and AP_HOLDS_ALL (payables matching), MTL_MATERIAL_TRANSACTIONS and MTL_SUPPLY (inventory), RCV_SUPPLY and RCV_ACCOUNTING_EVENTS (receiving accounting), CST_RCV_ACQ_COSTS (costing), and RCV_LOT_TRANSACTIONS / RCV_SERIAL_TRANSACTIONS (lot and serial tracking). Upstream, RCV_TRANSACTIONS itself references PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, RCV_SHIPMENT_HEADERS, MTL_ITEM_LOCATIONS, and RCV_TRANSACTIONS via PARENT_TRANSACTION_ID. The public API for creating records is the Receiving Transaction Processor, which writes to RCV_TRANSACTIONS_INTERFACE before committing to this table.