cancel
Showing results for 
Search instead for 
Did you mean: 

Absence Quota Issue

former_member182377
Active Contributor
0 Kudos

Hi SAP Experts,

I am trying to generate absence quota based on seniority based on Date type which we maintain it in IT0041, i chose 01 in IT0041 date is given as 03.08.2010,

I am running time evaulation for the employee from 01.01.2014 to 31.12.2014, but system not determining the seniority based on date type which i have maintained in the table V_T559L

Can any one help me out on this. it still considering the date from IT0000 only. not the date i have given in IT0041

Attached screenshot

Thanks

Sriram

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sriram,

1. Make sure you maintain and activate HDATE feature for malayasia - and set to the required date type in IT0041.

2. Make sure the quota grouping is set correctly in QUOMO feature based on whatever attributes you are using on this feature.

4. make sure quota bank is setup to generate from time evaluation.

4. Finally make sure employee you are using for testing is setup with correct master data.

5. run time evaluation with log on and double click on quota function and see the detailed log. It will show all the attributes TE is using to select data from quota configuration tables.

hope this helps.

former_member182377
Active Contributor
0 Kudos

Hi RK,

I maintained Feature HDATE return value my date type W2,

Quomo is maintained

Quota bank has been chosen as increase

Master data i dont get it . what should be fine

I have run and still generates the same

Thanks

Sri

Former Member
0 Kudos

When I say master data I mean IT0001, IT0007, IT0041...make sure that all this data is maintained correctly...coz typically your QUOMO decision is based on PA/PSA/EG/ESG etc...IT0007 to make sure you have the right time mgmt status..

can you send us the time eval log? run time eval with test mode and with log on...

also make sure you are running time eval from 01/01/2014 to 12/31/2014...I am not sure if you set the accural/transfer of quota to begning of the year or end of the year...double click on the quota function in the schema...and make sure system is selecting the correct quota grouping etc...

make sure HDATE feature is active...

former_member182377
Active Contributor
0 Kudos

Hi Reddy,

I will give you my screenshots to you , here you go, i have attached all

Thanks

Sri

former_member182377
Active Contributor
0 Kudos

Hi Rk,

My other screenshots

former_member182377
Active Contributor
0 Kudos

Hi Rk,

My other screenshots

former_member182377
Active Contributor
0 Kudos

here others

former_member182377
Active Contributor
0 Kudos

others

former_member182377
Active Contributor
0 Kudos

others

former_member182377
Active Contributor
0 Kudos

others

Former Member
0 Kudos

In the screen where you attached your calcualtion process...change the radio button "Key Date for Dtermining Seniority" to "End of Accural Period". This tells the system to calculate seniority from your date type in HDATE to 12.31.2014...

the way you have it right now (pointing to IT0041 date type)...system calculates seniority from IT0041 date type to current year (2014) plus it uses the same DD/MM from your IT0041 date. So if you have 03/08/2010 on your IT0041...then system will simply calcualte service from 03/08/2010 to 03/08/2014...

I also see you are using SENI as your calculation process for service period calculation...This is not really required if you maintain HDATE to point to IT0041 date type...calculation process is required if you have much complex service period calculations or if you have multiple date types to calculate service period. But if you want to use SENI then I am assuming you arleady modified this valuation model to include your date type.  By default they come delivered with date type 01 or calculate based on IT0000 status.

Can you run the program RPUSEN10 for your employee and see what is the service period it returns at end of 12.31.2014. Under calcualtion type use "Calcualte Employment Period Duration" enter from and to date as date type from IT0041 to 12/31/2014.

former_member182377
Active Contributor
0 Kudos

Hi Reddy,

This is awesome one from you. superb, i removed SENI its not required as i discussed with business. i am getting output only one problem i have its not calculation the proration.

03.08.2010 to 31.12.2014, comes around 4.4 years of experince. which means value should be 20.82, isn't but system showing 22 days ,

i have given proration. as you see in screenshot. any problem again for me in configuration.

thanks

Sri

Former Member
0 Kudos

I think that proration works in case of a new hire starting in the middle of the year...but in your case this employee is already with the company for more than a year...his service period is going past 4 years in Aug...but you have only one accural setup for 4 to 14 years...so system is not going to prorate this automatically.

