With the enterprise-level companies running SAP systems, it's easy for situations to arise where multiple projects are running at the same time, taking up similar resources. If the projects are related to a particular module, this isn't necessarily a problem -- but what happens when they involve something that touches the entire IT landscape, like data migration?
Yogesh Lohiya explores this topic in his latest SAP Professional Journal article, "Develop a Matrix So You Can Execute Multiple Data Migration Projects at Once." He shows you how to put together a matrix that lays out all the projects that will be running, and when they will be running and need certain resources.
Yogesh uses the following example to illuminate how this matrix can deliver value:
Consider a large tablet and notebook manufacturing organization that has multiple business units and is already on an SAP system, but is upgrading to the latest version. It decides to perform this SAP upgrade first on its two biggest business units — its tablet manufacturing unit (project P1), and its desktop and laptop manufacturing unit (p
roject P2). Although these units manufacture different products, most of the master data is common between them: Both units purchase raw materials from the same suppliers, both units have common material that is used in manufacturing the finished product, and both units have common subcontractors. Therefore, one single data migration team is going to perform data migration activities for both projects.
To see how Yogesh develops a matrix that allows these projects to run simultaneously, and without a hitch, SAP Professional Journal subscribers can go here. And if your data migration projects involve data conversion, this related article may be a good resource as well.