Search Results wms_ordered_tasks

Overview

WMS.WMS_ORDERED_TASKS is a Warehouse Management (WMS) transactional table in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores ordered or planned warehouse tasks that have been generated against an operation plan, capturing the discrete units of work — moves, picks, puts, and related execution steps — that the warehouse must perform. The table is central to the execution layer of Oracle Warehouse Management, bridging operational planning structures and the standard operation definitions that govern how a task is carried out.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault model. Because it carries both descriptive attributes (quantity, UOM, priority, effective dates) and foreign references to planning and operation definitions (OPERATION_PLAN_ID, STANDARD_OPERATION_ID), a Data Vault practitioner might equally model it as a link connecting plans and standard operations, with a dependent satellite for the descriptive columns. The documented FK structure does not, however, identify it as a pure junction, so the standalone recommendation reflects its role as a self-contained task record.

Key Information Stored

The table holds 17 documented columns. The most significant are:

• TASK_ID — the surrogate primary key uniquely identifying each ordered task row.
• TASK_SEQUENCE_ID — the sequence in which the task is ordered relative to others in the same plan; a business-key candidate alongside the plan.
• WMS_TASK_TYPE — the category of warehouse task (for example move, pick, put, or replenishment), which governs downstream processing rules.
• OPERATION_PLAN_ID — foreign key to WMS_OP_PLANS_B, tying the task to its parent operation plan.
• STANDARD_OPERATION_ID — foreign key to WSM_OPERATION_DETAILS, defining the standard operation the task executes.
• SUBINVENTORY_CODE and LOCATOR_ID — the inventory context (subinventory and specific locator) where the work occurs.
• REVISION, LOT_NUMBER, TRANSACTION_UOM, and TRANSACTION_QUANTITY — the material attributes and amount to be transacted.
• PRIORITY — the execution priority used for sequencing work in the warehouse.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the validity window for the task.
• PERSON_RESOURCE_ID and MACHINE_RESOURCE_ID — the assigned labor and equipment resources.
• MOVE_ORDER_LINE_ID — linkage to the originating move order line that spawned the task.

Operational keys combine WMS_TASK_TYPE, TASK_SEQUENCE_ID, and OPERATION_PLAN_ID to establish logical uniqueness of ordered work.

Common Use Cases and Queries

WMS_ORDERED_TASKS supports execution reporting, resource loading, and audit of planned warehouse work. Typical patterns include retrieving all tasks for a given operation plan or standard operation, listing pending tasks by priority and subinventory, and reconciling tasks against originating move orders.

• Task listing by plan: SELECT task_id, task_sequence_id, wms_task_type, priority FROM wms_ordered_tasks WHERE operation_plan_id = :plan_id ORDER BY task_sequence_id;
• Resource assignment review: SELECT task_id, person_resource_id, machine_resource_id FROM wms_ordered_tasks WHERE person_resource_id = :person_id;
• Material and locator breakdown: SELECT subinventory_code, locator_id, transaction_uom, transaction_quantity FROM wms_ordered_tasks WHERE task_id = :task_id;
• Move order trace: SELECT t.task_id, t.move_order_line_id FROM wms_ordered_tasks t WHERE t.move_order_line_id = :line_id;
• Effective-date filtering for point-in-time task validity: ... WHERE SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE);

These queries drive dashboards for labor utilization, task backlog, and execution throughput.

Related Objects

The ETRM metadata documents two explicit foreign-key relationships, both central to task definition:

• WMS_OP_PLANS_B — referenced via OPERATION_PLAN_ID; the parent operation plan header.
• WSM_OPERATION_DETAILS — referenced via STANDARD_OPERATION_ID; defines the standard operation performed.

Additional dependent structures — move order lines (via MOVE_ORDER_LINE_ID), resource definitions underlying the person and machine resource identifiers, and the WMS task execution and dispatch interfaces — complete the surrounding object set. Together these form the planning-to-execution chain that Oracle Warehouse Management relies upon.