A Dijous, 26 de gener de 2012 15:16:06, Cédric Krier va escriure: > On 26/01/12 08:35 -0500, Sharoon Thomas wrote: > > On Jan 26, 2012, at 7:53 AM, Cédric Krier wrote: > > > 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. > > > > I agree with cedk here and the basic module should just provide that. > > Probably the only constraint it should offer is ensure there are > > lot/batch numbers for products which are required to have them. > > > > I would prefer to have the serial numbers/lots on a separate table and > > not stock.move with the following structure. > > > > stock_move (m2o) > > quantity > > lot (m2o) [Agree with cedk's concept of product.lot against product] > > I think such design will give a bad UX. > I prefer to split stock moves when needed and a simple concept of modulo > on stock move quantity could make the job.
I agree it gives a bad UX. At the same time, I must admit that when working with serial numbers, splitting the lines can also be cumbersome. We've got a customer that can create a production of more than a thousand units and that creates shippments with a large number of lines. So if we found a good way of managing it, maybe Sharoon's idea would not be so bad. One idea would be to have two One2Many widgets in the shippment and once the user selects a stock.move line the second One2Many field is filled in with all related lots? -- 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
