AUTOMATICALLY LOCK LPN AFTER SYSTEM DRIVEN ALTERNATE LOCATION DURING PICKING

Summary:

During picking full LPN, in 23D the new functionality allows users pick an alternative LPN (RF ctrl+F) which then cancels the allocation and allocate a new found LPN for the order. The cancelled LPN is brought back to "located" status in the same location making it available for allocation when another wave run for the same item. Is there a way to automatically lock when system driven alternative location during pick is used so that it is skipped for allocation otherwise users are sent to the same location multiple times unless we manually lock the LPN?

We cab set the triggers to trigger a cycle count task when this action is done but that depends on how long it takes for a user to go and cycle count the location, in the mean time it can allocate to another order.