WMS Picking Trick

koalado

We are now implementing Warehouse module. What's the logic of Navision for picking? We prefer to use FIFO(First In First Out). How to reach the goal? Many thanks.

kriki

I think it is enough to put the "Costing Method" of the items as FIFO.

bbrown

The warehouse picking process has no relationship to the costing method or the order in which inventory was received. The system selects based on bin ranking and bin code order. If new inventory has been placed in a bin higher in the selction, then Navison will suggest picking it.

koalado

Yeah, I agree with bbrown.
Here's an example: we finished 3 production order and put-away finished goods to different bins on different days.

---

Item No. Qty Bin Put-away Date

---

P-001 100 B-700 2006-01-01
P-001 200 B-800 2006-01-05
P-001 300 B-900 2006-01-09

---

On 2006-01-20, I hope to ship 300 P-001. Navision will suggest us to pick from "B-900" but not "B-700"&"B-800" which we put-away to inventory early.
So, It seems that to achieve our goal, we have to either manage picking action by input the bin code manually or find out all pick-related actions (movement, bin replenishment, internal pick, whs Item journal, whs Item reclassification, ship...) in Navision to do the customization, right? ](*,)
for Put-way, Navision has "Put-away template" logic, but for Picking, it seems that there's no such a logic to support "FIFO".

bbrown

A common modification I see with WMS is to use lot tracking and modify the picking process to select based on lot age.

Also Navision will post to inventory in FIFO. In the example from Koalado, even though the item from bin B-900 (2006-01-09) is picked, Navision will apply the sale to the production output from 2006-01-01 (Bin B-700).

ataris

We have developed this area quite abit. Ours looks at SO and lists items which are in the warehouse and ready to go and picks from whatever location and bin these items are in. This allows our customers to get there stock in and out quickly.

There are some checks as to which bin would be best for example if bin A has more items in bin B it will take out bin A first before bin B.

mickuk

We have also come across this problem. We do not use the standard bin locations within our system (a previous employee of the company designed something very similar called warehouse locations). The same problem exists within this setup where our warehouse staff are taken to the location with the largest quantity of stock. This again works away from the FIFO method as you are continually "waterfalling" your stock down from different bin/warehouse locations.

I have made several modifications to the table that stores the data for the warehouse locations, one of which is a date field which can be checked from a custom report. Another slight hack/work around was to produce a picking list where the warehouse staff are able to see all of the locations that the stock is in along with date. This can be generated from the inventory->stock transfer section of our system.

I'm not sure if there is a date field within the bin locations table which you could use? This way you could raise stock requests from the bin location which has the oldest entry date?

kriki

bbrown wrote:

The warehouse picking process has no relationship to the costing method or the order in which inventory was received. The system selects based on bin ranking and bin code order. If new inventory has been placed in a bin higher in the selction, then Navison will suggest picking it.

Oops, I alway thought that when using FIFO or LIFO, the entry-applying was also done in this way. :oops:

bbrown

Kriki wrote:

Oops, I alway thought that when using FIFO or LIFO, the entry-applying was also done in this way

FIFO or LIFO (or other choice) applies to the way in which the sales are applied to the open positive Item Ledger Entries. Using warehouse does not change this. Taken strictly in the context of table 32 (Item Ledger Entry), the above statement is true.

However, the costing method does not contol the order in which product is pulled from bins.

koalado

Finally I solved the problem via Item Tracking. Default bin content doesn't include Lot/Sn info, so I create a new table including realted tracking info. The final edition shows Location/Bin/Item/Lot/Total Qty/Varience/Entry No./ Coming Exp.Date/ Last Entry No./ Last Date Used.... then warehouse keeper can do FIFO according to Last Date Used.