Types of SAP system copy
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).
Typically, the "homogeneous SAP system copy" process involves a large number of manual activities. A certain skill level is required for this, which leads to the fact that usually the employees of the SAP Basis department or external service providers realize the system copy. Depending on the structure and size of the systems, this process can take anywhere from hours to several days. In addition to making the target systems unavailable to operations and project teams, system and landscape copies also block SAP Basis administrators. Other challenges include the varying duration and quality (completeness) of the results depending on the processor, time dependency on the employees performing the work, etc.
Pre- and post-processing
The professional handling of test data is also important with regard to applicable data protection and compliance guidelines. Global companies in particular are required to take measures to protect sensitive data. They need to ensure compliance and reduce risks from data breaches, even in non-productive environments. Innovative test data management can protect data from internal and external misuse through encryption, among other things. Sensitive personal data is secured in accordance with current data protection requirements, while at the same time high test quality is achieved through realistic 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.
Powerful and sophisticated automation tools for the creation of SAP system copies provide a remedy here and, in addition to time and cost savings, demonstrably also make it possible, for example, to increase the process quality in system copying or to maintain it at a consistently high level. In effect, they free up SAP Basis. With "Shortcut for SAP Systems", you can sustainably relieve your administrators of the time-consuming routine activities of an SAP system copy.
For information from SAP about configuring and supporting the Connector for LaMa, see SAP Note 3078321.
This prevents a transport from unintentionally "overtaking" an earlier released one with the same objects.