Year-end HRSP testing for US Payroll

SAP has released their year-end customer letter for US HR/Payroll customers letting them know which HRSP levels they need to be at by the en dof the year. The HRSP's will be released on October 15, 2009 - and then there's the mad rush to apply them, get them tested and patched-up, and then into production before theend of the year. Or, at least before the first payroll of 2009, and the first W-2 run for 2009.

As we find out more about year-end HRSP issues - and there are always issues with these updates - we'll post them here on the blog. Please feel free to add your experiences in the comments section, too.

Comments

Re: Year-end HRSP testing for US Payroll

Hi Steve, First of all - Thanks for putting together this blog, so that folks like me, can hope for some assistance. The issue I am facing currently is: The organization has a number of PY-Areas based on the differences of their "Pay cycle" and "Pay Structure". Now, after applying the HRSPs 39 through 48 in the test environment, we noticed a slight difference in the payment wage type: "/559" for almost every employee we tested - but for ONLY SOME of the PY Areas (NOT ALL). On refreshing the test environment with the production data (without the HRSPs) these differences vanished, where ever they were occuring. Which leads us to think that the issue might be with the HRSPs - However what foxed us was why it did not occur for ALL the PY Areas. Just wanted to check, if anyone has come across this issue already, or if theres any help you can provide. Thanks.

Re: Year-end HRSP testing for US Payroll

A difference in /559 could also be caused by differences in master data, or in the calculation of gross, deductions or taxes. If /559 is different, then it is likely caused by a difference in one of those components. In the testing I've seen so far at other customer sites, no difference in /559 were found.

Re: Year-end HRSP testing for US Payroll

Hi Steve, Thanks for your prompt response, and your suggestions therein. It turns out that there was something that changed the Fed tax calculation in the test environment for those few PY Areas where we received differences. So, you were right - in a way it was the Master data which was creating the difference. After we refreshed the test system and re-applied the HRSPs - the calculations were correct. Thanks again for your assistance.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions. Registered users are not required to do this - you can register at http://www.insightcp.com/user/register

Copyright © 2001-2010 by Insight Consulting Partners - Contact Information