Search Results packaging_code




Overview
Explore in AI Chat

Overview

POR_RCV_SHIP_DISP_HEADERS_V is an Oracle E-Business Suite (EBS) database view owned by the APPS schema and assigned to the ICX — Oracle iProcurement product. It is a display-oriented view whose purpose is to retrieve shipment header level information for rendering the Shipment Details page within iProcurement. In EBS 12.1.1 and 12.2.2, the view serves as a reporting and presentation layer that joins receiving shipment data to either requisition lines or purchasing document line locations, allowing the Shipment Details page to distinguish between shipments originating from requisitions and those originating from purchase orders.

The view is defined as a UNION ALL of two branches. The first branch associates RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES with PO_REQUISITION_LINES and returns the literal ORDER_TYPE value 'REQ', exposing the requisition line identifier as LINE_ID. The second branch associates the same receiving tables with PO_LINE_LOCATIONS and returns the literal ORDER_TYPE value 'PO', exposing the line location identifier as LINE_ID, while restricting rows with the predicate RSH.ASN_TYPE IS NOT NULL. This UNION ALL structure enables a single query surface to service both requisition-sourced and order-sourced shipment headers.

Underlying Base Objects

The documented base objects referenced by the view include PO_CLM_INTG_GRP (a package), PO_LINE_LOCATIONS_TRX_V (a view), and the synonyms PO_REQUISITION_LINES, RCV_SHIPMENT_HEADERS, and RCV_SHIPMENT_LINES. The core data is drawn from the receiving tables RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES, which hold shipment header and line attributes respectively. The requisition branch reaches PO_REQUISITION_LINES through the REQUISITION_LINE_ID on RCV_SHIPMENT_LINES, while the purchasing branch reaches the PO_LINE_LOCATIONS structure through the PO_LINE_LOCATION_ID on RCV_SHIPMENT_LINES. PO_LINE_LOCATIONS_TRX_V and the PO_CLM_INTG_GRP package participate in the purchasing-side access path. Because the view sits over these base objects, its output reflects the transactional shipment and receiving data maintained by Oracle Purchasing and Oracle Receiving.

Key Columns

  • SHIPPED_DATE — the date the shipment was dispatched.
  • EXPECTED_RECEIPT_DATE — the date the shipment is anticipated at the destination.
  • FREIGHT_TERMS — the freight terms governing the shipment.
  • FREIGHT_CARRIER_CODE — the carrier responsible for transporting the shipment.
  • NUM_OF_CONTAINERS — the number of containers in the shipment.
  • WAYBILL_AIRBILL_NUM — the waybill or airbill number identifying the shipment.
  • PACKAGING_CODE — the packaging classification associated with the shipment header; this is the column relevant to the search term "packaging_code" and is sourced directly from RCV_SHIPMENT_HEADERS.
  • SHIPMENT_NUM — the shipment number.
  • SHIPMENT_HEADER_ID (documented as SHIP_HEADER_ID) — the unique identifier of the shipment header.
  • ORDER_TYPE — a literal discriminator returning 'REQ' or 'PO' to indicate the document source.
  • LINE_ID — the requisition line identifier for REQ rows, or the line location identifier for PO rows.

Common Use Cases and Queries

The view is primarily consumed by the iProcurement Shipment Details page, but it is equally useful for ad hoc reporting, data extracts, and diagnostics of shipment header attributes. A representative query retrieving header details for a given shipment is:

SELECT SHIPMENT_NUM, SHIPPED_DATE, EXPECTED_RECEIPT_DATE, FREIGHT_CARRIER_CODE, PACKAGING_CODE, ORDER_TYPE, LINE_ID FROM APPS.POR_RCV_SHIP_DISP_HEADERS_V WHERE SHIPMENT_HEADER_ID = :p_header_id;

To examine packaging information specifically, filter on PACKAGING_CODE to report shipments by packaging classification. To isolate shipments originating from purchase orders rather than requisitions, restrict the query with ORDER_TYPE = 'PO'. Joining the view back to PO_REQUISITION_LINES or PO_LINE_LOCATIONS on LINE_ID connects shipment header attributes to their originating documents, supporting reconciliation between receiving activity and demand or procurement records across EBS 12.1.1 and 12.2.2.