SAP landscapes support the implementation of an SAP system consisting of isolated and stable environments that provide a solid ”promote to production” change-management and control process for all configuration and development. SAP recommends this scenario for all SAP applications and any system that is based on SAP NetWeaver.
The typical SAP environment is a three-system landscape with one DEV system, one QAS system, and one PRD system. Many customers supplement a three-system landscape with additional environments, such as a sandbox (SBX) that is used for testing, learning, and destructive testing.
The following figure shows a typical SAP system landscape for a single application.
Figure 3. SAP system landscape
Most SAP customers have more than one SAP system landscape in their total landscape environment, including applications such as ERP, BW, customer relationship management (CRM), and supply chain management (SCM). If you replicate a three-system landscape approach for every system that you deploy in a landscape, the number of individual systems quickly inflates, requiring additional compute and storage resources. Managing the TCO and the expanding total landscape is a common challenge for all customers who have more than one system landscape.