on 08-19-2016 8:46 AM
Hi Experts,
While we are running payroll there are for some employees payroll didnt properly.. it says particular wage type is being missed on the table T512W , that wage type has been delimited on february 2016 itself.. we are not sure why system is searching for that wage type now .
here are the screenshots!!
Thanks
Sriram
Entries in important tables like T512W should not be delimited to a past date, as they are used by payroll functions when payroll retro's to a past period and the T512W data is absent for that period.
You can stop using a w/t in an infotype by delimiting a w/t from a certain date in V_T512Z.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is most likely that some part of payroll function AVERA or some other one is trying to get the w/t details inT512W during the payroll retro to the pay period in which the function fails.
I suggest as below to do
1. In QA for an employee or two with this problem:
a)Copy the data to QA using Infoshuttle or DSM or some such s/w you may have;
Or re-create the scenario in QA.
b)Run payroll to check if the same error exists; if not so, it'd be due to the QA environment or the QA empl data being different from that in production.
2. In Dev, in all the views of T512W (V_512W_B, V_512W_D), copy the delimited w/t entry from the last to-date plus 1 to 31.12.9999, save it in a transport and move transport to QA system/client.
3. In QA, re-test as in step 1.b). If the error is resolved, then you may move transport to prod system/clients.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.