Labor and burden hrs on "quantity only" operations

Yahoo Archive
1
I'm not sure if it's a bug, but that certainly Is the behavior I have
witnessed. Perhaps works as designed may be appropriate here? We use
quantity only operations for our continuous paint line process. Because
of the issues you're speaking of, among others, we elected to use a
'dummy' employee to record all those types of operations, and regular
employees use an indirect labor code to indicate they are clocked in to
those types of activities. Probably not what you're looking for though!



Rob Bucek

Manufacturing Engineer

PH: (715) 284-5376 ext 3111

FAX: (715)284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site) <http://www.dsmfg.com/>





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Tony Hughes
Sent: Tuesday, July 21, 2009 9:45 AM
To: vantage@yahoogroups.com
Subject: [Vantage] labor and burden hrs on "quantity only" operations





In a situation where the employee forgets to clock out for the day, and
is left clocked in to a "quantity only" operation, when you go in and
later clock him out and adjust the actual Clock in and Clock out times,
Vantage does not correctly adjust the read-only Labor and Burden hrs
fields in Labor Entry if the operation is a Quantity Only operation.

Is this a bug? yes, I understand that if it's quantity only, I shouldn't
care how much labor time there is, but there are shop leadmen here who
use that hour field to make sure that employees are clocked in to jobs.
(i.e., total the labordtl hours for a day, and compare with
laborhed.payrollhours)

Any advice?

Thank you





[Non-text portions of this message have been removed]
2
In a situation where the employee forgets to clock out for the day, and is left clocked in to a "quantity only" operation, when you go in and later clock him out and adjust the actual Clock in and Clock out times, Vantage does not correctly adjust the read-only Labor and Burden hrs fields in Labor Entry if the operation is a Quantity Only operation.

Is this a bug? yes, I understand that if it's quantity only, I shouldn't care how much labor time there is, but there are shop leadmen here who use that hour field to make sure that employees are clocked in to jobs. (i.e., total the labordtl hours for a day, and compare with laborhed.payrollhours)

Any advice?

Thank you