Search Results freight_terms_meaning




Overview
Explore in AI Chat

Overview

The IBE_SHIP_DLVY_V view is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema and associated with the IBE – iStore product family. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, the view "Stores information about Delivery header." In practice, it functions as a reporting and integration façade over the shipping delivery tables managed by Oracle Shipping Execution (WSH), presenting one consolidated row per delivery header enriched with decoded lookup meanings and a denormalized dropoff address. Because iStore and other fulfillment-facing modules require read-optimized access to delivery attributes without navigating the full Shipping Execution data model, this view centralizes the most frequently referenced delivery columns—identifiers, status, freight and shipping method descriptions, weights, volumes, carrier, and pickup/dropoff details—behind a single queryable object.

The view is especially relevant to searches involving INITIAL_PICKUP_LOCATION_ID, since it exposes that column directly from the underlying delivery header, alongside the corresponding pickup and dropoff date fields and the destination address components. This makes it a convenient source when tracing a delivery from its initial pickup point through to its ultimate dropoff location.

Underlying Base Objects

The documented base objects referenced by the view are:

  • WSH_NEW_DELIVERIES (synonym) — the delivery header table, the primary source of delivery-level attributes.
  • WSH_LOOKUPS (view) — provides lookup meanings for the delivery status code.
  • OE_LOOKUPS (view) — provides freight terms and shipping method lookup meanings, joined with outer joins ((+)) so deliveries lacking those codes are still returned.
  • OE_SHIP_METHODS_V (view) — source of the shipping method description.
  • HZ_LOCATIONS (synonym) — supplies the dropoff address detail via ULTIMATE_DROPOFF_LOCATION_ID.
  • MTL_UNITS_OF_MEASURE_TL (synonym) — resolves the weight unit of measure description, language-filtered through USERENV('LANG').
  • AR_LOOKUPS (view) — an additional documented dependency in the underlying object list.

The joins link delivery status to DELIVERY_STATUS, freight terms to FREIGHT_TERMS, and shipping method to SHIP_METHOD lookup types, while the location and UOM joins operate on location ID and UOM code respectively.

Key Columns

The view exposes columns drawn from each base object, including:

Common Use Cases and Queries

Typical scenarios include validating iStore shipment visibility, reconciling delivery weights and volumes against carrier waybills, verifying pickup-to-dropoff routing, and embedding delivery details in fulfillment dashboards. The INITIAL_PICKUP_LOCATION_ID column is commonly queried to trace shipments originating from a specific location.

Sample query returning delivery headers for a given pickup location:

  • SELECT delivery_id, delivery_name, dlvy_status_meaning, initial_pickup_date, initial_pickup_location_id, ultimate_dropoff_location_id, dropoff_town_or_city, dropoff_country FROM apps.ibe_ship_dlvy_v WHERE initial_pickup_location_id = :pickup_location_id ORDER BY initial_pickup_date DESC;

Sample query summarizing carrier volume:

  • SELECT carrier_id, ship_method_meaning, COUNT(*) delivery_count, SUM(gross_weight) total_weight FROM apps.ibe_ship_dlvy_v WHERE dlvy_status_code = 'CONFIRMED' GROUP BY carrier_id, ship_method_meaning;

Because the view filters the UOM description by USERENV('LANG'), results are returned in the session language, which should be considered when running multilingual reports or integrations.