Types of SAP system copy
The Refresh
To ensure that SAP solutions are nevertheless used optimally, decision-makers are well advised to regularly subject IT landscapes and applications to intensive testing. This helps to avoid potential errors and risks during operation, which can quickly lead to immense costs. But providing test data can also prove to be a challenge. Given the increased use of Big Data, storage space and resulting costs are constantly rising. In addition, testing is complicated by the growing complexity of applications and IT architecture. It can therefore be profitable for companies to invest in professional test data management, which offers decisive advantages.
Regular updating reduces operational risk and improves the quality of the multi-level system landscape. To update the non-productive systems of an SAP landscape, the data must be cloned from the productive system. This is time-consuming and requires very complex rework.
What is System Copy as a Service?
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.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
Unicode conversion: During the copy, the system is converted from non-Unicode to Unicode. This happens in the context of a homogeneous or heterogeneous system copy. In connection with Unicode must be differentiated between the system copy of a Unicode system and the Unicode conversion.
"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.
The process of a system copy usually does not change.
Some useful tips about SAP basis can be found on www.sap-corner.de.
Landscape copies refer to the update of not only one but a whole group of systems.