Bulletproof Your SAP Implementations and Legacy-to-SAP Conversions
- by Tom Sullivan, Senior IT Specialist
- August 7, 2009
Find out the pitfalls that occur most often when converting from a non-SAP legacy system to an SAP system. Then discover best practices to help you avoid these pitfalls and see how you can apply them to your project.
Project success can be defined as providing a well-developed system near its due date (with few or no workarounds or known issues) that provides better flexibility and quality than was available before executing the project. The new system must improve what is already in place and not increase the effort previously required with the legacy system.
Often companies underestimate the work involved with converting legacy system data for a new SAP implementation or upgrade. Because the teams involved tend to focus their skills in certain areas, they tend to use the same steps for each project.
What if the teams were to change their focus so that they continued to build on past experience to improve processes, plans, toolsets, and skills? Such a change in focus adds value to the ongoing conversion tasks and it makes it easier for the project teams to work together. More importantly, it provides the IT team more time to learn the new technologies involved.
I provide details about what you should consider when you plan a legacy-to-SAP conversion, using the materials management module as an example. In addition, I discuss items that may affect SAP system upgrades. To get the most out of this article, you should have a basic understanding of ABAP and BAPIs (for calling ABAP functionality). You should also have some general knowledge about networking and Windows file types, as well as databases and business systems in general.
Would you like to see this full item?