Reply from Nadir.Sheikh on Mar 16 at 12:38 AM Dear Leah Holton,
Error message is misleading as this table does not exist. It actually to table T549Q which in turn points to table T510W. This table holds the link between the payscale type and area and the period parameter. The permissible entries may point to a weekly period parameter - which is fine for weekly employees. Get the monthly combinations to point to a monthly period parameter e.g. 01 - GB Monthly.
Any issue pl. revert
Thanks & Regards,
Nadir Sheikh
| | | ---------------Original Message---------------
From: Leah Holton
Sent: Thursday, March 15, 2012 4:09 PM
Subject: An Error Occurred When Reading Table T549Q
Payroll is running OTMU IDOC and some EEs are kicking out due to following error:
"An error occurred when reading Table T549Q"
This only happening for some people, not all - and all EE's are within the SAME PAYROLL AREA.
I checked 0003, 0415 (in fact look at nearly all infotypes for these EE's) - and everything looks "fine" when compared to those EE's who pass through without issues.
In all case, EE's have dates that fall within created payroll period. Checked T549Q - looks good.
I have had this issue before, and we never got an answer that worked. Instead, payroll manually entered these people directly into ADP.
Someone had suggested running PU12 but this did not work. BUT perhaps I did not run it correctly. Can anyone advise as to how we would use PU12 to push these EE's through? Just odd to me that some EE's can "read Table T549Q" without any issues for the same payroll area and others cannot. |
| Reply to this email to post your response. __.____._ |  _.____.__ |
