Your IT landscape consists of all entities running your business software. To keep your business running and continuously improve your processes, both servers and software are changing constantly. In the big picture of things, you find, typically, three states of IT landscapes:
Figure 1: The landscape evolving constantly to keep pace with emerging business opportunities and new technologies.
In the picture, you see a landscape evolving from on-premise only to a hybrid landscape including cloud systems. The question, where the systems are running, and who is responsible for which layers, is described in Deployment Models and SAP Offerings - On-Premise, Cloud, and Hybrid.
The process steps to move from one state of the landscape to the next is based on the status quo to find the required changes to reach the next level. Having reached it, the cycle starts again. 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.
The steps shown for one cycle of planning and implementing changes are performed by different people in a company, fulfilling different roles. In this document, you'll find the roles involved and a list of key components and tools they need for their tasks.
To manage the required changes, people in different roles are involved. The main roles in landscape management are from the areas of:
So business, IT architecture, and Basis administration need to work closely together in planning changes to their company's landscape to identify required changes, plan and evaluate them based on the current landscape description, and prepare the implementation of new or additional software product versions.
In the next figure, the steps in changing a landscape are shown; in this example, the company is evolving its landscape from a pure on-premise set-up to a hybrid landscape. New options are identified by mapping existing functions to new offerings, the plan for changes is created and implemented:
Figure 3: Roles and their tasks in planning changes - where tasks overlap, coordination is highly recommended.
Note that this process will run the better, the better the communications between people in the different roles work. The tools you will use in planning landscape changes support communication.
In the next section, you'll get information on the entities and tools involved.
There are several tools that help in people in involved roles to perform the different steps during the planning of landscape changes. The most prominent is the SAP Solution Manger, which integrates mandatory tools and provides data for the whole landscape management and related processes in SAP Solution Manager, so it's the first in the list.
As shown in the following figure, SAP Solution Manager is a key component in landscape management:
For more information available at the SAP Support Portal, see Application Lifecycle Management in general; you'll find SAP Solution Manager, its Cloud Extensions, SAP Cloud ALM, Focused Solutions, and a Community link.
Figure 4: Systems in various deployment models and main applications and their connections in landscape management.
On the left-hand side of the above figure, you see the planning of a new landscape version. You can get recommendations, freely browse for innovations, and map your findings to your business needs.
The result will to a subscription to software and services and/or to planning new installations, updates, upgrades, or system conversion to be downloaded and applied to your landscape.
As described in the section on deployment models, on-premise will be addressed with the latter in different depth of responsibility. As an example, for the IaaS cloud, you will only subscribe to the infrastructure but handle the installation yourself – that's why you find it described as being a “direct” part of your landscape. As we will see later in the section on connecting all parts of your landscape, from that perspective, the view on IaaS is different.
In the following, you will find explanations of the elements shown in figures 3 and 4: Deployment models, landscape entities, tools for involved roles, and services in or related to SAP Solution Manager are explained.
The sections are described as tasks and follow a "natural" sequence, leading from understanding and describing hybrid landscapes, finding new options, mapping them to your needs to define a new landscape version, getting recommendations and detailed planning and implementations of the results. The list is closing with two offerings that help you in managing your landscape.
The following table explains deployment models, their purpose, names combinations and provides example of products in an SAP system landscape. Note that there are different sorts of public cloud offerings, that you can get from SAP and partners.
|On-Premise||Private Cloud||Public Cloud|
Pick your software
- SAP S/4HANA
- SAP ERP
Build and manage your cloud.
- Any SAP software you install and run behind your firewall
- SAP HANA Enterprise Cloud offers a similar scenario in a managed private cloud
|IaaS: Consume infrastructure as a service (network, CPU, DB, etc.); deploy SAP systems & your own software.
- Examples offered by SAP partners: Google Cloud Platform, Amazon Web Services, Microsoft Azure
|PaaS: Consume a platform as a service using services managed by SAP; build and control your own apps.
- Offering: SAP Cloud Platform
|SaaS: Consume software as a service and benefit from operations being handled for you including provisioning, updates, and security handling.
- Examples: SAP S/4HANA Cloud, SAP SuccessFactors
Combining any cloud offering with your on-premise systems, you will get a hybrid landscape.
Combining different cloud offerings to build your landscape w/o on-premise systems, you'll get a hybrid cloud.
The big difference of the various deployment model are not necessarily different technologies, but the responsibilities and level of control that you have. The following picture shows this in a generic, simplified way - concrete offerings can differ slightly from this:
Figure 5: Deployment models and responsibilities for stack layers and the relation to differentiation.
From the different level of control that you have, you can get to the fact that the more control you need for differentiation purposes for a certain function, the more probable you will choose an on-premise or private cloud solution. These, as shown in the table above, can, of course, be combined. On the other hand, with cloud-based solutions, you get predictability of costs and benefit from managed standardized services.
But note, that differentiation is also possible when consuming, for example, ERP as a service with SAP S/4HANA Cloud: Using the PaaS services of SAP Cloud Platform, you can develop on top of the digital core. For more detail, see Develop on Top of the Digital Core SAP S/4HANA - SAP Cloud Platform further down this page
The following link will provide you with a detailed description of responsibilities for stack layers for the SAP Cloud Platform development scenario.
In the following, you will find examples for SAP products in various deployment models. For a complete list sorted by portfolio categories, see All Products.
In addition, while information for on-premise systems regarding security, availability etc. are obviously available to you, to learn about SAP's offerings in the cloud on data centers, agreements, and availability of cloud products, see the SAP Cloud Trust Center.
As we can see from the table above, there are more ways to deploy software as there have been before. The reason to choose a hybrid setup lies in the functions offered by the vendor and in the level of control need for the functions - think of specific versions you want to use or maintenance windows. These requirements, by the way, will not be the same for all areas in your whole IT landscape: While you might go for maximum control for your core applications that you use to differentiate in the market, for other applications you might want to benefit more from consuming highly standardized cloud services that helps IT concentrate on your core tasks.
Examples by deployment model:
SAP's next generation ERP offering is available in a big variety of different deployment models:
In all deployment models you'll get a real-time enterprise resource management suite for digital business. The main difference is - as described above - mainly in the level of responsibility and control on system layers.
SAP Business One - ERP for Small Businesses
Describing your IT landscape is a prerequisite for its maintenance and monitoring using SAP Solution Manager - the central for the management of system landscapes. In detail information on the SAP Solution Manager can be found on the SAP Service Marketplace following the quick link solutionmanager. Here information on the landscape description is gathered. In the following you'll find a selection of blog posts that shall help you better handle you landscape data, which are a prerequisite for running business applications, systems, and Application Lifecycle Management processes alike.
Here, you find explanations, how products are maintained even if they have been installed on more than one system:
Here, you can find details about SAP software product versions, including availability and end of maintenance dates, upgrade paths, and technical release information (database platforms, Java platforms, operating systems, etc.).
Data describing your current landscape status is required to manage running processes and plan landscape changes.
The tools, what data you get, and what purpose you need to use them for, depends on the deployment models you use in your landscape.
Figure 6: Landscape information retrieval for various deployment models.
Following the responsibilities for the stack, landscape data from on-premise, private cloud, and IaaS installations are registered in the SLD and synced into the LMDB. Data from SAP HANA Enterprise Cloud (HEC) are also forwarded to an SLD in your landscape.
For HEC, PaaS and SaaS, the data (tenant and data center) is handled by SAP in a Cloud Landscape Directory (CLD) and made available in the One Support Launchpad and displayed in various apps like the Cloud Availability Center.
For monitoring purposes, these systems additionally can be represented by external services created in the LMDB and used like technical systems then. In the Wiki on Interface and Connection Monitoring Setup with SAP Solution Manager 7.2, under Channel Creation in Interface and Connection Monitoring you'll get an overview of where to use and create external services.
So, you need to gather data from systems that you run yourself on-premise, in a private cloud, or on top of a IaaS cloud you subscribed to. To learn more about the tools to gather landscape data follow the links to System Landscape Directory (SLD), and SAP Solution Manager Landscape Management Database (LMDB).
Data from SLD and LMDB is increasingly used in the SAP Support Portal, especially the Customer Profile used by the Maintenance Planner; this, however, will only work, if SLD and LMDB are used and connected correctly in your landscape and to the Customer Profile - we call this their topology. To learn about the topology recommendations, read...
Verification of landscape data is an important step in having a valid landscape description, now integrated in the Maintenance Planner for landscape data in the Customer Profile. For more information see:
While SLD, LMDB, and Customer Profile focus on the systems run by your company or directly assigned to it, you can directly access information on all your systems including those you consume in the cloud - as PaaS, and SaaS - in the SAP Support Portal. For more information, see ONE Support Launchpad.
Process Management is offered by SAP Solution Manager. As of SAP Solution Manager 7.2 we regard all the systems in your landscape and all your processes your solution: This comprises processes running in your systems, SAP and non-SAP, plus manual processes.
From this point of view the solution is what you address when you improve your business processes. Use Process Management to manage your solution bringing information of business and IT architecture together. This will help you draw the new landscape version that maps new functions to landscape entities; or simply: putting the right product version to the right system: You can now model your processes graphically, and you can manage their lifecycle holistically, based on your solution documentation. You can create artifacts that are shared between multiple processes efficiently.
Process Management is divided into two parts to plan the structure of your company's solution and administrate it.
SAP Solution Manager 7.2 offers a comprehensive structure to manage your company's solution:
To accomplish this, leverage the SAP Solution Manager 7.2 process modeling capabilities to create Business Process Model and Notation (BPMN) diagrams. In addition, model the relationship between processes to better understand how your processes are interrelated.
Through new process management capabilities, you can also call for subject matter expert assistance to document a company's core business processes. For detailed information see:
This is about the solution administration part of Process Management: The system landscape comprises all your applications and systems. Systems fulfill different purposes related to the products installed, - for example SAP S/4HANA - in different roles - development, test, production, etc. To make documenting your landscapes easier for you, SAP Solution Manager offers a flexible grouping mechanism called logical component groups to define the Logical System Architecture: These groups allow you to categorize systems according to their purpose and role, and to create abstraction layers that make it easier for non-technical users to link processes to systems or sets of systems.
Find the innovations and features that you can turn into tangible value for your business from the areas of SAP S/4HANA, digital transformation, and user experience (UX). Information is provided for both business, listing functions and benefits and IT architecture, stating the technical view on product versions and deployment options.
Available and planned features can be filtered by industry, line of business, and technology.
Before implementing an SAP product, you have to decide what to use in the future, how the main components of this product will be deployed in the system landscape, how custom code or your developments can be integrated, and how the new landscape is configured.
In the following, you'll find sources of information for the roles involved in landscape management.
Once you have a understanding of the big picture and where you want to go, here you'll find the detailed information relevant for the projects to manage it:
SAP Activate is a framework, focusing an SAP S/4HANA, meant to provide concrete help along the process of digital transformation: Once you have a understanding of the big picture and where you want to go, here you'll find the detailed information relevant for the projects to manage it.
You can get recommendations regarding new options to improve your business processes.
Two different sources are available also considering, how experienced you are with SAP:
Before implementing an SAP product, customers have to decide how the main components of this product will be deployed in the system landscape.
Typically, now, the products have various deployment models, which result in different system landscape architectures with different characteristics. It is therefore up to you as the owner of your landscape to decide which deployment option best suits your IT and business needs.
To find recommendations and tools to plan a new landscape state - which will very probably be a hybrid one - in advance and including its integration, see:
In most implementations of SAP systems, modifications exist. They need to be analyzed for being still necessary, compatibility with the new implementation, etc. For details on how-to manage custom code in conversion projects, see:
For SAP's new options for development, further down on this page, see Develop on Top of the Digital Core SAP S/4HANA - SAP Cloud Platform.
Usually, as a basis administrator, you will have to deal with the landscape planned mostly by business and IT Architecture; but - as discussed for the roles in landscape management at the beginning of this page -, you should be part of the discussions.
This is especially important when it comes to systems managing systems of your landscape: The topology of SLD, LMDB, and source of information on cloud systems. This is described in the following sections of this page:
To get started on your digital transformation journey, you need to map your business needs to the functions and ways to implement them offered by SAP. The SAP Transformation Navigator offers information for business (for example value drivers), and IT architecture (for example detailed information on available deployment options), plus guides for basis administration.
Mapping your current business functions to a new IT landscape can be done by freely selecting products and capabilities of interest or based on concrete information on your current landscape read from the customer profile.
For details, open the Transformation Navigator overview.
As shown in figure 3, there are several ways to make big changes in your landscape. The following picture shows the ways to get from an on-premise Business Suite around SAP ERP 6.0 to an SAP S/4HANA-centric landscape.
Figure 7: Ways to get from an SAP ERP 6.0-centric landscape to SAP S/4HANA / SAP S/4HANA Cloud-centric one.
So, as shown in the figure above, there are several deployment options:
In many cases, the change of your system would include taking over data from your former system. For detailed information on the ways to handle the move to the new ERP, see
For subscription information, you need to visit the vendor's product page. For you to get an overview of the differences of the deployment models, see Deployment Models and SAP Offerings - On-Premise, Cloud, and Hybrid. Here is examples of products offered for subscription with links to the product's pages (for a complete list sorted by portfolio categories, see All Products):
There is a wide area of functions offered by SAP as software as a service:
Usually, you will use these services in addition to your ERP solution. SAP has one platform as a service offering:
While SAP does not offer infrastructure as a service as a vendor; partners solutions are available:
Managed Private Cloud:
The Maintenance Planner combines functions required to plan system updates, upgrades, new installations and system conversion to SAP S/4HANA and SAP BW/4HANA. As has been discussed in the section on deployment models, this also applies to systems run in a private or IaaS cloud.
All calculations of changes affecting existing systems are based on system information mostly provided via System Landscape Directory and SAP Solution Manager Landscape Management Database.
The Maintenance Planner offers maintenance dependencies as a successor of product systems - learn about scenarios of using one or the other:
The Maintenance Planner is constantly developed adding with new functions and integration of related steps. For more details. see the blogs on release highlights of the Maintenance Planner.
The following functions of SAP Solution Manager are related to landscape data or Maintenance Planner output and support your planning process:
Landscape data are used to manage your landscape. You do not create them just for the tools managing them, but you need to see them in the big picture: System and landscape data is emerging when you install software and is needed to define changes in the landscape, which are applied then by software logistic tools.
Find out more about the tools:
In a typical landscape, you have to manage cloud systems as well as on-premise. You will find two major tasks:
While configuration of on-premise systems is well known, for many people integration with the cloud may be new but becoming increasingly important. Until today, the scenario integration of SAP Cloud solutions was based on integration guides and go through them from beginning to the end.
Figure 8a: Connections in hybrid landscapes offered by the SAP Cloud Platform.
As shown in the figure above, the SAP Cloud Platform is a central part of the connectivity in hybrid landscapes: It handles connections that go via the Internet into your on-premise landscape.
In addition, message-based communication to other businesses, can also be handled by the SAP Cloud Platform.
For connections within the hybrid landscape, to connect systems you run on-premise to the cloud services you use, you need to install SAP Cloud Connector, As stated earlier, from a connectivity point of view, IaaS being a public cloud is working like a SaaS offering.
Especially for the B2B integration, SAP offers the Integration Content Advisor for SAP Cloud Platform Integration (ICA), an application that helps you to simplify and streamline the flow of your B2B integration process. For details. see:
The Connectivity Service is always needed for the integration of SAP Cloud Platform to other systems -on-premise or the various cloud options.
In addition, depending on your scenario, Cloud Integration Service or API Management can be used or create a pure point-to-point connection using the Connectivity Service.
For more information, see SAP Cloud Platform Integration.
Cloud Integration Automation Service provides guided work flows for selected cloud scenarios:
Figure 8b: Invoking a work flow for a hybrid cloud integration scenario.
They make use of:
For more information, read Cloud Integration Automation Service – What is it? or watch the CIAS step-by-step video.
The following picture shows, which tools are available for planning and implementing changes during installation, updates, upgrades, and by transports:
Figure 9: Central tools for planning and implementing changes and doing transports - customers' view.
As shown in the figure, for the same task, no matter in which deployment model, in most cases the same tool is used - the list focuses on systems handled by customers:
The following monitoring types are available with SAP Solution Manager 7.2:
For more information, open the SAP Solution Manager 7.2 Application Operations – Expert Portal.
Using the development environment of SAP Cloud Platform is the recommended way to create your applications for an SAP S/4HANA backend system. In the SAP Cloud Platform Cockpit:
For more information, see the SAP Help Portal on the SAP Cloud Platform Cockpit.
Cloud applications can be heterogeneous. To come to a combined, working deployment, transports need to be harmonized. To achieve this, SAP introduced Multi-Target Applications (MTAs) to enable hand-over artifact between development and operation plus delivery construct for partners.
One very important aspect of SAP systems lies in the option to enhance functionality by partner software or custom development.
Figure 10: Development using the SAP Cloud Platform to enhance capabilities of on-premise, private, or public cloud functions.
Use development with the SAP Cloud Platform against another system in on-premise or cloud providing data or having other dependencies to differentiate without modifying the system you develop against.
You can set-up sub-nodes in SAP Cloud Platform development according to the tiers in your landscape. The example shows a three-tier landscape in on-premise and private cloud/IaaS. For more information on planning an SAP Cloud Platform landscape, see the SAP Cloud Platform Planning Guide.
As a developer, you can add functionality to SAP S/4HANA as you did in SAP ERP. Here are some pieces of information:
For more information, see SAP Cloud Platform: Official Tutorials & Resources - SAP.com.
Using the development environment of SAP Cloud Platform is the recommended way to create your applications for an SAP S/4HANA backend system. In the SAP Cloud Platform Cockpit:
For more information, see the SAP Help Portal on SAP Cloud Platform Cockpit.
SAP Landscape Management (LaMa) helps you automate repetitive tasks and gain unprecedented visibility and control over SAP and non-SAP systems in both traditional, virtual, and cloud infrastructures. In particular, it provides an end-to-end system copy with fully automated post-copy steps. As a result, you can boost efficiency and agility and lower operating costs.
Note: After a name change the product SAP Landscape Management (LaMa) might be mixed with the topic of this page but is part of the process described here.
Use LaMa to perform activities/tasks to change your IT landscape on-premise and in the cloud:
The following figure shows an example of a task including several steps being available with LaMa:
Figure 11: Example of a task performed with LaMa: Automated take over of secondary HANA DB in case of an error on the primary.
As shown in the figure above, in case of a required landscape change, LaMa can be used to apply the change. LaMa executes the task/activity you picked. Even complex tasks can be automated substituting error-prone manual steps.
Tasks and activity are available with LaMa; additional tasks creation is supported.
For more information, see SAP Landscape Management.
We are working on this process in a group dedicated to Release Management and Innovation Adoption. The recommendation for the complete process is described using the example of the EHP-update of an SAP ERP 6.0 system in a Planning Landscape Changes - a Best Practice Guide.
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 are describes below.
Figure 12: Roles, their steps and tools involved in the process of planning landscape changes taken from the best practices guide.
The example chosen for this document is a EHP update of an ERP 6.0 on-premise system. As discussed earlier, the process will be involving the tools also used for systems running in a private or in an IaaS cloud.
This guide is reflecting the progress in process described and exist in different versions. Therefore, the links to the versions are available via an overview page: Planning Landscape Changes - a Best Practice Guide.