Proven tips to avoid the most common and costly SAP ERP HCM 6.0 upgrade pitfalls

by Amy Thistle

July 24, 2012

The following are just some of the tips Winnie Chu, AspireHR will discuss in detail during her presenation on "Proven tips to avoid the most common and costly SAP ERP HCM 6.0 upgrade pitfalls" at the upcoming HR Singapore event, 16-18 October.

Project Prep:
•Utilize Project Templates to avoid rework
- Logistics, as well as the functional and technical scripts, can be re-utilized for future upgrade projects
•Identify the Process Integration
- The key activities, such as Planning, Standards Definition, Testing Plan, Execution of QA Testing, Approvals for Production were developed with the participation of all the business process teams working together in the same facility
•Go-live date
- Should not have an impact on Business system requirements (Month-end close, etc.)

•Oracle and SAP GUI should be upgraded prior to the SAP upgrade
•Discovery phase: Access to an ECC 6.0 sandbox system is a must-have
- Make sure that this is in place prior to the Blueprinting Phase
•Keep a copy of the pre-upgrade SAP system around (i.e., v4.6c) for at least one month after Go-Live

•Review all custom programs no longer used in the pre-upgrade system so that they can be deleted prior to upgrade
•If all roles were not maintained in a pre-upgrade system using transaction “SU24,” they will not be migrated and, therefore, must be updated manually
•The better the quality of documentation on modifications, the easier the modification adjustments can be performed
•Ensure that testing includes archived data
•Test printers by sending a spool to at least one of each different printer model type
•Conduct daily “open defect” meetings/conference calls during final testing

An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!