Reply from dhar06 on May 3 at 8:57 AM Just lock their record.
Also, if you go into IT0003 and delete the dates from 2 Fields namely Master data change and Bonus date below that, it should not retro back.
Try deleting the dates first without locking them. If this does not help, lock them in IT0003.
Thanks,
Srini
| | | ---------------Original Message---------------
From: Jagan Gunja
Sent: Friday, May 02, 2014 10:57 PM
Subject: Termed Emp Is Pulled Into Rpcalcu0
Let us say dd.mm.yyyy is the payroll period start date corresponding to the payroll period where the retro occurred and the previous pay period start date is aa.bb.cccc
To see the last updates for an employee, do the following:
a. In PA10 txn, go through the infotypes display and see when it was changed.
b. If the change date for an infotype is between the above two dates aa.bb.cccc and dd.mm.yyyy
- check if this infotype could be changing the IT 3 MD Change date.
If so, then this could be the record which caused payroll retro.
If PA10 is not serving the purpose, then you may need to SE16 display for each IT which causes payroll retro and with change date between the above two dates.
Further, I am surprised your config for IT logging has only IT 167/8/9. Standard practivce is that any IT that is sensitive to payroll or time (e.g., 0, 1, 7, 8, 9, 14, 15, 27, 2001-2013) is set for logging. It helps to audit the changes. A System Audit should include checking such change reports. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
