Mailing-List: contact user-help@ofbiz.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ofbiz.apache.org
Received-SPF: pass (nike.apache.org: domain of christian.carlow@gmail.com
 designates 209.85.216.52 as permitted sender)
Message-ID: <52F3F0F5.1060007@gmail.com>
Date: Thu, 06 Feb 2014 14:30:45 -0600
From: Christian Carlow <christian.carlow@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: user@ofbiz.apache.org
Subject: Re: Should a single production run task allow for tracking multiple
 declarations? How to determine number of rejected pieces by employee?
References: <52F3E22A.5080104@gmail.com>
In-Reply-To: <52F3E22A.5080104@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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?