← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 670451] 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).

-- 
[trunk][stock and mrp] LOT traceability is broken
https://bugs.launchpad.net/bugs/670451
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: Opinion
Status in OpenObject Addons 5.0 series: Confirmed
Status in OpenObject Addons trunk series: Opinion

Bug description:
Product traceability works only in the simplest cases: When You buy product and sell them from the same location.
But if internal moves or manufacturing operations are involved then traceability can't be guaranteed or even impossible.

The one single reason for this is that there is no way to set "Tracking moves between physical locations" on products. You can track only incoming, outgoing and manufacturing LOTs: The ones from and to virtual locations but not between physical locations.
Doing internal moves the system don't force the usage of LOTs even if all tracking options is checked for a product.

The worst case is when You use mrp module for managing Manufacturing operations:
Two sets of stock.move object is generated when You click on "Confirm Production" in a Manufacturing Order. One set is for Consuming Products on which You are forced to set LOTs (when "tracking manufacturing LOTs"  option is checked on the product). The other set of stock.move object (a picking list) is done behind the scenes. Since these (hidden) moves are internal moves and done automatically LOT assignment is not forced.

The effect is that the system moves the raw materials from Stock to the Work Center Location without LOT. Then when the user tries to set LOTs on the products to consume (from the Work Center Location to the virtual Production location) a warning message is shown: "Bad LOT assignation. You are moving 5 products but only 0 available in this lot." The available quantity turns to negative and the shortage is increasing by every Manufacturing Order.

The work around is to set the LOTs on both the products to consume and the internal picking list. But it's not forced by the system (so no guarantied) and is even a lot of unnecessary work. Imagine to do it on 20 ingredients: 2x20=40 LOT assignment. You have to set the same LOT on every two related moves one by one. Double work for nothing to gain. But certainly it's not intuitive.

Anyway I don't understand why are there 3 options for tracking LOTs? And it's even don't cover all the possibilities. So either there should be a 4th option to track internal moves or there should be only one to track all moves for a LOT (as in some other ERP systems)

As I know LOT tracking is for traceability. So what is the purpose of the possibility of partial LOT tracking? (only incoming or only outgoing) What useful information can You get from them? For product traceability You need to track all LOT moves.

While OpenERP is a promising product it's not yet usable in Food, chemical and pharma manufacturing industry where LOT management and full traceability is vital.

In essence two development would be needed:
1. Ability to track internal moves (Preferably with one single option on products for all LOT tracking)
2. In Manufacturing orders to automatically copy the LOT attribute from the products to be consumed to the internal picking list. (So that the user should not have to repeat the LOT assignment and tracking would be guarantied)







References