Results for “wms_active_tasks_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WMS_ACTIVE_TASKS_V is a seeded, read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is shipped as part of the Warehouse Management (WMS) product and presents the set of currently active warehouse tasks that have been dispatched against pending material transactions. Conceptually, the view joins dispatched task records to the material transaction staging area so that both the demand (the transaction to be performed) and the resource assignment (the dispatched task) are visible through a single query surface.

The name of the view reflects its intended use: it returns work that is "active" in the sense that it has been routed to a warehouse resource — a person, piece of equipment, or machine — but has not necessarily been completed or purged from the temporary transaction tables. Because it exposes the raw transactional and dispatch attributes together, WMS_ACTIVE_TASKS_V is commonly used as the reporting and integration foundation for custom inquiries, mobile/warehouse dashboards, label and pick-list generation, and downstream interfaces that need to observe in-flight warehouse execution. Oracle does not document this view as an officially supported public API; consumers should treat its column list as internal and version-dependent.

Underlying Base Objects

The view is defined over the WMS dispatch and inventory cycle-count tables, accessed through APPS synonyms. The documented referenced base objects are:

• WMS_DISPATCHED_TASKS — holds the dispatched task header, including the assigned resource, task status, dispatch, load, and drop-off timestamps, priority, and the descriptive attribute columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15).
• MTL_MATERIAL_TRANSACTIONS_TEMP — the temporary material transaction interface table that carries the transaction type, transaction action, source, item, revision, subinventory, locator, quantity, and UOM for the pending movement.
• MTL_CYCLE_COUNT_ENTRIES and MTL_CYCLE_COUNT_HEADERS — the physical inventory/count tables, contributing the second UNION ALL branch of the view that surfaces cycle-count related tasks.

The primary branch joins WMS_DISPATCHED_TASKS to MTL_MATERIAL_TRANSACTIONS_TEMP on TRANSACTION_TEMP_ID, additionally constraining WDT.TASK_TYPE to MMTT.WMS_TASK_TYPE and restricting MMTT.PARENT_LINE_ID to NULL. The cycle-count branch is combined with UNION ALL, so a single result set presents both movement tasks and counting tasks.

Key Columns

The view exposes a merged column list rooted in the two branches. Important columns include:

• TRANSACTION_TEMP_ID — from the transaction staging table; the join key to the dispatched task and a primary handle for the pending transaction.
• TRANSACTION_ACTION_ID and TRANSACTION_TYPE_ID — identify what action and transaction type the task represents (for example, a move or pick). The commented-out transaction_action search term maps directly to the TRANSACTION_ACTION_ID attribute.
• TASK_ID — the dispatched task identifier, used to track and update execution status.
• STATUS — the task status, defaulted to 1 via NVL(WDT.STATUS, 1) when no dispatch status is recorded.
• PERSON_ID, PERSON_RESOURCE_ID, MACHINE_RESOURCE_ID, EQUIPMENT_ID, EQUIPMENT_INSTANCE — the assigned resource details.
• DISPATCHED_TIME, LOADED_TIME, DROP_OFF_TIME — execution timestamps for the task lifecycle.
• INVENTORY_ITEM_ID, REVISION, SUBINVENTORY_CODE, LOCATOR_ID, TRANSACTION_UOM, TRANSACTION_QUANTITY — the item and location context of the movement.
• PICK_SLIP_NUMBER, MOVE_ORDER_LINE_ID, CARTONIZATION_ID, ALLOCATED_LPN_ID, CONTAINER_ITEM_ID — fulfillment and LPN context carried through from the transaction.
• PRIORITY, USER_TASK_TYPE, TASK_TYPE — task classification and sequencing attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The view is typically queried to monitor outstanding warehouse work, to reconcile dispatched tasks against their underlying transactions, and to join task activity to item and resource master data.

• Listing all active tasks for an organization, showing item, action, and assigned person or equipment.
• Reporting task status and dispatch versus drop-off lag for throughput analysis.
• Feeding custom mobile or dashboard interfaces that require both transaction and dispatch context in one row.
• Filtering tasks by TRANSACTION_ACTION_ID to isolate a specific action (for example, picking versus replenishment).

A representative query:

SELECT v.TASK_ID,
       v.ORGANIZATION_ID,
       v.INVENTORY_ITEM_ID,
       v.TRANSACTION_ACTION_ID,
       v.TRANSACTION_TYPE_ID,
       v.TRANSACTION_QUANTITY,
       v.TRANSACTION_UOM,
       v.SUBINVENTORY_CODE,
       v.LOCATOR_ID,
       v.STATUS,
       v.PERSON_ID,
       v.EQUIPMENT_ID,
       v.DISPATCHED_TIME,
       v.DROP_OFF_TIME
  FROM APPS.WMS_ACTIVE_TASKS_V v
 WHERE v.ORGANIZATION_ID = :org_id
   AND v.STATUS IN (1, 2)
 ORDER BY v.DISPATCHED_TIME;

Because the view performs a UNION ALL over tasks and cycle counts, filters on columns that are populated in only one branch (such as TASK_ID or CYCLE_COUNT_ENTRY_ID) will implicitly restrict the result to that branch. This behavior is useful when segregating movement tasks from counting tasks.