Search Results wms_waveplan_tasks_temp




Overview
Explore in AI Chat

Overview

The WMS.WMS_WAVEPLAN_TASKS_TEMP table is a transient staging structure within the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It holds pre-release wave planning task records that are generated during wave plan execution and dispatched to operators, equipment, and work areas before the tasks are written to the permanent task execution tables. Because the object is a temporary staging surface, rows are typically created, processed, and purged within the wave release cycle rather than retained as long-term transactional history.

Functionally, the table stores a denormalized snapshot of task attributes—item, locator, quantity, source and destination, personnel, equipment, LPN, cartonization, and shipment context—so that the wave planning engine can build, validate, and stage tasks before committing them to the broader WMS task model. Below the staging layer, records are consumed by the task dispatcher and the operation plan engine.

The ETRM relationship data classifies this object heuristically as standalone within a Data Vault model, since no other table was mined as referencing it via foreign keys. This is consistent with its role as a temporary work structure: it behaves more like a satellite of the wave planning process than a durable hub or link. Practitioners modeling WMS wave data for analytics should treat it as a staging or satellite source rather than a key integration anchor.

Key Information Stored

The table contains 121 documented columns. The most significant fall into the following groupings:

Documented foreign keys include TRANSACTION_SOURCE_TYPE_ID to MTL_TXN_SOURCE_TYPES, DEPARTMENT_ID to BOM_DEPARTMENTS, and OPERATION_PLAN_ID to WMS_OP_PLANS_B. No unique business-key index is documented in the ETRM metadata, so TASK_ID is the practical surrogate identifier, while combinations such as WAVE_HEADER_ID plus LINE_NUMBER or TRANSACTION_TEMP_ID act as business-key candidates in practice.

Common Use Cases and Queries

Because this table is a staging area, it is most often queried during wave release troubleshooting and dispatch diagnostics. Typical scenarios include identifying tasks not yet dispatched, reviewing resource assignments, and reconciling planned versus executed quantities.

  • Retrieve pending tasks for a wave: SELECT TASK_ID, ITEM, TRANSACTION_QUANTITY, STATUS, PRIORITY FROM WMS.WMS_WAVEPLAN_TASKS_TEMP WHERE WAVE_HEADER_ID = :wave_id ORDER BY PRIORITY;
  • Trace unassigned work: SELECT TASK_ID, PERSON, MACHINE_RESOURCE_CODE, DISPATCHED_TIME FROM WMS.WMS_WAVEPLAN_TASKS_TEMP WHERE PERSON_ID IS NULL AND STATUS = 'PENDING';
  • Join to operation plans to see routing context: SELECT t.TASK_ID, p.OPERATION_PLAN, t.DEPARTMENT_ID FROM WMS.WMS_WAVEPLAN_TASKS_TEMP t JOIN WMS.WMS_OP_PLANS_B p ON p.OPERATION_PLAN_ID = t.OPERATION_PLAN_ID;

Reporting should treat these rows as volatile; production analytics normally read from the consolidated task tables after the wave commits.

Related Objects

  • MTL_TXN_SOURCE_TYPES — joined on TRANSACTION_SOURCE_TYPE_ID to classify the origin of the transaction.
  • BOM_DEPARTMENTS — joined on DEPARTMENT_ID to identify the responsible department.
  • WMS_OP_PLANS_B — joined on OPERATION_PLAN_ID to link tasks to their operation plan definition.
  • WMS_WAVEPLAN_TASKS and related task tables — the persistent destination of staged task rows after wave release.
  • MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID for item attributes.
  • WMS_LPN_SERIAL_NUMBERS / LPN master tables — joined on ALLOCATED_LPN_ID, TO_LPN_ID, and PICKED_LPN_ID for license plate context.
  • WMS Task Dispatcher / Wave Planning concurrent programs — the business processes that insert and consume these staging rows.