Many IT professionals know this time-consuming task: for adequate and consistent testing and acceptance of changes in programs and processes, SAP recommends a regular "Homogeneous System Copy." After taking a look at manual system copies in general in the blog post „System copy – Manual vs. Automated“ we now look at the challenges of this task.
First of all, a (manual) system copy means enormous effort from internal or external SAP Basis professionals in addition to the unavailability of the target systems for operational and project teams.
Secondly, the basic core of a homogeneous system copy consists of performing a large number of standardized and manual pre- and post-processing steps in a specific sequence. Depending on the operating system and database management system, the steps to be performed can also differ significantly.
In the environment of complex structures of interrelated environments, it is also necessary to be able to update the complete landscapes consistently in order to be able to test business processes end-to-end.
Because of these challenges, the processes involved in preparation, execution, and post-processing must be clearly defined and executed in the correct sequence. The large number of steps and the associated complexity should be recognized and taken into account by every SAP professional.
Despite a defined process, however, errors can still occur at any time. In this case, a decision must be made as to whether the copy should be continued or the process restarted. Whether for a sole system copy, the combination of system and client copy, a single line or complex landscapes, Libelle AG offers an easy-to-use solution that helps to master the above challenges in an automated way -Libelle SystemCopy. Find out more now and get your free whitepaper.
Many administrators and consultants who have experience with system and landscape copies are aware of the complexity and duration of this process. One reason for this lies in the SAP environments themselves, as the scope of typical SAP landscapes has always evolved.
From quite straightforward ABAP-based SAP R/3® software to complex, service-oriented architectures with any number of extension options and a broad portfolio of applications. Starting with the standard ERP to the most diverse specialised modules. In addition, new technologies - such as most recently the conversion to HANA - are constantly finding their way into the infrastructures. These are operated partly independently, partly in parallel, and partly already with dependencies on/to the conventional structures.
With the improved capabilities and scalability of today's SAP landscapes, administrators and system managers face many challenges in the face of growing complexity. Thus, these responsible persons must always educate themselves and keep an eye on the market in order to be prepared for the next one, even after the system copy.