Landscape Management Process - the Big Picture

The Landscape Management Processes in the IT landscape runs across several tools: It provides information on IT landscapes as a basis for landscape operation and change planning of SAP centric solutions and helps customers to best manage and use the existing landscape and evolve it through new installations, update of Support Packages and enhancement packages, system upgrades or conversion to SAP S/4HANA and SAP BW/4HANA.

Your IT landscape consists of all entities running your business software. Depending on the used deployment model, these are systems or tenants, servers, and so on. 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:

  • The state, which is currently used - here, ideally, a project is running where the landscape is analyzed to provide input to change planning.
  • The next version of the landscape, which is currently in the phase of detailed planning and implementation on the system level. 
  • The future vision of the landscape to implement your strategy for the long-term planning - here, specifically, exploring fundamentally new options and getting recommendations on the implementation on the landscape level is key.

Figure 1: A landscape going through a change process in iterations to adapt to emerging business opportunities and new technologies. 
(To see a video explaining the picture step-by-step, click the figure; use the cc button to switch sub-titles on or off.)

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.  

Roles, Their Tasks, Tools and Entities in the Landscape Management Process

To manage the required changes, people in different roles are involved. The main roles in landscape management are from the areas of:

  • Business
  • IT Architecture
  • Basis Administration
  • Development

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.

Figure 2: Main roles and their tasks in the process of landscape management - the big picture.
(To see a video explaining the picture step-by-step, click the figure; use the cc button to switch sub-titles on or off.)

The picture describes roles involved in the landscape management process and their tasks on the level of functional areas: Business, IT Architecture, Basis Administration, and Development. 
The inner circle describes the tasks in the existing landscape, the outer circle describes the phases of planning and implementation of changes.

In the next figure, the steps in changing a landscape are shown. 

Main Steps in Planning and Implementing Landscape Changes

In this example, the company is evolving its landscape from a pure on-premise set-up to a hybrid landscape. New options offered are identified by mapping required functions to new offerings; the plan for changes is created and implemented:

Figure 3: The functional view on planning changes - where tasks overlap, coordination is highly recommended and supported by the tools. (For a step-by-step video explanation, click the figure; use the cc button to toggle sub-titles.)

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.

Main Entities and Tools in Landscape Management

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 SAP Solution Manager, 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:

  • It is the provider of landscape data consumed by the Maintenance Planner (which is provided as a service of SAP Solution Manager)
  • It offers functions that help you to run the systems in your landscape and supports the planning of changes

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: An IT landscape comprising systems of various deployment models with tools and steps of the landscape management process.(For a step-by-step video explanation, click the figure; use the cc button to toggle sub-titles.)

The picture shows a customer landscape and the tools used in landscape management. 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 Maintenance Planner allows planning of changes for SAP systems in your landscape. Several functions have been integrated with the Maintenance Planner as utilities:

The following functions consume landscape data or Maintenance Planner output:

Left and right of the Landscape Management Process you find the main tools related to or supporting the process. 
The lower part of the landscape comprises systems directly managed by the customer installed on-premise or in a private or an IaaS cloud. The upper part comprises cloud solutions (mostly) managed by the provider as managed private cloud, PaaS or SaaS cloud. These deployment models are described in the details section.

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, systems or tenants of the different models are addressed with in different depth of responsibility by customers and providers. As an example, for the IaaS cloud, you will only subscribe to the infrastructure but handle the installation of systems running on-top of it 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.

Entities, Steps, and Tools in Detail

In this section, you will find details on the elements shown in figures 3 and 4: Deployment models, landscape entitiestools 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 implementation of the results. The list is closing with a offering that help you manage your landscape.

Project Set-Up & Prerequisite Knowledge

The SAP Activate methodology is designed to support project teams in the new implementation, or conversion, etc. of SAP solutions on-premise or in the cloud environment. It can be used as standalone or as part of an SAP Premium Engagement:

