[ https://issues.apache.org/jira/browse/OFBIZ-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322945#comment-14322945 ]
Christian Carlow commented on OFBIZ-5548: ----------------------------------------- Hey Pierre, I'll revise this issue with a better title. It closely relates to OFBIZ-5569 and may be a duplicate. Below line 2162 of ProductionRunServices.java for updateProductionRunTask, I uncommented the TimeEntry code so it could be used to determine who performed which tasks, when, and how many were produced and rejected by them. But TimeEntry does not provide a way to determine the different reject reasons and the quantity of them. InventoryItemDetail has a reasonEnumId field which seems sufficient for determining the various reject reasons but would have to include a timeEntryId field to link back to the task. > Improve production run task declarations to allow for rejected by-products > from workers to be determined > -------------------------------------------------------------------------------------------------------- > > Key: OFBIZ-5548 > URL: https://issues.apache.org/jira/browse/OFBIZ-5548 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing > Affects Versions: Trunk > Reporter: Christian Carlow > Assignee: Pierre Smits > > I think the production run task declaration form that allows by-products to > be created should be improved to allow relations to time entries created from > the other declaration form. > This improvement will be dependent on the added production run declaration > time entry functionality provided in OFBIZ-5532. It would be nice to be able > to declare quantityRejected in the by-product declaration form and have it > automatically update the workEffort.quantityRejected of the time entry that > will be specified. I think the timeEntryId field should be added to the > InventoryItemDetail entity to relate the by-products to the worker > responsible for the rejects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)