Search Results cancellation_status




Overview
Explore in AI Chat

Overview

APPS.POS_VIEW_ASN is a reporting and integration view in Oracle E-Business Suite (available in both 12.1.1 and 12.2.2) that consolidates Advance Shipment Notice (ASN) information from two distinct sources: shipment data still residing in the receiving interface tables, and shipment data that has already been processed into the permanent receiving tables. The view presents a unified, DISTINCT result set of ASN header-level attributes, allowing downstream consumers to query pending and confirmed shipments through a single object.

Because the view unions data from RCV_HEADERS_INTERFACE/RCV_TRANSACTIONS_INTERFACE with RCV_SHIPMENT_HEADERS/RCV_SHIPMENT_LINES, it is particularly useful in supplier collaboration, iSupplier, and inbound logistics reporting where both staged and completed ASN records must be visible. It is owned by APPS and sits at the boundary between the open interface and the transactional receiving model.

Underlying Base Objects

The documented base objects underlying the view are AP_INVOICES_ALL, FND_GLOBAL, HZ_PARTY_SITES, PO_VENDORS, PO_VENDOR_SITES_ALL, RCV_HEADERS_INTERFACE, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS_INTERFACE. The first SELECT joins RCV_HEADERS_INTERFACE to RCV_TRANSACTIONS_INTERFACE on HEADER_INTERFACE_ID, and outer-joins PO_VENDORS, PO_VENDOR_SITES_ALL, and HZ_PARTY_SITES to enrich vendor and location detail. This branch filters to ASN_TYPE in ('ASN','ASBN') and excludes rows where TRANSACTION_TYPE = 'CANCEL'.

The second SELECT joins RCV_SHIPMENT_HEADERS to RCV_SHIPMENT_LINES and AP_INVOICES_ALL, again with outer joins to the vendor and party site views. Both branches are combined with UNION ALL and projected through SELECT DISTINCT to suppress duplicates. Note that CANCELLATION_STATUS and PROCESSING_STATUS are hard-coded as empty strings (''), and PAYMENT_STATUS_FLAG is supplied as NULL in the interface branch and from AP_INVOICES_ALL in the shipment branch.

Key Columns

Regarding the searched term "cancellation_status": the column exists in the projection but is returned as an empty string in both branches. Users seeking cancellation state must rely on the TRANSACTION_TYPE filter rather than on this column.

Common Use Cases and Queries

Typical scenarios include ASN tracking dashboards, supplier collaboration extracts, and reconciliation of inbound receipts. A representative query:

  • SELECT shipment_num, vendor_name, shipped_date, expected_receipt_date, payment_status_flag FROM apps.pos_view_asn WHERE expected_receipt_date >= SYSDATE;
  • SELECT shipment_num, location_code, num_of_containers FROM apps.pos_view_asn WHERE vendor_number = :vendor;
  • SELECT shipment_num FROM apps.pos_view_asn WHERE cancellation_status IS NULL; — noting cancellation_status is always blank, so filter on the underlying interface logic instead.

The view is read-only and should be used for reporting or integration extraction rather than for updates, since CANCELLATION_STATUS and PROCESSING_STATUS are non-persistent computed placeholders.