Consideration of additional QA clients
The target system
When executing a system copy, all tables, processes, databases, etc. are taken into account when copying. Logical system names must also be converted (using the BDLS trasaction code). The process of a system copy usually does not change. If no structural changes have been made to the SAP systems involved, the process is even 100% identical. Due to the very high repeatability of the nevertheless complex process, it is advisable to automate it to a large extent.
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.
Several advantages at once
Security-conscious companies usually keep their mission-critical IT infrastructures redundant anyway. Storage systems are usually secured in disk arrays by multi-level raid, spatially separated from each other and networked by a storage area network (SAN). Connected to this are at least two computers, also spatially separated. One of these acts as a backup system.
The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years. The first tools for SAP system copy creation came from the mainframe environment.
"Shortcut for SAP Systems" can considerably simplify and shorten a number of activities within the scope of a system copy or a system refresh. By using this application in conjunction with the information on system-specific tables from the PCA tool, the system-specific data can be backed up and restored after the system copy / system refresh. As a result, many of the activities mentioned here regarding data backup / restore can be performed much more easily; the creation of screenshots and the subsequent manual restoration of the state documented in this way can then be completely eliminated.
Due to the SAP system copy, the test and development systems are up to date and tests can be performed reliably and trustworthily on the non-production systems.
Further selection options, for example by organizational units or fiscal year, allow a percentage of the data to be filtered out of the system as consistent test data.