Explain SAP System Copy & Landscape Refresh in SAP

18 / 65

Basisadvanced

SAP System Copy & Landscape Refresh

Homogeneous and heterogeneous system copies used to build new SAP systems or refresh existing ones from a source system.

System copy is a heavier, more infrastructural cousin of client copy, and it comes up in Basis interviews specifically to test whether a candidate understands SAP's software logistics tooling (SWPM) beyond just clicking through a wizard, since a botched system copy can mean days of downtime and a system that's inconsistent at the database level.

A client copy is like duplicating one tenant's apartment inside the same building; a system copy is constructing an entirely new building and, for a heterogeneous copy, doing it with different construction materials (a different database engine) while still recreating every room exactly as it was.

Key Concepts

A homogeneous system copy keeps both the operating system and the database platform identical between source and target (e.g., copying a Linux/HANA system to another Linux/HANA system), typically done via a database-level backup/restore or export/import using the vendor's native tools, orchestrated by SAP's Software Provisioning Manager (SWPM). A heterogeneous system copy changes the OS and/or the database platform (e.g., migrating from a traditional RDBMS on Windows to HANA on Linux, the classic use case for the DMO - Database Migration Option of SUM), which requires an R3load-based export/import that unloads data into a database-neutral format and reloads it into the new platform, since a direct binary copy across incompatible platforms isn't possible.

System copies are the standard mechanism for building a fresh sandbox from production, refreshing QAS with a recent PRD snapshot ahead of a major testing cycle, or as the technical first step of a system landscape consolidation or client merge. Post-copy activities are extensive and easy to underestimate in an interview answer: adjusting the SID and hostname references, regenerating RFC destinations and trusted connections, resetting logical system names (BDLS for converting logical system names across an entire copied system, notably in ALE/IDoc-integrated landscapes), reactivating or deactivating outbound interfaces so the copy doesn't accidentally fire real messages at production partner systems, and license key regeneration.

BDLS

A senior-level answer should mention that DMO (Database Migration Option) combines an SAP release upgrade and a database migration to HANA into a single, shorter downtime procedure, which is why it became the standard path for ECC-to-S/4HANA-on-HANA migrations before greenfield or full re-implementation approaches, and should be able to contrast system copy (infrastructure-level, whole system) against client copy (logical, single-client-level) to show clear layered understanding.