Solution infrastructure
Food for thought for another productive system: until when must the system be identical, keyword: transaction log
The task of a system copy created for updates is a carefully integrated system that takes on a specific role in an SAP system landscape. That is why customizing the SAP database of the target system differs significantly from customizing the database of the production system. In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system. Therefore, all SAP-specific customization of the target system must be performed after the update with the system copy. The pre- and post-processing is often performed manually while the target system is running. Specific SAP transactions are used to customize the system. Execution can take a long time and is a source of human error. To automate most transactions, UC4 Automated System Copy for SAP can also be used. Before the update, UC4 Automated System Copy takes care of downloading the required content for the SAP customization from the target system and after the update is complete, uploading the content back to the 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.
Automation tool reduces time required to create test environments
A non-production SAP system should also have the same repository status as the source system, regardless of the data transfer method chosen for the refresh. All the data that makes up an SAP system is stored in the repository. This includes, among other things, the definitions for the database fields and tables for master and transaction data.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Suitable tools make it possible to automate and accelerate the necessary creation of true-to-original SAP system copies, for example. This means that you have all production data available on your test system in a short time.
With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.
Based on these results, it is possible to analyze how the runtime can be further optimized.
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.