Search Results rcv_shipment_headers

Overview

RCV_SHIPMENT_HEADERS is the receiving hub table owned by the PO schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores shipment and receipt header information: the top-level record that groups the individual receipt lines, lot/serial transactions, and put-away activity generated when goods arrive against a purchase order, an internal requisition, or a customer return. Each row represents one shipment or receipt document, identified by SHIPMENT_HEADER_ID, and serves as the anchor for downstream receiving, inspection, delivery, and return-to-vendor processing.

The table operates at the header grain. Line-level detail resides in RCV_SHIPMENT_LINES, and every movement of material — receive, deliver, inspect, transfer, correct, or return — is captured in RCV_TRANSACTIONS. Because RCV_SHIPMENT_HEADERS sits at the intersection of supplier, ship-to organization, ship-to location, carrier, and employee data, it is a natural hub in a dimensional or Data Vault sense. The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning; modeling it as a hub on SHIPMENT_HEADER_ID, with supplier and ship-to attributes resolved through links to PO_VENDORS and PO_VENDOR_SITES_ALL, is a reasonable design suggestion.

Key Information Stored

The surrogate primary key is SHIPMENT_HEADER_ID, enforced by the RCV_SHIPMENT_HEADERS_PK constraint and also present as unique index RCV_SHIPMENT_HEADERS_U1. The business-key candidate for the table is the combination of RECEIPT_NUM and SHIP_TO_ORG_ID, enforced by RCV_SHIPMENT_HEADERS_UK01; RECEIPT_NUM is the user-visible receipt number used on receiving forms and reports. The table is documented with 91 columns, of which the following are the most operationally significant.

• SHIPMENT_HEADER_ID — surrogate primary key referenced by all child tables.
• RECEIPT_NUM and SHIPMENT_NUM — the business document numbers presented to users.
• RECEIPT_SOURCE_CODE — identifies whether the receipt originates from a purchase order, an internal requisition, or a return.
• VENDOR_ID and VENDOR_SITE_ID — the supplier and supplier site, resolved against PO_VENDORS and PO_VENDOR_SITES_ALL.
• ORGANIZATION_ID and SHIP_TO_ORG_ID — the inventory organization and destination receiving organization.
• SHIP_TO_LOCATION_ID and SHIP_FROM_LOCATION_ID — origin and destination addresses.
• SHIPPED_DATE and EXPECTED_RECEIPT_DATE — scheduled and actual shipment dates.
• BILL_OF_LADING, PACKING_SLIP, and WAYBILL_AIRBILL_NUM — transport and documentation references.
• FREIGHT_CARRIER_CODE, FREIGHT_TERMS, and FREIGHT_BILL_NUMBER — carrier and freight settlement data.
• EMPLOYEE_ID — the receiving or responsible employee.
• ASN_TYPE and ASN_STATUS — advance shipping notice classification and processing state.
• INVOICE_NUM, INVOICE_DATE, and INVOICE_AMOUNT — supplier invoice references used in receipt matching.
• CURRENCY_CODE and CONVERSION_RATE — currency context for invoice and freight amounts.
• APPROVAL_STATUS, WF_ITEM_TYPE, and WF_ITEM_KEY — workflow state for receipts requiring approval.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard extensible descriptive flexfield columns.

Common Use Cases and Queries

Typical reporting and integration scenarios include locating a receipt by number or supplier, reconciling received quantities against purchase order schedules, reporting receiving activity by organization and date, and tracing returns to vendor and RMA processing. A representative query joining the header to its supplier is shown below.

• Receipt inquiry by number: SELECT shipment_header_id, receipt_num, receipt_source_code, vendor_id, ship_to_org_id FROM rcv_shipment_headers WHERE receipt_num = :receipt_num AND ship_to_org_id = :org_id;
• Receipts by supplier and period: SELECT rsh.receipt_num, rsh.shipped_date, rsh.invoice_num FROM rcv_shipment_headers rsh WHERE rsh.vendor_id = :vendor_id AND rsh.shipped_date BETWEEN :from_date AND :to_date ORDER BY rsh.shipped_date DESC;
• Header-to-line drill-down: SELECT rsh.receipt_num, rsl.line_num, rsl.item_id, rsl.quantity_received FROM rcv_shipment_headers rsh JOIN rcv_shipment_lines rsl ON rsl.shipment_header_id = rsh.shipment_header_id WHERE rsh.receipt_num = :receipt_num;
• Transaction activity for a receipt: join RCV_TRANSACTIONS on SHIPMENT_HEADER_ID to report receive, inspect, deliver, and return transactions.
• Pending ASN processing: filter on ASN_STATUS and ASN_TYPE to identify advance shipping notices awaiting receipt confirmation.

Receiving data is also surfaced through the Receiving Open Interface, the RCV_SHIPMENT_HEADERS view layer used by purchasing and inventory forms, and standard reports such as the Receiving Transactions Summary.

Related Objects

The most significant dependent objects are those that reference RCV_SHIPMENT_HEADERS through SHIPMENT_HEADER_ID.

• RCV_SHIPMENT_LINES — line-level receipt detail; joined on SHIPMENT_HEADER_ID.
• RCV_TRANSACTIONS — all material movements against the receipt; joined on SHIPMENT_HEADER_ID.
• RCV_TRANSACTIONS_INTERFACE — inbound interface through which external receiving transactions are staged.
• RCV_SUPPLY and MTL_SUPPLY — supply records created from the receipt for availability and planning.
• PO_RCV_CHARGES — receipt-level charges such as freight and tax.
• PO_VENDORS and PO_VENDOR_SITES_ALL — supplier and supplier site master, referenced by VENDOR_ID and VENDOR_SITE_ID.
• PSB_EMPLOYEES — employee master referenced by EMPLOYEE_ID.
• JAI_* tables — the Oracle Financials for India (JAI) localization tables, including JAI_RCV_LINES, JAI_RCV_TRANSACTIONS, JAI_CMN_LINES, and JAI_AP_MATCH_INV_TAXES, each referencing SHIPMENT_HEADER_ID for excise and tax determination.