TM-TMS (Transport Manager)
Automate SAP system copies
The guideline that integrated job logic is preferable to customizing has also proven its worth. The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
While homogeneous SAP system copy expects identical combinations of operating/database systems on the source and target systems, there is also a requirement for different combinations of operating/database systems on the source and target systems in the project environment (eg, during migrations). This is referred to as a "heterogeneous SAP system copy". Technically, it is quite possible to build up a degree of automation here as well, but officially certified consultants ("migration consultants") are required to perform the heterogeneous system copy.
Scope of the SAP system copy
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.
After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level. To automate the creation of the technical system copy for upgrade, HP System Copy can be used for the following steps.
With "Shortcut for SAP Systems" you get additional functions for the SAP system copy.
However, the system does not have the same identity in the SAP landscape as it had before the update.
In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system.