Conclusion
Before shutting down the target system
Acceleration/table export: up to 4 times faster. The larger the table and the higher the effort for sorting, the greater the time gain during export.
Also of increasing relevance to companies is the rapid provision of test data or systems in different data centers or in the cloud. A modern test data solution can implement these requirements in a largely automated manner, reducing manual effort, lowering the susceptibility to errors, and saving time and money.
Purpose of the SAP system copy
Advantage of the system copy: Users receive one hundred percent consistent test data. A disadvantage, however, is the high storage space requirement of such a test system, which corresponds to that of the productive system. In addition, an authorization concept for the system copy is required to protect the authentic data it contains. Otherwise, company secrets are at risk, and there is a violation of regulations such as the Federal Data Protection Act and the Sarbanes-Oxley Act.
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.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
On www.sap-corner.de you will also find useful information about SAP basis.
The use of standard protocols for the interaction of tool (client/server) and source system and tool with target system has proven itself, exclusively for the purpose of system copy creation.
In this context, generated jobs adapt to changes, even if, for example, a DB change, a release change or other changes have taken place.