Results for “sales_order_number”

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

Overview

WSH_SS2_SHIPITEMS_V is a Shipping Execution (WSH) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents an aggregated, shipment-oriented summary of outbound delivery detail lines originating from the Order Management (OE) source. Its design aligns delivery detail records at the shipment batch level, rolling up requested quantities by item unit of measure. This makes the view particularly useful in the context of shipment confirmation, packing, and manifesting processes where a consolidated count of shippable items per shipment batch is required.

The view is categorized as an SS2 (Shipping Systems 2) interface object, a naming convention applied to a family of Shipping Execution views used to expose structured shipment data for reporting, label printing, and external integration. Because it joins item master information through the key flexfield view, it also supplies descriptive item context alongside shipment metrics.

The SHIPMENT_LINE_NUMBER column is a primary grouping attribute in this view. It identifies the line on the shipment (delivery) associated with the delivery detail, enabling downstream consumers to count and group shipped items by their shipment line identifier.

Underlying Base Objects

The view is defined over two referenced base objects, both accessed through synonyms in the APPS schema:

• WSH_DELIVERY_DETAILS (aliased WDD) — the core Shipping Execution table that stores delivery detail lines. The view filters this table on SOURCE_CODE = 'OE', restricting output to delivery details sourced from Order Management, and on SHIPMENT_BATCH_ID IS NOT NULL, ensuring only records assigned to a shipment batch are included.
• MTL_SYSTEM_ITEMS_KFV (aliased MSIK) — the item key flexfield view over the item master. It is joined on both INVENTORY_ITEM_ID and ORGANIZATION_ID, providing item context constrained to the correct inventory organization.

The join is an inner join, so delivery details must resolve to a valid item in the organization to appear. Results are grouped by shipment batch, shipment line number, sales order number, reference line ID, and requested quantity UOM, with REQUESTED_QUANTITY summed.

Key Columns

• SHIPMENT_BATCH_ID — Identifier of the shipment batch to which the delivery detail belongs.
• SHIPMENT_LINE_NUMBER — The line number on the shipment associated with the delivery detail; a principal grouping and search attribute.
• SALES_ORDER_NUMBER — Derived from WDD.SOURCE_HEADER_NUMBER; the originating sales order header number.
• REFERENCE_LINE_ID — Reference line identifier, typically linking back to the order line reference.
• REQUESTED_QUANTITY_UOM — Unit of measure in which the requested quantity is expressed.
• REQUESTED_QUANTITY — Sum of requested quantities for the grouped delivery details.

Common Use Cases and Queries

Typical scenarios include verifying aggregated item counts per shipment batch before manifesting, reconciling shipment lines to sales orders, and generating reports keyed on SHIPMENT_LINE_NUMBER. A representative query follows:

• Retrieve aggregated requested quantities for a given shipment batch.
• List all shipment lines associated with a sales order number.
• Audit UOM distribution across shipment lines.

Sample SQL:

SELECT shipment_batch_id,
       shipment_line_number,
       sales_order_number,
       requested_quantity_uom,
       requested_quantity
FROM   apps.wsh_ss2_shipitems_v
WHERE  shipment_batch_id = :p_batch_id
ORDER BY shipment_line_number;

Because the view exposes only OE-sourced, batch-assigned details, it should be used in conjunction with base WSH tables when non-OE sources or unbatched lines must be reported.