When using a BOM or a Workflow for a Manufacturing Order (MO) we should check first if these entities are validated/verified (check IsValid/IsVerified flag). Any not verified BOM should be forbiden.
I am agree with the workflow, but I have doubt about the !product.isVerified() because this was use for old approach to validate the BOM, but the current approach validate the cyclical BOM when a component is added.
Current continue work the Verification BOM?
kind regards
Victor Perez
www.e-evolution.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regarding the BOM.isVerified we neded to reuse those fields even if the bom check process is not completed. The idea is to complete the process (verify cycles etc).
WDYT?
Best regards,
Teo Sarca - www.arhipac.ro
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Teo, yes this will the ideal, but the problem is that the old approach is based on single BOM and Libero support multiple BOM, So my doubts how can use the old approach with new approach?.
kind regards
Victor Perez
www.e-evolution.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm, i think we should consider M_Product.IsVerified if all BOMs for that product is verified.
Another option would be to introduce PP_Product_BOM.IsValid flag and validate each BOM individually. Maybe this is a better apporach.
WDYT?
PS: checking M_Product.IsVerified is better then not checking anything.
Best regards,
Teo Sarca - www.arhipac.ro
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Revision: 9612
http://adempiere.svn.sourceforge.net/adempiere/?rev=9612&view=rev
Author: teo_sarca
Date: 2009-07-07 09:08:40 +0000 (Tue, 07 Jul 2009)
Log Message:
-----------
[ 2817870 ] MO should use only validated BOMs and WFs
https://sourceforge.net/tracker/?func=detail&aid=2817870&group_id=176962&atid=934929
Modified Paths:
--------------
branches/libero/extension/eevolution/libero/src/main/java/org/eevolution/model/MPPOrder.java
Revision: 9611
http://adempiere.svn.sourceforge.net/adempiere/?rev=9611&view=rev
Author: teo_sarca
Date: 2009-07-07 09:02:58 +0000 (Tue, 07 Jul 2009)
Log Message:
-----------
[ 2817870 ] MO should use only validated BOMs and WFs
https://sourceforge.net/tracker/?func=detail&aid=2817870&group_id=176962&atid=934929
Product Planning window, Product tab (first) - Verify BOM button should be editable
Added Paths:
-----------
trunk/migration/353a-trunk/oracle/495_BF2817870.sql
trunk/migration/353a-trunk/postgresql/495_BF2817870.sql
HI Teo!
I am agree with the workflow, but I have doubt about the !product.isVerified() because this was use for old approach to validate the BOM, but the current approach validate the cyclical BOM when a component is added.
Current continue work the Verification BOM?
kind regards
Victor Perez
www.e-evolution.com
Hi Victor,
Regarding the BOM.isVerified we neded to reuse those fields even if the bom check process is not completed. The idea is to complete the process (verify cycles etc).
WDYT?
Best regards,
Teo Sarca - www.arhipac.ro
Teo, yes this will the ideal, but the problem is that the old approach is based on single BOM and Libero support multiple BOM, So my doubts how can use the old approach with new approach?.
kind regards
Victor Perez
www.e-evolution.com
Hmm, i think we should consider M_Product.IsVerified if all BOMs for that product is verified.
Another option would be to introduce PP_Product_BOM.IsValid flag and validate each BOM individually. Maybe this is a better apporach.
WDYT?
PS: checking M_Product.IsVerified is better then not checking anything.
Best regards,
Teo Sarca - www.arhipac.ro
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).