Types of SAP system copy
Challenges with SAP system copies
Tests are already worthwhile for the introduction of SAP solutions in the company and also for release upgrades and migration projects, the import of patches, customizing, modifications and in-house developments. A three-tier SAP landscape typically consists of development, test and production systems. In addition, there are often training systems.
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.
The third-party providers have adapted their tools to various special areas. For example, the "Clone & Test" tool from Pecaso, which is now part of Accenture, specializes in transferring data from SAP's HR module. In addition to HR data, the "Data Sync Manager" from the provider Epi-Use makes it possible to select additional objects from the areas of accounting and logistics. As with TDMS, "Infoshuttle" from Gamma Enterprise Technologies gives users the option of selecting any data from the SAP system. For transport, the tool uses Idocs, which, however, can only be used to transfer small amounts of test data. SNP's "Data Distillery" can either write extracted data directly into the tables of the target system via RFC or generate an export file that can be imported into target systems multiple times. In the source system, users can select by objects, processes and transactions. 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.
An alternative to this is a refresh using a client copy. The test environment will then be missing audit documents, among other things, but the development objects will remain untouched. The client copy only works from a running SAP system, but it burdens the system with database queries and transfers data more slowly than a system copy. The affected client is not available during the copy process. Since there are no options within the client to select what all should be copied, the runtime is often unacceptable.
To shorten the list of activities and to simplify the complete process of a system copy or a system refresh and to save manual activities, you can use "Shortcut for SAP Systems". Several manual activities can be omitted because with "Shortcut for SAP Systems" the system-specific data can be saved before the copy and imported again afterwards - also automated. This reduces the error-proneness that is inevitably caused by manual activities and enormously reduces the time span until the system is available again.
This is the case when dependencies of the source systems are also to be mapped in the target environments.
The tools are imported into SAP systems via transports and enable the data to be copied to be written in.