SAP landscape
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.
The landscape is the safety mechanism of SAP change management.
- 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.