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] So if 10 units of a product with serial number needs to be sold: 1. The lot numbers against each stock.move could be stored in this table. 2. The state change from Assigned to Packed is stopped with an exception if there are not enough lot numbers against the move in the stock.move.lots table For extended applications, which need to constrain quantity in each batch, they could inherit and modify the validation step which checks for existence of the lots to check for availability also. Thanks, Sharoon Thomas Director & CEO, Openlabs Technologies & Consulting Pvt Limited Regd Office: 2J-Skyline Daffodil, Trippunithura - Kochi - IN 682013 Mobile: +1 786 247 1317 http://openlabs.co.in
signature.asc
Description: Message signed with OpenPGP using GPGMail
