The issue is that we need a restriction for the put away in the system. This is true for a lot of different work types.

Right now we are handling that with the valid put location on the work class. But the system is only checking the valid put location on the override function during the put process.

If we do not set up a location directive there is no check for the location type in the work class. Same is true if we set up a location directive with an invalid location.

If we set up a correct location directive the worker has to override the put location every time because the customer is not able to define a strategy for location stocking limits. The system will always suggest the 1st location of the type set in the location directive (valid put location is also not working here).

If the user is using the overwrite he has to define a reason. This takes some time to do the process but it adds up quickly if a lot of material is moved).

The product team of MS has already product team has reviewed it. While they have identified it as a product limitation, they do have an internal deliverable in place to address it

If you are facing the same challenge, your vote would certainly help accelerating the fixing process.

Thanks and best regards,

Dieter