The new Maintenance Plannerapplication hosted at the SAP Support Portal offers a simplified way to plan new installations, updates, and upgrades. As a key prerequisite, the Maintenance Planner consumes system data from the Customer Profile, which is provided by the SAP Solution Manager systems in the customers’ landscapes. With SAP Solution Manager 7.1 you had to take several use cases into account – see Product Systems and Maintenance Planner in SAP Solution Manager 7.1– now, let’s talk about simplification in that area with SAP Solution Manager 7.2 …
Entities and Consuming Applications in the Different Scenarios
So let’s have to have a look at the big picture of landscape entities, their relations, and consuming tools with SAP Solution Manager 7.2 – you’ll see them in the following figure:
Figure 1: The detailed big picture of landscape management with SAP Solution Manager 7.2 and the Maintenance Planner. Data of technical systems are sent to the LMDB via the SLD. In the LMDB they are enriched and uploaded to the Customer Profile to be available for the Maintenance Planner.
Using Data in SAP Solution Manager 7.2
With SAP Solution Manager 7.2, tools, entities and processes are significantly simplified.
In the on-premise part of SAP Solution Manager, technical systems’ data is used to create…
… technical scenarios, which are used in monitoring
… maintenance dependencies in the Maintenance Planner and
… logical components, required e.g. by Change Request Mgmt (ChaRM)
Product systems and Maintenance Optimizer (MOpz) are gone; the LMDB concentrates on gathering and enrichment of technical systems’ data.
The Scope & Effort Analyzer consumes maintenance transactions from the Maintenance Planner.
Using Data in SAP Support Portal Services
Product system data is uploaded together with technical systems’ data. Technical systems’ data is used for the Maintenance Planner as a target for planning including the definition of dependencies between systems, namely maintenance dependencies, used to update product installation that run across technical systems and system tracks, used to keep product versions in systems in roles like development, quality assurance, and production in sync.