Figure: Main phases of the SAP Activate methodology.

The methodology is structured into project phases, each containing a list of deliverables and supporting tasks. Within the project phases hierarchy project teams will be able to find accelerators like project plans, templates and examples to support their SAP implementation project. 
Implementation Roadmaps for on-premise and cloud are available in the Roadmap Viewer

More information can be found in the SAP Activate Methodology Jam group. This group has been created to guide you through the SAP implementation and delivery methodology, SAP Activate. This group provides two sub-groups for SAP Activate...

Each methodology sub-group is in its own individual Jam collaboration group that users can join according to their preference and level of access.


The following table explains the deployment models mentioned above, 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
Install what you need and add custom code.
Fully manage your own landscape.

Offering, examples:



Build and manage your cloud.
Offer services for users inside your firewall.

Offering, examples:

- 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
Hybrid Landscape

Combining any cloud offering with your on-premise systems, you will get a hybrid landscape.
A typical use case would be to use your on-premise ERP system (for example SAP ERP or SAP S/4HANA) and connect it to SAP SuccessFactors.

  Hybrid Cloud

Combining two or more cloud deployment models to build your landscape, you'll get a hybrid cloud.
A typical use case is to enhance your SAP S/4HANA Cloud (SaaS) using the SAP Cloud Platform (PaaS).

Deployment Models and Responsibilities for Stack Layers

The big difference between 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:

Deployment models, their variants, and responsibilities for stack layers and the relation to standardization and differentiation.
(For a step-by-step video explanation, click the figure; use the cc button to switch sub-titles on or off.)

In IT-landscapes, you can find, more or less, the following deployment models and variants:

  • On-premise:
    - On-premise systems only
  • Private cloud:
    - Systems deployed by the customer on-top of a cloud infrastructure owned by the customer
    - Tenant-based / cloud native software solutions deployed by the customer on his own infrastructure
  • Managed private cloud:
    - Dedicated systems or cloud native solutions and infrastructure run by the provider for the customer 
  • Infrastructure as a Service (IaaS) cloud:
    - Systems deployed by the customer on-top of a cloud infrastructure of a provider
    - Tenant-based / cloud native software solutions installed and run by the customer on-top of a cloud infrastructure of a provider
  • Platform as a Service (PaaS) cloud:
    - Tenant-based cloud software, usually, run by the provider, offering infrastructure plus services
    - Software developed and deployed by the customer or partner on top of the platform using its services
  • Software as a Service (SaaS) cloud:
    - Tenant-based cloud software, usually

So, from a landscape management view, it is necessary to clearly state not only if you are talking on on-premise or cloud, but also, which type of cloud you use for a specific part of your landscape.
From the different levels 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 your choice will be an on-premise or private cloud solution. With SaaS solutions, on the other side, you get predictability of costs and benefit from managed standardized services. All options, as shown in the table above, can, of course, be combined selecting services from the SaaS cloud for standard functions and having your core functions in your private cloud, plus putting certain functions into the PaaS cloud, for example. 

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. is 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.

SAP Offerings in Various Deployment Models and Their Purposes in the Landscape

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.

Products Offered in One Deployment Model

