[
https://issues.apache.org/jira/browse/OFBIZ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326170#comment-14326170
]
Christian Carlow commented on OFBIZ-5569:
-----------------------------------------
Sorry Pierre,
I think this issue is still relevant even if support for the dependency of
tracking of partyId at InventoryItemDetail level is handled by another JIRA
issue as you propose because this issue is meant to find a way to link the
parties at InventoryItemDetail level together to determine inspection work of
operator work.
> 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)
