I received a call a few days ago from Wendy in Product Development at Epicor
and also have some more 'Clues" about this "bug" where the labor edit report
shows incorrect hrs, often exactly split in half. The difference from the
payroll hrs then shows as idle time if it does not get caught and corrected.
Epicor has closed the call on this because they are assuming that it is
related to situations where two forms of labor entry are being used at the
same time thereby making it look to the system like the person is on two
jobs at the same time. They say this can occur when a person does not clock
out and then manual labor entry is also done. Apparently Labor Entry does
not check to see if a person is clocked in while entries are being made and
it treats the person as being on multiple jobs at the same time. This
explanation was "clear as mud" to me too. So now, since they have stopped
working on finding the real cause, it is up to "users" to find a
reproduceable situation.
I have written several RB reports to dump all of the labor header and detail
records for a given employee on a date as well as everyone who worked on a
job/seq/oper on a date. These show that the labor hrs total is incorrect
(split in half) before the labor edit report is run. The reports are run
after Labor Edit is printed and splits are identified but before any
adjustments or labor entry is done. A couple more situations I have seen
for this bug are:
- Up until today's report if a person at any split hrs ALL the hours for the
day were split. Yesterday a person had an OK job then two with split hrs
then two more OK. So the All or Nothing theory goes out the window.
- I used to see more 2nd shift (3:15 to 11:45pm) cases but lately it has
been mostly 1st shift (6:30 - 3:00). So it clearly is not related to
exactly midnight. I also see it far more often on Setup records than
Production but it is on both as well as on Indirect where no job at all is
involved.
- Yesterday I confirmed a case where a person's records were all flagged as
"Data Collection = Yes" and had no manual labor entry done, any time, ever.
Her single method of labor record creation was Data Collection. This
completely contradicts the "explanation" given for closing the call.
- I have one person who seems to have this happen more often than others (a
setup guy) and I am running the employee labor details dump that I wrote
several times a day to see if it occurs before any other labor activities
are done. But because this does not happen every day it may take a week or
so of watching. I also want to see if they look OK all day and then
"change" when he goes home.
At this point I am aggressively collecting data and when I can make a very
clear case that Epicor has closed this prematurely I will present the
evidence to them and get this re-opened.
-Todd Caughey
Harvey Vogel Mfg. Co.
-----Original Message-----
From: John Sage [mailto:
jsage@...]
Sent: Thursday, February 15, 2001 11:20 AM
To:
vantage@yahoogroups.com
Subject: RE: [Vantage] Labor Edit/Collection Errors
Patrick,
OK, I've studied it a bit closer. It mostly happens with
people whose shift ends at midnight. However for those who
are on a longer shift, their time _after_ midnight gets
thrown into indirect idle.
have fun,
John
> -----Original Message-----
> From: Winter, Patrick [mailto:pjw@...]
> Sent: Thursday, February 08, 2001 11:40 AM
> To: 'vantage@yahoogroups.com'
> Subject: RE: [Vantage] Labor Edit/Collection Errors
>
>
> Just a wild thought to add, to see if an old problem is
> reoccurring, are any of your shifts starting or ending
> exactly at midnight?
Yahoo! Groups Sponsor
<
http://rd.yahoo.com/M=176325.1312152.2904070.1252795/D=egroupmail/S=1700007
183:N/A=567139/R=1/*
http://domains.yahoo.com>
<
http://rd.yahoo.com/M=176325.1312152.2904070.1252795/D=egroupmail/S=1700007
183:N/A=567139/R=2/*
http://domains.yahoo.com>
www.
<
http://us.adserver.yahoo.com/l?M=176325.1312152.2904070.1252795/D=egroupmai
l/S=1700007183:N/A=567139/rand=525641730>
To unsubscribe from this group, send an email to:
vantage-unsubscribe@egroups.com
[Non-text portions of this message have been removed]