I’m facing the following problem: when I run “Create Pick” code unit from “Pick Worksheet” if I have the same item in two different location called for example A0001 and A0014 Navision suggests me first the location A0014 because follows a descending alphabetical order. By me it wolud be more useful following an ascending alphabetical order and the location I expected it was suggest me was A0001.
Do you know why?
You can change this behavior by ranking your bins. Navision picks from the bin with the highest ranking first (I also find it a bit odd that Navision uses descending order to pick when the bins have the same ranking).
To solve you problem go to Administration → Application Setup → Warehouse → Locations → Locations (bottom) → Bins. Show the hidden field and change for A0001 to a higher value than A0014.
first of all I want to thank you for answering me.
I knew “Bin Ranking” functionality, but I’m not really convenced in using it. Think of a very complex warehouse where I have many shelfs with many levels and bins. Is difficult for me to fix a single ranking number for each location in order to define an optimized route. I would have preferred an ascending alphabetical order in “create pick” and codify my location taking care of route. Do you agree?
Anyway I am not a warehouse expert but I can understand you find the ascending order odd. The technical reason for this is that Navision uses a FIND.(‘-’) to find the bin in C7312, function FindPickBin and the records need to be sorted ascending to find the record with the highest .
Why is it difficult for you to rank your bins in opposite order of the Bin Code sorting (just start with a high number and decrease with 10 in case you need to create new bins later)?
I think the best solution for you would be to rank your bin even thought this is a big task in a big warehouse.
Another approach is to modify the bin table to include a pick sequence and then alter the picks to print in this order. In other words although you have aisles A-Z with levels and positions the pick sequence is numerical to define the route - so you go to A1, then B1, which is opposite, and not A2. I am aware we have altered the system in this manner when integrating with HHT’s. It is an option you may want to consider.
thanks to everybody: the solution that Tony has suggest me about customization is exacltly what I’ve done. It seems to fit. The reason why I’ve opened this case on support was to understand why this CU have been developed with “ASCENDING(FALSE)” instead of “ASCENDING(TRUE)”. It seems that is a precise intention of the developer to define a descending order taht for me is since now still a mistery!