Examples by deployment model:

  • IaaS: While SAP does not offer this product type as a vendor, partners solutions are available with Google Cloud Platform, Amazon Web ServicesMicrosoft Azure, ...
  • PaaS: Other than IaaS, PaaS does offer not just the means to run your systems, but additional functions; build and deploy apps with the SAP Cloud Platform and connect systems within you IT landscape:
    - Use comprehensive application development capabilities to extend, integrate and build innovative applications.
    - Use services for mobile, Big Data, Machine Learning, Internet of Things, and more to deliver secure business app.
    - Use SAP Cloud Platform Integration to connect and optimize your IT landscape including high performance
      messaging to connect to business partners.
    It's also worth mentioning that while many functions are available in various deployment models to choose from - most prominently SAP S/4HANA - in all hybrid setups you will require the SAP Cloud Platform to manage the integration.
  • Managed Private Cloud: Utilize SAP HANA Enterprise Cloud to innovate at your own pace. Enjoy the full power of SAP HANA in a private, managed cloud environment from infrastructure to applications.
  • SaaS offerings cover a wide range of business services: They offer business functions to be consumed with the least manual effort in landscape management. SAP offers cloud based solutions to manage HR with SAP SuccessFactors, selling, buying, and marketing with SAP Ariba and SAP Customer Experience, or manage travel costs with SAP Concur, and integrate it with your SAP on-premise or cloud backend systems or even 3rd-Party systems, etc...
    You also find SAP Business ByDesign, an ERP solution for the mid-market business and other solutions.
    Usually, you will use these services in addition to your ERP solution. If so, the integration is done in the SAP Cloud Platform.

ERP Software Offered in Different Deployment Models

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

Like SAP's ERP for enterprises, SAP Business One can be deployed on-premise or in the cloud.  

Describing your IT landscape is a prerequisite for its maintenance and monitoring using SAP Solution Manager - the central tool for the management of system landscapes. 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 is a prerequisite for running business applications, systems, and Application Lifecycle Management processes alike.  

Maintaining Products - Product Systems and Maintenance Dependencies

Here, you find explanations, how products are maintained even if they have been installed on more than one system:

Find Availability Dates, Technical Details, and Documentation - SAP Product Availability Matrix

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.).

Status Quo Analysis

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.

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.

Gathering Your Landscape Data in SLD, LMDB, and Customer Profile

To plan landscape changes on a systems level, you need data from systems that you run yourself on-premise, in a private cloud, or on top of a IaaS cloud. In addition, for monitoring of the whole landscape you need data from HEC, PaaS and SaaS as well. 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

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:

Accessing Information on All Your Systems or Tenants

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. 

Process Design and Modeling - Solution Documentation

SAP Solution Manager 7.2 offers a comprehensive structure to manage your company's solution:

  • Document the operational processes, application landscape, and system landscape to apply to your solution.
  • Manage your operational processes for better business communication, increased consistency, and improved efficiency.

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:

Categorization of the Systems in Your Landscape - Solution Administration

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, like development, test, production, etc. To make documenting your landscapes easier, 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.

Discover New Options

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.

Recommendations on the Business Process

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:


Recommendations on Implementation Options and Prerequisites

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:   

  • SAP S/4HANA Readiness Check 2.0 dealing with...
    - SAP S/4HANA sizing simulation & Data Volume Management
    - Required project activities related to Simplification Items
    - Simplification Item relevancy and consistency checks 
    Business Process Discovery analysis
    - Recommended Fiori Apps
    - Integration topics (IDoc Interface Analysis, Business Warehouse Extractors, ...)
    - ...
    If you're going to plan a conversion to SAP S/4HANA, use SAP Readiness Check 2.0 to identify the relevant Simplification Items and get information many other relevant aspects.
    If you additionally want to identify data inconsistencies, which need to be solved before SAP S/4HANA conversion, please follow the instructions of SAP Note 2502552 and upload the resulting ZIP-archive into SAP Readiness Check 2.0 or process the output in our SAP GUI screen.
  • To define the blueprint for the architecture of the next version of your landscape - the new landscape plan in figure 2 - the SAP Enterprise Architecture Designer is available - with costs - for subscription or as installation in your system.
  • SAP Cloud Platform Planning Guide informs on new development options using an SAP Cloud Platform landscape.
  • Integration Solution Advisory Methodology (ISA-M) helps you define your integration approach. For details, see ISA-M: Define Integration Guidelines for Your Organization.

For information on custom code handling, see the recommendations for development.

Recommendations on New Development Options and Custom Code Handling

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.  

Getting Recommendations on the Handling of New Landscape Components

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:

