RE:
It would also be useful to have this at load header level, for quick identification of loads which do not have all work creation. This is one of the holes in our release / work creation validation
RE:
Users who frequently move between warehouses bump up against this regularly, and the errors that hint at the problem (eg. LP doesn' exist / seeing an empty lookup) don't directly tell you what the problem is
RE:
We've found this awkward in the scenario where pallets are not labelled. Receive by item would be convenient as can enquire on the transfer order lines but this isn't available where the TRANSIT location is LP controlled. We have worked around it by looking up the LP using the closed work lines for the transfer order pick - however this isn't ideal and the list doesn't shorten as LPs are scanned in
RE:
This would be very useful. We have locations with large numbers of products in them, and it is impractical to have to remember items which are not in location on the system until the end of the location.A counter should be able to process counts in the order in which he physically counts it, regardless of the data-state of the system.
RE:
This is one example of plenty of steps on the WM app which are not value add and add "drag" to its use
RE:
We have ~4k products in quite a small warehouse and operatives do change picking locations on a regular basis especially in the fresh produce area when large deliveries come in due to space constraints. It would be very handy for them to be able to update fixed locations on the warehouse app as they do the rest of their job on a mobile device
RE:
Great idea, that would be very helpful!
RE:
Great Idea!
RE:
This is a singificant limit to the data enquiry functionality, and we've bumped up against it several times in our implementation
RE:
We customised to create a single list page of lines requiring approval - and it was the difference between the count approval functionality being unusable versus it being very useful