Search Results rcv_shipment_headers_v




Overview
Explore in AI Chat

Overview

RCV_SHIPMENT_HEADERS_V is an APPS-owned view in Oracle E-Business Suite that exposes the shipment header records used by the Receiving module of the Purchasing (PO) product family. It is a straightforward projection of the RCV_SHIPMENT_HEADERS base table, listed in the ETRM 12.2.2 metadata with a status of VALID and a description of "10SC ONLY - Retrofitted." The "10SC" reference indicates the view was introduced as part of the Oracle 10SC (Supply Chain) retrofit stream and is retained for backward compatibility in 12.1.1 and 12.2.2. A shipment header represents the top-level container of a receiving transaction: it carries the receipt number, shipment number, vendor and ship-to information, and the shipping details associated with an inbound delivery. Because the view preserves the column names of the underlying table without transformation, it serves as a stable, read-oriented access point for reports, interfaces, and custom extensions that need shipment header data without binding directly to the base table.

Underlying Base Objects

The view is defined over RCV_SHIPMENT_HEADERS, which the metadata records as a referenced base object via a synonym. The defining query is a simple SELECT of all columns from that table, aliased as RSH. No joins, filters, or computed expressions are applied, so the view is fully row-for-row equivalent to the base table. All DML against the base table is reflected immediately in the view. In 12.1.1 and 12.2.2, the primary Receiving flow writes through the RCV_SHIPMENT_HEADERS table directly; this view is therefore a reporting and integration convenience rather than a functional interface of the receiving API. The synonym reference in the metadata confirms that the view resolves through the standard APPS synonym layer.

Key Columns

The view exposes the complete column set of the shipment header. Notable columns include:

Common Use Cases and Queries

This view is typically used for shipment-level reporting, reconciliation between expected and actual receipts, and data extracts feeding downstream systems such as WMS or analytics. A representative query lists receipt headers for an organization within a date range:

  • SELECT rsh.receipt_num, rsh.shipment_num, rsh.receipt_source_code, rsh.vendor_id, rsh.shipped_date, rsh.expected_receipt_date FROM rcv_shipment_headers_v rsh WHERE rsh.organization_id = :org_id AND rsh.creation_date >= :from_date;

A second common pattern joins the view to shipment lines to derive header-to-line detail:

  • SELECT rsh.receipt_num, rsl.line_num, rsl.item_id, rsl.quantity_received FROM rcv_shipment_headers_v rsh, rcv_shipment_lines rsl WHERE rsh.shipment_header_id = rsl.shipment_header_id AND rsh.receipt_num = :receipt_num;

Because the view is read-only in intent (no WITH CHECK OPTION or INSTEAD OF trigger), custom code should not attempt DML through it; inserts and updates must target RCV_SHIPMENT_HEADERS or the supported Receiving APIs. The view remains valid and available in both 12.1.1 and 12.2.2, and its simplicity makes it a low-risk object for custom reporting extensions.