On the left-hand side of the above figure, you see the planning of a new landscape version. These deployment models are described in the details section. The upper part comprises cloud solutions (mostly) managed by the provider as managed private cloud, PaaS or SaaS cloud. The lower part of the landscape comprises systems directly managed by the customer installed on-premise or in a private or an IaaS cloud. Left and right of the Landscape Management Process you find the main tools related to or supporting the process.
The following functions consume landscape data or Maintenance Planner output: The Maintenance Planner allows planning of changes for SAP systems in your landscape. Several functions have been integrated with the Maintenance Planner as utilities: Also see a comparison of SAP Solution Manager, SAP Focused Run (FRUN), and SAP Cloud ALM (CALM). The green frame at the center shows its core functions: System Landscape Directory and SAP Solution Manager Landscape Management Database provide data for various other processes like monitoring. The picture shows a customer landscape and the tools used in landscape management. (For a step-by-step video explanation, click the link or the figure use the cc button to toggle sub-titles.) In this document, you'll find the roles involved and a list of key components and tools they need for their tasks.įigure 4 : An IT landscape comprising systems of various deployment models with tools and steps of the landscape management process. The steps shown for one cycle of planning and implementing changes are performed by different people in a company, fulfilling different roles. These iterations, are, of course, not clearly separated: Running in cycles, in the next step, the "new landscape" being planned becomes the one you use, and the next level gets into the details planning phase. Having reached it, the cycle starts again. The steps to move from one state of the landscape to the next are based on the status quo to find the required changes to reach the next level. The question where the landscape's layers are running, and who is responsible for which layers, is described in Deployment Models and SAP Offerings - On-Premise, Cloud, and Hybrid. In the picture, you see a landscape evolving from an pure on-premise to a hybrid landscape including cloud systems. (To see a video explaining the picture step-by-step, click the link or the figure use the cc button to switch sub-titles on or off.) The following figure shows the landscape evolution and its phases:įigure 1: A landscape going through a change process in iterations to adapt to emerging business opportunities and new technologies.
Information required to integrate software you subscribed to.Ways to change your landscape comprise installations, updates, upgrades, and conversion to SAP S/4HANA and SAP BW/4HANA.Information on IT landscape's status quo as a basis for both landscape operation and change planning of SAP centric solutions.The landscape management process helps you, run and evolve your IT landscape providing: Here, specifically, exploring fundamentally new options and getting recommendations on the implementation on the landscape level is key.
Often, it will introduce "natural" changes, such as the next Support Package or enhancement package.
Global License Audit & Compliance Services.