Search Results po_shipment_num




Overview
Explore in AI Chat

Overview

APPS.POS_ASN_REVIEW_SHIPMENTS_V is an Oracle E-Business Suite internal view owned by the APPS schema and registered under FND Design Data as ICX.POS_ASN_REVIEW_SHIPMENTS_V. It is classified as an internal view type, and Oracle marks it with the standard warning that it is for Oracle Internal Use Only and is not supported for direct customer access except through standard Oracle Applications programs. Functionally, it supports the Supplier Portal / iSupplier Advanced Shipment Notice (ASN) review process, presenting shipment line details from the ASN shopping cart and related purchasing documents in a denormalized, presentation-oriented form. The view surfaces purchase order context, item context, shipment logistics, receipt expectations, tax and pricing information, and invoice-quantity data in a single row per ASN line or line split, making it suitable for both interactive review pages and downstream reporting extracts that must remain independent of the underlying transactional tables.

Underlying Base Objects

The view is defined over, or references, the following documented base objects: POS_ASN_SHOP_CART_DETAILS, PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES, MTL_SYSTEM_ITEMS_KFV, MTL_TRANSACTION_REASONS, AP_TAX_CODES, FND_TERRITORIES_TL, HR_LOCATIONS, ORG_FREIGHT, and the HR_GENERAL package. POS_ASN_SHOP_CART_DETAILS acts as the driving source of ASN line and split information and supplies the SESSION_ID and SEQ_NUM session keys that group rows for a given shipment submission. PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, and PO_RELEASES supply purchase order number, line number, shipment number, due date, and ship-to context; PO_LINE_LOCATIONS is the join point for the PO_LINE_LOCATION_ID foreign key. MTL_SYSTEM_ITEMS_KFV provides concatenated item number and description, while MTL_TRANSACTION_REASONS supplies the reason name returned for returned or adjusted lines. AP_TAX_CODES and FND_TERRITORIES_TL provide tax name, rate, and country-of-origin descriptions. HR_LOCATIONS supplies ship-to location descriptions. ORG_FREIGHT provides freight carrier information, and HR_GENERAL is invoked for organizational or session attribute resolution. Because the view spans HR and financials objects in addition to purchasing tables, it is tightly bound to the standard EBS data model and to the security and MOAC policies applied by those objects.

Key Columns

The view exposes thirty-plus columns. The SESSION_ID, SEQ_NUM, ASN_LINE_ID, and ASN_LINE_SPLIT_ID columns identify the ASN session and the specific line or split being reviewed. PO_LINE_LOCATION_ID is the key used to tie the row back to the purchase order shipment; PO_NUM, PO_LINE_NUM, PO_SHIPMENT_NUM, and DUE_DATE describe that shipment, with PO_SHIPMENT_NUM being the specific attribute most users search for. Item context is provided by ITEM_NUMBER, ITEM_DESCRIPTION, and VENDOR_PRODUCT_NUM. Quantity and pricing information includes QUANTITY_SHIPPED, UNIT_OF_MEASURE, QUANTITY_INVOICED, UNIT_PRICE, EXTENDED_PRICE, VENDOR_CUM_SHIPPED_QTY, and TAXABLE_FLAG. Tax columns include TAX_NAME and TAX_RATE. Logistics and transport details include EXPECTED_RECEIPT_DATE, SHIP_TO_LOCATION, PACKING_SLIP, BARCODE_LABEL, WAYBILL_AIRBILL_NUM, BILL_OF_LADING, CONTAINER_NUM, NUM_OF_CONTAINERS, TRUCK_NUM, COUNTRY_OF_ORIGIN, and FREIGHT_CARRIER. Additional attributes are VENDOR_LOT_NUM, REASON_NAME, and COMMENTS.

Common Use Cases and Queries

Typical uses include retrieving all lines belonging to an ASN review session, validating that a shipment is associated with the correct PO shipment, and extracting shipment or tax details for reconciliation. Because the object is internal, queries should be treated as diagnostic or read-only and not embedded in custom production code. A typical lookup by purchase order shipment number is:

  • SELECT asn.po_num, asn.po_line_num, asn.po_shipment_num, asn.item_number, asn.item_description, asn.quantity_shipped, asn.unit_of_measure, asn.expected_receipt_date, asn.ship_to_location FROM apps.pos_asn_review_shipments_v asn WHERE asn.po_num = :p_po_num AND asn.po_shipment_num = :p_shipment_num ORDER BY asn.po_line_num;
  • SELECT * FROM apps.pos_asn_review_shipments_v WHERE session_id = :p_session_id ORDER BY seq_num;
  • SELECT po_num, po_shipment_num, item_number, quantity_shipped, quantity_invoiced, vendor_cum_shipped_qty FROM apps.pos_asn_review_shipments_v WHERE po_line_location_id = :p_line_location_id;

These queries are appropriate for verification and reconciliation reporting. Production integrations should rely on the corresponding supported purchasing and receiving APIs, which apply the same business rules as this internal view.