Understanding System Landscapes

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Explain SAP system landscapes involved in implementation, training, and demonstration

System Landscapes for Implementation

SAP for Me

SAP for Me is the digital platform for customers and partners to find the information they need and use a variety of self-service features to easily request support, provision systems, and resolve issues. SAP for Me is free and uses your existing SAP ID.

Customers can provision their cloud systems (e.g. SAP Cloud ALM) from the Systems & Provisioning Dashboard and view their licenses and consumption of SAP solutions from the Portfolio & Products dashboard. Partners can manage their customers' license portfolio, cloud consumption, upcoming renewals, and more with the Customer Success Dashboard.

At the beginning of an implementation, a customer administrator provisions the following systems via SAP for Me:

  1. SAP Cloud ALM
  2. SAP Central Business Configuration
  3. SAP S/4HANA Cloud Starter System
  4. SAP S/4HANA Cloud Development System
  5. SAP S/4HANA Cloud Test System
  6. SAP S/4HANA Cloud Production System

Choose the Continue button to learn more about SAP for Me.

SAP Cloud Identity Services

SAP Cloud Identity Services consists of two separate systems hosted in SAP Business Technology Platform: Identity Authentication Service (IAS) and Identity Provisioning Service (IPS). The identity tenants are the first to be provisioned for an SAP S/4HANA Cloud customer because the other systems are connected to them. Identity Authentication is a cloud service for authentication, single sign-on, and user management in SAP cloud and on-premise applications. It can act as an identity provider itself or be used as a proxy to integrate with an existing single sign-on infrastructure. Identity Provisioning offers a comprehensive, low-cost approach to identity lifecycle management in the cloud. It helps you provision identities and their authorizations to various cloud and on-premise business applications. Collectively, IAS and IPS enable customers to manage access to applications across their landscape.


SAP Cloud ALM is an application lifecycle management tool that provides implementation and operations capabilities for SAP cloud solutions. SAP Cloud ALM is hosted on the SAP Business Technology Platform, and is included in the SAP Enterprise Support for cloud editions that automatically comes with a customer's SAP S/4HANA Cloud software at no additional cost.

During implementation, project team members (both customer and partner) can use the project management capabilities to view the project progress, assign tasks to team members, mark tasks as complete, and more. The tasks and deliverables that must be completed during each implementation phase are populated from the SAP Activate Implementation Roadmap, and scope item information is populated from SAP Best Practices Explorer to support in Fit-to-Standard Workshops when configuration data is gathered. There are additional capabilities for test management, change management, and analytics that will be discussed in future lessons. After implementation, the IT team can use the operations capabilities for full-stack monitoring and alerting of business processes, integrations, users, applications, and health of all managed systems. SAP Cloud ALM can monitor multiple SAP solutions in addition to SAP S/4HANA Cloud to provide transparency into the health of the entire landscape.

SAP Central Business Configuration

SAP Central Business Configuration is hosted on SAP Business Technology Platform and is used to provision, activate business content, and configure the SAP S/4HANA Cloud systems. First, SAP Central Business Configuration is used to activate the predefined content and configuration in the SAP S/4HANA Cloud Starter System. The Starter System is used to gather customer configuration requirements and finalize the scope during Fit-to-Standard Workshops. After all configuration values have been gathered, SAP Central Business Configuration is used to provision the customer's SAP S/4HANA Cloud systems, activate business scope, define the organizational structure and primary finance settings, configure business processes, and maintain transports between the systems. After go-live, customers continue to use SAP Central Business Configuration to maintain their SAP S/4HANA Cloud systems through future release upgrades and business changes. For example, new country or business scope activation, defining additional organizational entities, or making configuration changes.

Click on the orange frames below to learn more about the project experience in SAP Central Business Configuration.

SAP Business Technology Platform

