SAP SYSTEM COPY - in a nutshell
Technical system copy for the upgrade
In practice, customers have either built their own tools to make the appropriate configurations, or there are extensive lists of steps to be processed manually. This approach is time-consuming and error-prone.
Especially in complex environments, SAP system copies regularly represent a critical challenge in terms of time and expertise and thus become a real cost factor in the long run. This is because system copies must be scheduled at an early stage, are complex, time-consuming and resource-intensive, require specific knowledge, tie up important employee capacities due to the large number of manual interventions, and are error-prone.
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
Creating a consistent storage replica - splitting a clone or creating a snapshot on the disk array. Regardless of the storage size, this process takes only a few seconds.
To build a target system that can be used for testing, development and training purposes, there are two different approaches: Users can reinstall an SAP system and import all transports and support packages that have also made it into the production system to date. However, when their number reaches the hundreds and thousands, the effort becomes disproportionately high. In addition, the data still has to be imported from the production system, for example via a client copy.
With "Shortcut for SAP Systems" you can sustainably relieve your administrators of time-consuming routine activities of an SAP system copy.
In this context, generated jobs adapt to changes, even if, for example, a DB change, a release change or other changes have taken place.
It is not unusual for them to have to introduce new processes and projects particularly quickly and securely for the benefit of their own competitiveness.