Search Results pos_asn_headers_v




Overview
Explore in AI Chat

Overview

The view APPS.POS_ASN_HEADERS_V is a reporting construct within the Oracle iProcurement module (product code ICX) in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the header-level attributes of Advance Shipment Notices (ASNs) that originate from the iProcurement shop cart flow, joining supplier, freight, currency, weight, and shipping detail into a single denormalized projection. Its principal role is to support iProcurement receiving and shipment-tracking pages, allowing internal users to review inbound shipment headers describing what a supplier has dispatched before the corresponding goods are physically received. Because it encapsulates numerous foreign-key resolutions (vendor name, vendor site code, unit-of-measure descriptions, freight terms) and applies canonical-number conversions through FND_NUMBER, it is well suited for both page-level display and ad hoc reporting against shipment header data. The view carries a status of VALID in the APPS schema.

Underlying Base Objects

The view is defined primarily over the synonym POS_ASN_SHOP_CART_HEADERS (aliased ASNH), which supplies the shipment header rows. It outer-joins and inner-joins a wide set of supporting objects: PO_VENDORS and PO_VENDOR_SITES for supplier identity; AP_TERMS_VAL_V for payment terms, resolved via the package function POS_HEADER_INFO_S.GETPAYMENTTERMS; MTL_UNITS_OF_MEASURE (joined three times) for gross, net, and tare weight UOM descriptions; PO_LOOKUP_CODES for freight terms; ORG_FREIGHT for carrier description; and the HR organization and location objects (HR_ORG_UNITS_NO_JOIN, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS) for the ship-to organization and location details. Utility packages FND_DATE, FND_NUMBER, FND_GLOBAL, HR_GENERAL, and HR_SECURITY are referenced for date formatting, canonical number conversion, and security context.

Key Columns

Prominent columns include VENDOR_NAME, VENDOR_SITE_CODE, and LOCATION_CODE for supplier and origin information; SHIPMENT_NUM, BILL_OF_LADING, and WAYBILL_AIRBILL_NUM as shipment identifiers; and SHIP_DATE, EXPECTED_RECEIPT_DATE, and INVOICE_DATE for scheduling, with dates defaulted via FND_DATE.DATE_TO_CHARDATE(SYSDATE) when null. Weight and container metrics — NUM_OF_CONTAINERS, GROSS_WEIGHT, NET_WEIGHT, and TAR_WEIGHT — are converted with FND_NUMBER.NUMBER_TO_CANONICAL and paired with their UOM descriptions. Notably, SPECIAL_HANDLING_CODE is exposed directly from the base header table to convey handling instructions such as hazardous or fragile designations. Freight-related attributes include FREIGHT_CARRIER_CODE, FREIGHT_TERMS (via the lookup display field), CARRIER_EQUIPMENT, CARRIER_METHOD, and FREIGHT_BILL_NUMBER, alongside financial columns CURRENCY_CODE, TOTAL_INVOICE_AMOUNT, TAX_AMOUNT, and SESSION_ID.

Common Use Cases and Queries

Typical usage centers on inbound shipment visibility and receipt preparation. A query filtered by SPECIAL_HANDLING_CODE supports compliance and warehouse routing, while joins to organization columns isolate shipments for a specific ship-to location.

  • Retrieve shipment headers by carrier: SELECT shipment_num, vendor_name, expected_receipt_date FROM pos_asn_headers_v WHERE freight_carrier_code = :carrier;
  • Identify special-handling shipments: SELECT shipment_num, vendor_name, special_handling_code FROM pos_asn_headers_v WHERE special_handling_code IS NOT NULL;
  • Reconcile invoice detail: SELECT shipment_num, invoice_num, total_invoice_amount, tax_amount FROM pos_asn_headers_v WHERE session_id = :session_id;

These queries are read-only and rely on the view's inherent joins for descriptive enrichment.