Search Results asn_seq_number

Overview

WSHBV_DELIVERY is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite, residing in the Order Entry (OE) product family. Its ETRM description carries the annotation "Retrofitted," indicating that the object was recreated to preserve the interface expected by downstream components, reports, or customizations following a change in the underlying data model. The view exposes delivery header information sourced from the WSH_DELIVERIES table and carries the standard "BV" suffix convention used for such compatibility objects in the Oracle Shipping (WSH) module.

The view presents one row per delivery, including delivery identifiers, status, shipping destination identifiers, weight and volume attributes, carrier and freight terms, and ASN-related state. Its principal role is to provide a stable query surface for delivery-level reporting and integration, so that dependent code does not need to be rewritten when internal table structures evolve. Because it selects directly from WSH_DELIVERIES without joins or filters, the view is a straightforward projection rather than a denormalized reporting structure.

Underlying Base Objects

The view is defined over a single documented base object: WSH_DELIVERIES, referenced through a synonym. The defining query aliases the base table as DEL and projects a fixed list of columns. No aggregation, filtering, or additional joins appear in the view text, so cardinality and data volume match the underlying delivery table exactly. This one-to-one relationship means that any row-level security or organization-level filtering applied at query time must be supplied by the calling application or report, not by the view itself.

The alias mapping also indicates lineage renaming: PLANNED_DEPARTURE_ID is exposed as DPW_DEPARTURE_ID, and ACTUAL_DEPARTURE_ID is exposed as SC_DEPARTURE_ID, reflecting terminology from the earlier Departure Planning Workbench and Shipping Confirm contexts. The remainder of the columns retain their base table names.

Key Columns

• DELIVERY_ID / DELIVERY_NAME — Primary identifier and user-facing delivery number. DELIVERY_ID is the join key to delivery detail (WSH_DELIVERY_DETAILS) and to delivery assignment records.
• ORGANIZATION_ID — Inventory organization that owns the delivery; essential for multi-org query filtering.
• STATUS_CODE and SOURCE_CODE — Current delivery status (for example, open, staged, confirmed, or closed) and the origin of the delivery.
• ASN_SEQ_NUMBER — Sequence number associated with the advance ship notice, used to order or distinguish ASN transmissions for the delivery.
• ASN_DATE_SENT — Timestamp indicating when the ASN was transmitted; combined with ASN_SEQ_NUMBER, it supports ASN audit and reconciliation reporting.
• CUSTOMER_ID, ULTIMATE_SHIP_TO_ID, INTERMEDIATE_SHIP_TO_ID, POOLED_SHIP_TO_ID — Ship-to hierarchy identifiers used in order and shipping analytics.
• WAYBILL, FREIGHT_CARRIER_CODE, FREIGHT_TERMS_CODE, FOB_CODE, CURRENCY_CODE — Transportation and commercial attributes captured against the delivery.
• GROSS_WEIGHT / WEIGHT_UOM_CODE, VOLUME / VOLUME_UOM_CODE — Physical shipment measures with their units of measure.
• DATE_CLOSED, SEQUENCE_NUMBER, LOADING_ORDER_FLAG — Closure date, ordering sequence, and load sequencing indicator.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID support change tracking and concurrent program traceability.

Common Use Cases and Queries

The view is typically used for delivery status reporting, ASN tracking, and freight analysis, and as a compatibility source for reports written against the pre-existing WSHBV_DELIVERY interface. A representative query retrieves delivery headers for an organization within a date range:

• SELECT delivery_id, delivery_name, status_code, waybill, asn_seq_number, asn_date_sent FROM wshbv_delivery WHERE organization_id = :org_id AND creation_date >= :start_date;
• SELECT delivery_name, freight_carrier_code, gross_weight, weight_uom_code FROM wshbv_delivery WHERE status_code = 'CLOSED' AND date_closed BETWEEN :from_date AND :to_date;
• SELECT customer_id, COUNT(*) delivery_count FROM wshbv_delivery GROUP BY customer_id ORDER BY delivery_count DESC;

Because the view selects directly from WSH_DELIVERIES, no additional WHERE clause is imposed; callers should always constrain by ORGANIZATION_ID and date ranges to control result size, and must ensure the operating unit context is set when running through Oracle Reports or BI Publisher.