[ 
https://issues.apache.org/jira/browse/OFBIZ-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925782#comment-13925782
 ] 

Christian Carlow commented on OFBIZ-5568:
-----------------------------------------

I updated the description of this issue again since the last description was 
deemed not an issue on the ML.  I've determined that Routing Task Deliverable 
Products can be used to limit the productId field that appears in the 
production run inventory declaration form.  Specifying a deliverable product 
causes the declaration form productId field to change from a lookup to a drop 
down listing only those products specified as deliverable products for the 
task.  This limitation is only implemented on the front end however and should 
be implemented in the backend as well because there is nothing that prevents a 
user from hacking the system by changing the drop down value to something other 
than the intended deliverable product to create inventory for a product that 
isn't supposed to be a deliverable for the task.

I feel additional quantity checking rules should also be applied.  Pierre, for 
your yeast-residue scenario, shouldn't there be a rule to prevent more residue 
from being declared than can possibly exist for a certain brew size?  

> Production Run improvements to increase power of by-product declarations 
> limitation rules
> -----------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-5568
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5568
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: manufacturing
>            Reporter: Christian Carlow
>
> The production run inventory declaration form should be limited to defective 
> products associated with either the finished good or raw materials.  
> Currently is allows any product to be produced which is incorrect.  
> ProductAssoc with type "PRODUCT_DEFECT" needs to be added to handle the 
> limitation logic in the service.  Then the reason field of ProductAssoc could 
> be used to indicate defective variants more clearly to the user.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to