Reply from rodychk on Jun 11 at 10:15 AM RBS said: I have one doubt on this IF you do the data upload/ Hiring action the system will generate no then that employee will get two perners then what we do? I don't remember the exact config steps or set up steps, since we did this just over 4 years ago. However, we turned off the automatic assignment of PERNR and included our 'legacy' employee numbers as part of our data upload into SAP. We loaded virtually everything using LSMWs and stored original hire dates in IT0041 and did not end up with two PERNRs.
| | | ---------------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. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today. _.____.__ |
No comments:
Post a Comment