Search Results insert_task

Overview

APPS.WMS_TASK_DISPATCH_GEN is a core Warehouse Management System (WMS) PL/SQL package in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to generate, dispatch, and confirm warehouse execution tasks — principally picking, put-away, and pick-drop operations — that drive material movement within the warehouse. The package is classified as an API of type OTHER, meaning it exposes public program units used internally across the WMS module rather than a formally published open interface. It is a VALID object owned by the APPS schema, and it depends on the FND_API foundation package and the SYS.STANDARD package, indicating that it leverages Oracle Application Object Library error-handling and standard PL/SQL constructs in its implementation.

Because it is referenced by ten other packages, WMS_TASK_DISPATCH_GEN acts as a shared task-dispatch engine, centralizing the logic by which WMS task execution records are created and progressed across mobile and desktop warehouse flows.

Key Procedures and Functions

The documented interface exposes 35 program units. The principal units include NEXT_TASK and NEXT_CLUSTER_PICK_TASK, which select the next available picking task — including cluster picking — for a warehouse operator. Task creation is handled by INSERT_TASK, and completion by COMPLETE_PICK and PICK_DROP. Supporting LPN processing includes CREATE_LPN, CHANGE_LPN, LOAD_PICK, LPN_MATCH, VALIDATE_PICK_TO_LPN, and MULTIPLE_LPN_PICK, which govern license plate number handling during pick and drop. Quantity and item logic is provided by GET_LPN_LOT_QTY, GET_PRIMARY_QUANTITY, PROCESS_LOT_SERIAL, and MULTIPLE_PICK, while CAN_PICKDROP validates whether a pick-drop operation is permitted. INSERT_MMTT_PACK writes to the material transaction temp structures. PICK_BY_LABEL and MANUAL_PICK support label-driven and manual picking scenarios. MYDEBUG is a diagnostic utility. Parameter lists are intentionally not specified here; callers must consult the package specification for exact signatures.

Tables Accessed

Through APPS synonyms the package reads and writes core inventory and warehouse tables. On-hand and reservation data are drawn from MTL_ONHAND_QUANTITIES_DETAIL and MTL_RESERVATIONS; transaction records are staged through MTL_MATERIAL_TRANSACTIONS_TEMP and committed via MTL_MATERIAL_TRANSACTIONS_S. Location, subinventory, and item control data come from MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, and MTL_PARAMETERS. Lot and serial controlled items are handled through MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, and MTL_SERIAL_NUMBERS_TEMP. Cycle counting is supported via MTL_CYCLE_COUNT_HEADERS and MTL_CYCLE_COUNT_ENTRIES. Resource-related tables BOM_RESOURCES, BOM_RESOURCE_EQUIPMENTS, and BOM_STD_OP_RESOURCES tie tasks to warehouse equipment and resources.

Usage Notes

WMS_TASK_DISPATCH_GEN is invoked indirectly rather than directly by end users. Its documented callers include WMA_INV_WRAPPERS, WMS_PICKING_PKG, WMS_DEVICE_CONFIRMATION_PUB, WMS_PUTAWAY_UTILS, WMS_TASK_DISPATCH_PUT_AWAY, WMS_ATF_RUNTIME_PUB_APIS, WMS_EXPRESS_PICK_TASK, WMS_LPN_LOVS, WMS_PICK_DROP_PVT, and WMS_TXNRSN_ACTIONS_PUB. These are typically exercised through WMS mobile radio-frequency (RF) pages, the warehouse execution forms, and concurrent task-dispatch processing. Customizations should call the package's public APIs only and avoid referencing the package body directly, since internal signatures may change across point releases. Because it interacts with MTL_MATERIAL_TRANSACTIONS_S, all operations should be performed within appropriate transaction control and access to the MTL and BOM tables should be granted through standard APPS synonyms.