Search Results rcv_shipment_headers

Overview

The RCV_SHIPMENT_HEADERS table is a core transactional entity within the Oracle E-Business Suite Purchasing (PO) module for versions 12.1.1 and 12.2.2. It serves as the primary repository for header-level information pertaining to inbound shipments and receipts. Each record in this table represents a distinct receipt transaction or shipment from a supplier, functioning as the parent container for detailed line-item receipt data. Its role is critical for tracking the lifecycle of goods from vendor shipment through organizational receipt, forming the foundation for three-way matching, inventory updates, and supplier payment processes.

Key Information Stored

The table's structure captures essential metadata for a receipt shipment. The primary identifier is the SHIPMENT_HEADER_ID column, which is the system-generated unique key. A significant business key is the combination of RECEIPT_NUM and SHIP_TO_ORG_ID, which must be unique per the table's alternate key constraint. Critical foreign key relationships include VENDOR_ID (linking to PO_VENDORS) and VENDOR_SITE_ID (linking to PO_VENDOR_SITES_ALL), which identify the supplier and delivery location. While the provided metadata does not list all columns, typical data stored includes receipt dates, shipment methods, carrier information, receiving transaction types, and status flags governing the processing state of the entire shipment.

Common Use Cases and Queries

This table is central to reporting and troubleshooting in the receiving process. Common use cases include analyzing receipt history by vendor, tracking open shipments, and reconciling receipt transactions. A fundamental query pattern joins RCV_SHIPMENT_HEADERS with its child table, RCV_SHIPMENT_LINES, to obtain a complete receipt view. For example, to list all receipts from a specific vendor:

• SELECT rsh.RECEIPT_NUM, rsh.SHIPMENT_HEADER_ID, rsh.VENDOR_ID, rsl.PO_LINE_ID FROM RCV_SHIPMENT_HEADERS rsh, RCV_SHIPMENT_LINES rsl WHERE rsh.SHIPMENT_HEADER_ID = rsl.SHIPMENT_HEADER_ID AND rsh.VENDOR_ID = <VENDOR_ID>;

It is also frequently joined to PO_HEADERS and PO_LINES for end-to-end procurement reporting and is a key source for custom interfaces or data extracts related to inbound logistics.

Related Objects

As indicated by the foreign key relationships, RCV_SHIPMENT_HEADERS is a pivotal hub within the receiving schema. Its most direct child is the RCV_SHIPMENT_LINES table, which holds the detailed items received. Transactional data flows to RCV_TRANSACTIONS and RCV_TRANSACTIONS_INTERFACE. It is also referenced by supply-related tables like MTL_SUPPLY and RCV_SUPPLY, linking receiving to inventory planning. The numerous references from JAI (Java Accounting Interface) tables, such as JAI_RCV_LINES and JAI_RCV_TRANSACTIONS, highlight its importance in localized tax and regulatory compliance processes, particularly for implementations in regions like India.