[
https://issues.apache.org/jira/browse/OFBIZ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326081#comment-14326081
]
Christian Carlow commented on OFBIZ-5569:
-----------------------------------------
Pierre,
Right, I'm no longer proposing extending TimeEntry to track quantity but rather
using InventoryItemDetail for tracking quantities and TimeEntry for tracking
the distinct unit of work and time spent by the worker then using an
association between InventoryItemDetail and TimeEntry to determine the quantity
per unit of work.
InventoryItemDetail.workEffortId and InventoryItem.partyId are not granular
enough to breakdown the quantity good and bad by worker. Adding partyId to
InventoryItemDetail could provide such granularity but I thought using
timeEntryId would be a better approach since technically the
InventoryItemDetail record would represent an inventory move as a result of
time spent completing a task.
> 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)
