Search Results pos_view_asn




Overview
Explore in AI Chat

Overview

POS_VIEW_ASN is a database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the POS product family, commonly known as iSupplier Portal, and its documented purpose is to display Advance Shipment Notices (ASNs) within the buyer's system. The view consolidates shipment header and interface information so that buyers, receiving personnel, and procurement users can review inbound shipment notifications submitted by suppliers through iSupplier Portal without querying the underlying interface and transaction tables directly.

Because ASN data originates from supplier-facing portal activity, the view serves as a reporting and integration layer. It presents supplier, vendor site, freight, weight, and shipment identification attributes in a single denormalized result set. The view combines data from live shipment header records and staging interface records, allowing buyers to see both confirmed shipments and those still flowing through the receiving interface. This dual sourcing makes the view useful for monitoring ASN activity across the procurement and receiving lifecycle.

Underlying Base Objects

The documented view metadata for release 12.2.2 lists the following referenced objects: AP_INVOICES_ALL (synonym), FND_GLOBAL (package), HZ_PARTY_SITES (synonym), PO_VENDORS (view), PO_VENDOR_SITES_ALL (view), RCV_HEADERS_INTERFACE (synonym), RCV_SHIPMENT_HEADERS (synonym), RCV_SHIPMENT_LINES (synonym), and RCV_TRANSACTIONS_INTERFACE (synonym).

The view text confirms that the primary shipment data is drawn first from RCV_HEADERS_INTERFACE joined to RCV_TRANSACTIONS_INTERFACE, and then via a UNION ALL from RCV_SHIPMENT_HEADERS. Vendor information is supplied through PO_VENDORS and PO_VENDOR_SITES_ALL, while shipment location details are resolved through HZ_PARTY_SITES. AP_INVOICES_ALL is referenced for invoice-related linkage, and FND_GLOBAL typically supplies session context such as the current user or organization. The UNION ALL structure explains why the view surfaces ASN records regardless of whether they remain in the interface tables or have already posted to the shipment tables.

Key Columns

Common Use Cases and Queries

The view is typically queried to list inbound ASNs for a buyer organization, to reconcile supplier submissions against expected receipts, and to feed custom reports or integrations requiring shipment notice data. A basic query retrieving recent shipments follows:

  • SELECT shipment_num, shipped_date, expected_receipt_date, vendor_name, vendor_site_code, processing_status FROM apps.pos_view_asn WHERE shipped_date >= SYSDATE - 30;
  • SELECT shipment_num, waybill_airbill_num, freight_carrier_code, num_of_containers FROM apps.pos_view_asn WHERE vendor_number = :vendor_num;
  • SELECT header_id, shipment_num, invoice_num, payment_status_flag FROM apps.pos_view_asn WHERE shipment_num = :shipment_num;

Users searching for "processing_status" should note that the column exists in the view but is defined as a literal empty string in this definition. It therefore does not carry meaningful runtime values and should not be relied upon for status filtering or workflow logic in this version of the view.