Search Results container_num




Overview
Explore in AI Chat

Overview

The APPS.POR_RCV_SHIP_DISP_LINES_V view is a reporting construct within the Oracle iProcurement (ICX) product module of Oracle E-Business Suite. Its documented purpose is to supply the shipment line level information rendered on the Shipment Details page, aggregating receiving shipment data against both requisition and purchasing sources so that a single, uniform result set can be presented to the iProcurement user. The view is owned by the APPS schema and carries a VALID status in the ETRM 12.2.2 dictionary. Because it presents receipt-side shipment lines alongside their originating demand documents, it functions as a lightweight integration and reporting layer rather than as a transactional entity; no data is written back through it, and all columns are derived from existing base objects. The UNION ALL structure is significant: it allows requisition-sourced and purchase-order-sourced shipment lines to coexist in one shape, distinguished by an ORG/order-type discriminator column, which is essential for downstream pages that must display shipments regardless of their procurement origin. The user search term "container_num" resolves directly to a column exposed by this view, confirming that container-level packing detail is a first-class attribute of the shipment line display.

Underlying Base Objects

Per the ETRM metadata, the view is defined over several documented base objects. RCV_SHIPMENT_LINES is the central source, supplying the shipment line facts such as quantity shipped, packing slip, and container number. PO_REQUISITION_LINES and PO_HEADERS, PO_LINES_TRX_V, and PO_LINE_LOCATIONS_TRX_V provide the requisition and purchase-order context, while HR_LOCATIONS_ALL_TL and FND_TERRITORIES_VL furnish descriptive location and territory lookups. Two PL/SQL packages, PO_INQ_SV and PO_CLM_INTG_GRP, are referenced, the former being invoked in the select list to resolve the sales or order number via GET_SO_NUMBER. The UNION ALL arms join RCV_SHIPMENT_LINES either to PO_REQUISITION_LINES through REQUISITION_LINE_ID, or to PO_LINE_LOCATIONS_TRX_V through PO_LINE_LOCATION_ID with further joins to PO_LINES_TRX_V and PO_HEADERS. Outer joins to the HR and FND lookup views are applied so that missing location or country data does not suppress a shipment line, and the HR_LOCATIONS_ALL_TL join is additionally constrained by the session language.

Key Columns

  • LINE_NUM — the shipment line number from the receiving record.
  • SHIP_HEADER_ID — identifier of the parent shipment header, linking display lines to the shipment.
  • ORDER_NUMBER — the requisition or purchase-order document number, resolved per union arm.
  • ITEM_DESCRIPTION — item description drawn from the requisition or PO line.
  • SUPPLIER_ITEM_NUMBER — suggested vendor product code or vendor product number.
  • SHIP_TO_LOCATION — location code from HR_LOCATIONS_ALL_TL.
  • QUANTITY_SHIPPED — received/shipped quantity on the line.
  • PACKING_SLIP — packing slip reference captured at receipt.
  • CONTAINER_NUM — the container number associated with the shipment line, the attribute most commonly queried in this context.
  • COUNTRY_OF_ORIGIN_CODE — territory description resolved via FND_TERRITORIES_VL.
  • COMMENTS — free-text shipment line comments.
  • ORDER_TYPE — literal discriminator, 'REQ' or 'PO', identifying the sourcing document class.
  • LINE_ID — requisition line identifier or PO line location identifier, depending on ORDER_TYPE.

Common Use Cases and Queries

Typical usage centers on shipment detail reporting, container-level receipt tracking, and reconciliation between received quantities and their originating demand. A representative query retrieving container detail for a shipment is:

  • SELECT line_num, order_type, order_number, container_num, quantity_shipped FROM apps.por_rcv_ship_disp_lines_v WHERE ship_header_id = :p_header_id ORDER BY line_num;
  • SELECT container_num, packing_slip, item_description, quantity_shipped FROM apps.por_rcv_ship_disp_lines_v WHERE order_type = 'PO' AND container_num IS NOT NULL;

Because ORDER_TYPE isolates requisition from purchase-order rows, analysts can filter to a specific procurement path, while the CONTAINER_NUM and PACKING_SLIP columns support warehouse and logistics verification tasks. The view should be treated as read-only reference data; filters on SHIP_HEADER_ID are recommended to limit result sets in high-volume environments.