Search Results hazard_code




Overview
Explore in AI Chat

Overview

POS_HEADERS_V is an APPS-owned view in the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, defined within the iSupplier Portal (POS) product family. The view is used to select header-level information for Advance Shipment Notices (ASNs) created through the iSupplier Portal and related receiving flows. In practice, it provides a consolidated, read-oriented projection of shipment header data that bridges supplier-entered ASN content with the Receiving Open Interface (RCV) structures and the underlying purchasing and payables reference data.

Because it draws from interface and reference objects rather than a single transactional table, POS_HEADERS_V functions as a reporting and integration convenience view. It exposes shipment header attributes alongside vendor details, shipping locations, payment terms, currency, freight, weight, hazard, and invoicing information, thereby allowing downstream pages, reports, and interfaces to retrieve ASN header data without repeatedly writing multi-table joins. The presence of AP_TERMS_VL among its referenced base objects reflects the documented user search context of "ap_terms_vl": payment terms names surfaced in the view are sourced from the payables terms view.

Underlying Base Objects

The documented base objects underlying POS_HEADERS_V are:

The view text shows a UNION of branches. The first branch joins RCV_HEADERS_INTERFACE to RCV_TRANSACTIONS_INTERFACE, with outer joins to HR_LOCATIONS_ALL_TL and HZ_LOCATIONS, and computes LOCATION_CODE using location code or a concatenation of address1 and city. The second branch sources equivalent header data from the shipment header structures and derives PAYMENT_TERMS_NAME from the terms view (AP.NAME), confirming the AP_TERMS_VL dependency. Both branches align the same column list so the union is consistent.

Key Columns

Common Use Cases and Queries

Typical scenarios include supplier ASN inquiry, receiving interface validation, and reporting on inbound shipments prior to receipt creation. A common query retrieves shipment header and vendor context for a given supplier:

  • SELECT shipment_num, shipped_date, expected_receipt_date, vendor_name, vendor_site_code, payment_terms_name, currency_code FROM apps.pos_headers_v WHERE vendor_id = :p_vendor_id;
  • SELECT shipment_num, invoice_num, total_invoice_amount, invoice_status_code FROM apps.pos_headers_v WHERE invoice_status_code IS NOT NULL ORDER BY shipped_date DESC;
  • SELECT shipment_num, location_code, ship_to_organization_code, gross_weight, gross_weight_uom_code FROM apps.pos_headers_v WHERE header_id = :p_header_id;

Because the view depends on interface tables and a union of branches, queries should be filtered by shipment number, header interface ID, or vendor to avoid scanning unnecessary rows. The view is read-only; it does not support DML. When reconciling payment terms in ASN output, note that PAYMENT_TERMS_NAME originates from AP_TERMS_VL, so any change to payables terms definitions will be reflected in subsequent query results.