Performing SAP system copies automatically
Critical factor: Availability
Strategy as of NetWeaver 2007: Prerequisite: in the case of a Unicode conversion, conversion must be performed during export. If the target database can be built with unsorted unloaded data, all packages are automatically unloaded unsorted. R3load ensures that tables that must always be unloaded sorted are unloaded sorted.
We will be happy to advise you and work out the most suitable solution for you together with you - so that you profit 100% from Systemcopy as a Service. Contact us.
Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
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.
The tools we use can be easily operated either in the cloud or on premise. For this, the SAP systems to be copied must allow access at operating system level. The typical cloud infrastructures, such as AWS or Azure, are not a hurdle for this service.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
The disruption of the production system - sooner or later - is then already pre-programmed.
Training courses, for example, can only be held expediently if the working conditions largely correspond to those on the production system.