Search Results po_shipment_num

Overview

The POS_ASN_REVIEW_SHIPMENTS_V view is an Oracle iProcurement (ICX) reporting object owned by the APPS schema. It presents Advance Shipment Notice (ASN) line details submitted by suppliers through the iProcurement supplier portal, enriching each shipment line with purchasing, receiving, tax, freight, and location context. Its primary role is to support the "Review ASN" pages and related reporting flows where buyers and administrators inspect shipment notices prior to receipt.

The view is central to any inquiry that must reconcile an ASN line against its originating purchase order shipment. In particular, it exposes the purchase order shipment number through the PLL.SHIPMENT_NUM column, derived from PO_LINE_LOCATIONS. This makes the view directly relevant to searches involving po_shipment_num, since it bridges the ASN shop cart data and the PO shipment numbering scheme. The object's status is VALID and it is documented for both 12.1.1 and 12.2.2 releases, with the 12.2.2 metadata confirming the same APPS ownership and base object set.

Underlying Base Objects

The view is defined over eleven documented base objects. The driving table is POS_ASN_SHOP_CART_DETAILS (aliased ASND), which holds the supplier-entered ASN lines. It is joined to the purchasing tables PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, and, through an outer join, PO_RELEASES. The join keys are PO_LINE_LOCATION_ID and PO_HEADER_ID/PO_LINE_ID, linking each ASN line to its PO shipment.

• MTL_SYSTEM_ITEMS_KFV (outer) supplies concatenated item segments.
• ORG_FREIGHT, HR_LOCATIONS, and FND_TERRITORIES_TL provide freight carrier, ship-to location, and country-of-origin descriptions.
• MTL_TRANSACTION_REASONS and AP_TAX_CODES (both outer) resolve reason names and tax codes.
• HR_GENERAL is referenced as a package, likely for language or user-environment resolution used in the territory join predicate.

Most secondary joins are outer joins (denoted by (+)), ensuring ASN lines remain visible even when freight, reason, tax, or territory data is absent.

Key Columns

• ASN_LINE_ID / ASN_LINE_SPLIT_ID — identifiers for the ASN line; a concatenated display key is also produced.
• PO_LINE_LOCATION_ID — the join to the PO shipment; the view surfaces SHIPMENT_NUM from PO_LINE_LOCATIONS, directly answering a po_shipment_num query.
• QUANTITY_SHIPPED, UNIT_OF_MEASURE, EXPECTED_RECEIPT_DATE, VENDOR_CUM_SHIPPED_QTY, QUANTITY_INVOICED — shipment and cumulative quantities.
• LINE_NUM, release number, and the concatenated PO number present purchasing context.
• CONCATENATED_SEGMENTS, ITEM_DESCRIPTION, VENDOR_PRODUCT_NUM — item identification.
• Logistics columns: PACKING_SLIP, WAYBILL_AIRBILL_NUM, BILL_OF_LADING, CONTAINER_NUM, TRUCK_NUM, NUM_OF_CONTAINERS.
• Tax columns: TAXABLE_FLAG, NAME, TAX_RATE; plus NOTICE_UNIT_PRICE and an extended amount.

Common Use Cases and Queries

Typical scenarios include buyer review of incoming ASNs, shipment reconciliation to PO shipments, and freight/tax auditing. A representative query retrieving shipment number and shipped quantity is:

SELECT asn_line_id, shipment_num, po_line_location_id,
       quantity_shipped, expected_receipt_date
FROM   apps.pos_asn_review_shipments_v
WHERE  shipment_num = :po_shipment_num;

The view may also be aggregated for shipment receipt summaries or joined back to purchasing tables for reconciliation reports.