Search Results commodity_code_int




Overview

WSH_DSNO_ITEMS_COMM_V is a Shipping Execution (WSH) reporting view owned by the APPS schema. Its name reflects its purpose: it exposes delivery detail line information in a flattened, communications-oriented form ("DSNO" denotes Delivery Shipping Notification, and "ITEMS_COMM" indicates item-level commerce content). The view consolidates order, item, customer, and packaging attributes into a single denormalized projection, making it suitable for outbound shipping notifications, integration feeds, and ad hoc reporting without requiring the consumer to join the delivery, order, and item schemas manually.

In both 12.1.1 and 12.2.2, the view is defined in the APPS schema and is reported as VALID. It draws heavily on WSH_DELIVERY_DETAILS and WSH_NEW_DELIVERIES, joining to inventory item and customer item master data. The column alias CUSTOMER_ORDER_FLAG, which maps to MSI.CUSTOMER_ORDER_ENABLED_FLAG, is the attribute most frequently searched by developers querying this view, since it identifies whether an inventory item is enabled for customer order processing.

Underlying Base Objects

The documented base objects for this view are:

  • WSH_DELIVERY_DETAILS (SYNONYM) — the primary driver, aliased WDD, supplying inventory item, source header/line, quantities, prices, and descriptive flexfield attributes.
  • WSH_NEW_DELIVERIES (SYNONYM) — aliased WND, providing delivery identity and confirmation date.
  • WSH_DELIVERY_ASSIGNMENTS_V (VIEW) — supplying container assignment context through PARENT_DELIVERY_DETAIL_ID.
  • WSH_DSNO_PACKED_QUANTITY_V (VIEW) — used in a scalar subquery to derive packed quantity per container.
  • MTL_SYSTEM_ITEMS (SYNONYM) — aliased MSI, the source of container flags, container type, and CUSTOMER_ORDER_ENABLED_FLAG.
  • MTL_CUSTOMER_ITEMS (SYNONYM) and MTL_ITEM_FLEXFIELDS (VIEW) — aliased MCI and MIF, supplying customer part number, description, and supplier part number.
  • MTL_COMMODITY_CODES (SYNONYM) — aliased MCC, for commodity classification.
  • PO_HAZARD_CLASSES (SYNONYM) — aliased PHC, for hazard class and description.
  • WMS_DEPLOY (PACKAGE) — referenced for warehouse management deployment context.

The view is therefore a read-only integration surface layered over the delivery, order, and item masters, and it should be treated as a reporting object rather than one that supports DML.

Key Columns

Common Use Cases and Queries

The view is typically queried to produce shipping notification content, customer-facing item summaries, or container/packing reconciliations. A frequent pattern filters on the customer order flag to isolate sellable items:

  • Extract all order lines for a delivery for an outbound 856/ASN style feed.
  • Report shipped versus ordered and cancelled quantities by item and customer part number.
  • Reconcile packed quantity against shipped quantity by container.
  • Identify items on a delivery that are flagged for customer order processing versus container-only items.

Sample query:

SELECT delivery_id, delivery_detail_id, order_header_id, order_line_id,
  customer_part_number, shipped_quantity, ordered_quantity,
  customer_order_flag, container_item_flag, packed_quantity
FROM  apps.wsh_dsno_items_comm_v
WHERE customer_order_flag = 'Y'
AND   delivery_id = :p_delivery_id;

Because the view internally joins several delivery and master views, including a scalar subquery against WSH_DSNO_PACKED_QUANTITY_V, performance is best when queries are constrained by DELIVERY_ID or DELIVERY_DETAIL_ID. Consumers should expect the result set to reflect the state of the shipping transaction at query time and should not attempt to write back through the view.