Retro Time Evaluation

[Former Member]

Time has been entered and approved up until Friday 5/22/15.  Then on 5/31 the end of the month rules process to determine the total number of hours for pay in efforts to pro-rate the holiday credit they will receive on 5/25/15 ( Memorial Day).

Now on 6/1, after the EOM rules have run, a time recorder went back into the time sheet to enter more time for the days of 5/26 - 5/29.  The addition of these hours increases the total hours for pay and subsequently increased the amount of pro-rated holiday credit the employee should receive.

If I run a time evaluation from 5/22 - 5/31, does time evaluation re-calculate time for EVERY day in that date range?  Or does it only pick up the "changes" or the new time that was posted on 6/1?  I ask because when a time eval was ran for that date range, it picked up the additional hours that were posted, but it did not re-calculate the pro-rated amount of holiday credit.  I read somewhere that SAP does not automatically re-calculate time pairs that are already in the table, so you must perform a forced re-calculation.  With that said, could that explain why the pro-rated holiday credits were not updated?  Because there was already a value in the table for that day and therefore time evaluation would not re-calculate unless a force recalculation was performed?

[seg_hr_it]

It is hard to understand what you mean.

If your design Time Eval with ADDMB, there are some issue if retro Time Eval. Please look at the following document to clear how to resolve it:

And some other documents for you to refer Useful documents for Schema & PCR configuration

[Former Member]

Hi Ian,

A very log question. I lost in-between.

Anyway, a few things want to tell which will help you. Time evaluation run daily. In case of retro, it will run since retro date till now. When you change any infotype which will force retro, the date is set in PDC recalculation of IT 0003. and when you run time evaluation it reads this field and push retro since this PDC recalculation date.

PDC recalculation - This field specifies the date on which the next time evaluation run should start. When time evaluation is complete, the date is set to the first day for which the report has not yet been run.

To answer your question, i need to know what is relation between addition hrs, total hours for pay and pro-rated holiday credit. First it is good to tell business rule then what is written in PCR. But what i told you above will reduce your confusion. And if you focus now, you can find the answers.

Regards

Aj

[Former Member]

It does help a little, so with what you said about the PDC recalculation date being the first day for which the report has not yet been run, will time evaluation recalculate pro-rated totals based on the additional hours it picked up?

In my scenario an employee received 4 hours of holiday credit for 80 hours worked up until 5/22 and time eval ran through to the end of the month and technically completed the evaluation for the month.  On the first day of the next month , 6/1, an additional 32 hours was entered and approved.  When time eval ran on 6/1, it picked up the additional 32 hours making the total hours for pay 112, which should have given the employee 6 hours of pro-rated holiday credit, however, the pro-rated amount did not recalculate to the correct amount.  The only way I achieved the correct amount was by running a forced recalculation on the entire month.  So the question is why is a force re-calculation necessary?  Based on time evlaution's general behavior, why didn't it recalculate the pro-rated hours?

[Former Member]

Hi Ian,

Technically you are right, it should not need to do forced retro. You have to find out why it is needed. To do so,

Check PDC recalculation date at each time before and after you run time evaluation.

What makes difference and on which date when you run time evaluation without forced retro and with forced retro?

Which schema do you run?

What is the frequency of running schema?

What you put as date when you run on 5/22 and end of month?

Now what i guess is :

Your rule is to create 4 hrs for 80 hrs of work. lets say you run on 22nd of month and some value is generated. that time your PDC recalculation will be 23rd of month, because up to 22nd time evaluation is already made.

Now someone create absence from 15th to 18th and entry has been created after 22nd. Then retro should happen to recalculate worked hours, shouldn't it? You must keep watch PDC calculation after each change in time infotypes.

Regards

Aj