[
https://issues.apache.org/jira/browse/OFBIZ-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951091#comment-13951091
]
Christian Carlow commented on OFBIZ-5561:
-----------------------------------------
I'm closing this issue for now because it no longer seems relevant as a
solution to the original problem it was created to solve. If eventually
implemented, it should be optional for routes/production runs since the current
functionality of allowing task declarations in arbitrary order is valuable and
necessary as part of the solution to the original problem. I assumed that all
tasks would be performed according to their sequenceNum ordering in an attempt
to generate a WIP report indicating how many pieces were at particular fixed
assets by subtracting the quantityProduced of the prior task from the
quantityProduced + quantityRejected of the current task. Due to the arbitrary
ordering of task declarations that may occur, this approach is insufficient.
Instead I propose adding some field to indicate the next task during
declaration which will be dependent on the time entry functionality added in
OFBIZ-5532.
> Production Run task quantity produced can be greater than the prior task
> ------------------------------------------------------------------------
>
> Key: OFBIZ-5561
> URL: https://issues.apache.org/jira/browse/OFBIZ-5561
> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing
> Affects Versions: SVN trunk
> Reporter: Christian Carlow
>
> When completing a production run task, the quantity produced is not limited
> to the quantity produced of the prior task. This issue was mentioned in
> OFBIZ-5526 which is a related issue.
> I created a production run to create 100 pizzas and declared 1 reject for the
> first task and then completed producing 99. Then I started and completed the
> next task and the quantity produced was set to 100. This seems incorrect and
> the quantity produced for the next task should be limited to 99 based on the
> previous task. So if I declared 1 reject also for the second task then the
> third would be limited to 98.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
