Tweak Time Eval

[Former Member]

At our client there are various groups of people as far as IT0007 is concerned. The Time data for hourly paid employees come through Kronos in IT2010 and their TMSTA in IT0007 is 0 - No Time Evaluation. For other group of non-exempts employees, TMSTA is 9 - Time Eval for planned times. Since they automatically get paid for 40 hours a week and they do exception time recording.

Recently, somehow for few people whose Time comes through Kronos, their TMSTA in IT0007 was , by mistake, changed to 9 from 0. So these guys were paid for whatever hours came through Kronos as well as regular 40 hours by default. So their regular pay was in the range of 70 + hours.

My question is -- Can we write a rule in time eval to check such mishappenings. Can we tweak the Time Eval so that for those people whose Time comes through Kronos, if the RPTIME00 sees TMSTA as anything but 0, thse employees should be kicked out?

Any suggestion would be appreciated.

Thanks

Wills

[Former Member]

Sure you can easily. How can you recognise these group? Do they have a specific grouping/ subarea/ or what ? You just have to create a small rule that when you encounter them, you generate an error message (because they should never go though time eval you don't have to check any condition right?)

[Former Member]

Hi Valerie

Thanks for your reply. Yes, the group is identified for which we have to write the rule so that when Time Eval encounters them , they are kicked out because they should never go though time eval and no need to check any other condition. Any idea, where / how to write such rule?

Thanks

Wills

[Former Member]

In fact you have probably a lot of choices

examples: assuming XXXX is your group of EE

OUTTIBDEGR (if you are using IT0050)

****

XXXX colerZZe (ZZ is the message number you set in T555E)

or

VARTP2011

N

Y XXXX colerZZe

It all depends on how you recognise them, so choose the appropriate operation....

Put that rule at the begining of the day processing so you catch them quickly; Once again it depend of which schema you are using....