.409C Labor Entry Weirdness

Yahoo Archive
1
Hi Vic; Unfortunately, don't have any solutions for you but we experince both #1 & #2 in 408. We don't worry too much about #1 since we use MES, but #2 becomes quite annoying when correcting labor entries that were not recorded correctly in MES.

Virginia Joseph


--- In vantage@yahoogroups.com, "Vic Drecchio" <vic.drecchio@...> wrote:
>
> I'm curious if anyone has seen this or duplicated this:
>
>
>
> In our .409C test environment, in Labor Entry, as we enter Labor Detail
> transactions for one Employee on the same payroll date, I see two things
> happening:
>
>
>
> 1) Only when the Shift spans midnight, as you enter multiple labor
> detail transactions on the left side in the "tree" as you enter new
> details, the new clock-in time auto-defaults to the previous clock-out
> time. That logic works on the 2nd detail transaction only. When I
> enter the 3rd detail transaction, it still uses the clock-out time of
> the *first* detail transaction instead of the second detail transaction.
> And all subsequent transactions still default to the clock-out time of
> the first detail transaction instead of the previous transaction.
> Again, this ONLY happens when the current shift for this record happens
> to span midnight. If the shift DOES NOT span midnight, the subsequent
> detail transactions work fine. I don't see the Labor Type making a
> difference, either. By the way, I've also seen this behavior duplicated
> in .408B (our current version).
>
> 2) A second problem: As you enter detail transactions, on the
> Labor Detail tab, in the top right corner, the "Labor" field accumulates
> as you enter transactions for that payroll date. In .408B, this works
> fine. In .409C this accumulation is NOT occurring. The Labor field
> remains at ZERO. It will update if I refresh the record, but I
> shouldn't have to do that after each labor detail transaction.
>
>
>
>
>
> Has anyone seen this and/or heard of an SCR?
>
>
>
>
>
> Thank you in advance.
>
>
>
>
>
>
>
> Vic
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
2
I'm curious if anyone has seen this or duplicated this:



In our .409C test environment, in Labor Entry, as we enter Labor Detail
transactions for one Employee on the same payroll date, I see two things
happening:



1) Only when the Shift spans midnight, as you enter multiple labor
detail transactions on the left side in the "tree" as you enter new
details, the new clock-in time auto-defaults to the previous clock-out
time. That logic works on the 2nd detail transaction only. When I
enter the 3rd detail transaction, it still uses the clock-out time of
the *first* detail transaction instead of the second detail transaction.
And all subsequent transactions still default to the clock-out time of
the first detail transaction instead of the previous transaction.
Again, this ONLY happens when the current shift for this record happens
to span midnight. If the shift DOES NOT span midnight, the subsequent
detail transactions work fine. I don't see the Labor Type making a
difference, either. By the way, I've also seen this behavior duplicated
in .408B (our current version).

2) A second problem: As you enter detail transactions, on the
Labor Detail tab, in the top right corner, the "Labor" field accumulates
as you enter transactions for that payroll date. In .408B, this works
fine. In .409C this accumulation is NOT occurring. The Labor field
remains at ZERO. It will update if I refresh the record, but I
shouldn't have to do that after each labor detail transaction.





Has anyone seen this and/or heard of an SCR?





Thank you in advance.







Vic





[Non-text portions of this message have been removed]
3
We've seen it and have compensated for it. Don't know of an SCR. We are just very cautious now on labor entry.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Vic Drecchio
Sent: Monday, November 22, 2010 11:42 AM
To: vantage@yahoogroups.com
Subject: [Vantage] .409C Labor Entry Weirdness



I'm curious if anyone has seen this or duplicated this:

In our .409C test environment, in Labor Entry, as we enter Labor Detail
transactions for one Employee on the same payroll date, I see two things
happening:

1) Only when the Shift spans midnight, as you enter multiple labor
detail transactions on the left side in the "tree" as you enter new
details, the new clock-in time auto-defaults to the previous clock-out
time. That logic works on the 2nd detail transaction only. When I
enter the 3rd detail transaction, it still uses the clock-out time of
the *first* detail transaction instead of the second detail transaction.
And all subsequent transactions still default to the clock-out time of
the first detail transaction instead of the previous transaction.
Again, this ONLY happens when the current shift for this record happens
to span midnight. If the shift DOES NOT span midnight, the subsequent
detail transactions work fine. I don't see the Labor Type making a
difference, either. By the way, I've also seen this behavior duplicated
in .408B (our current version).

2) A second problem: As you enter detail transactions, on the
Labor Detail tab, in the top right corner, the "Labor" field accumulates
as you enter transactions for that payroll date. In .408B, this works
fine. In .409C this accumulation is NOT occurring. The Labor field
remains at ZERO. It will update if I refresh the record, but I
shouldn't have to do that after each labor detail transaction.

Has anyone seen this and/or heard of an SCR?

Thank you in advance.

Vic

[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
4
For what its worth, I noticed issue #2 in patch 409a.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Vic Drecchio
Sent: Monday, November 22, 2010 11:42 AM
To: vantage@yahoogroups.com
Subject: [Vantage] .409C Labor Entry Weirdness





I'm curious if anyone has seen this or duplicated this:

In our .409C test environment, in Labor Entry, as we enter Labor Detail
transactions for one Employee on the same payroll date, I see two things
happening:

1) Only when the Shift spans midnight, as you enter multiple labor
detail transactions on the left side in the "tree" as you enter new
details, the new clock-in time auto-defaults to the previous clock-out
time. That logic works on the 2nd detail transaction only. When I
enter the 3rd detail transaction, it still uses the clock-out time of
the *first* detail transaction instead of the second detail transaction.
And all subsequent transactions still default to the clock-out time of
the first detail transaction instead of the previous transaction.
Again, this ONLY happens when the current shift for this record happens
to span midnight. If the shift DOES NOT span midnight, the subsequent
detail transactions work fine. I don't see the Labor Type making a
difference, either. By the way, I've also seen this behavior duplicated
in .408B (our current version).

2) A second problem: As you enter detail transactions, on the
Labor Detail tab, in the top right corner, the "Labor" field accumulates
as you enter transactions for that payroll date. In .408B, this works
fine. In .409C this accumulation is NOT occurring. The Labor field
remains at ZERO. It will update if I refresh the record, but I
shouldn't have to do that after each labor detail transaction.

Has anyone seen this and/or heard of an SCR?

Thank you in advance.

Vic

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]