[
https://issues.apache.org/jira/browse/OFBIZ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326470#comment-14326470 ]
Christian Carlow commented on OFBIZ-5569:
-----------------------------------------
WorkEffortNote is not sufficient for tracking the times and quantities of production of multiple workers per task. My proposal is to support creation of TimeEntries and InventoryItemDetail during task declarations and then use InventoryItemDetail.timeEntryId as the unit work identifier to derive who produced how much and when. Then timeEntryIds could then be used by TimeEntryAssoc to support inspection tracking. Support for inventory tracking within the production run should probably be handled in another issue upon which this issue is dependent.
> Add production run task inspection capabilities using time entry improvements
> -----------------------------------------------------------------------------
>
> Key: OFBIZ-5569
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5569> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Trunk
> Reporter: Christian Carlow
> Assignee: Pierre Smits
>
> There doesn't seem to be a standard method for handling production run inspections that offer any real power in terms of reporting. The system already lacks time entry functionality which will be added in OFBIZ-5532. Once time entry functionality is added to the declaration services, TimeEntryAssoc could be created to link an inspection time entries to a manufacturing work time entries to represent an inspection of manufacturing work. The goal is to be able to determine the number of bad pieces produced per manufacturing worker and who was the inspector. The functionality should also be flexible and powerful enough to distinguish who is actually at fault for the bad piece. In most cases, the manufacturing workers will be at fault, but there could be times where an inspector might accidentally drop a good or potentially good piece and the system should be able to flag them as the party actually responsible for the defect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
