Search Results wsh_dsno_items_specific_v




Overview
Explore in AI Chat

Overview

WSH_DSNO_ITEMS_SPECIFIC_V is a Shipping Execution (WSH) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the DSNO (Delivery Shipment Notification / outbound interface) family of views used by the shipping and order-to-cash integration layer. Its purpose is to expose item-level, order-line-specific attributes in a normalized form suitable for outbound message generation, XML/trading-partner mapping, and reporting that requires order line context alongside shipping detail.

The view carries a literal constant column, SOURCE_CODE, hard-coded to 'OE' (Order Entry), which identifies the source system for the returned rows. This is a common DSNO construct: a source discriminator allows the consuming process to distinguish rows originating from Order Management versus rows originating from other upstream systems in the same interface.

Underlying Base Objects

Per the ETRM metadata, the view is defined over the following referenced objects:

The visible SELECT list is dominated by OE_ORDER_LINES_ALL (aliased OEL) joined to OE_ORDER_HEADERS_ALL (aliased OEH). Within the full view text, the contract, deliverables, and RLM objects supply additional columns for contract-referenced and return-schedule scenarios, while WSH_ECE_VIEWS_DEF governs which columns are exposed for a given interface configuration. The DISTINCT keyword in the view text indicates the query is intended to suppress duplicates that can arise from these multi-table joins.

Key Columns

The principal columns exposed by the view include:

These columns make the view a flattened, integration-ready projection of order line attribute data, including both keyed flexfield segments and their descriptive contexts.

Common Use Cases and Queries

The view is typically consumed by outbound shipping/order interfaces and by custom reports needing order-line attributes at the item level without joining multiple OE tables directly. A representative query follows:

  • SELECT SOURCE_CODE, ORDER_HEADER_ID, ORDER_LINE_ID, ORDER_LINE_NUMBER, PROMISE_DATE, ITEM_TYPE_CODE_INT FROM APPS.WSH_DSNO_ITEMS_SPECIFIC_V WHERE ORDER_HEADER_ID = :p_header_id ORDER BY ORDER_LINE_NUMBER;
  • SELECT ORDER_LINE_ID, ORDER_LINE_CONTEXT, ORDER_LINE_ATTRIBUTE1, ORDER_LINE_ATTRIBUTE2 FROM APPS.WSH_DSNO_ITEMS_SPECIFIC_V WHERE ORIGINAL_SYSTEM_LINE_REF = :p_ref;

Note that the user search term "handling_code_ext" does not appear among the documented columns of this view; handling-code attributes are more commonly associated with WSH delivery and delivery-detail entities rather than this order-line-specific DSNO view. When troubleshooting, confirm the correct DSNO view for the desired attribute, and always query the synonym in the APPS schema in a reporting or read-only capacity.