Search Results dropoff_postal_code

Overview

APPS.IBE_SHIP_DLVY_V is a reporting and integration view in the Oracle E-Business Suite Applications schema (APPS). It consolidates delivery header information with shipping, freight, weight, volume, carrier, and drop-off address attributes, exposing them as a single denormalized row per delivery. The view is registered as Oracle internal use only and is not supported for direct customer access except through standard Oracle Applications programs. In Oracle EBS 12.1.1 and 12.2.2 it is used within the iStore/IBE and shipping (WSH) functional areas to present delivery details for display and downstream processing.

The view is especially relevant for users searching on dropoff_address_lines_phonetic, since it exposes the ultimate drop-off address components (lines 1–3, town/city, country, postal code) alongside the delivery and carrier context. Phonetic matching against these address lines is typically performed by Oracle's fuzzy/phony search utilities rather than by the view itself, but the view provides the source address columns those utilities index.

Underlying Base Objects

The documented metadata identifies the following base objects for the view in ETRM 12.2.2:

• WSH_NEW_DELIVERIES (synonym) — the primary delivery table, supplying DELIVERY_ID, delivery name, status, freight terms, waybill, weights, volumes, ship method, carrier, pickup/drop-off dates and location IDs.
• HZ_LOCATIONS (synonym) — the Trading Community Architecture location table, providing the drop-off address lines, town/city, country and postal code.
• OE_SHIP_METHODS_V (view) — supplies ship method code and meaning.
• MTL_UNITS_OF_MEASURE_TL (synonym) — supplies the translated unit-of-measure meanings for weight and volume.
• AR_LOOKUPS, OE_LOOKUPS and WSH_LOOKUPS (views) — supply the lookup codes and UI-facing meanings for status, freight terms and related attributes.

The view therefore joins transactional delivery data to reference and lookup data plus location details, presenting pre-resolved codes and meanings for ease of consumption.

Key Columns

The view is keyed by DELIVERY_ID and organizes its columns into functional groups:

• Delivery identity: DELIVERY_ID, DELIVERY_NAME, ORGANIZATION_ID (operating unit).
• Status and terms: DLVY_STATUS_CODE / DLVY_STATUS_MEANING, FREIGHT_TERMS_CODE / FREIGHT_TERMS_MEANING.
• Logistics: WAYBILL (often the tracking number), SHIP_METHOD_CODE / SHIP_METHOD_MEANING, CARRIER_ID.
• Measures: GROSS_WEIGHT, NET_WEIGHT, WEIGHT_UOM_CODE / WEIGHT_UOM_MEANING, VOLUME, VOLUME_UOM_CODE.
• Routing: INITIAL_PICKUP_DATE and INITIAL_PICKUP_LOCATION_ID; ULTIMATE_DROPOFF_DATE and ULTIMATE_DROPOFF_LOCATION_ID.
• Drop-off address: DROPOFF_ADDRESS_LINE_1, DROPOFF_ADDRESS_LINE_2, DROPOFF_ADDRESS_LINE_3, DROPOFF_TOWN_OR_CITY, DROPOFF_COUNTRY, DROPOFF_POSTAL_CODE, and the truncated DROPOFF_ADDRESS_LINES_ column.

Common Use Cases and Queries

Typical scenarios include delivery-status reporting, shipment tracking lookups, carrier/freight analysis, and address-based delivery searches such as the dropoff_address_lines_phonetic case.

• Open deliveries for an operating unit: filter on DLVY_STATUS_CODE = 'OP' and ORGANIZATION_ID.
• Tracking by waybill or carrier: join on CARRIER_ID or search WAYBILL.
• Address search: query DROPOFF_ADDRESS_LINE_1–3, DROPOFF_TOWN_OR_CITY and DROPOFF_POSTAL_CODE.

Sample query:

SELECT delivery_id, delivery_name, dlvy_status_meaning, ship_method_meaning, waybill, ultimate_dropoff_date, dropoff_address_line_1, dropoff_town_or_city, dropoff_country FROM apps.ibe_ship_dlvy_v WHERE organization_id = :p_org AND dlvy_status_code = 'OP' ORDER BY ultimate_dropoff_date;