SAP system copy Test and training system: data anomyization, migration of master data, migration of user data / passwords - SAP Basis

Direkt zum Seiteninhalt
Test and training system: data anomyization, migration of master data, migration of user data / passwords
Performing SAP system copies automatically
The demands on your business are constantly changing. For this reason, there is also a need to adapt processes and functionalities. This cannot be done directly in the production system, but must first be extensively tested, which in turn requires data that is as realistic as possible. The SAP system copies required for this are quite time-consuming and complex, but also offer very great automation potential. We support you in the execution of SAP system copies and, within the framework of our partnership with Libelle, we can also set up automation mechanisms for you if you have the need for regular system copies. We are also happy to support you with any data anonymization that may become necessary after such a copy.

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.
Multicloud: the systems involved with different hyperscalers
Of course, time savings also mean money savings. In addition, these processes for system copying using such automation tools can be planned, standardized and always run at a high level of process quality. Especially the latter is of great importance in SAP Basis departments (and of course also for service providers).

Basically, a distinction is made between the initial setup and refresh of a non-productive SAP system. In the past, the cost of a refresh, i.e., updating the environment with new data, often corresponded to the cost of the initial setup. This also restricted the availability of the productive system, which is hardly tolerable for companies that operate internationally and in different time zones.

With "Shortcut for SAP Systems" any tables can be saved and restored. This is especially useful in the context of an SAP system copy - quite a few tables are system-specific and must exist unchanged in the system after a system copy.Shortcut for SAP Systems uses R3trans - a utility from SAP that is essentially used in the Transport Management System (TMS) environment. With "Shortcut for SAP Systems" it is now also available outside the TMS and enables completely new and diverse application possibilities. Among others in the environment of a system copy. R3trans works database independent. I.e. even in the case of a system refresh from an SAP system with an Oracle DB to a system with HANA, the backup and restore process works!

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.

Incremental Migration (IMIG): - OS- and DB- independent - for homogeneous and heterogeneous system copies - for Unicode conversions - for ABAP systems as of 4.0B.
SAP BASIS
Zurück zum Seiteninhalt