SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
SAP system/instance move
SAP offers its own solution for this: With the Test Data Migration Server (TDMS), individual tables can be selected and written indirectly, via a third SAP system, from the source to the target system via Remote Function Call (RFC). However, the selection of business objects is not possible in the standard system. The tables to be copied can only be determined on the basis of the date. The content restriction applies from a certain point in time. At least the SAP tool can be used to reduce the runtime of an extraction of test data compared to the system copy or client 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.
Performing SAP system copies automatically
In order to be able to work with the most up-to-date data possible on the development and quality assurance systems, it is necessary to bring an up-to-date production status onto these systems. 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). Every SAP system copy then carries the risk of losing the development status achieved and can lead to inconsistencies in programs and customizing, and any damage repair is usually very time-consuming.
An SAP system copy is an important part of a company's IT operations, as it helps reduce the risk of data loss. However, it is important to regularly schedule and monitor the creation of system copies to ensure that a working copy of the system is available in the event of an emergency.
With "Shortcut for SAP Systems" the effort for many work steps is reduced. The work done by "Shortcut for SAP Systems" lies in the preparation and post-processing of the data - by backing up the system-specific data before the system copy and restoring it after the system copy. Efforts for preparation and post-processing are thus reduced to a minimum.
A non-production SAP system should also have the same repository status as the source system, regardless of the data transfer method chosen for the refresh.
When you install the Connector for LaMa, the following SAP Landscape Management operations are enabled in Google Cloud.