Scope of the SAP system copy
SAP system deployment scenarios
Partial copies from SAP systems with the help of tools open up potential savings and in many cases make system copies and complete client copies superfluous. The ability to anonymize data reduces the effort required to comply with data protection regulations in training systems, for example. In addition, up-to-date, consistent test data improves the flexibility and quality of development and test environments. Users save money through reduced resource requirements.
Third-party tools sometimes have a different focus than TDMS. The tools each offer a more or less generally understandable user guidance and are thus "out-of-the-box" products that do not require external consulting on implementation or application.
Job logic instead of customizing
In order to check whether the usable settings are correctly adjusted, especially in the case of large databases, the runtimes are automatically logged during the BDLS. Based on these results, it is possible to analyze how the runtime can be further optimized. By the way, BDLS reports and optimization options are displayed in the BSC GUI, including modification options.
As mentioned above, an SAP system copy created for updates is a special use case of homogeneous system copy. Here, a production system represents the source and a non-production system with a specific long-term task in the SAP system landscape represents the target. The most common update scenario involves updating a QA system in the SAP transport system.
SAP system copy is made much easier by the "Shortcut for SAP Systems" application.
An SAP system copy is an important part of a company's IT operations, as it helps reduce the risk of data loss.
Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible.