Search Results rcv_supply

Overview

The RCV_SUPPLY table is a core transactional table within the Oracle E-Business Suite Purchasing (PO) module for versions 12.1.1 and 12.2.2. It serves as a summary repository for tracking the status and details of items as they move through the receiving and inspection processes. Its primary role is to maintain a consolidated, real-time view of supply originating from various sources—such as purchase orders, requisitions, and internal transfers—that is pending receipt or has been partially received. This table is fundamental for providing visibility into inbound supply, enabling accurate material planning, and supporting the execution of receiving transactions.

Key Information Stored

The table's structure is defined by a composite primary key consisting of SUPPLY_TYPE_CODE and SUPPLY_SOURCE_ID, which classifies the supply source and identifies the specific originating document line. Key columns store references to major purchasing and receiving entities, creating a central hub for supply data. These include PO_HEADER_ID, PO_LINE_ID, PO_DISTRIBUTION_ID, REQ_HEADER_ID, REQ_LINE_ID, and SHIPMENT_LINE_ID. Critical quantitative columns track quantities, such as the quantity expected, quantity delivered, and quantity still outstanding. The table also holds organizational and subinventory details (TO_ORGANIZATION_ID, TO_SUBINVENTORY) specifying the destination for the received goods, and links directly to receiving transactions via RCV_TRANSACTION_ID.

Common Use Cases and Queries

A primary use case is generating reports on open receipts or inbound supply status for procurement and planning teams. Analysts frequently query this table to reconcile purchase order lines with actual receipts. Another critical scenario is supporting the receiving process itself, where applications reference RCV_SUPPLY to determine available quantities to receive. Common SQL patterns involve joining to related purchasing and inventory tables.

• Open Receipts Report: SELECT poh.segment1 po_num, pol.line_num, msi.segment1 item, rs.quantity_delivered, rs.quantity_expected FROM rcv_supply rs, po_headers_all poh, po_lines_all pol, mtl_system_items_b msi WHERE rs.po_header_id = poh.po_header_id AND rs.po_line_id = pol.po_line_id AND pol.item_id = msi.inventory_item_id AND msi.organization_id = pol.org_id AND rs.quantity_expected > rs.quantity_delivered;
• Supply for a Specific Shipment: Queries often filter by SHIPMENT_LINE_ID to examine all supply records tied to a specific advanced shipment notice (ASN) or receipt line.

Related Objects

As indicated by its extensive foreign key relationships, RCV_SUPPLY is a central nexus connecting purchasing, receiving, and inventory entities. Key related objects include:

• Purchasing Documents: PO_HEADERS_ALL, PO_LINES_ALL, PO_DISTRIBUTIONS_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, PO_RELEASES_ALL.
• Receiving Transactions: RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS, which record the actual receipt events against the supply.
• Inventory Structures: MTL_SECONDARY_INVENTORIES, defining the FROM and TO subinventories referenced.
• Key View: RCV_SUPPLY_SUMMARY_V, a common view that aggregates and simplifies data from this table for reporting purposes.