"Weird" was the only way I could describe it because I wasn't sure what was happening myself. The only thing I've noticed so far is that the pay hours will total differently each day for some employees if I do a report that includes all of the employees vs. a report that only includes the individual employee. Why this would effect an individual's total pay hours for a given day is beyond me . . . much like this entire report is!
But let me see if I can explain what I've got:
This is a BAQ Report. I have two groups, the first being LaborHed.EmployeeNum the second being LaborHed.PayrollDate. In the details section I have LaborHed.PayHours and LaborDtl.LaborHrs, but I have hidden this section because I don't need these results to be visible. In the footer for group 2 (payrolldate) I have the running total for payhours and a summary of laborhrs. The running total is comprised like this: Field to summarize: LaborHead.PayHours as a sum; Evaluated on change of field LaborHed.LaborHedSeq; being reset on change of field LaborHed.PayrollDate.
But let me see if I can explain what I've got:
This is a BAQ Report. I have two groups, the first being LaborHed.EmployeeNum the second being LaborHed.PayrollDate. In the details section I have LaborHed.PayHours and LaborDtl.LaborHrs, but I have hidden this section because I don't need these results to be visible. In the footer for group 2 (payrolldate) I have the running total for payhours and a summary of laborhrs. The running total is comprised like this: Field to summarize: LaborHead.PayHours as a sum; Evaluated on change of field LaborHed.LaborHedSeq; being reset on change of field LaborHed.PayrollDate.
--- In vantage@yahoogroups.com, "Brian Roberts" <broberts@...> wrote:
>
> "Weird"? Check your crystal formulas and links between tables in
> Crystal, make sure you aren't counting a record twice or excluding it
> with a too restrictive join.
>
>
>
> The other possibility is unusual data... is the labour still active, so
> the end time is not valid yet (check ActiveTrans & TimeStatus)? Are you
> trying to manually adjust for lunch/breaks/absences? Are people
> temporarily loaned to other depts, so employee & labordtl JCDept don't
> match when you expect them to? (Making some guesses as to what you're
> doing, might be on the wrong track).
>
>
>
> Brian.
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Sean Toler
> Sent: Monday, August 08, 2011 9:33 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Clock Time VS. Labor Time Report
>
>
>
>
>
> I spoke too soon. I'm getting some weird pay hour totals here and there
> and I'm not sure why.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Sean Toler" <seantoler@> wrote:
> >
> > That worked so well it brought a tear to my eye!
> > Thanks again!
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Sean Toler" <seantoler@> wrote:
> > >
> > > Ooooh! OK, gotcha! Thanks again!
> > >
> > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Brian Roberts" <broberts@> wrote:
> > > >
> > > > To do this task in Crystal: "only add hours on LaborHed on change
> of
> > > > LaborHedSeq" ... do this: create a running total field, and have
> it
> > > > evaluate only on "change of field" (or possibly "change of
> group").
> > > > Then manually add that field to your report.
> > > >
> > > >
> > > >
> > > > The "insert summary" option in Crystal makes the wrong assumptions
> for
> > > > this calculation.
> > > >
> > > >
> > > >
> > > > Brian.
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> > > > Of Sean Toler
> > > > Sent: Thursday, August 04, 2011 11:22 AM
> > > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > > > Subject: [Vantage] Re: Clock Time VS. Labor Time Report
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > This is still giving me some trouble. Would you mind elaborating a
> bit
> > > > more please? Thanks.
> > > >
> > > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,
> > > > "Sean Toler" <seantoler@> wrote:
> > > > >
> > > > > Thank you very much! I will go and give that a try when I get
> some
> > > > time. It's interesting that you mentioned someone clocking out and
> back
> > > > in on the same day because that was the first problem I started
> having
> > > > with this report!
> > > > >
> > > > > --- In vantage@yahoogroups.com
> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ,
> > > > "al2trace" <allen.larsen@> wrote:
> > > > > >
> > > > > > The field that uniquely ties LaborHed and LaborDtl together is
> > > > LaborHedSeq. Grouping on payroll date will work for many
> transactions
> > > > but not when someone punches out and then back in on the same day.
> If
> > > > you need to group on the day, you will need to be careful how you
> sum
> > > > the header records. Your final group level should be LaborHedSeq
> and
> > > > then only add hours on LaborHed on change of LaborHedSeq.
> > > > > >
> > > > > >
> > > > > > --- In vantage@yahoogroups.com
> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ,
> > > > "Sean Toler" <seantoler@> wrote:
> > > > > > >
> > > > > > > Hello.
> > > > > > > I am attempting to create a report for management that
> compares an
> > > > employee's clock time to his/her labor time. I am using
> > > > LaborDtl.LaborHrs and LaborHed.PayHrs for this. My problem arises
> when I
> > > > try to get a sum of the hours. I have grouped by employee # and
> then by
> > > > Payroll Date. When I do a sum of the labor hours and place it in
> the
> > > > footer of the payroll date group the sum is correct. However, when
> I do
> > > > the same thing for pay hours, I am getting some off the wall sums.
> > > > Anyone have any suggestions to correct this?
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>