Search Results wms_dispatched_tasks_histor_u1

Overview

WMS.WMS_DISPATCHED_TASKS_HISTORY is an Oracle E-Business Suite warehouse management table owned by the WMS schema. It functions as the history (archive) counterpart to WMS_DISPATCHED_TASKS, storing information about all warehouse tasks that have been completed. In Oracle EBS 12.1.1 and 12.2.2, this object resides in the APPS_TS_TX_DATA tablespace and is registered under FND Design Data as WMS.WMS_DISPATCHED_TASKS_HISTORY with status VALID. The table is one of the principal sources for auditing and reporting on executed warehouse activity, capturing both the operational context of a task and the material transaction it produced.

Metadata mining of the foreign key structure suggests a Data Vault classification of link. This is a modeling suggestion, reflecting that the table chiefly records associations between business entities—people, resources, organizations, inventory items, and transactions—rather than serving as a standalone hub. The table carries 68 documented columns, an extensive descriptive attribute set, and 13 documented indexes, of which one is unique.

Key Information Stored

The surrogate primary key is TASK_ID, which is also the single column of the unique index WMS_DISPATCHED_TASKS_HISTOR_U1. That unique constraint is therefore the primary business-key candidate for row-level identification, and it makes TASK_ID the most reliable join and lookup predicate.

• TASK_ID — primary key and unique index column; identifies the completed task.
• TRANSACTION_ID — links the historical task to the material transaction it generated.
• ORGANIZATION_ID — the inventory organization in which the task was executed.
• USER_TASK_TYPE — the standard operation ID describing the type of task performed; indexed non-uniquely.
• PERSON_ID — the employee who performed the task; indexed together with the effective dates.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — task start and end timestamps, forming the dated component of the PERSON_ID index.
• PERSON_RESOURCE_ID and MACHINE_RESOURCE_ID — the labor and equipment resources consumed.
• EQUIPMENT_ID and EQUIPMENT_INSTANCE — equipment used and the specific serialized instance.
• DISPATCHED_TIME, LOADED_TIME, and DROP_OFF_TIME — timestamps tracing the task through its lifecycle; DROP_OFF_TIME is indexed for elapsed-time analysis.
• INVENTORY_ITEM_ID, REVISION, TRANSACTION_QUANTITY, and TRANSACTION_UOM_CODE — the item and quantity moved, supported by LPN_ID, CONTENT_LPN_ID, and TRANSFER_LPN_ID.
• STATUS and TASK_METHOD — outcome and execution mode of the task.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY — standard EBS audit columns; LAST_UPDATE_DATE is indexed with ORGANIZATION_ID.

Common Use Cases and Queries

Primary applications include warehouse labor productivity reporting, task throughput and cycle-time analysis, and audit reconciliation between completed tasks and inventory transactions. The composite indexes are designed to accelerate precisely these queries: WMS_DISPATCHED_TASKS_HISTOR_N1 supports per-person productivity over a date range, N3 supports drop-off timing analysis, and N9 supports item/transaction/status lookups scoped to an organization.

A representative query retrieves completed tasks for a person over a period:

• SELECT task_id, user_task_type, dispatched_time, drop_off_time, transaction_quantity FROM wms.wms_dispatched_tasks_history WHERE person_id = :person_id AND effective_start_date >= :from_date AND effective_start_date < :to_date;

Cycle-time reporting by task type uses the DISPATCHED_TIME and DROP_OFF_TIME columns, grouped by USER_TASK_TYPE. Reconciliation joins to MTL_MATERIAL_TRANSACTIONS on TRANSACTION_ID to validate that each completed task produced a matching inventory transaction. Organization-scoped extraction commonly filters on ORGANIZATION_ID and LAST_UPDATE_DATE, matching index N8.

Related Objects

The documented foreign keys identify the following significant relationships:

• MTL_MATERIAL_TRANSACTIONS — joined on TRANSACTION_ID; the inventory transaction resulting from the task.
• MTL_SERIAL_NUMBERS — joined on EQUIPMENT_INSTANCE for serialized equipment.
• MTL_PARAMETERS — joined on ORGANIZATION_ID for inventory organization context.
• BOM_RESOURCES — referenced twice, via PERSON_RESOURCE_ID and MACHINE_RESOURCE_ID.
• PER_ALL_PEOPLE_F — joined on PERSON_ID for the operator's person record.
• WMS_OP_PLANS_B — joined on OPERATION_PLAN_ID for the originating operation plan.
• MTL_TXN_SOURCE_TYPES — joined on TRANSACTION_SOURCE_TYPE_ID for transaction origin classification.

WMS_DISPATCHED_TASKS_HISTOR_N5 on OPERATION_PLAN_ID and MOVE_ORDER_LINE_ID, together with N12 on SOURCE_DOCUMENT_ID, additionally points to move order and source document flows used by WMS-directed operations. Together these relationships make the table a central link between warehouse execution, inventory transaction, and resource accounting data.