[
https://issues.apache.org/jira/browse/OFBIZ-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522577 ]
Jacopo Cappellato commented on OFBIZ-1214:
------------------------------------------
Si,
what you describe is actually what is implemented.
The issue is with the user interface in the edit production run screen that can be confusing.
A quick fix could be that of changing the label "Estimated Run Time" to "Estimated Unit Run Time"; and maybe also adding a new calculated column for "Estimated Total Run Time".
For example, have a look at the order I have created here:
https://demo.hotwaxmedia.com/manufacturing/control/EditProductionRun?productionRunId=10000setup: 600 sec
(unit) run time: 300
qty: 2
and in fact the task's "Calculated Completion Date" is exactly 20 minutes after the start date (600 + 300*2).
> production run task times are not related to quantity produced
> --------------------------------------------------------------
>
> Key: OFBIZ-1214
> URL:
https://issues.apache.org/jira/browse/OFBIZ-1214> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing
> Reporter: Si Chen
>
> I just noticed that a production run task's run times are not related to the quantity produced, so if you make 1or 1000 of an item, the same setup time and run time are created on all the tasks.
> I think a simple but reasonable solution is to make the setup time (estimatedSetupMillis) constant in all cases, but make the estimatedMilliSeconds the original template multiplied by the quantity of the item.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Locked
