SAP Landscape Management: Strategy for Complex System Landscapes
Manage SAP system landscapes efficiently: multi-system and lifecycle management.
Read more →SAP system copies are among the regularly recurring tasks of every Basis team. Whether for project refreshes, performance tests or error reproduction – a clean system copy saves time and avoids problems. At the same time, every copy carries risks: from data protection violations through unmasked production data to faulty post-copy activities that render the target system unusable.
Homogeneous vs. Heterogeneous Copies
In homogeneous system copies, the operating system and database platform remain identical – the simplest and fastest method. Heterogeneous copies change the platform (e.g. from Oracle to HANA) and require the Software Provisioning Manager (SWPM) with export/import. For S/4HANA migrations, the heterogeneous copy is often the only option. Plan for double to triple the time for heterogeneous copies.
Pre-Copy Checklist
Before every system copy, the following points must be clarified:
- Sizing: Does the target system have sufficient storage for the database and transport directory?
- Licences: Are licence keys available for the target system?
- Connectivity: Are network connections, DNS entries and firewall rules prepared?
- Communication: Are all affected teams informed and the time window agreed?
- Backup: Does a current backup of the target system exist as a fallback?
Post-Copy Activities
The post-copy phase is decisive for a usable copy. Core activities: adjust logical system names (BDLS), check and adjust client settings, update RFC connections (SM59), deactivate or adjust background jobs, check printer settings, clean up the transport directory and reset batch user passwords. Automate these steps as far as possible – a post-copy script reduces errors and significantly shortens throughput time.
Data Masking and GDPR
Production data in non-production systems is a serious data protection issue. GDPR requires that personal data is processed only for the defined purpose. In development and test systems, this purpose is generally not given. Implement data masking for critical fields: names, addresses, bank details, HR master data. Tools such as SAP Data Services, ILM or specialised third-party solutions automate masking as part of the post-copy activities.
Security Aspects After the Copy
After a system copy, the target system contains the users and authorisations of the source system. This can be problematic: production users with extensive authorisations suddenly exist in the development system. Measures: lock all dialog users and unlock only those needed. Change the passwords of all privileged users. Clean up RFC connections with stored credentials. Remove emergency user assignments. Check client settings (SCC4) for the correct protection level.
Automation and Tooling
For regular system copies, investing in automation pays off. SAP Landscape Management (LaMa) offers an integrated workflow for system copies including post-copy automation. Alternatively, shell scripts or Ansible playbooks can automate the post-copy steps. Goal: a system copy should be executable as a standard workflow in a maximum of one day – including all post-copy activities.
Conclusion
System copies are not rocket science, but they require careful planning and standardised processes. Invest in good post-copy automation and do not forget data masking – it is not just a compliance requirement but protects your organisation from real risks.
Related Articles
Securing the SAP Transport System: Risks, Controls & Best Practices
Secure the transport system: authorisations, dual control and audit trail.
Read more →S/4HANA Migration Checklist: 12 Points for Your Basis Team
12 points your Basis team must clarify before project start.
Read more →Need support with this topic?
We help you with implementation – from analysis to go-live.
Get in touch