Adding selective moves options
A sequence of move tasks is created to move inventory to the final destination according to configured pick and drop location restrictions.
At any time, a pick and drop location can contain a number of pallets, either relating to putaways or to replenishments. Because these pallets can be physically stacked in any sequence within the pick and drop locations, inefficiency problems can arise if RF moves are completely application-directed according to the current Task Manager Move configuration.
For example, the application asks for a specific pallet, which is at the bottom of a stack to be moved first, requiring the fork driver to restack pallets so the pallet requested by the application can be accessed. To overcome this, the Task Manager Move option must be configured so that the RF user can select which pallet ID is accessible. This is similar to the current Task Manager Putaway feature, except that a suggested pallet ID displays. You can then override the suggested pallet ID.
When this happens, the application must re-order the priority of tasks. Users should limit use of the override for this reason. Because you are choosing the work to perform, this overrides any priorities that can be set on the move task, such as moves created as part of replenishment that retain the replenishment priority.
For the Task Manager selective moves feature to work, the following must occur:
- You must have a Task Manager Dispatch Strategy for Selective Moves.
- The Task Manager User must be configured with the following strategy.