As nearly every SAP customer knows, “extended support” of many earlier versions of their software will end by March 31, 2013, causing many companies that have delayed their SAP upgrades to now be faced with a large and potentially disruptive effort in a compressed timeframe.
Last week we published a whitepaper entitled “The Seven Deadly Sins of SAP Maintenance” that addresses this issue. It highlights the seven mistakes that companies MUST avoid when they upgrade their SAP systems in order to stay current with their software going forward.
Ensuring that you avoid each of these Seven Deadly Sins means fundamentally changing the way you look at SAP upgrades and enhancements—including implementation of new process methodology. The advice discussed in the paper is true regardless of whether you are focused on a major upgrade such as going from ECC 4.6c, 4.7 or 5 to the new ECC 6, or simply implementing the latest enhancement and/or support packs. By recognizing the perils presented by the Seven Deadly Sins prior to beginning of a major upgrade process, your company now can guard against ever being in this uncomfortable position again.
The first Deadly Sin that companies must avoid is: Treating SAP Maintenance as an Isolated Event.
We polled our customers and found that companies that viewed their original SAP implementation as a one-time project were more likely to be behind on upgrades, enhancement packs and transports than those companies that looked at SAP maintenance as an ongoing endeavor. Devoting steady, ongoing resources to the maintenance of SAP is essential to avoiding accumulation of a backlog so daunting that it begins to look insurmountable.