Minimum Version Required: 22.01
Pre-Conditions
User must have bin inventory edit permission
Products, source bins, and target bins must already exist in the system
Sufficient inventory must be available in source bins when creating move task transactions
Valid location identifiers must be used
WMS Move Task Type must be a valid value (Replenish, PutAway, Move, DynamicPick, or Slotting)
Steps
EDBL Routines Disclaimer: This EDBL routine represents advanced functionality primarily intended for use by Encompass technical staff. While technically proficient customers may utilize these routines, please be aware that they fall outside the scope of standard support. Assistance with EDBL routines is not covered under standard support agreements and may require billable services from our Professional Services team. Please ensure you thoroughly understand this routine before implementation in your production environment
The WMSMoveTaskOrTaskTransAdd routine enables you to create new WMS Move Tasks and add associated Task Transactions.
This import routine supports two main scenarios:
Adding transactions to an existing WMS Move Task (by providing WMSMoveTaskID)
Creating new WMS Move Tasks with transactions (by providing LocationID and WMSMoveTaskType)
This routine only executes for "Add Only" or "Update or Add" import actions. It will not process data with "Update Only" action.
When creating new task transactions, the system validates that sufficient inventory exists in the source bin before proceeding. If inventory is insufficient, those transactions will be skipped.
For each valid record in your import file, the system will:
Create a new WMS Move Task (if providing LocationID/WMSMoveTaskType)
Add task transactions to the move task
Associate proper bin information and product quantities
Set proper task statuses
Fields And Definitions
When adding transactions to existing tasks (Scenario 1):
WMSMoveTaskID: The ID of the existing move task to add transactions to
ProductID: The product to be moved
FromBinID: Source bin identifier
ToBinID: Destination bin identifier
NumUnits: Quantity of product to move
PurchaseTransID: Optional purchase transaction reference
LicensePlateID: Optional license plate identifier
When creating new move tasks (Scenario 2):
LocationID: The location where the move task will be created
WMSMoveTaskType: Type of move task (determines behavior)
AssignedToUserID: User assigned to the task
WMSReplenishPlanID: Optional reference to a replenishment plan
LoadSequence: Optional sequence number for load ordering
ProductID: The product to be moved
FromBinID: Source bin identifier
ToBinID: Destination bin identifier
NumUnits: Quantity of product to move
PurchaseTransID: Optional purchase transaction reference
LicensePlateID: Optional license plate identifier
Best Practices
Always verify your source bins have sufficient inventory before creating the import file
Group records by WMSMoveTaskType when creating new tasks to ensure efficient processing
When adding to existing tasks, verify the WMSMoveTaskID is valid and in an appropriate status
For better traceability, include PurchaseTransID when available
Include LicensePlateID when moving entire license plates rather than loose inventory
Ensure NumUnits is properly formatted and matches your inventory unit expectations
Location-specific bin references should be validated prior to import
Consider breaking large imports into smaller batches for better performance and error tracking