Introduction
IT landscapes constantly change for different reasons: Updates may be required for technical reasons or – very importantly – because there is an way to improve a business process. Such a change, however requires several roles to work together: Line of Business, finding ways to improve a business process, the IT Architect, evaluating planning the best way to implement the change requested by the Line of Business (or even a user), and the Basis Administrator proving the landscape data for the planning process and perform the implementation.
Best Practice Guide to Planning Landscape Changes
This process, which involves several roles, also requires the use of several tools. Now, the recommended process is described in a document:
Planning Landscape Changes – a Best Practice Guide – is available in a new version now
Best Practice Guide – Planning Landscape Changes
New Version
2nd published version – description of process steps and tools as shown in figure 1 using the Maintenance Planner.
Figure 1: Tools and activities involved in the best practice process of innovation adoption to update or upgrade installations of SAP Business Suite products taken from the best practices guide. You see that the maintenance planner has taken over the place of the maintenance optimizer.
1st published version
Description of process steps and tools as shown in figure 2 using the maintenance optimizer.
Figure 2: Tools and activities involved in the best practice process of innovation adoption to update or upgrade installations of SAP Business Suite products taken from the best practices guide.
Feedback
We are working on this process in a group dedicated to Release Management and Innovation Adoption. This guide will be updated reflecting progress in process described – please feel invited to give your feedback!
One hint: I plan to inform about updates of the guide in this blog – so you may want to bookmark it.
.
.
.
Hi Wolf,
some feedback, since you invited feedback.
As somebody who architects landscape upgrades I can say, this guide is excellent, especially the detail it goes into regarding setting up the lmdb as one of the tools for identifying version dependencies between systems in collaboration with the /uda as this is one of the biggest challenges for me, checking to the nth degree the version dependencies between systems. If we get this wrong, we’re in trouble.
Best regards,
Andy.
Hi Wolf,
Thank you very much for sharing this information. It is a good orientation of SAP landscape changes.
This is useful for all and just a suggestion that if this gonna be added to guides.
Best Regards,
Prabhu Reddy.