| 2010-11-03 15:49:11 |
Tamás Dénes |
bug |
|
|
added bug |
| 2010-11-03 20:37:15 |
Tamás Dénes |
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 LOT management is not involved.
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.
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 pharmacy industry where LOT management and full traceability is vital.
But if You use OpenERP simply in trade industry and must track serial numbers You are suck when You move products between internal locations. If the user forget to set LOT on internal moves then You loose important information.
Please fix LOT management! |
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 LOT management is not involved.
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 pharmacy 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)
|
|
| 2010-11-03 20:45:09 |
Tamás Dénes |
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 LOT management is not involved.
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 pharmacy 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)
|
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 pharmacy 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)
|
|
| 2010-11-03 20:50:38 |
Tamás Dénes |
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 pharmacy 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)
|
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)
|
|
| 2010-11-03 21:06:36 |
Nhomar - Vauxoo |
openobject-addons: importance |
Undecided |
Medium |
|
| 2010-11-03 21:06:40 |
Nhomar - Vauxoo |
openobject-addons: status |
New |
Confirmed |
|
| 2010-11-03 21:06:49 |
Nhomar - Vauxoo |
openobject-addons: milestone |
|
5.0.15 |
|
| 2010-11-03 21:07:34 |
Nhomar - Vauxoo |
openobject-addons: status |
Confirmed |
Opinion |
|
| 2010-11-03 21:07:42 |
Nhomar - Vauxoo |
openobject-addons: importance |
Medium |
High |
|
| 2010-11-03 21:12:06 |
Nhomar - Vauxoo |
nominated for series |
|
openobject-addons/trunk |
|
| 2010-11-03 21:12:06 |
Nhomar - Vauxoo |
bug task added |
|
openobject-addons/trunk |
|
| 2010-11-03 21:12:24 |
Nhomar - Vauxoo |
nominated for series |
|
openobject-addons/5.0 |
|
| 2010-11-03 21:12:24 |
Nhomar - Vauxoo |
bug task added |
|
openobject-addons/5.0 |
|
| 2010-11-03 21:12:41 |
Nhomar - Vauxoo |
openobject-addons/5.0: status |
New |
Confirmed |
|
| 2010-11-03 21:12:50 |
Nhomar - Vauxoo |
openobject-addons/5.0: importance |
Undecided |
Medium |
|
| 2010-11-03 21:13:05 |
Nhomar - Vauxoo |
openobject-addons/5.0: milestone |
|
6.0-rc2 |
|
| 2010-12-15 21:38:03 |
Galtys |
bug |
|
|
added subscriber Jan Troler |
| 2011-02-11 19:17:30 |
Steffi Frank (Bremskerl, DE) |
bug |
|
|
added subscriber Steffi Frank (Bremskerl, DE) |
| 2011-02-14 13:36:46 |
Steffi Frank (Bremskerl, DE) |
bug |
|
|
added subscriber Bremskerl |
| 2011-02-14 13:36:51 |
Steffi Frank (Bremskerl, DE) |
removed subscriber Steffi Frank (Bremskerl, DE) |
|
|
|
| 2011-02-14 13:42:13 |
Steffi Frank (Bremskerl, DE) |
bug |
|
|
added subscriber Steffi Frank (Bremskerl, DE) |
| 2011-03-14 08:52:14 |
Vinay Rana (OpenERP) |
openobject-addons/5.0: milestone |
6.0-rc2 |
|
|
| 2011-03-14 08:52:19 |
Vinay Rana (OpenERP) |
openobject-addons/trunk: milestone |
5.0.15 |
|
|
| 2011-03-14 09:03:36 |
Vinay Rana (OpenERP) |
openobject-addons/5.0: importance |
Medium |
Undecided |
|
| 2011-03-14 09:03:43 |
Vinay Rana (OpenERP) |
openobject-addons/trunk: importance |
High |
Undecided |
|
| 2011-03-14 09:06:22 |
Vinay Rana (OpenERP) |
openobject-addons/5.0: status |
Confirmed |
Won't Fix |
|
| 2011-03-31 14:20:13 |
Olivier Dony (Odoo) |
summary |
[trunk][stock and mrp] LOT traceability is broken |
[trunk] No support for forcing full traceability of production lot # in internal stock moves |
|
| 2011-03-31 15:52:44 |
Olivier Dony (Odoo) |
openobject-addons/trunk: importance |
Undecided |
Wishlist |
|
| 2011-03-31 15:52:44 |
Olivier Dony (Odoo) |
openobject-addons/trunk: status |
Opinion |
Confirmed |
|
| 2011-03-31 17:17:32 |
Steffi Frank (Bremskerl, DE) |
bug |
|
|
added subscriber Jacques-Etienne Baudoux (OpenERP) |
| 2011-04-01 22:57:44 |
Borja López Soilán (NeoPolus) |
bug |
|
|
added subscriber Omar (Pexego) |
| 2011-04-01 22:58:08 |
Borja López Soilán (NeoPolus) |
bug |
|
|
added subscriber Carlos Liebana |
| 2011-04-01 22:58:27 |
Borja López Soilán (NeoPolus) |
bug |
|
|
added subscriber Ana Juaristi Olalde |
| 2011-04-04 22:24:12 |
claude dunnigan |
bug |
|
|
added subscriber claude dunnigan |
| 2011-04-05 08:25:27 |
Leonardo Pistone |
bug |
|
|
added subscriber Leonardo Pistone - Domsense |
| 2011-04-05 09:30:03 |
Lorenzo Battistini |
bug |
|
|
added subscriber Lorenzo Battistini - agilebg.com |
| 2011-04-13 11:24:33 |
Vinay Rana (OpenERP) |
openobject-addons/trunk: assignee |
|
OpenERP R&D Addons Team 2 (openerp-dev-addons2) |
|
| 2011-07-15 07:23:16 |
Colm |
bug |
|
|
added subscriber Colm |
| 2011-07-18 13:38:52 |
TArpi |
bug |
|
|
added subscriber TArpi |
| 2011-11-09 19:09:47 |
Andy Wild |
bug |
|
|
added subscriber Andy Wild |
| 2012-02-14 10:42:26 |
Numérigraphe |
tags |
|
traceability |
|
| 2012-03-16 17:24:12 |
Dimitri John Ledkov (ex-credativ) |
bug |
|
|
added subscriber credativ |
| 2013-09-12 04:57:51 |
Naresh(OpenERP) |
tags |
traceability |
maintenance traceability |
|
| 2014-07-30 09:56:15 |
Lionel Sausin - Initiatives/Numérigraphe |
bug |
|
|
added subscriber Lionel Sausin - Numérigraphe |
