Results for “source_header_id”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view WSH_DSNO_PACKED_QUANTITY_V is an APPS-owned database view within the Oracle E-Business Suite Shipping Execution (WSH) module. Its name reflects its purpose: it exposes the "packed quantity" associated with outbound delivery details, aggregated per delivery, container, inventory item, and source document reference. The "DSNO" segment of the name associates it with delivery/shipping number and outbound processing logic used across WSH reporting and integration. The view is documented with a status of VALID in both Oracle EBS 12.1.1 and 12.2.2 and is defined in the APPS schema.

As a reporting and integration object, the view provides a normalized, pre-aggregated representation of shipped quantities for delivery details that are not themselves containers. This makes it suitable for downstream queries, concurrent programs, and interface extracts that require authoritative packed quantity values without reconstructing the aggregation logic from base tables.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over the following base objects:

The join is driven by WDA.DELIVERY_DETAIL_ID = WDD.DELIVERY_DETAIL_ID. The view filters to rows where WDD.CONTAINER_FLAG = 'N' and NVL(WDD.SHIPPED_QUANTITY, 0) > 0, excluding container records and zero-quantity lines. Results are then grouped by delivery, parent delivery detail, item, and source identifiers.

Key Columns

  • DELIVERY_ID — identifier of the delivery header to which the assignment belongs.
  • CONTAINER_ID — the parent delivery detail identifier representing the container (NULL when the detail is not packed into a container).
  • INVENTORY_ITEM_ID — inventory item for the shipped detail.
  • SOURCE_CODE — code identifying the originating document type (for example, order or transfer).
  • SOURCE_HEADER_ID / SOURCE_LINE_ID — header and line identifiers of the source document.
  • PACKED_QUANTITY — SUM of SHIPPED_QUANTITY across qualifying details, returning 0 when CONTAINER_ID is NULL.
  • PACKED_QUANTITY2 — the same aggregation applied to SHIPPED_QUANTITY2, the secondary unit of measure.

Common Use Cases and Queries

Typical scenarios include reporting packed quantities per delivery and item, reconciling shipped versus packed quantities, and extracting data for shipping documentation or interfaces. A representative query:

  • Retrieve packed totals for a delivery: SELECT DELIVERY_ID, INVENTORY_ITEM_ID, SOURCE_CODE, PACKED_QUANTITY, PACKED_QUANTITY2 FROM APPS.WSH_DSNO_PACKED_QUANTITY_V WHERE DELIVERY_ID = :p_delivery_id;
  • Aggregate packed quantity by item across deliveries: SELECT INVENTORY_ITEM_ID, SUM(PACKED_QUANTITY) FROM APPS.WSH_DSNO_PACKED_QUANTITY_V GROUP BY INVENTORY_ITEM_ID;
  • Reconcile against source lines: join on SOURCE_HEADER_ID and SOURCE_LINE_ID to compare ordered versus packed quantities.

Because the view applies aggregation and filtering internally, consumers should not re-apply container or zero-quantity filters, and should treat PACKED_QUANTITY as already summarized at the documented grouping grain.