What is SAP Landscape

The arrangement of SAP systems in a sequential order is called as a SAP Landscape. Based on the Landscape architecture, the data flows from one server to another server through transport request (TR) in the SAP system.

  • The SAP system Landscape will be designed by the Basis team for both ECC and S4 Hana servers.
  • The design of SAP Landscape varies from one client to another client, means BIG MNC organizations may use 5 to 6 SAP systems landscape, and medium organizations may use 3 systems landscape.
  • As a SAP consultant, when you are working on any SAP project, first you need to understand the Landscape of your project.
  • By understanding Landscape, you will understand -in which you are allowed to configure, in which system you are allowed to test the system on so on.
  • Each SAP server can have multiple clients (3-digit numerical key) as per the business requirement.

SAP Landscape

Note: The client number can be different from project to project. As per the below example, we have used 100 (Development client), 110 (Unit Testing Client), 200 (Testing Client), 300 (Pre Production Client), 310 (Production Client)

Example -1

3- System Landscape

  • Development System
  • Quality System
  • Production System

SAP Development System

Functional Consultants do the Functional Module configuration and the SAP ABAP team develops the programs, reports, and forms in the development system. The Development system consists of multiple clients for different purposes.

Note: Client number varies from one project to another project.

  • Client 100 (Development Client):
    • This client is called a development client/ configuration client.
    • The development system is used for configuration by the functional consultant and development by the ABAP consultant.
    • In this development client, the master data and transaction data will be not created.
  • Client 110 (Testing Client) :
    • This client is called a development test client/ configuration test client.
    • Used for unit testing by the functional and ABAP consultants.
    • SCC1 transaction code is used to transport the data from Dev client (100)  –> Testing client (110)
    • The master data and transactional data is posted and the unit is tested by the consultants.
    • Once unit testing is successful, the configuration will be moved to the quality server for further

SAP Landscape - Arrangement of SAP Servers & TR movement

Before you move the changes to the quality system, you need to release sub-TR only, and not the main TR (transport request). If any changes are required further, you can create a Sub-TR and save the changes in that Sub-TR.

SAP Quality System

After the configuration in the development server and unit testing, the configuration will be moved to the quality server through TR (Transport Request) movement.

Further Quality system can have multiple clients for testing and training.

Client 200 (Quality System)

    • This is the client where the business user performs the UAT (User Acceptance Testing).
    • Once UAT is successful, the changes will be moved from the development server to the Pre-Production Client & Production Client.

Now from the development system, release the Sub-TR and Main TR, and transport them to the product system.

Pre-Production System

    • The pre-production server is the copy mirror of the production system.
    • This system is used to simulate the issues that occur in the production system.
    • The pre-Production system can be maintained as a separate server server or a different client under the production system.

SAP Production System

    • The production server is the system where the end-users perform day-to-day business transactions.
    • The production system will be set with the display mode only, this production server is not modifiable.

Scenario: In the production system, we found that there are some wrong configurations, and now we need to correct those issues. How can we correct the configurations?

  • The production system is not modifiable and you can’t make the changes directly from the production system.
  • To make the changes, we need to follow the systemic manner as per the SAP Landscape.
  • First, we need to make the changes in the development server and move the changes to other servers -> Quality Server -> Production system through the transport management system.