Search Results deliver_to_location_code

Overview

WSH_DEL_DTL_ASSGN_V is a Shipping Execution (WSH) view owned by the APPS schema. It is a denormalized, read-only join that simultaneously exposes both delivery-assignment interface data and delivery-detail interface data within a single flattened structure. In Oracle EBS 12.1.1 and 12.2.2 this view is primarily used during the inbound shipping interface cycle, where external systems or staged flat-file loaders populate the interface tables before the Shipping Execution concurrent programs (such as the Delivery Interface or Ship Confirm Interface) validate and transfer the records into the operational delivery tables.

The view answers the question of which delivery-detail interface rows belong to which delivery-assignment interface row, and enriches each line with the full set of shipment, address, quantity, weight, volume, and descriptive-flexfield attributes stored on the detail interface record. For users searching on deliver_to_location_code, the view is relevant because the deliver-to address handling is carried on the detail interface side through DELIVER_TO_LOCATION_ID; the corresponding descriptive code is normally resolved by joining to the location table hierarchy, not stored directly in this view.

Underlying Base Objects

The ETRM documentation identifies two referenced base objects, both exposed as synonyms:

• WSH_DEL_ASSGN_INTERFACE (SYNONYM) — supplies the delivery-assignment level identifier, aliased in the view text as WDA.DELIVERY_INTERFACE_ID.
• WSH_DEL_DETAILS_INTERFACE (SYNONYM) — supplies the delivery-detail level identifier and the bulk of attribute columns, aliased as WDD.

The view is defined as a join between these two interface entities: the assignment record provides the delivery grouping key (DELIVERY_INTERFACE_ID), while the detail record provides the line-level content (DELIVERY_DETAIL_INTERFACE_ID, DELIVERY_DETAIL_ID, and all shipment attributes). Because it is a view over interface tables, it is transient by nature — records exist only during active interface processing and are purged or archived after the Shipping Execution interface programs consume them.

Key Columns

• DELIVERY_INTERFACE_ID — delivery-assignment interface identifier; the parent grouping key.
• DELIVERY_DETAIL_INTERFACE_ID / DELIVERY_DETAIL_ID — detail interface row identifier and target delivery detail identifier.
• SOURCE_CODE, SOURCE_HEADER_ID, SOURCE_LINE_ID — originating order or source document that generated the line.
• SHIP_FROM_LOCATION_ID, SHIP_TO_LOCATION_ID, DELIVER_TO_LOCATION_ID, INTMED_SHIP_TO_LOCATION_ID — the four address/location roles; DELIVER_TO_LOCATION_ID is the technical anchor for the "deliver to location code" search.
• CUSTOMER_ID, SOLD_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, DELIVER_TO_CONTACT_ID, INTMED_SHIP_TO_CONTACT_ID — party and contact context.
• INVENTORY_ITEM_ID, ITEM_DESCRIPTION, REVISION, LOT_NUMBER, SERIAL_NUMBER, COUNTRY_OF_ORIGIN — item and lot/serial identity.
• REQUESTED_QUANTITY, SHIPPED_QUANTITY, DELIVERED_QUANTITY, CANCELLED_QUANTITY, REQUESTED_QUANTITY_UOM, SHIPPING_QUANTITY_UOM — quantity measures and units.
• DATE_REQUESTED, DATE_SCHEDULED, SHIP_METHOD_CODE, CARRIER_ID, FREIGHT_TERMS_CODE, FOB_CODE, SHIPMENT_PRIORITY_CODE — scheduling and transportation attributes.
• GROSS_WEIGHT, NET_WEIGHT, WEIGHT_UOM_CODE, VOLUME, VOLUME_UOM_CODE — weight and volume measures.
• ATTRIBUTE1–15 / ATTRIBUTE_CATEGORY and TP_ATTRIBUTE1–15 / TP_ATTRIBUTE_CATEGORY — descriptive and trading-partner flexfield segments.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID — audit and concurrent-program context.

Common Use Cases and Queries

The principal use case is troubleshooting and validating staged interface records prior to running the Delivery Interface. Users typically query the view to confirm that detail records are correctly parented to an assignment, and to resolve the deliver-to location identifier.

SELECT v.delivery_interface_id,
       v.delivery_detail_interface_id,
       v.deliver_to_location_id,
       v.ship_to_location_id,
       v.inventory_item_id,
       v.requested_quantity,
       v.date_scheduled
FROM   apps.wsh_del_dtl_assgn_v v
WHERE  v.delivery_interface_id = :p_delivery_interface_id;

To translate DELIVER_TO_LOCATION_ID into the human-readable deliver-to location code, join the location tables:

SELECT v.delivery_detail_interface_id,
       v.deliver_to_location_id,
       h.location_code
FROM   apps.wsh_del_dtl_assgn_v v,
       apps.hr_locations_all    h
WHERE  v.deliver_to_location_id = h.location_id;

Additional scenarios include detecting staging rows with missing or invalid location identifiers before interface submission, reconciling requested versus scheduled quantities, and auditing trading-partner descriptive flexfield values carried on the detail interface record.