What is System Copy as a Service?
Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy
Nowadays, companies are required more than ever to react agilely and flexibly to the demands of the global market. It is not unusual for them to have to introduce new processes and projects particularly quickly and securely for the benefit of their own competitiveness. At the same time, their system landscapes are becoming increasingly complex due to mergers and acquisitions and the use of new technologies.
Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date. In these cases, a single client or the entire SAP system is duplicated. The corresponding instances of the SAP system have to be reinstalled. In addition, a copy of the source database must be created. These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes. SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.
Before shutting down the target system
The database import can be performed using various tools. Sapinstaller provides a working way to import the database cleanly.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
There are now a number of tools that simplify refresh activities of non-production SAP systems. The tools are imported into SAP systems via transports and enable the data to be copied to be written in. The more precise the selection, the greater the potential savings in storage space and extraction time compared to client copy. As with the latter, the configuration is retained and ongoing development and test processes remain undisturbed.
With "Shortcut for SAP Systems", tasks in the area of SAP system copying are simplified and can also be automated via the command line interface.
This is often done via a complete system copy (production system -> development system, production system -> quality assurance system) and is very error-prone and user-intensive in ad-hoc configuration (especially if each developer/customizing user is responsible for saving the transports and importing them again after the copy).
Thus, the proposed solution allows you to optimize the automation and acceleration of SAP system copies generated for upgrades and reduce IT administration costs.
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.