Re: Should a single production run task allow for tracking multiple declarations? How to determine number of rejected pieces by employee?

[Christian Carlow <ch...@gmail.com>]

I've determined that time entries are supposed to handle this 
functionality. ProductionRunServices.updateProductionRunTask accepts the 
partyId as a parameter but code that is supposed to use it to create 
timesheet entries has been commented out.  Rev 910230 shows that the 
commented code has always existed.  There are also FIXME comments to add 
quantityProduced, quantityRejected, and setupTime fields to the 
timesheet entity.

On 02/06/2014 01:27 PM, Christian Carlow wrote:
> Sometimes a work center will receive 16 pieces but split work 
> resulting in one employee finishing 12 pieces earlier than the 
> remaining 4 finished later by another employee. For these cases, 
> shouldn't production run tasks support multiple declarations?  How 
> would one track which employee is at fault for rejected pieces?

Re: Should a single production run task allow for tracking multiple declarations? How to determine number of rejected pieces by employee?

[Christian Carlow <ch...@gmail.com>]

Sorry,

> There are also FIXME comments to add quantityProduced, 
> quantityRejected, and setupTime fields to the timesheet entity.

*time_entry entity (not timesheet)