cancel
Showing results for 
Search instead for 
Did you mean: 

Payroll Error

former_member182377
Active Contributor
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

jagan_gunja
Active Contributor
0 Kudos

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.

former_member182377
Active Contributor
0 Kudos

Hi Jagan,

Thanks a lot it was really helpful. But i would like to know the error why it causing.. how it is fetching that?

Could you please help me on that!!

Thanks

sRiram

Former Member
0 Kudos

Dear Sriram,

Kindly check the wage type Start & End date of that wage type in T512W

Regardsm

Vazid

former_member219272
Active Contributor
0 Kudos

you said that the wagetype got delimited in feb 2016 but what was the delimitation date for the wagetype 9390? is it before 31.05.2015?

former_member182377
Active Contributor
0 Kudos

Hi Vijay,

Delimited date is 28.02.2016, but when we run retro on month of 05/2016, it throws an error stating that on this period in T512W it is missing?

thanks

Sriram

former_member182377
Active Contributor
0 Kudos

Hi ,

Start date and end date is 01.01.1900 to 29.02.2016.

Thanks

Sriram

former_member219272
Active Contributor
0 Kudos

sorry i didnt check the year properly it is not 3105.2015 it is 31.05.2016

please can you share the screen shot of 9390 in T512W

can you please is there any IT0014 or IT0015 maintained for 9390 in 2016? if yes then please share the screen shot here

jagan_gunja
Active Contributor
0 Kudos

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.

former_member182377
Active Contributor
0 Kudos

Hi Vijay,

9390 is not stored in the current period.. i have just seen that!! it was one on 2006 after that they didnt capture for any!

Thanks

Sriram

former_member182377
Active Contributor
0 Kudos

Hi Jagan.

Thanks for the reply.. this is what exactly i have done to overcome.. the error. but i was able to reproduce the error in QA, but the problem customer keeps asking why? how come it searches for ?

Thanks

Sriram

former_member193210
Active Contributor
0 Kudos

For that, you have to identify why WT 9390 gets generated in the first place.

Try executing program RPDASC00 for your Payroll Schema

and when you have the report on screen, search for WT 9390.

Answers (0)