Landscape Planner offers
- Visualization of the landscape based on the customer profile data uploaded to the SAP Service Marketplace
- Planning of changes in the landscape and defining it in a landscape plan
- Hand over of a released landscape plan to Maintenance Optimizer as a basis for download basket calculation
Landscape Planner is now generally available hosted on the SAP Service Marketplace.
Prerequisites for the Use of Landscape Planner
Landscape Planner works on landscape data available in the customer profile, which companies upload from their SAP Solution Manager for the purposes of Early Watch Alert and the setup of support connections. These data go from the technical systems to the SLD to the SAP Solution Manager, where based on the technical systems’ data, landscape data are created – here you need the product systems, which are created in SMSY or LMDB.
Apart from that only a few notes need to be implemented in SAP Solution Manager 7.0 or 7.1.
Use of the Landscape Planner
Landscape Planner consumes data of technical systems ond product systems uploaded to the SMP from the local SAP Solution Manager.
Note, that landscape data should be verified prior to the upload to the SMP.
Figure 1 describes the use of the Landscape Planner:
Figure 1: Workflow in the creation and consumption of a landscape plan – you see the phase in landscape plan creation and consumption; the screenshot shows a product system with the installed product version its technical systems (at the bottom) and the button for the available update options.
- In step 1 the landscape architect uses the Landscape Planner to visualize the IT landscape and check for update options.
By selecting one or more target systems and the changes to apply (add-on or EHP installation, update or upgrade) he or she creates the landscape plan.
This can be validated printed discussed and in the end released.
- In step 2 the landscape plan is evaluated and released and handed over to the IT Admin.
- In step 3 the IT Admin imports it into the SAP Solution Manager Maintenance Optimizer (MOpz).
The defined targets like product version or stack level in the landscape plan cannot be changed – the only things open are for instance kernel, additional
Java patches or certain Business Packages.
- The Stack-XML and download basket can then be handed over to the local IT Admin.
- The implementation is done with the Software Update Manager (SUM).
You can go and try it on the SAP Service Marketplace. All necessary information on the Landscape Planner and where to start it, you’ll find on the SMP under http://service.sap.com/mopz.
So in a nutshell, Landscape Planner eases the planning of changes by visualizing the effects and allows for a defined process in handing over the result one role reached to the next responsible person.
More you’ll find at the SCN under