Purpose of the SAP system copy
Consideration of additional QA clients
Installing the Connector for LaMa enables a Cloud Manager feature for Google Cloud in SAP Landscape Management. This guide does not provide instructions for installing, configuring, or operating SAP Landscape Management. For information on installing and configuring SAP Landscape Management, see the latest SAP documentation on the SAP Help Portal. For information from SAP about configuring and supporting the Connector for LaMa, see SAP Note 3078321.
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.
Automation tool reduces time required to create test environments
In SAP, the admin must be happy to build new landscapes so that testing, development and enhancement can take place. In a system copy, the approaches are as colorful and varied as the philosophies of the administrators. The important thing is to think about the target system before building it. After all, after the database is removed and the system is rebuilt, there will be two identical systems on the network.
An SAP system copy is a process in which an exact copy of an existing SAP system is created. This copy can be used to run tests, perform development, or back up the system.
With "Shortcut for SAP Systems" the effort for many work steps is reduced. The work done by "Shortcut for SAP Systems" lies in the preparation and post-processing of the data - by backing up the system-specific data before the system copy and restoring it after the system copy. Efforts for preparation and post-processing are thus reduced to a minimum.
To meet ever-changing business requirements, a production system must be continuously developed and adapted after the initial installation.
A system copy can be created either with SAP transactions (R3trans, from R4.6C SAPinst) or at file and database level.