Search Results trailer_number




Overview
Explore in AI Chat

Overview

WSH_POD_DETAIL_V is a Shipping Execution (WSH) reporting view that exposes Proof of Delivery (POD) header-level detail together with associated carrier, shipment, and shipper address information. It consolidates data captured on a bill of lading or waybill — including signatures (shipper, carrier, and POD recipient), dates, port references, Incoterms, and tracking numbers — and joins that data to delivery and trading-partner attributes.

The view is documented as part of the ETRM metadata repository but is not implemented in the database referenced by that metadata. It is a read-only presentation object, intended for use in reporting layers, DBI/BI Publisher templates, and integration extracts where a flat, human-readable POD record is required. Because the view aliases cryptic base columns into business-friendly names (for example, WDI.BOL_NOTIFY_PARTY is exposed as NOTIFY_PARTY), it simplifies query construction for developers who are not familiar with the underlying WSH schema.

Underlying Base Objects

The ETRM metadata records no formally documented referenced base objects. The view text, however, reveals the aliases used in its definition, which map to the following underlying entities:

The view therefore sits above several WSH transactional tables joined to HR and organization reference data, producing one consolidated POD row per document instance.

Key Columns

Common Use Cases and Queries

Typical uses include POD audit reporting, carrier performance analysis keyed on supplier or carrier, and extracting signed POD detail for downstream freight settlement. Because SUPPLIER_CODE is a first-class column, a frequent retrieval pattern filters POD records by trading partner:

  • List all POD documents for a given supplier code.
  • Reconcile delivery waybills against carrier tracking numbers.
  • Produce printable POD certificates showing shipper address and signature detail.

Illustrative SQL:

  • SELECT bill_of_lading_number, supplier_code, delivery_id, carrier_tracking_number, export_carrier, pod_signed_by, pod_signed_date FROM wsh_pod_detail_v WHERE supplier_code = :p_supplier_code;
  • SELECT delivery_id, incoterms, port_of_loading, port_of_discharge, shipper_name, shipper_address FROM wsh_pod_detail_v WHERE pod_signed_date IS NOT NULL ORDER BY pod_signed_date DESC;

Because the view is documented as not implemented in the reference database, availability should be verified in the target instance (12.1.1 or 12.2.2) before use, and the actual column list should be confirmed against the shipped view definition.