On 25/01/12 14:43 +0100, Bertrand Chenal wrote: > Le Wed, 25 Jan 2012 13:45:25 +0100, > Cédric Krier <[email protected]> a écrit : > > > > - "Adapt assign_try() and pick_product() to take 'lot' field into > > account." > > > > I'm not sure this is good. For me, lot is more like a tag on moves > > and it should not prevent to validate the move. > > IMO there is at least two use case for lots: > A) I have a problem with a sold product, I want to trace back where it > comes from. > B) My products are not homogeneous (like wine, whiskey, fragrance, ...) > and I let my customer pick the exact lot he want. > > For case A I agree that it's just a tag. But not for case B. Do we want > to support case B? Is there any use case for lots?
Is not it a variant instead of a lot? Because if you consider that the product sets is not homogeneous, I think it is not a product (in the Tryton meaning). > > Also I think such behavior will be very resource consuming. > > I'm not sure but I think it's just a matter of changing > > GROUP BY to_location, product > > to > > GROUP BY to_location, product, lot > > in the products_by_location method, except that it must be done > through inheritance. Or update stock module to take care of lot with a default lot NULL. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpCBx4h4rX8p.pgp
Description: PGP signature
