Reply from ranjanatiwari on Jun 11 at 1:45 AM Hi Kiran,
In general, when we upload the data while Go Live, we keep the start date of hiring action as one common date for all employee who have joined before the data load date and maintain original date of hire in IT0041 so that the payroll can be executed from one particular month.
Ex - Date in SAP . 01.04.2010 and maintain Actual Date in SAP in IT0041 if the employee has joined before 01.04.2010.
In your case since the employee's original date of hire 09.04.2004. the ideal way is to use 01.04.2010 as an action date. maintain actual date of hiring in IT0041. Also if you need to correct it. You can use PA41 and change the date of action. Since the date is changing to a later date there will not be any retro accounting. After changing the date , check IT3 and change the dates accordingly .
Thanks.
| | | ---------------Original Message---------------
From: kirankumar
Sent: Saturday, June 09, 2012 8:27 AM
Subject: Changing Date of Joining After Payroll Run
Hi Consultanats,
Please go through below one and could you please suggest whethre we can do or not?
Reference Information:
1. First payroll run date: 01.04.2010
2. First go live date of system: 01.11.2010
1. Changing date of joining after payroll run:
For some employees date of joining was wrongly entered during initial hr personnel actions data upload prior to go-live. For these employees the payroll initial has been run from Dec 2010,
Ex:
Employee with personnel number 00000010 has actual date of joining is 09.04.2004, but in sap it is wrongly entered as 09.04.2001.
Please suggest the process as to how we change the date of joining for these employees.
Also let us know the following
1. Impact on payroll, our main concern is retroactive payroll run for these employees. How can we prevent this? The current retro payroll period is :01.11.2010 in payroll control record.
2. Impact on Time Evaluation retro run. The current time evaluation retro date is 01.04.2012 at employee level maintained in infotype 0003 ( Payroll Status).
3. Any other impact which can put the sap hr system at high risk.
Regards,
Kiran |
| Reply to this email to post your response. __.____._ |   _.____.__ |
No comments:
Post a Comment