Search Results pick_rule_id




Overview
Explore in AI Chat

Overview

APPS.WMS_DISPATCHABLE_TASKS_V is a union view in Oracle E-Business Suite Warehouse Management System (WMS) that consolidates dispatchable warehouse tasks into a single, unified result set for the Warehouse Management and Mobile Supply Chain Applications execution engines. It presents work ready to be dispatched to warehouse operators, drawing from two distinct sources: pending material transactions staged in the transaction interface and open cycle count entries awaiting processing. The view is used by the WMS task dispatching framework to determine which tasks are available for assignment, sequencing, and execution on handheld devices and within the warehouse control system.

Because the view underpins task dispatching, its contents directly influence how work is presented to warehouse personnel. Each row represents a candidate task with its associated zone, locator, item, quantity, and priority information, allowing the dispatch engine to apply pick rules and prioritization logic uniformly across disparate task types.

Underlying Base Objects

The view is defined as a UNION ALL over two documented base objects, both referenced through APPS synonyms:

Both branches share a common column projection, which is why the union is possible. The material transaction branch produces task identifiers directly from TRANSACTION_TEMP_ID, while the cycle count branch synthesizes a task using MIN(CYCLE_COUNT_ENTRY_ID) and assigns a fixed WMS_TASK_TYPE_ID of 3 to distinguish cycle counting tasks from other task types.

Key Columns

The view exposes a normalized task structure. The most commonly referenced columns include:

  • TASK_ID — the unique task identifier, sourced from TRANSACTION_TEMP_ID or the minimum CYCLE_COUNT_ENTRY_ID.
  • WMS_TASK_TYPE_ID — the task category. Material transaction tasks carry the source WMS_TASK_TYPE; cycle count tasks are hard-coded to 3.
  • ORGANIZATION_ID — the inventory organization owning the task.
  • ZONE — the subinventory code mapped as the task zone.
  • LOCATOR_ID — the specific locator where the task must be performed. This is the column most often filtered by users searching for locator-specific work, and it appears in both branches of the union as well as in the cycle count GROUP BY clause.
  • TASK_PRIORITY — relative priority used for sequencing dispatch.
  • REVISION, LOT_NUMBER — item revision and lot context.
  • TRANSACTION_UOM, TRANSACTION_QUANTITY — the unit of measure and quantity for material movement tasks; these are null for cycle count rows, which instead carry empty string or null placeholders.
  • INVENTORY_ITEM_ID — the item to be moved or counted.
  • PICK_RULE_ID, PICK_SLIP_NUMBER, CARTONIZATION_ID, MOVE_ORDER_LINE_ID — linkage to picking, cartonization, and move order processing; these are populated only for material transaction tasks.

Common Use Cases and Queries

Typical usage centers on identifying dispatchable work by zone, locator, or item. A common requirement is to list all pending tasks for a specific locator, which the locator_id column supports directly:

  • Query all ready tasks in an organization: SELECT task_id, wms_task_type_id, zone, locator_id, task_priority, inventory_item_id FROM apps.wms_dispatchable_tasks_v WHERE organization_id = :org_id ORDER BY task_priority;
  • Filter by locator: SELECT task_id, wms_task_type_id, locator_id, transaction_quantity FROM apps.wms_dispatchable_tasks_v WHERE locator_id = :locator_id;
  • Isolate cycle count tasks: SELECT task_id, locator_id, inventory_item_id FROM apps.wms_dispatchable_tasks_v WHERE wms_task_type_id = 3;
  • Isolate material movement tasks with pick details: SELECT task_id, pick_slip_number, move_order_line_id, cartonization_id FROM apps.wms_dispatchable_tasks_v WHERE wms_task_type_id <> 3;

These queries are commonly embedded in custom dispatch reports, mobile device integrations, and warehouse dashboards that need a unified, real-time picture of all work available for assignment across both transaction-driven and cycle count-driven activities.