How to control control Earl.pers.rec.date in -ve Time Evaluation

[Former Member]

Hi guys,

My company have go-live -ve time evaluation in the early year of 2010. However because of some

user/config problem, we have decided to open leave quota to allow HR key-in leave quota manually.

We decided to use program RPTIME00 started early 2012. However, I have a few question to ask :

1. How to config to control Earl.pers.rec.date so that the Earl retro start only 01/01/2012.I don't want system to retro to 2010 because it will cause havoc to the system.

2. If I control the earl. retro start 01/01/2012, how can system determine carry forward for 2011.

For example :

01/01/2011-31/12/2011 Annual leave -20 days(User key-in manually)

Staff don't use leave so that his/her carry forward will be 5 days in 2012.

For Program rptime00 Earl.pers.rec.date start 01/01/2012,it won't generate carry forward for 2012 based on 2011

leave.How to allow system to generate carry forward 2012

3. For certain leave, for example medical leave,leave entitlement based on seniority. 0-2 year is 18 days and 2 years onwards 20 days.In 2012, staff exist since 2010 will get mc 20 days. IF I control Earl.pers.rec.date the sytem will calculate as 18 days. How to avoid this and let the system calculate 20 days

TQ in advance

[Former Member]

The modifier for Earliest Recalculation date indicates the date in 6 recalculation categories. These six categories are:

■01 u2013 Incentive wages

■02 u2013 Time evaluation

■03 u2013 Time statement

■04 u2013 Pair formation

■05 u2013 Earliest time data carry-over

■06 u2013 Latest time data carry-over

Once these dates are configured, the system will not allow retro accounting before the date specified.

A classic example for configuring these dates is particularly during Go-Live. We do not want the Time Evaluation or Pair formation to occur prior to the Go-Live date

There are two steps in configuration:

Step 1: Configuration of table V_T569R:

In Table V_T569R we specify the recalculation category and specify the date.

Step 2: Config of the Feature TIMMO

Feature TIMMO defines the modifier to read the table T569R within time management. The return value in TIMMO can be configured based on employeeu2019s Company Code, Personnel Area, Personnel Subarea, Employee Group, Employee Subgroup, or Country Grouping

[Former Member]

1. How to config to control Earl.pers.rec.date so that the Earl retro start only 01/01/2012.I don't want system to retro to 2010 because it will cause havoc to the system.

You may want to update it0003 using a bdc/lsmw for this... a bit of testing is required though and it is best you have a sap-time/py consultant at hand.

2. If I control the earl. retro start 01/01/2012, how can system determine carry forward for 2011.

For example :

01/01/2011-31/12/2011 Annual leave -20 days(User key-in manually)

Staff don't use leave so that his/her carry forward will be 5 days in 2012.

For Program rptime00 Earl.pers.rec.date start 01/01/2012,it won't generate carry forward for 2012 based on 2011

leave.How to allow system to generate carry forward 2012

A simple way would be changing the end date of the quota....

3. For certain leave, for example medical leave,leave entitlement based on seniority. 0-2 year is 18 days and 2 years onwards 20 days.In 2012, staff exist since 2010 will get mc 20 days. IF I control Earl.pers.rec.date the sytem will calculate as 18 days. How to avoid this and let the system calculate 20 days

hmmm I am not a time consultant so not sure how to answer this but from a logical point of view shouldnt the seniority be taken from it0000 by the time-eval ?? and not based on it0003? Dont know personally but would assume so,.. if that is true then again answer to point 2 should solve this...

Last but not the least: you would do well to have a time and pay specialist to address your issues mate..

cheers