when you say 0 - 4 years is 20 days - is that inclusive? I mean <=4 years get 20 days...or < 4 years get 20 days? The way you have it setup, 0 - 4...SAP treats this as 0 to <=3. So it is bumping you into the next tier which is 4 - 14...and thus giving 22 days. If it should be <= 4 = 20 days then you need to change your configuration to 0 to 5 years = 20 days...

can you tell me how much vacation will an employee with only 2 months of service will get? lets say employee is hired in Feb 2014...when will they get their vacation and how much will they get?

former_member182377
Active Contributor
0 Kudos

Hi Reddy,

So far thank you so much for your reply, its really appreciated .

He 0 to 4, he completes 4 years of experience right, but here has 4.4, which 5 has been started , so last months system should consider 4 to 14, isn't it ?

Moreover. if i give key date of determining seniority on T559L as For Exact day which system should calculate from IT000, right? that moment i get the desired results as 20.82, which means proration works there and its correct isn't it?

Why not here?

Thanks

Sri

Former Member
0 Kudos

I am sorry but if its working correctly then what is the issue you are having? I thought system was calculating 22 days instead of 20.82 days.

If HDATE is maintained then system will go by this first...otherwise it will use IT0000 (I think). In your case I am not sure if you consider employee has 5 years of service when they complete 5 or when they complete 4...and enter into 5th year. Depends on your company rules.

former_member182377
Active Contributor
0 Kudos

Hi Reddy,

before your suggestion i was not getting desired results , it was showing 20 days in constant though i change the years. after your suggestion HDATE i got the results.

Problem is only proration. 22 days system calculates but i should get 20.82, if proration happens,

when system considers IT0000 for seniority , it calculates 20.82 which is correct. but when i gave HDATE, its showing 22 days, so HDATE  not calculation the pro-ration isn't it ?

Thanks

Sri

former_member182377
Active Contributor
0 Kudos

Hi Reddy,

Its working now ,  i have given my customized date type M2 in the feature HDATE, and in V_T559L , i chose for exact day detemining seniority, now it showing pro-ration as i said 20.82 days,

Thank you so so much for your assistance this is really great , you have not only helped me. you have taught me the new thing.

Thanks

Sri

Answers (4)

Answers (4)

former_member182306
Active Contributor
0 Kudos

Hi Sriram

Just go through below thread its clearly mentioned, quotas based on seniority

HCM - Absence Quota Generation

former_member182377
Active Contributor
0 Kudos

Hi Rajesh,

Thanks for your valuable sharing. this is useful too for my other regions who works without time evaluation.

Thanks

Sri

vianshu
Active Contributor
0 Kudos

Hi Sriram,

Can you tell me what is the grant you have to make for different seniority levels? Also, are the validity and deduction intervals as per the seniority date?

Regards,
Vivek

former_member182377
Active Contributor
0 Kudos

Hi Vivek,

thanks for your reply. i do different seniority level like this, 0 to 4yrs, 20 days, and 4 to 14yrs, 22days, 14 to 999yrs 24 days.

so seniority based on years. for example if employee is hired on 01.01.2006 , but date  type working date(W2) is being maintained as 03.08.2010 and they run time evalaution for 2014 from

01.01.2014 to 31.12.2014, it should read from the date type W2 and it should give the value as 20.81 with rounding rule 21 should come. but system still gives 22 days which is wrong isn't it?

Validity date is like this, though he has date type maintained as 03.08.2010, when they run time evaluation for him, it should bring  validity date as 01.01.2010 to 31.12.2010.

Thanks

Sri

former_member182377
Active Contributor
0 Kudos

Hi Vivek,

Any reply to my issue. i am just struggling here and client pressuring me more on this. your help is more appreciated.

Thanks

Sir

Former Member
0 Kudos

Hi,

PCR need two dates to calculate seniority it,s define by your operation which you have mention in HRS=YSAXX ........normally first date is IT0000 begda only ......second date is IT0041..

check with dates... with other employess..

former_member182377
Active Contributor
0 Kudos

Hi Ali,

Thanks for you reply on this.

Actually i tried with my customized date type. But i heard customized doesnt work, you have to use standard one. so i used 01 maintained it in It0041, given the same in the table V_T559L, in the field keyfield to determine the seniority, But still not working. Any idea? why.

If not would you please let me know the how to do this Via a PCR, it would be so helpful to me.

Thanks

Sriram

Former Member
0 Kudos

Hi ,

i already given you how to read the date from It0041 using operation  HRS=YSAYXX where XX  is your date type..

rajasekhar_reddy3
Active Contributor
0 Kudos

Hi,

