Search Results move_order_line_number




Overview
Explore in AI Chat

Overview

WMS_WAVEPLAN_TASK_EXCEPTIONS_V is an APPS-owned reporting view within the Oracle Warehouse Management (WMS) module. Its purpose is to consolidate exception records raised against wave planning and dispatched warehouse tasks, exposing them in a denormalized, human-readable form suitable for operational reporting, dashboards, and integration extract programs. Rather than requiring report authors to join the low-level WMS execution tables directly, the view pre-resolves surrogate keys into descriptive attributes—reason name and description, person full name, concatenated locator and item flexfield segments, and move order header and line numbers.

In Oracle EBS 12.1.1 and 12.2.2, the object is delivered as a VALID view in the APPS schema. Because it is a view rather than a table, it carries no storage of its own; all data is materialized at query time from the underlying transaction and exception tables. This makes it appropriate for read-only reporting, BI Publisher datasets, and custom concurrent programs, but unsuitable as a target for DML.

Underlying Base Objects

The documented base objects referenced by the view are:

The view is assembled from an inline subquery that joins WMS_EXCEPTIONS, WMS_DISPATCHED_TASKS_HISTORY, MTL_TXN_REQUEST_LINES, WMS_WAVEPLAN_TASKS_TEMP, and MTL_MATERIAL_TRANSACTIONS, and is then outer-joined to MTL_TRANSACTION_REASONS, PER_ALL_PEOPLE_F, MTL_SYSTEM_ITEMS_KFV, and MTL_ITEM_LOCATIONS_KFV, with a DISTINCT applied to eliminate duplicates arising from the multi-way joins.

Key Columns

Common Use Cases and Queries

Typical usage includes exception trend reporting by reason, operator productivity analysis, and tracing exceptions back to their originating move order line for corrective action. A representative query filtering by move order line number is:

  • SELECT move_order_number, move_order_line_number, item, locator, reason_name, full_name, exception_time FROM wms_waveplan_task_exceptions_v WHERE organization_id = :org_id AND move_order_line_number = :line_number ORDER BY exception_time DESC;
  • SELECT reason_name, COUNT(*) FROM wms_waveplan_task_exceptions_v WHERE exception_time >= :from_date GROUP BY reason_name ORDER BY 2 DESC;

The first query is the standard path for a "move_order_line_number" lookup, returning all exceptions associated with a specific move order line together with the item, locator, reason, and operator. Because the view applies DISTINCT over a multi-table join, large date ranges should be bounded by organization and time predicates to preserve performance.