Efficient options for SAP system copies
Planning Guide for the Connector for SAP Landscape Management
Normally, therefore, the target system is created using a copy of the production system. The advantages here are: After the initial setup, data is already available, and users receive a completely identical test environment. However, the disadvantages of this procedure are the high memory requirements, the lack of anonymization of the data and the long runtime of the copy process.
The initial screen will then, for example, already show an overview of the - in some cases automatically - integrated systems and their status, as well as system information such as release, patch level and the like. The use of a comprehensive dashboard will then also be included.
Automatic determination of delta states after SAP system copy/recovery
The database import can be performed using various tools. Sapinstaller provides a working way to import the database cleanly.
The freeware Scribble Papers is a "note box" in which all kinds of data can be stored. It takes in typed texts as well as graphics and entire documents. The data is then organised in folders and pages.
The steps to be taken before shutting down the target SAP system can be summarized as follows: Well before performing the upgrade, inform the target system users - especially project managers, developers, and testers - about the planned maintenance work via e-mail, SAP system messages, and/or a message at the system logon. Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible. Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system. After logging users off and locking them out, download system-specific content from the target system database for customization (including security settings, Remote Function Call (RFC) targets, and operating modes).
"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.
We support you in the execution of SAP system copies and, within the framework of our partnership with Libelle, we can also set up automation mechanisms for you if you have the need for regular system copies.
R3load ensures that tables that must always be unloaded sorted are unloaded sorted.