Search Results intmed_ship_to_org_id

Overview

WSH_OE_LINES_V2 is a Shipping Execution (WSH) view owned by the APPS schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents a denormalized, shipping-oriented projection of order line data, joining order lines to their parent order headers so that header-level attributes such as ORDER_NUMBER are available alongside line-level detail. The "_V2" suffix indicates a versioned interface view used by Shipping Execution and its integration points to expose order line information in a consistent, read-only form. Because the view selects from the order management base tables rather than from shipping tables, it functions as a bridge that allows shipping logic to consume sales order line attributes — including ship-from, ship-to, deliver-to, and sold-to organization identifiers — without directly querying OE_ORDER_LINES_ALL. This is the view that answers the common search for the deliver_to_org_id column: it exposes OE.DELIVER_TO_ORG_ID directly, making the deliver-to organization of an order line accessible to shipping reports, concurrent programs, and integration queries.

Note that the view populates DELIVERY_ID and DELIVERY_NAME as hard-coded NULLs (TO_NUMBER(NULL) and TO_CHAR(NULL)), so it does not surface actual delivery associations; those must be obtained from the shipping delivery tables separately.

Underlying Base Objects

Per the documented metadata, WSH_OE_LINES_V2 is defined over two referenced base objects, both exposed as synonyms in the APPS schema:

• OE_ORDER_LINES_ALL — the primary source of line-level columns (LINE_ID, ORDERED_ITEM, ORDERED_QUANTITY, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, DELIVER_TO_ORG_ID, and the remaining org and quantity attributes).
• OE_ORDER_HEADERS_ALL — joined via OH.HEADER_ID = OE.HEADER_ID, supplying header-level context such as ORDER_NUMBER and HEADER_ID.

The join is an inner equijoin on HEADER_ID, so only lines with a matching header are returned. The view does not reference WSH delivery, trip, or stop tables; it is purely an order-line projection relabeled for shipping consumption.

Key Columns

• DELIVER_TO_ORG_ID — the organization to which goods are to be delivered; the column most frequently searched and the reason this view is used for deliver-to reporting.
• HEADER_ID / LINE_ID — primary keys of the parent header and the line, used for joins to other order and shipping entities.
• ORDER_NUMBER — the user-visible order number sourced from OE_ORDER_HEADERS_ALL.
• ORG_ID — the operating unit that owns the order line, essential for multi-org (MOAC) filtering.
• SHIP_FROM_ORG_ID / SHIP_TO_ORG_ID / INVOICE_TO_ORG_ID / INTMED_SHIP_TO_ORG_ID / SOLD_FROM_ORG_ID / SOLD_TO_ORG_ID — the full set of organization role identifiers associated with the line.
• ORDERED_ITEM, INVENTORY_ITEM_ID, ORDERED_ITEM_ID — item identification in both flexible and internal forms.
• ORDERED_QUANTITY, SHIPPED_QUANTITY, ORDER_QUANTITY_UOM — requested versus shipped amounts and the unit of measure; the column set repeats with the "2" suffix (ORDERED_QUANTITY2, SHIPPED_QUANTITY2, ORDERED_QUANTITY_UOM2) to carry secondary UOM values.
• LINE_NUMBER, SHIPMENT_NUMBER, OPTION_NUMBER, COMPONENT_NUMBER, SERVICE_NUMBER — structural identifiers for the line and its configuration context.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

This view is typically used to report order lines by delivery destination, to reconcile shipping demand against ordered quantities, and to feed integrations that require organization identifiers. A representative query retrieving lines for a specific deliver-to organization follows:

• SELECT order_number, line_id, ordered_item, deliver_to_org_id FROM apps.wsh_oe_lines_v2 WHERE org_id = :p_org_id AND deliver_to_org_id = :p_deliver_to;
• SELECT h.order_number, l.line_number, l.ordered_quantity, l.shipped_quantity, l.ship_to_org_id, l.deliver_to_org_id FROM apps.wsh_oe_lines_v2 l WHERE l.org_id = :p_org_id AND l.shipped_quantity < l.ordered_quantity;
• SELECT COUNT(*) FROM apps.wsh_oe_lines_v2 WHERE deliver_to_org_id IS NULL AND org_id = :p_org_id;

Because DELIVERY_ID and DELIVERY_NAME are always NULL, do not rely on this view for delivery grouping; join to the WSH delivery detail tables on LINE_ID instead. Always constrain queries by ORG_ID when MOAC is enabled to avoid cross-operating-unit results.