ale_baan
14th March 2006, 09:53
Hello,
We have set up picking priorities, and also sequence numbers, per warehouse location. So for example location "A" has priority 996 and sequence 1, whereas location "B" has priority 998 and sequence 2.
- This suggests that, provided both "A" and "B" have stock enough of a certain product, the picking list will suggest "A" as the location from which to take the items.
- But the problem is that in *many occasions* like the above described, Baan proposes to pick the material from "B"; a typical high location and far away location (that's why is low priority).
Anyone able to explain what would be causing this? or if there is an alternative solution to priorities and sequences? Note: already tried "bulk" and "picking" profiles, but this is not the case, both "A" and "B" should be a "picking" location.
Many thanks!
We have set up picking priorities, and also sequence numbers, per warehouse location. So for example location "A" has priority 996 and sequence 1, whereas location "B" has priority 998 and sequence 2.
- This suggests that, provided both "A" and "B" have stock enough of a certain product, the picking list will suggest "A" as the location from which to take the items.
- But the problem is that in *many occasions* like the above described, Baan proposes to pick the material from "B"; a typical high location and far away location (that's why is low priority).
Anyone able to explain what would be causing this? or if there is an alternative solution to priorities and sequences? Note: already tried "bulk" and "picking" profiles, but this is not the case, both "A" and "B" should be a "picking" location.
Many thanks!