The SAP Business Technology Platform (BTP) is integral to SAP S/4HANA Cloud. You can run and monitor integrations on SAP BTP to connect your SAP and non-SAP solutions with the Integration Suite. Many of our prepackaged integrations already run on SAP BTP. You can develop and run side-by-side extensions or apps on SAP BTP to customize your SAP S/4HANA Cloud solution with the Extension Suite. You can enable Fiori Launchpad apps for the SAP Mobile Start app with the SAP Build Work Zone so employees can access their desktop apps on mobile devices (access to this service is included in GROW with SAP). You can also deploy and run database and data management solutions and develop customized analytics across your solutions on SAP BTP. View all SAP BTP services in the SAP Discovery Center.

SAP S/4HANA Cloud Systems

SAP S/4HANA Cloud Trial System

The SAP S/4HANA Cloud, public edition Trial System is a shared landscape with guided tours to help you experience SAP S/4HANA Cloud applications as different business roles. Each tour guides you through business process flows and apps the user would work with to complete their job tasks. Start your 14-day free trial here.

SAP S/4HANA Cloud Starter System

The SAP S/4HANA Cloud Starter System is a preconfigured system with the enterprise scope (all lines of business enabled) and business data that aligns with the SAP Best Practices test scripts. Consultants use the Starter system to deliver Fit-to-Standard workshops to customer business experts in each line of business during the Explore phase of the SAP Activate Methodology. The purpose is to teach the customer experts how to navigate the new system and to gather configuration data and extension requirements. Customization requirements are documented in SAP Cloud ALM to ensure there is a record of each requirements the consultants must implement in the customer’s actual system during the Realize phase of the SAP Activate Methodology. The Starter system can be decommissioned after the customer’s own systems are implemented, as it would not be needed any longer.

Development System

Within a system, there can be one or more client tenants with different purposes. A client is an organizational unit in the system with specific user master records and authorizations. The SAP S/4HANA Cloud Starter and Development systems have two client tenants:

  • Development tenant / client 080 is for developer extensibility in the SAP S/4HANA Cloud ABAP environment, where developers have full ABAP development tool access to released SAP S/4HANA Cloud business objects and extension points. The development tenant is client-independent, meaning development objects built here can be accessed from the customizing tenant if permission is granted. This is because development objects are stored in database tables without a client column. Changes are recorded on development workbench requests and are released for transport with the Transport Organizer view in ABAP Development Tools.
  • Customizing tenant / client 100 is the main project, used for business process configuration and key user extensibility with the SAP Fiori extensibility apps. The customizing tenant is client-dependent, meaning configurations or extensions made here can only be accessed within the customizing tenant. This is because master and transactional data is stored in database tables within a client column. Changes to business configuration in this tenant are recorded on customizing requests and are released for transport with the Export Customizing Requests SAP Fiori app. Key user extensions built with the SAP Fiori extensibility apps in this tenant are added to software collections and released for transport with the Export Software Collections SAP Fiori app.

Test System

An administrator imports development requests, customizing requests, and software collections with the Import Collection SAP Fiori app, in the Test system to validate business configurations and extensions.

Production System

An administrator imports development requests, customizing requests, and software collections with the Import Collection SAP Fiori app in the Production system to make the configurations and extensions available for productive use.

3-System Landscape (3SL) for SAP S/4HANA Cloud, public edition

In August of the year 2022 (release 2208), the 3-system landscape (3SL) became available. The 2-system landscape included a Quality system, where customizations were both created and tested, and a Production system. 3SL includes a Development system, Test system (previously named, Quality), and Production system. This enables developers to build more complex on-stack extensions using stable SAP objects in the Development system, and separates testing activities into a dedicated Test system.

Click on each pictogram to display additional information.

Start your 14-day free trial here.

Additional Systems for Training or Demonstration

Additional Systems for Training or Demonstration

Select each option to display further information:

  • To learn more about Partner Test, Demo, and Development (TDD): Learn more
  • To learn more about Partner Shared Demo Environment (PDE): Learn more
  • To learn more about SAP Learning System Access: Learn more

Log in to track your progress & complete quizzes