SAP system deployment scenarios
Update more efficiently
When executing a system copy, all tables, processes, databases, etc. are taken into account when copying. Logical system names must also be converted (using the BDLS trasaction code). The process of a system copy usually does not change. If no structural changes have been made to the SAP systems involved, the process is even 100% identical. Due to the very high repeatability of the nevertheless complex process, it is advisable to automate it to a large extent.
By using the automation solution, errors that typically occur with manual process steps - just like additional costs due to repetition - can be avoided. To date, the IT team has created 88 SAP system copies. "If we had wanted to do this with SAP board resources, we would not have been able to pay for it as a medium-sized company," Rudi Scharf knows.
Reliable and fast rework after SAP® system copies
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed. In addition to this area of activity, additional automation tools are also available, for example up to the creation of sandboxes, which provide valuable services.
SAP system copies are necessary, regardless of the basic infrastructure. Particularly in the context of automation, preference should be given to solutions that support all relevant types of SAP system operation.
Tools such as "Shortcut for SAP Systems" supplement missing functions in the area of SAP system copy.
Large or complex tables with an extremely long runtime can lead to a very long total runtime, even if a separate package has already been defined for the table.
In addition, a refresh also interrupts all processes on the target system.