Employee Clock in Report in Vantage 6.1

Yahoo Archive
1
I just assumed that when someone wants to see when their employees
clocked in, they want to see when they really clocked in. But then,
I'm not a finance guy. :)

To relate to the empbasic table, you can edit the query generated by
the query builder and add the following after the for each loop on
laborhed, just in front of the colon. Note the comma at the
beginning:

, each empbasic no-lock where empbasic.company = laborhed.company and
empbasic.empid = laborhed.employeenum


--- In vantage@yahoogroups.com, "saab_barracuda" <chris.clunn@...>
wrote:
>
> Tom,
> The adjusted time is the "official" time for payroll and job costing
> so I would use laborhed.dspclockintime and laborhed.dspclockouttime
> rather than the actuals. The adjusted time takes into account the
> grace period (if setup in Company) instead of the actual minute the
> employee clocked in. We also have a policy if any changes are to be
> made, they are made to the adjusted rather than actual. The dsp
table
> prefix is for the display time in conventional HH:MM format rather
> than decimal time (if setup). Also, I would strongly recommend the
> use of payrolldate rather than clockindate. Payrolldate handles
third
> shift better, shows when people forget to clock out, etc. The stock
> labor edit report is based on clock-in date and is complete garbage
if
> you run 3 shifts around the clock or want to troubleshoot labor
entry
> errors.
>
> I'm a not very good with the 6.1 BAQ but I couldn't get the query
> wizard to relate the laborhed and empbasic tables. You might need
to
> do a report builder or ODBC report.
>
> Good luck.
>
> Chris
>
> --- In vantage@yahoogroups.com, "markewhittaker" <markewhittaker@>
> wrote:
> >
> > That's all in the laborhed and empbasic tables. Fields are:
> >
> > laborhed.actualclockindate, laborhed.employeenum, empbasic.name,
> > laborhed.actualclockintime, laborhed.actualclockouttime
> >
> > Is that what you needed to know?
> >
> > Mark
> > --- In vantage@yahoogroups.com, "sh4m4n71x" <lunar@> wrote:
> > >
> > > Is it possible to create a csv report in Business Activity
Query
> > that
> > > would show employee clock in time for particular day and shift?
> > > I'd appreciate if anyone could point me in the right direction.
> > > Something like this would be nice:
> > >
> > > Date, Clock Number, Name, Clock in time, Clock out time.
> > >
> > >
> > > Thanks,
> > > Tom.
> > >
> >
>
2
Is it possible to create a csv report in Business Activity Query that
would show employee clock in time for particular day and shift?
I'd appreciate if anyone could point me in the right direction.
Something like this would be nice:

Date, Clock Number, Name, Clock in time, Clock out time.


Thanks,
Tom.
3
That's all in the laborhed and empbasic tables. Fields are:

laborhed.actualclockindate, laborhed.employeenum, empbasic.name,
laborhed.actualclockintime, laborhed.actualclockouttime

Is that what you needed to know?

Mark
--- In vantage@yahoogroups.com, "sh4m4n71x" <lunar@...> wrote:
>
> Is it possible to create a csv report in Business Activity Query
that
> would show employee clock in time for particular day and shift?
> I'd appreciate if anyone could point me in the right direction.
> Something like this would be nice:
>
> Date, Clock Number, Name, Clock in time, Clock out time.
>
>
> Thanks,
> Tom.
>
4
Tom,
The adjusted time is the "official" time for payroll and job costing
so I would use laborhed.dspclockintime and laborhed.dspclockouttime
rather than the actuals. The adjusted time takes into account the
grace period (if setup in Company) instead of the actual minute the
employee clocked in. We also have a policy if any changes are to be
made, they are made to the adjusted rather than actual. The dsp table
prefix is for the display time in conventional HH:MM format rather
than decimal time (if setup). Also, I would strongly recommend the
use of payrolldate rather than clockindate. Payrolldate handles third
shift better, shows when people forget to clock out, etc. The stock
labor edit report is based on clock-in date and is complete garbage if
you run 3 shifts around the clock or want to troubleshoot labor entry
errors.

I'm a not very good with the 6.1 BAQ but I couldn't get the query
wizard to relate the laborhed and empbasic tables. You might need to
do a report builder or ODBC report.

Good luck.

Chris

--- In vantage@yahoogroups.com, "markewhittaker" <markewhittaker@...>
wrote:
>
> That's all in the laborhed and empbasic tables. Fields are:
>
> laborhed.actualclockindate, laborhed.employeenum, empbasic.name,
> laborhed.actualclockintime, laborhed.actualclockouttime
>
> Is that what you needed to know?
>
> Mark
> --- In vantage@yahoogroups.com, "sh4m4n71x" <lunar@> wrote:
> >
> > Is it possible to create a csv report in Business Activity Query
> that
> > would show employee clock in time for particular day and shift?
> > I'd appreciate if anyone could point me in the right direction.
> > Something like this would be nice:
> >
> > Date, Clock Number, Name, Clock in time, Clock out time.
> >
> >
> > Thanks,
> > Tom.
> >
>