PT60 with error no. 83 - Complex application error has occured

[former_member103011]

Hi,

Our client has a error while running PT60 for one employee. The employee was under worksmen cadre got confirmed on 01.04.2014 and changed to staff cadre, so his EG & ESG is also changed on the same date.

Now they have changed his date specification as Technical date of entry as 01.05.2015 and they have run PT60 and got the error as in attached doc.

The error comes in the processing of 01.04 2015 month datas. The CL and SL is not fetched. But Earned leave is fetched for him for 01.01.2015 to 31.12 2015.

Kindly help me out to resolve this issue. Its very urgent.

Thanks

[Former Member · Accepted solution]

Hi Raja,

Looks like worksmen has different CL and SL quota than confirmed employee.

Thumb rule : When you change ( employee group / sub group ) or (Personnel area / Personnel sub area), And some existing quota is not valid for new combination ---> delimit the existing quota in IT2006.

Regards

Ajay

[former_member103011 · Accepted solution]

Hi Ajay,

Thanks for the reply. As you said unable to see the previous entries of CL, S in IT 2006. Only the newly fetched EL appears. Let me know how to check it.

[Former Member · Accepted solution]

Also , If you change technical date of entry then system will consider it has been hired on that date.

Do as below.

1. Change technical date of entry and this should be hiring date.

2. Run time evaluation from 01.01.2015 to 31.03.2015 (last date in his earlier employee group).

3. Run time evaluation again from 01.04.2015 to 31.12.2015.

Share what are you getting, now.

Regards

Ajay

[former_member103011 · Accepted solution]

Hi,

Thanks for the reply.

Already they have maintained Date of Hiring in Date specification, the Technical date of entry was changed from 01.10.2014 to 01.05.2015. I cannot change in PRD, I need to inform the client to change. So let me know if I change there will be no error, then I can inform them to change.

Pls let me know if i need to check any more details

[venkat_polisetty · Accepted solution]

Hi,

Kindly check the configuration entries in table "V_T559L"

Regards,

Venkat Polisetty.

[former_member103011 · Accepted solution]

Hi

I have checked the details. But every thing is perfect. Only this employee is in error..

Let me know any thing to check particularly

thanks

[venkat_polisetty · Accepted solution]

Hi,

The issue is in your configuration only. Kindly check configuration in the table V_T559D and if you configured wrong intervals the program couldn't determine the validity period.

Please, review your configuration steps and if you don't figure out what is causing the issue let us know how you configured the tables.

Regards,

Venkat Polisetty

[former_member103011 · Accepted solution]

Hi

This is the screen shot of V_T559D  for Cl, same as Sl

All configurations have ES-1 PSG 40.

Any more need to check.

Thanks

[former_member182377 · Accepted solution]

Hi Premavathi.

Please check the configurations , is there any grouping is missing.. any Date Type has maintained in sick leave configuration.

please check the dates as well.. once..

Thanks

Sriram

[venkat_polisetty · Accepted solution]

Hi,

It seems a configuration Issue, kindly cross check your entire TM configuration once.

Regards,

Venkat Polisetty

[former_member103011 · Accepted solution]

Hi

I have checked the configurations. Not able to find out.

Pls check the below screens. Any more to check, pls let me know.

Thanks

[vianshu · Accepted solution]

Hi Premavathi,

Honestly speaking, this is so generic an error message from SAP that one would require access to your system to analyze and find it.

I would recommend that you get this issue debugged by your ABAPer and try to address it.

This is my opinion.

Regards,

Vivek

[former_member103011 · Accepted solution]

Hi ,

I created the same scenario for an employee in DEV. Understood that the issue raised for employee when he is changed from worksmen to staff cadre (EG, ESG only changed). When he was worksmen he is not allocated to any leave. When PT60 is run for him, the system has to replace the new CL & Sl on the old.

As there is no old entries for CL & SL, I used the SAP Note No.484834 - Quota generation after organizational reassignment and created dummy Absence Type - CL & SL (T556A). Again its showing same error. Can any one help me out.

Thanks in Advance.

[former_member103011 · Accepted solution]

Hi All,

Thanks for the replies. I rectified the error. Now Time evaluatin is working fine

[former_member182377 · Accepted solution]

Hi Premavathi,

Glad to see that you have solved the issue.. it would be really great if you let us know what was the issue and how did you fix it..

That would be great and benefit for other SCN users a well.

Thanks

Sriram

[former_member103011 · Accepted solution]

That's fine.

The error incurred as there was no CL, SL for the worksman cadre. When we run PT60 it over writes the existing entries of CL/SL.

As per the SAP Note 4848234, I copy created the existing CL, SL types for the Old grouping. Then run PT60 for the employee and found no error.

Thanks

[venkateshorusu]

Go through below link and you will get lot of information once you google it.

error no 83 in sap hr - Bing

Time Evaluation error – ‘error no. 83′ | SAP HR

Time evaluation Error 83 - Toolbox for IT Groups

Time Evaluation error - 'error no. 83' - Wiki NewForum

Regards

Venkatesh

[former_member103011]

Hi Venkat,

Thanks for the reply. I have checked in google, still unable to rectify it.

[jagan_gunja]

This message is displayed for any one of several errors that can happen during the processing of QUOTA function.  The function does not provide full details of error/s.

What we have been able to do, is to search the code for QUOTA function or RPTIME00 pgm for the message number or something similar and set a break point before it displays.  and even for each one of the several hits of the message.  Then run time eval for the employee and find the reason/s in ABAP debugging.

Since the error has not displayed for some quota types, the problem is in the one or those not displayed.