Search Results entry_status_code

Overview

The APPS.WMS_DISPATCHABLE_TASKS_V view is a consolidated reporting and integration interface within the Oracle Warehouse Management (WMS) module. Its purpose is to expose tasks that are eligible for dispatching by the warehouse task dispatching engine. The view presents a normalized projection of pending warehouse work, combining material movement tasks with cycle count tasks into a single, uniformly structured result set. It carries a status of VALID in the APPS schema and is owned by APPS, making it available to reporting tools, concurrent programs, and integration layers that require a real-time or near-real-time view of dispatchable work across the warehouse. Because the view unifies multiple task sources under a common column layout, it is well suited to task board displays, workload balancing queries, and downstream systems that poll for open tasks.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through synonyms: MTL_MATERIAL_TRANSACTIONS_TEMP and MTL_CYCLE_COUNT_ENTRIES. These two sources are combined using a UNION ALL, producing a single result set with a consistent column structure.

• MTL_MATERIAL_TRANSACTIONS_TEMP supplies the material movement portion of the result. It is filtered to rows where WMS_TASK_TYPE IS NOT NULL and TRANSACTION_STATUS = 2, indicating tasks that have been staged for dispatching. Columns such as TRANSACTION_TEMP_ID, STANDARD_OPERATION_ID, TRANSACTION_UOM, and TRANSACTION_QUANTITY originate from this table.
• MTL_CYCLE_COUNT_ENTRIES supplies the cycle count portion. Rows are filtered to those with ENTRY_STATUS_CODE IN (1, 3) and NVL(EXPORT_FLAG, 2) = 2, and are aggregated by cycle count header, organization, subinventory, locator, item, and revision. This branch assigns a constant WMS_TASK_TYPE_ID of 3 and returns empty or NULL placeholders for movement-specific columns such as TRANSACTION_UOM and TRANSACTION_QUANTITY.

Key Columns

• TASK_ID — Maps to TRANSACTION_TEMP_ID for movement tasks and to MIN(CYCLE_COUNT_ENTRY_ID) for cycle count tasks; identifies the individual dispatchable task.
• USER_TASK_TYPE_ID — Derived from STANDARD_OPERATION_ID, identifying the user-facing task or operation type.
• WMS_TASK_TYPE_ID — The WMS task type classification; movement tasks inherit WMS_TASK_TYPE while cycle count tasks are fixed at 3.
• ORGANIZATION_ID / ZONE / LOCATOR_ID — Identify the inventory organization, subinventory zone, and locator where the task resides.
• TASK_PRIORITY — Priority used by the dispatching engine for task sequencing.
• TRANSACTION_UOM — The unit of measure for the task quantity. This column is populated from MTL_MATERIAL_TRANSACTIONS_TEMP for movement tasks and is returned as an empty string for cycle count tasks.
• TRANSACTION_QUANTITY — The quantity to be transacted; populated for movement tasks and NULL for cycle count tasks.
• REVISION, LOT_NUMBER, INVENTORY_ITEM_ID — Item and lot/revision identification for the task.
• PICK_RULE_ID, PICK_SLIP_NUMBER, CARTONIZATION_ID, MOVE_ORDER_LINE_ID — Movement-specific attributes that are NULL for cycle count tasks.

Common Use Cases and Queries

Typical usage involves listing open dispatchable tasks, prioritizing work, and extracting tasks by organization or zone. The following query returns dispatchable tasks with their transaction UOM and quantity for a given organization.

• SELECT task_id, wms_task_type_id, organization_id, zone, locator_id, transaction_uom, transaction_quantity FROM apps.wms_dispatchable_tasks_v WHERE organization_id = :org_id ORDER BY task_priority, task_id;
• SELECT wms_task_type_id, COUNT(*) task_count FROM apps.wms_dispatchable_tasks_v GROUP BY wms_task_type_id;
• SELECT task_id, inventory_item_id, lot_number, revision, task_priority FROM apps.wms_dispatchable_tasks_v WHERE zone = :zone ORDER BY task_priority;

Because the cycle count branch suppresses TRANSACTION_UOM and TRANSACTION_QUANTITY, queries filtering or aggregating on these columns should account for NULL values when combining both task categories.