Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date. In these cases, a single client or the entire SAP system is duplicated. The corresponding instances of the SAP system have to be reinstalled. In addition, a copy of the source database must be created. These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes. SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.
Landscape copies refer to the update of not only one but a whole group of systems. This is the case when dependencies of the source systems are also to be mapped in the target environments. Similar to the simple system copy, the landscape copy also offers potential for automation, but this cannot be implemented by every tool on the market.
SAP system/instance move
There are now a number of tools that simplify refresh activities of non-production SAP systems. The tools are imported into SAP systems via transports and enable the data to be copied to be written in. The more precise the selection, the greater the potential savings in storage space and extraction time compared to client copy. As with the latter, the configuration is retained and ongoing development and test processes remain undisturbed.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
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.
With "Shortcut for SAP Systems" you get additional functions for the SAP system copy.
Database tuning: - Database partner recommendations - SAP notes (eg 936441).
That's why post-processing is required.