Search Results shipped_quantity2




Overview
Explore in AI Chat

Overview

APPS.WSH_OE_LINES_V2 is an internal Oracle E-Business Suite view owned by the APPS schema and shipped as part of the Shipping Execution (WSH) module. It exposes order line and shipment information drawn from the Oracle Order Management (OE) transactional tables, presenting a denormalized projection suitable for shipping-related processing and reporting. The view is registered in FND Design Data under the product short name WSH and carries a status of VALID in both the 12.1.1 and 12.2.2 release streams.

The object carries the standard Oracle warning that it is intended for internal use only and is not supported for direct customer access except through standard Oracle Applications programs. Despite this restriction, it is widely referenced by reports, interfaces, and diagnostic queries because it consolidates ordered and shipped quantity columns alongside organization, item, and delivery identifiers. The inclusion of both legacy quantity columns and their "_2" counterparts reflects the view's role during the multi-organization and dual-unit-of-measure migration that characterized the R12 codebase.

Underlying Base Objects

The documented dependency list identifies two base objects referenced by WSH_OE_LINES_V2:

  • OE_ORDER_HEADERS_ALL (synonym) — the order header table supplying header-level context such as the order number and header identifier.
  • OE_ORDER_LINES_ALL (synonym) — the order line table supplying line-level attributes including items, quantities, units of measure, and the various organization identifiers (ship-from, ship-to, invoice-to, deliver-to, sold-from, and sold-to).

The view is defined as an internal view type and joins the header and line entities so that each row corresponds to an order line within its header context. Because the synonyms resolve to the transactional OE tables, the view reflects live order data rather than a snapshot, and its column list mirrors the underlying OE column semantics with WSH-oriented naming.

Key Columns

The view exposes thirty-five columns. The most significant include:

Common Use Cases and Queries

Typical use cases include shipment reconciliation, shipped-versus-ordered quantity variance analysis, and delivery tracking. Because the view is unsupported for direct access, it should be used primarily in diagnostics or as a reference when building supported solutions against the OE base tables.

To locate secondary shipped quantities for a given order, a query such as the following is representative:

  • SELECT order_number, line_number, ordered_item, shipped_quantity, shipped_quantity2, ordered_quantity2, order_quantity_uom2, delivery_name FROM apps.wsh_oe_lines_v2 WHERE shipped_quantity2 > 0 AND order_number = :p_order_number;

A variance-oriented query compares primary and secondary shipped quantities against ordered amounts to flag short shipments or over-shipments. Joining on HEADER_ID and LINE_ID preserves the header-line relationship, while SHIP_FROM_ORG_ID and ORG_ID support multi-organization filtering. Given the internal-use designation, references should be confined to controlled reporting and troubleshooting contexts.