Search Results wms_dispatched_tasks




Overview
Explore in AI Chat

Overview

The WMS_DISPATCHED_TASKS table is a core transactional data object within the Oracle E-Business Suite Warehouse Management (WMS) module. It serves as the central repository for all tasks that have been dispatched to warehouse personnel or equipment for execution. The table's primary role is to track the lifecycle of a work assignment from the moment it is released from the planning engine to its final completion or cancellation. It is integral to the real-time operational control of warehouse activities, enabling task management, status monitoring, and exception handling within the WMS task dispatcher framework. The table's design, with foreign key relationships to inventory, resources, and personnel tables, ensures data integrity and provides the necessary context for each dispatched unit of work.

Key Information Stored

The table's structure is designed to capture the essential attributes of a dispatched task. The primary key, TASK_ID, uniquely identifies each task record. Critical contextual columns include ORGANIZATION_ID, linking the task to a specific inventory organization, and EQUIPMENT_INSTANCE or EQUIPMENT_ID for tasks assigned to material handling equipment. For personnel assignments, PERSON_ID (linked to HR records) and PERSON_RESOURCE_ID or MACHINE_RESOURCE_ID (linked to manufacturing resources in BOM_RESOURCES) are pivotal. The table also tracks temporal data through EFFECTIVE_START_DATE and EFFECTIVE_END_DATE for personnel assignments. While the provided metadata does not list all columns, the foreign key relationships imply the storage of data pertaining to the specific work instruction, such as source and destination locations, item details, and task quantities, which are typically inherited from the parent task definition.

Common Use Cases and Queries

This table is central to operational reporting and troubleshooting in WMS. Common use cases include monitoring open task backlogs, analyzing worker or equipment productivity, and investigating task-related exceptions. A fundamental query retrieves all active dispatched tasks for a given organization to provide a real-time work dashboard. For performance analysis, one might join with PER_ALL_PEOPLE_F or BOM_RESOURCES to report on tasks completed per operator or resource over a period. When tasks fail or are skipped, the related WMS_EXCEPTIONS and WMS_SKIP_TASK_EXCEPTIONS tables are queried alongside WMS_DISPATCHED_TASKS using TASK_ID to diagnose issues. A typical pattern for finding dispatched tasks for a specific person would be:

  • SELECT * FROM WMS_DISPATCHED_TASKS wdt
  • WHERE wdt.PERSON_ID = :p_person_id
  • AND SYSDATE BETWEEN wdt.EFFECTIVE_START_DATE AND NVL(wdt.EFFECTIVE_END_DATE, SYSDATE);

Related Objects

The WMS_DISPATCHED_TASKS table exists within a tightly integrated schema. Its primary key is referenced by the WMS_EXCEPTIONS and WMS_SKIP_TASK_EXCEPTIONS tables, which log deviations from the normal task flow. It draws master and contextual data from several key tables via foreign key constraints: MTL_PARAMETERS for organization parameters, MTL_SERIAL_NUMBERS for equipment instance details, BOM_RESOURCES for manufacturing resource definitions, and PER_ALL_PEOPLE_F for human resources information. This table is a primary source for the WMS task dispatcher user interface and is heavily utilized by internal WMS APIs and concurrent processes responsible for task creation, assignment, and status updates. Understanding these relationships is crucial for developing custom integrations or extracting meaningful operational data.