SAP landscape: transports and QAS refreshes
The system landscape is the arrangement of connected SAP systems, typically Development, Quality Assurance and Production, through which changes flow in a controlled way. It is the architectural backbone of safe SAP change management.
Once DEV, QAS and PRD exist, keeping the landscape trustworthy is two disciplines: import transports in release order, and refresh QAS from PRD periodically so testing resembles production. Transports move forward only, which is what guarantees anything live has been through test. Landscape drift is the usual cause of works in QAS, fails in PRD.
- The standard is DEV → QAS → PRD.
- Watch out: Changing production directly.
The three-system landscape
This lesson is about keeping a landscape trustworthy once it exists: transports imported in the right order, and a QAS that still resembles PRD. For what the three systems are, start with the landscape lesson in fundamentals.
The standard is DEV → QAS → PRD. Configuration and code are built in DEV, tested in QAS, and run the business in PRD. Changes move only forward, packaged as transports, so nothing reaches production without passing through quality assurance.
Why one direction only
Unidirectional transport flow protects production: it guarantees that anything live has been through test, and it gives a clean, auditable trail of every change. Making changes directly in PRD is the cardinal sin of SAP operations.
Extended landscapes
- A sandbox for experimentation, outside the transport path.
- A pre-production system mirroring PRD for final validation.
- Separate landscapes for connected systems (BW, PI/PO, Solution Manager).
Keeping systems in sync
For testing to be meaningful, QAS must resemble PRD (via periodic system copies/refreshes), and transports must be imported in the right sequence. Landscape drift is a common cause of "works in QAS, fails in PRD".
Common pitfalls
- Changing production directly.
- Letting QAS drift from PRD, invalidating tests.
- Importing transports out of sequence.