Consideration of additional QA clients
Import of delta statuses after SAP system copy / restore
Quasi tick boxes instead of time-consuming handling of programming lines, so that the use is also possible for less experienced experts who have never or only few SAP system copies created. And this after little system training.
The term "system copy" describes the process of creating a copy of an SAP system on a new server. There are two types to be distinguished: homogeneous and heterogeneous system copy and one can get to the system copy in different ways.
Automation of homogeneous SAP system copies
Such system copies, with their enormous manual effort and SAP checklists that are often hundreds of items long, must be performed before every refresh. Usually, three to four days have to be planned for this, during which the QA system - which in two-tier SAP environments is also the development system - is not available for the actual work. The delay is actually only caused by the meticulous matching of trivial things, such as directory names. Because such SAP system copies have to be created for each SAP application on the QA system and can thus quickly require dozens of system copies, they tie up a lot of resources and staff.
Today, thanks to tools for creating SAP system copies, it is possible to create such system duplications practically at the push of a button, and that too in a very short time. Even several at once.
Use "Shortcut for SAP Systems" to make a required SAP system copy easier and faster.
In addition, the data still has to be imported from the production system, for example via a client copy.
Cloud Manager supports the following SAP Landscape Management scenarios for SAP HANA system replication tiers.