Challenges with SAP system copies
As mentioned above, an SAP system copy created for updates is a special use case of homogeneous system copy. Here, a production system represents the source and a non-production system with a specific long-term task in the SAP system landscape represents the target. The most common update scenario involves updating a QA system in the SAP transport system.
The initial screen will then, for example, already show an overview of the - in some cases automatically - integrated systems and their status, as well as system information such as release, patch level and the like. The use of a comprehensive dashboard will then also be included.
Ways of SAP system copy: export / import
Often, the development and test systems of an SAP landscape are far removed from the status of the productive systems used on a daily basis: Outdated developments, customizing settings and master data reduce the quality and trustworthiness of test and emergency scenarios. It also becomes increasingly difficult to make reliable statements about the behavior of the production system after changes in customizing.
The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.
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.
With "Shortcut for SAP Systems" you can sustainably relieve your administrators of time-consuming routine activities of an SAP system copy.
In that case, it's best to do this on a system copy.
The tool from Automic, a specialist in business automation, allows SAP system copies to be created almost fully automatically.