Have you maintained feature HDATE ??

Regards,

Raja Sekhar

former_member182377
Active Contributor
0 Kudos

Hi Reddy,

i am working for malayasia, but i have not maintained for any, it got default as otherwise = 01 in that feature.

Thanks

Sriram

former_member182377
Active Contributor
0 Kudos

Hi Shan,

As you know my requirement in clear. would you please let me know is it possible to achieve through a PCR, if yes would you please add more light on this issue,

I have three seniority levels 0 to 4 years 20 days, 4 to 14 years 22 days, 14 to 999 years 24 days,

how to achieve this through a time type and PCR

employee hiring date maintained as 03.08.2010 and i am running time evaluation for the whole year 01.01.2014 to 31.12.2014, which means 03.08.2010 to 31.12.2014 will be 4.4 years. so as per pro-ration for 4 years it should consider 20 days for 2014 up to august it will be 11.66 and rest of months for 2014 should be considered as 22 days i mean for that 0.4 years it should be 9.16 days , so on total will it calculate 20.82 days in IT2006,

Is that possible?

Thanks

Sri

Former Member
0 Kudos

HI Sriram,

You did not mentioned that seniority is depend on age or service in a particular company?

generating absence guota base on seniority is possible via configaring "base entitlement" according to your screen print, I can assume that it's based on service in a company which your reading the date of appointment from IT0041. If so. You can write PCR using operation HRS=YSAYXX

Y  Operator

S   will read IT0041 or IT0000.

A  (Date of evaluated date)

Y  (Total years)

XX is your date type.  (01)

Lets say your maintaing date type (01)in IT0041  as  01.01.2000 and running time evaluation upto date  26.02.2014 so system will calulate the years from 01.01.2000 to 26.02.2014 so it will store as 14 years. this you have to add any time type and in another PCR you can compare this years of service an pass the number of quota in to another time type. This time type you have to attached in the base entitlement configuration. ( I'm assuming your using positive time)

Hope this will be helpfull to you.

Regards,

Dinesh

former_member182377
Active Contributor
0 Kudos

Hi Dinesh,

thanks for your very quick reply, My seniority depends on service not an age!!

I have configured three types of base entitlement depend on year 0 to 4 years, 20 days and 4 to 14 years, 30 days 14 to 999 years 45 days in the table V_T559E,

In the table V_T559L, i have chosen date type which is 01 to calculate the seniority , as you mentioned employee was hired on 01.01.2006, But 01 has been maintained in IT0041 from 03.08.2010 only,

Still i need to go for PCR to achieve this??

Thanks

Sriram

Former Member
0 Kudos

Pls can you paste your base entitlement config screen. V_T559E

former_member182377
Active Contributor
0 Kudos

Hi Dinesh,

Please find screenshots attached three screenshots i have attached .  from 01.01.2014 absence quotas we are generating through time evaluation only,

System is calculating the seniority from the date mentioned in IT0000 not from Date type 01 which i have maintained.

Please help me on this. it would be really great. i also heard 01 only can be used not our customized date types.

former_member182377
Active Contributor
0 Kudos

Hi Shan,

Sorry for not completing it, hence the balance screenshots.

Former Member
0 Kudos

In your screen shot. I did not find that you have attached IT0041 (01)

former_member182377
Active Contributor
0 Kudos

Hi Shan,

here you go,

attached screenshot

Thanks

Sriram

Former Member
0 Kudos

Hi ,

you have to attached the related date type in base entitlement config. Look at the screen T559E (down)


and try

former_member182377
Active Contributor
0 Kudos

Hi Shan,

I missed this. i will try wit this. what should i give LNGTH field over there. because system not accepting blank values.

thanks

Sriram

leelamohan_kavali
Active Contributor
0 Kudos

Dear Sriram,

I think so If It's correct or not...?

Instead of going to IT 0041 why don't you try with IT 0019 Monitoring of task.

I tried with IT 0019 It is worked, my scenario is different but like similar to your scenario...!

Ur's

Mohan

former_member182377
Active Contributor
0 Kudos

Hi mohan,

Sorry for late reply. i have consulsted with clients, they are not accepting with IT0019, only with IT0041, why its not working when i go for standard itself.

Any idea? or is there anyway can it be achieved through a PCR    

Thanks

Sriram


former_member182377
Active Contributor
0 Kudos

Hi Shan,

any idea on the issue? any alternative way to achieve this functionality

thanks

Sriram