On 2015-09-17 15:27, Jesús Martín Jiménez wrote: > Hi, > > 2015-09-17 15:02 GMT+02:00 Cédric Krier <[email protected]>: > > > On 2015-09-17 04:18, Mindaugas Kašalynas wrote: > > > So if I freeze stock.moves with closing periods, new calculations (during > > > stock.move Assign/done process) will not include moves before closing > > date? > > > > It will but only using the cached value and not by summing all the old > > moves. > > > > > We have an issue with stock move locking during assigning / run / done > > > process because of 5-10 users working parallel (we use huge amounts of > > > products (around 10k periodic ones)) and do not use stock period closing > > > still. So process takes long time (few minutes) and during that time > > other > > > users try to do parallel tasks. > > > > That's precisely the goal of the period reduces the computation time > > (and so the locking time). > > Also you should look if you really need the assignation process because > > on large warehouse, assignation is probably not the best management > > solution. Instead using fix places for products can be much more faster > > and user will only record the quantity picked without prior assignation. > > > > Is there any module that implements that way of working?
There is stock_product_location to define the location but I don't think there is a module to remove the assignation (maybe it could be a standard option). -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
