credativ team mailing list archive

[Launchpad Bug Tracker <670451@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug by Dmitrijs Ledkovs (credativ) (dle-credativ):

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)

** Affects: openobject-addons
     Importance: Wishlist
     Assignee: OpenERP R&D Addons Team 2 (openerp-dev-addons2)
         Status: Confirmed

** Affects: openobject-addons/5.0
     Importance: Undecided
         Status: Won't Fix

** Affects: openobject-addons/trunk
     Importance: Wishlist
     Assignee: OpenERP R&D Addons Team 2 (openerp-dev-addons2)
         Status: Confirmed


** Tags: traceability
-- 
[trunk] No support for forcing full traceability of production lot # in internal stock moves
https://bugs.launchpad.net/bugs/670451
You received this bug notification because you are a member of credativ, which is subscribed to the bug report.