Search Results line_direction




Overview
Explore in AI Chat

Overview

APPS.WSH_DLVB_SHIP_FROM_TO_V is a lightweight reporting and integration view defined in the Oracle E-Business Suite shipping module (WSH). It exposes a filtered subset of delivery detail records together with the ship-from and ship-to location identifiers and container information. The view is particularly relevant to users who search on the container_flag attribute, because that column is explicitly projected by the view and originates directly from the underlying delivery details table.

The view presents only those rows from WSH_DELIVERY_DETAILS where the line direction is outbound. Specifically, the WHERE clause applies NVL(line_direction, 'O') IN ('O', 'IO'), meaning rows with a null line direction are treated as outbound, and rows marked as outbound ('O') or internal outbound ('IO') are retained. Inbound, return, and other non-outbound line directions are excluded. This makes the view a convenient, pre-filtered source for downstream reports, interfaces, and integration programs that must work exclusively with outbound shipment details.

Two columns, DELIVERY_ID and DELIVERY_NAME, are deliberately stubbed out as NULL casts (to_number(null) and to_char(null)). This design allows the view to conform to a common column contract expected by consuming programs while remaining decoupled from the delivery header, effectively providing ship-from/ship-to and container-level detail without requiring a join to the delivery header table.

Underlying Base Objects

The view is defined over a single base object: the synonym WSH_DELIVERY_DETAILS, which resolves to the core shipping table of the same name. There are no joins, unions, or aggregation in the view text. Consequently, every row in WSH_DLVB_SHIP_FROM_TO_V corresponds one-to-one with a qualifying row in WSH_DELIVERY_DETAILS. Because the definition relies on a synonym rather than a fully qualified schema reference, the view resolves against the APPS schema objects as shipped in EBS 12.1.1 and 12.2.2.

Key Columns

  • CONTAINER_FLAG — Indicates whether the delivery detail line is associated with a container (such as a carton or pallet) or is handled as loose/bulk material. This is the column most often used to partition packed versus unpacked shipment lines.
  • DELIVERY_DETAIL_ID — The primary identifier of the delivery detail line, used to join back to the base table or to related shipping entities.
  • CONTAINER_NAME — The name or identifier of the container (LPN) associated with the line, when populated.
  • ORGANIZATION_ID — The inventory organization owning the shipped item.
  • INVENTORY_ITEM_ID — The item being shipped.
  • SHIP_FROM_LOCATION_ID — The location from which the goods are dispatched.
  • SHIP_TO_LOCATION_ID — The destination location for the shipment.
  • DELIVERY_ID / DELIVERY_NAME — Null placeholders, retained to satisfy a consistent column contract; they carry no data.

Common Use Cases and Queries

A frequent requirement is to identify all containerized outbound lines for a given organization or item, which the search term "container_flag" suggests:

  • Report packed versus loose outbound deliveries by filtering on CONTAINER_FLAG.
  • Extract ship-from and ship-to location pairs for logistics or transportation planning.
  • Feed interfaces that require outbound-only delivery detail records without headers.

Sample query:

SELECT container_flag,
       container_name,
       organization_id,
       inventory_item_id,
       ship_from_location_id,
       ship_to_location_id
FROM   apps.wsh_dlvb_ship_from_to_v
WHERE  container_flag = 'Y'
AND    organization_id = :p_org_id;

Because reserved words such as CONTAINER_FLAG are not Oracle SQL reserved terms, they may be referenced without quoting. The absence of a delivery header join means the view is efficient for row-level reporting but must be joined to WSH_DELIVERY_HEADERS externally when delivery-level attributes are required.