[
https://issues.apache.org/jira/browse/OFBIZ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326035#comment-14326035 ]
Pierre Smits commented on OFBIZ-5569:
-------------------------------------
Christian,
Like I said in another comment/issue/thread, in current design (based on the DMRB) time registration is for registering time spent by operators (persons), not for registering quantities produced. Extending that would create a redundancy and confusion. It wouldn't solve your issue.
The inventoryItemDetail has the workEffortId field to track from which task or run the declarations came. And inventoryItems are shown in a production run. From the inventory item shown in the overview (in a production run) you can access the inventoryItemDetail record.
Furthermore, the InventoryItem has the partyId field. That could be used to track who created the record.
> 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
