A system landscape is the set of SAP S/4HANA Cloud Public Edition systems and tenants used to configure, develop, test, and operate the solution. The landscape determines how change is separated from production and how configuration and extensions move through controlled stages.
SAP's current documentation describes both 2-system and 3-system landscapes, depending on the installation and commercial setup. The legacy statement that every Public Edition subscription automatically includes exactly three systems should therefore not be reused.
A system is a deployed SAP S/4HANA Cloud environment with a defined role in the landscape. A tenant is a logically separated environment within a system for a specific purpose. The available tenants, names, and capabilities depend on the landscape type and current SAP release.
| Topic | 2-system landscape | 3-system landscape |
|---|---|---|
| Primary structure | Non-production and production are separated within the applicable SAP setup | Development, test, and production systems are separate |
| Change route | Uses the configuration and transport path defined for the 2-system model | Changes move from development through test to production |
| Developer extensibility | Depends on supported capabilities for the setup | SAP S/4HANA Cloud ABAP environment supports developer extensibility in development |
| Governance need | Strong separation of configuration, test, and production duties | Strong change, transport, test, and release controls across three systems |
| Suitability | Confirm against contracted capabilities and project needs | Supports more explicit development and validation separation |
SAP Central Business Configuration supports scoping, organizational structure, and configuration activities. Where a configuration activity is performed and how it reaches production depends on the landscape.
The change process should specify:
Key-user adaptations and developer extensions follow different lifecycles. In a 3-system landscape, developer extensibility uses the SAP S/4HANA Cloud ABAP environment and released objects in the development system, followed by the defined transport route.
Extensions should never bypass architecture review because they are technically possible. Confirm the released object, security model, test coverage, ownership, and upgrade behavior.
A test system provides separation from production, but it does not automatically create quality. The customer must maintain representative end-to-end scenarios, integration coverage, roles, data, defect management, business sign-off, and release criteria.
Current SAP upgrade guidance applies the major upgrade to the test system before development and production, giving customers time to validate. The organization should use that window for risk-based regression testing and required remediation.
Maintain a record containing:
Review this record after contract changes, landscape provisioning, new extension types, and changes in SAP lifecycle guidance.