Automate SAP system copies
Reliable and fast rework after SAP® system copies
SAP environments can quickly become time-consuming. For example, when it comes to creating system copies of a production environment on the test and quality assurance (QA) system. Because of the time required, some QA systems turn out to be outdated and thus even ticking time bombs. A software tool from Libelle now makes it easier to update QA systems in SAP architectures on System i as well.
System copy of a Unicode system: Source and target system are Unicode systems. The same procedures can be used for the copy, as with the copy of non-Unicode systems.
Types of SAP system copy
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.
Tests are already worthwhile for the introduction of SAP solutions in the company and also for release upgrades and migration projects, the import of patches, customizing, modifications and in-house developments. A three-tier SAP landscape typically consists of development, test and production systems. In addition, there are often training systems.
With "Shortcut for SAP Systems" you can sustainably relieve your administrators of time-consuming routine activities of an SAP system copy.
Once the copy is effectively through, the BDLS is automatically started.
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed.