Key solution steps
Efficient options for SAP system copies
SAP production system copies are created for a variety of reasons, including: - Generating a new non-production system for short- or long-term use - Updating an existing non-production system An SAP system copy is called homogeneous if the source and target operating and database systems are identical. If this is not the case, the system copy is considered heterogeneous. Heterogeneous system copies or platform migrations are not supported by the HP StorageWorks System Copy software for SAP and are therefore not discussed further in this document. In addition, this document deals exclusively with system copies for non-production target systems. Overview of a homogeneous system copy Figure 1 shows copies of an SAP production system that are created for non-production systems. Some copies are short-term (ad hoc) in nature, while others are intended for long-term use. Note that when a long-term system is created from a system copy, a system copy may be needed for updates later in the system's life cycle. This adds the latest transactional data from the original production system. Given their particular importance, this document focuses on scenarios with system copies created for updates. Figure 1: Overview of scenarios with homogeneous SAP system copies Scenario with system copies for updates In order to meet constantly changing business requirements, a production system must be continuously developed and adapted after the initial installation. To do this, you need development, consolidation, and quality assurance (QA) systems that can provide the production system with the appropriate updates as SAP transports.
With the entry into force of the GDPR, the topic of system copies has been expanded to include the aspect of anonymization: In many cases, personal or other sensitive data is operated on non-productive systems that usually have lower security levels and also allow access for those persons who are not normally allowed to work with GDPR-relevant data (eg developers or external consultants). For this reason, when defining the processes around system copy and, if necessary, also when selecting tools for automation, care must be taken to ensure that these also map data anonymization in accordance with the GDPR.
Downtime
On the other hand, such a tool must ensure that traceability or transparency is always available. What happens in the smallest detail during an SAP system copy creation must be visible in whatever form in order to be able to track down possible errors, but also, for example, to optimize the actual copying process or to accelerate it even further, for example by using log files and more.
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
A solution such as "Shortcut for SAP Systems" offers an automatable solution for many of the activities involved in an SAP system copy.
For appropriate and consistent testing and acceptance of changes in programs and processes, SAP recommends the "homogeneous system copy" approach to provide non-production systems with up-to-date data.
Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.
The test environment will then be missing audit documents, among other things, but the development objects will remain untouched.