Skip to content
IT Canvass
Getting started · Lesson

SAP landscape

Quick answer

The landscape is the safety mechanism of SAP change management.

Key takeaways

  • The standard arrangement is DEV → QAS → PRD: a Development system where configuration and code are built, a Quality Assurance…
  • Each SAP system is divided into clients, self-contained tenants with their own master and transaction data.
  • Real landscapes include more: a sandbox for experimentation, a pre-production system that mirrors PRD, and separate landscapes for…
  • Watch out: Making changes directly in production, the cardinal sin of SAP operations.

The classic three-system landscape

The standard arrangement is DEV → QAS → PRD: a Development system where configuration and code are built, a Quality Assurance system where they are tested, and a Production system that runs the real business. Changes flow in one direction through the Transport Management System, so nothing reaches production without passing through test.

Clients within a system

Each SAP system is divided into clients, self-contained tenants with their own master and transaction data. A typical DEV system has a customizing client, a sandbox client and sometimes a golden configuration client. Understanding the client concept is essential to avoid changing the wrong data.

Beyond the core three

Real landscapes include more: a sandbox for experimentation, a pre-production system that mirrors PRD, and separate landscapes for connected products (BW, PI/PO, Solution Manager). Each must be sized, secured and kept in sync.

Why the landscape matters

The landscape is the safety mechanism of SAP change management. It lets teams build boldly in DEV, prove changes in QAS, and protect PRD, while transports give a controlled, auditable path for every change.

Common pitfalls

  • Making changes directly in production, the cardinal sin of SAP operations.
  • Confusing systems and clients, they are different layers of isolation.
  • Letting DEV/QAS/PRD drift out of sync, tests then do not reflect reality.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. Which statement is true of SAP landscape?

    • A. The standard arrangement is DEV → QAS → PRD: a Development system where configuration and code are built, a…
    • B. The application layer is the heart of an SAP system, the tier where business logic actually executes.
    • C. A work center is where a production operation is performed, a machine, a line, or a group of people, with…
    Show answer

    A. The standard arrangement is DEV → QAS → PRD: a Development system where configuration and code are built, a…

    Covered in the “The classic three-system landscape” section of this lesson.

  2. Which of these also applies to SAP landscape?

    • A. Using the wrong variant (create vs change vs display).
    • B. Changes flow in one direction through the Transport Management System, so nothing reaches production without…
    • C. Skipping the discipline under delivery pressure.
    Show answer

    B. Changes flow in one direction through the Transport Management System, so nothing reaches production without…

    Covered in the “The classic three-system landscape” section of this lesson.

  3. Which part of the Learn SAP curriculum covers SAP landscape?

    • A. SAP integration
    • B. Getting started
    • C. SAP fundamentals
    Show answer

    B. Getting started

    This lesson sits in the Getting started section of the Learn SAP course.

Frequently asked questions

What does the term SAP landscape refer to in SAP?

An SAP landscape is the set of connected SAP systems an organisation runs, together with how they are arranged for development, testing and production. Designing and understanding the landscape is fundamental, it determines how changes are built, tested and safely moved into the live business.

What is involved in configuring SAP landscape?

Each SAP system is divided into clients, self-contained tenants with their own master and transaction data.

What is another point to note about SAP landscape?

The landscape is the safety mechanism of SAP change management.

What tends to go wrong with SAP landscape?

Making changes directly in production, the cardinal sin of SAP operations. Confusing systems and clients, they are different layers of isolation. Letting DEV/QAS/PRD drift out of sync, tests then do not reflect reality.
CallWhatsAppEnquire