The Refresh
SAP system clone and copy
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.
The guideline that integrated job logic is preferable to customizing has also proven its worth. The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
We take over your SAP system copies as a service
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.
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.
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed, such as "Shortcut for SAP Systems". Nothing has to be installed in your SAP systems for this - no transport requests, no AddOns!
On the other hand, such a tool must ensure that traceability or transparency is always available.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
The term "system copy" describes the process of creating a copy of an SAP system on a new server.