70

Could we have some sort of automation for configuration so we don't have to add extra lines to the Location directive action queries just to filter out locations that are blocked for inbound/outbound? e.g. a tick-box on Location directive actions "Use location blocking codes". Would just add a line to the query. Or alternatively a global parameter (or per warehouse) which enforces this.


Simple but would save precious setup hours as we currently need to do this manually on ALL put actions.

STATUS DETAILS
New

Comments

N

Agree would be really good to have this function on, so we don't have to add more and more location directives.

Category: Warehouse management

N

Agree with below comments

Category: Warehouse management

N

Had to do this twice as a customization so there are definitely customers with this need.

Category: Warehouse management

N

Agree with Simon, we need policies that can be added at the Line and Action levels rather than re-keying in the same information time and time again! I suggest this be a separate idea.

For location blocking this should be system enforced for whatever movement is done. Ad-hoc movements would not be blocked with my suggestion. We need a hard block for all movement types. I suggest adding a field to the Blocking causes table to define causes that block WHS movements.

Category: Warehouse management

N

I would go further and restructure the location directive form so that the middle and bottom sections are decoupled from the directive - this allows them to be reused - reducing the mammoth amount of work required in configuring any warehouse with moderate complexity.

Category: Warehouse management