SAP system copy and the cloud
Update more efficiently
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.
In order to have up-to-date data and exactly the same software versions on an SAP test system for meaningful tests as are active on the production system, the production systems are regularly copied completely to the test system. However, many settings in the test system must be retained, because a test system should not act like a production system and, for example, send documents to customers and suppliers or trigger something in production.
Consideration of additional QA clients
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.
Heterogeneous system copy: As the name suggests, the operating system and/or database on the source and target systems are different. One takes thus in the context of the copy a platform change. This procedure is currently gaining in relevance, as it is required for the migration from SAP ERP to S/4HANA. If the current system runs on Windows Server and SQL Server or Oracle, the target system must now run on Linux and SAP Hana.
From now on, this will be easier. "Shortcut for SAP Systems" contributes to a time-optimized execution of this complex process, no matter when and at what frequency, and while maintaining a high degree of flexibility even in changing environments.
An SAP system copy is not done in an hour.
And last, but not least, such tools must allow for extensibility or enable customer-specific extensions/requirements, such as integration into a scheduler or consideration of SAP double-stack systems.