Search Results order_progress

Overview

APPS.WMS_WP_WWB_ORDERS_V is a reporting view in the Oracle E-Business Suite Warehouse Management System (WMS) module. It aggregates order-level wave planning and execution data, presenting a consolidated status for sales orders that have been associated with a wave. The view is part of the Oracle Warehouse Management "Wave Workbench" reporting layer, designed specifically to surface the progress of an order as it moves through the outbound logistics lifecycle — from release through picking, packing, staging, and shipment.

This view is significant for the search term "order_progress" because ORDER_PROGRESS is a derived, human-readable column at its core. It translates numeric line progress identifiers into descriptive status strings, allowing users and downstream reports to understand at a glance where an order stands within a wave. The view is read-only and intended for query and reporting purposes rather than transactional updates, making it suitable for dashboards, exception reports, and integration extracts that monitor fulfillment progress.

Underlying Base Objects

The view is defined over a set of documented base objects that span order management, shipping, and warehouse execution:

• WSH_DELIVERY_DETAILS — Provides the delivery line detail, source header number (order number), source header type, customer, and customer PO reference.
• OE_ORDER_HEADERS_ALL — Supplies the order header data, notably ORDERED_DATE and REQUEST_DATE (exposed as ORDER_REQUEST_DATE).
• HZ_PARTIES and HZ_CUST_ACCOUNTS — Return the customer party name; the join filters to active customer accounts (status = 'A').
• WMS_WP_WAVE_LINES — Links delivery details to a wave via WAVE_HEADER_ID and organization.
• WMS_WP_WWB_LINES_V — A nested view that computes per-line fill rates and the maximum line progress, which the outer query aggregates.
• WMS_WAVE_PLANNING_PVT — The wave planning package referenced in the definition, supporting the underlying wave logic.

An inner inline view (aliased wwlv1) aggregates WMS_WP_WWB_LINES_V by order number and wave header, deriving average planned, release, and pick fill rates plus a distinct progress count used to detect partial progress.

Key Columns

• ORDER_NUMBER — The source header number, identifying the sales order.
• CUSTOMER — Customer party name, aggregated with MAX.
• PLANNED_FILL_RATE, RELEASE_FILL_RATE, PICK_FILL_RATE — Average fill rates (rounded) at each planning stage.
• ORDER_PROGRESS — A decoded status string: blank (single status), or prefixed "Partially " when multiple progress states coexist. Values include Ready to Release, Backordered, Crossdock Planned, Replenishment Created, Tasked, Picked, Staged, In Packing, Loaded to Dock, and Shipped.
• ORDER_TYPE, CUSTOMER_ID, CUST_PO_NUMBER, ORDERED_DATE, ORDER_REQUEST_DATE — Descriptive order attributes.
• WAVE_HEADER_ID — The wave identifier, also the ORDER BY key.

Common Use Cases and Queries

Typical scenarios include monitoring wave fulfillment, identifying backordered orders, and reporting on fill-rate performance. A representative query:

SELECT order_number, customer, order_progress, order_type
FROM   apps.wms_wp_wwb_orders_v
WHERE  order_progress LIKE 'Partially%'
ORDER BY wave_header_id;

To review fill-rate performance by wave:

SELECT wave_header_id, order_number,
       planned_fill_rate, release_fill_rate, pick_fill_rate
FROM   apps.wms_wp_wwb_orders_v
WHERE  order_progress <> 'Shipped';

Because the view aggregates and orders by wave, it is well suited to exception reporting and operational dashboards tracking outbound order progress.