Several advantages at once
Downtime
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.
Powerful and sophisticated automation tools for the creation of SAP system copies provide a remedy here and demonstrably make it possible, in addition to time and cost savings, to increase the process quality of system copying, for example, or to maintain it at a consistently high level. In effect, they free up SAP Basis.
Automation of homogeneous SAP system copies
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.
A system copy can be created either with SAP transactions (R3trans, from R4.6C SAPinst) or at file and database level. Costs and effort increase with the size of the system and the requirements for availability and data protection. In addition, administrative rework is often necessary, starting with the system name and extending to printers and interfaces.
From now on, this will be easier. "Shortcut for SAP Systems" contributes to a time-optimized execution of this complex process, no matter when and at what frequency, and while maintaining a high degree of flexibility even in changing environments.
This is often done via a complete system copy (production system -> development system, production system -> quality assurance system) and is very error-prone and user-intensive in ad-hoc configuration (especially if each developer/customizing user is responsible for saving the transports and importing them again after the copy).
In this guide we focus on the data to be backed up.