Search Results release_fill_rate




Overview
Explore in AI Chat

Overview

WMS_WP_WWB_ORDERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Warehouse Management (WMS) product family. In Release 12.1.1 and 12.2.2 it belongs to the Wave Planning and Wave Workbench reporting layer, presenting order-level fill-rate and progress information for orders being processed through wave planning and execution. Its principal purpose is to consolidate the fulfillment performance of an order — measured against planned demand, released demand, and picked demand — into a single aggregated row per order and wave combination.

The view is the order-level counterpart to WMS_WP_WWB_LINES_V, which operates at the individual wave line level. Where the line-level view exposes granular detail, this view aggregates upward using AVG and MAX functions so that the fill-rate percentages are expressed as whole-number values per order. The inclusion of the PLANNED_FILL_RATE column makes this object the standard reference point for the search term planned_fill_rate, since it is the highest-level published view in the WMS Workbench set exposing that metric.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects: HZ_CUST_ACCOUNTS and HZ_PARTIES (both accessed through synonyms) provide customer identity and party name information; OE_ORDER_HEADERS_ALL supplies order header attributes such as the ordered date and request date; WSH_DELIVERY_DETAILS links the order to its delivery detail records; WMS_WP_WAVE_LINES associates the delivery detail with the wave; and WMS_WP_WWB_LINES_V is the inline view from which the fill-rate metrics originate. The WMS_WAVE_PLANNING_PVT package is also referenced, reflecting the wave planning logic that underpins the Workbench screens.

The join conditions are strict: the customer ID on WSH_DELIVERY_DETAILS must match an active HZ_CUST_ACCOUNTS record (STATUS = 'A'), whose party ID in turn resolves to HZ_PARTIES. The source header ID on the delivery detail must match the OE order header, and the wave line must agree on both delivery detail ID and organization ID. Finally, the aggregated line set must match on both order number and wave header ID, ensuring the fill rates are scoped to the correct wave.

Key Columns

  • ORDER_NUMBER — the source header number from WSH_DELIVERY_DETAILS; the group-by key at the order level.
  • CUSTOMER / CUSTOMER_ID — party name and customer account identifier.
  • PLANNED_FILL_RATE — rounded average of the planned fill rate across the order's wave lines; measures how completely the order was planned against demand.
  • RELEASE_FILL_RATE — rounded average of the release fill rate; indicates how much of the planned quantity was actually released to the warehouse.
  • PICK_FILL_RATE — rounded average of the pick fill rate; indicates how much of the released quantity was picked.
  • ORDER_TYPE — the source header type name (for example, sales order or transfer order).
  • CUST_PO_NUMBER — the customer purchase order reference carried on the order.
  • ORDERED_DATE / ORDER_REQUEST_DATE — order entry date and requested ship date, used for aging and on-time analysis.
  • ORDER_PROGRESS — a decoded status string derived from the maximum line progress: READY TO RELEASE, BACKORDERED, CROSSDOCK PLANNED, REPLENISHMENT CREATED, TASKED, PICKED, IN PACKING, STAGED, LOADED TO DOCK, or SHIPPED. The string is prefixed with "PARTIALLY " when the order's wave lines are not all at the same progress point.
  • WAVE_HEADER_ID — the wave grouping identifier and the secondary grouping key, with results ordered by it.

Common Use Cases and Queries

The view is typically used to build wave performance dashboards, to identify orders whose planned fill rate is materially higher than their pick fill rate (indicating execution shortfalls), and to track partially progressed orders. A representative query retrieving orders with a weak planned fill rate is:

SELECT order_number, customer, planned_fill_rate, release_fill_rate, pick_fill_rate, order_progress
FROM apps.wms_wp_wwb_orders_v
WHERE planned_fill_rate < 100
ORDER BY planned_fill_rate, order_number;

A second common pattern filters by wave to review a single wave run:

SELECT order_number, customer, cust_po_number, order_progress, planned_fill_rate
FROM apps.wms_wp_wwb_orders_v
WHERE wave_header_id = :p_wave_header_id
ORDER BY order_number;

Because the view performs aggregation, filtering on ORDER_PROGRESS using the LIKE operator (for example, WHERE order_progress LIKE 'PARTIALLY%') allows users to isolate orders split across multiple progress states. All queries should be issued under an APPS or reporting responsibility with the appropriate MO: Operating Unit context, since the underlying delivery and order tables are organization-sensitive.