There also is a series of documents to better understand the usage of SAP BW powered by SAP HANA and BW/4HANA. Furthermore, these documents deliver additional information on the implementation aspects of SAP BW on SAP HANA and SAP S/4HANA:

The first process steps that lead - bigger - changes to your landscape are those of the discovery phase. To find new options for your business, you need to browse the options available, learn about them - for very important changes, you might want to test the application in question. 

Tools supporting discovery and evaluation of new functions and product versions on-premise and in the cloud.

The process steps in the discovery phase will look like this:

  1. Browse the software catalog (web page All Products)
  2. Choose products or functions you want to learn details about (Innovation Discovery)
    - Filter for your specific needs and preferences
    - See features and technical requirements
  3. Evaluation of products can be done for
    - Cloud applications (SAP S/4HANA Cloud, SAP SuccessFactors, SAP Concur, ...) with trials offered by the products
    - On-premise applications (SAP S/4HANA, SAP BW/4HANA) via SAP Cloud Appliance Library

Filter for Products and Learn about Functional and Technical Detail - Innovation Discovery

Find the innovations and features that you can turn into tangible value for your business from the areas of SAP S/4HANAdigital 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 industryline of business, and technology.


Quickly Set-Up Evaluation Environments for Products on Your Short-List - Trial Accounts and CAL

As stated already, for cloud applications (SAP S/4HANA Cloud, SAP SuccessFactors, SAP Concur, ...) you'll find trial versions on the product's page. When it comes to on-premise, there would be considerable effort to install and configure from scratch. Instead, you can use the service of the SAP Cloud Appliance Library.   

SAP Cloud Appliance Library offers a quick and easy way to consume the SAP on-premise solutions  (e.g. SAP S/4HANA, SAP HANA Express Edition, SAP Data Hub, industry solutions, model companies, etc.) deployed on-top of an IaaS cloud. The CAL self-service solution offers an online library of preconfigured, ready-to-use SAP business solutions with a fully automated deployment into your own IaaS cloud account.

  • Instant access to a library of latest SAP (on-premise) business solutions
  • Preconfigured test, demo, trial and development systems
  • Fully automated deployment into your own public cloud account
  • Start your SAP project within few hours

In most cases, new functions have to be seen in the context of the ones currently used. To learn about how to map the new functions to the existing landscape, see the next section Map New Functions and Deployment Models to Your Landscape - SAP Transformation Navigator.

Plan on System or Tenant Level

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.

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:

Implement Changes

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. 

Ways to get from an SAP ERP 6.0-centric landscape to an SAP S/4HANA / SAP S/4HANA Cloud-centric one.

So, as shown in the figure above, there are several deployment options:

  • You can keep the system in your on-premise landscape converting it into an SAP S/4HANA system
  • You can use a private cloud setup and install SAP S/4HANA there - note, that this would not be SAP S/4HANA Cloud
  • You can subscribe to the infrastructure of an IaaS provider and install your SAP S/4HANA on top (with the same "note" as for a private cloud)
  • You can use the on-boarding process to have your SAP S/4HANA managed in the SAP HANA Enterprise Cloud (HEC)
  • Or you could subscribe to SAP S/4HANA Cloud SaaS offering
All of the options offered above can be extended, for example, with additional cloud services.

Migration and Subscription

Migration in Detail

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

Subscription in Detail

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:

  • Google Cloud Platform
  • Amazon Web Services
  • Microsoft Azure
  • ...

Managed Private Cloud:

Landscape data is 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:

A comprehensive list is available at the Software Logistics Tools page.

Configure & Adapt

In a typical landscape, you have to manage cloud systems as well as on-premise. You will find two major tasks:

  • Configuring the connection to services you consume from an SaaS cloud system, which are exchanging data with other systems or tenants
  • Managing applications you created yourself in SAP's PaaS cloud SAP Cloud Platform
You'll also find more information on that topic:

