A Dijous, 26 de gener de 2012 13:53:34, Cédric Krier va escriure: > On 26/01/12 13:50 +0100, Bertrand Chenal wrote: > > Le Thu, 26 Jan 2012 13:33:55 +0100, > > > > Cédric Krier <[email protected]> a écrit : > > > On 26/01/12 13:26 +0100, Albert Cervera i Areny wrote: > > > > A Dijous, 26 de gener de 2012 13:24:44, Cédric Krier va escriure: > > > > > > I agree that caching per location and per lot is not a good > > > > > > idea. > > > > > > > > > > > > So, new proposal: > > > > > > > > > > > > > > > > > > a naive product_by_lot function will be slow, so we need > > > > > > caching. As lots are a bit like temporary locations, > > > > > > > > > > If so, why not use location instead of lot? > > > > > > > > Because you can have several products with different lots in the > > > > same location :) > > > > > > This is not an answer. If you consider that a lot is like a temporary > > > location than you can not put different lots in the same location. > > > > 1) I was talking about caching, noting else. > > 2) Your answer looks like you think that the concept of lot is > > completely non-needed, what's your point of view? > > I think lot management is just about information and nothing more. > All cases, where people think they can be solved by using restrictive lot > management, can be solved differently.
In fact, it's about traceability. I need to be able to know that the 3 units of product A that I sold with lot 1112 was composed (once we've got prodution ;-) of 5 units of product B with lot 782 and 5 units of product C with lot 818 (2 units) and 551 (3 units). Product B with lot 782 has supplier reference YYUI889 and was recevied from supplier S1 on 30/12/2011. They were stored until 05/01/2012 on location L1 and later moved to L2 until 20/01/2012 when they were finally used for production. Etc, etc. I also need to know how many units of each product (A, B and C) I have available and how many units I have of each of their lots and were they are located. As mentioned, I also need to know were they have been located at each given time. I think the only way to manage this is by adding a new field in stock.move called produt_lot which points to (Many2One) a new model called product_lot or so. Given that we've discussed several things, I'm not sure we agree on that or not. -- Albert Cervera i Areny http://www.NaN-tic.com Tel: +34 93 553 18 03 http://twitter.com/albertnan http://www.nan-tic.com/blog -- [email protected] mailing list
