Comment 3 for bug 670451

Revision history for this message
Tamás Dénes (tamas-denes) wrote : Re: [trunk][stock and mrp] LOT traceability is broken

Hello Nhomar!

Thanks for such fast response!
I think the possibility to deal with three kind of tracking options independently is conceptually wrong. It's even not usable in real life.
Try it Yourself:
1. Check "Track incoming LOTs" only for a product.
2. Buy 10 PCE from this product. So You have 10 PCE in LOT 0000001 now.
3. Buy 5 PCE from this product again with another LOT. So You have 10 PCE in LOT 0000001 and 5 PCE in LOT 0000002 now.
4. Sell 2 PCE from this product without LOT.
5. You have 10 PCE in Stock with LOT 0000001, 5 PCE in stock with LOT 0000002 and You have -2 PCE in stock with LOT 'Undefined'.

Have You expected this?

The fact is that the implementation is fine. You have to manage stocks with LOTs and without LOTs independently. Otherwise how could the software found out from which LOT should it fulfill Your Sale Orders? From LOT 0000001? Or from LOT 0000002? So it is implemented correctly according to the concept.

So my opinion is that the concept of 3 independent tracking options is fundamentally wrong. If You want to manage LOTs for a product You have to do it from beginning to the end.

But there is a chance that I don't know something what would prove the present functionality. So please show me the use case for that three kind of tracking options if there are any.

In my opinion there should be only one single tracking option for the product and it should include moves between physical locations and not just moves between physical and virtual locations.

In the present state the software manages internal moves similarly to the above example. There is no way to make the "Production LOT" attribute mandatory for internal moves. (There is no such option on the product form)

Anyway I have had the chance to extensively test some other commercial ERP softwares and there are only one tracking option for products in these softwares. (Namely the Italian Mago.Net and the German ABAS).