Configuring Connections between On-Premise, IaaS, PaaS, and SaaS clouds

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.

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:

Connectivity Service, Cloud Integration, and API Management

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 (CIAS)

Cloud Integration Automation Service provides guided work flows for selected cloud scenarios:

Invoking a work flow for a hybrid cloud integration scenario.  

They make use of:

  • Customer specific system information (e.g. target URLs)
  • Reusable configuration settings between tasks, and
  • Automated execution capabilities

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:

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:

  • SWPM and SAINT address systems handled on-premise and on IaaS or private cloud
  • HANA XSA Product Installer addresses installations on SAP HANA
  • SUM addresses update/upgrade/conversion for systems on-premise, on IaaS, and private cloud
  • TMS runs and handles transports in the SAP Cloud Platform
  • CTS/CTS+ handle transports for systems on-premise, on IaaS or private cloud, SAP Cloud Platform, and SAP HANA
  • HTA handles transports systems handled by the customer on-premise and on IaaS or private cloud pus SAP HANA
  • HALM handles transports SAP HANA
  • SAP Solution Manager allows to monitor systems on-premise and in the cloud

Monitoring-Capabilities offered by SAP Solution Manager

The following monitoring types are available with SAP Solution Manager 7.2:

  • End-User Experience-Monitoring for availability monitoring of SAP Cloud Platform applications
  • Exception Monitoring for error messages from SAP Cloud Platform applications
  • Integration Monitoring for Cloud Integration Service

For more information, open the SAP Solution Manager 7.2 Application Operations – Expert Portal.

Managing Applications and Transports in SAP Cloud Platform - SAP Cloud Platform Cockpit for OPS

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:

  • Get an overview of your applications
  • Manage transports from DEV to QA and from QA to PRD

For more information, see the SAP Help Portal on the SAP Cloud Platform Cockpit.

Installation & Transports in Heterogeneous Systems: MTAs in XSA Product Installer and CTS+

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.

Transport for SAP HANA and SAP Cloud Platform - HTA, and TMS

  • Hana Transport for ABAP (HTA) allows transporting native SAP HANA objects with CTS:
    - ABAP stack with HANA XSC. No configuration after a SAP NetWeaver update/upgrade
    - ABAP stack with SAP HANA HDI (HANA Deployment Infrastructure)
    For more information, see HTA for HDI at the SAP Help Portal.

  • SAP Cloud Platform Transport Management service (TMS), like CTS, allows transporting:
    - Development objects
    - Application specific content
    For more information, see SAP Cloud Platform Transport Management service generally available.

Extend & Run

One very important aspect of SAP systems lies in the option to enhance functionality by partner software or custom development.

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.

Adding Functions to Your SAP S/4HANA Implementation

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 -

Managing Applications and Transports in SAP Cloud Platform - SAP Cloud Platform Cockpit for DEV

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:

  • Get an overview of your applications
  • Manage transports from DEV to QA and from QA to PRD

For more information, see the SAP Help Portal on SAP Cloud Platform Cockpit.

SAP Landscape Management (LaMa) helps you automate repetitive tasks and gain visibility of and control over SAP and non-SAP systems in both traditional, virtual, and cloud infrastructures. In particular, LaMa provides 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:

  • Automate and standardize operations on SAP systems such as system clone/copy/refresh activities including automation of post-copy tasks, mass operations on systems and hosts; get landscape visualization plus dashboards
  • Manage and operate SAP HANA in automated tenant move/copies, tenant visualization, as well as mass operations on tenant systems, performing critical HA/DR operations for SAP HANA such as takeover; includes near-zero downtime maintenance procedures for SAP HANA
  • Manage hybrid SAP landscapes with cloud adapters for Microsoft Azure, Amazon EC2, and Open Stack

The following figure shows an example of a task including several steps being available with LaMa:

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.

Best Practice Guide to Planning Landscape Changes

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.

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.