Possibility of manual intervention in case of delta import
Performing SAP system copies automatically
The Migration Monitor: is a standalone tool implemented in Java, takes over the management and control of the R3load processes, is downward compatible. Use the latest Migration Monitor version of the highest release!
Users do not have to deal with individual tables, but can access a database of business entities. This means that they do not select tables, but business objects such as employees or documents. To do this, however, the tools must contain the object dependencies for SAP's complex data model. Even companies that offer the setup of test systems as a service rarely do this for any SAP dataset. In addition, users can define objects themselves to accommodate customizing and in-house developments.
SAP system copies and the DSGVO
One to two pre-tests are required, one of which should be performed on the production system. The additional load on the production system caused by the IMIG has been negligible. Split/mirror techniques allow many actions to be moved from the production machine to another machine.
Powerful and sophisticated automation tools for the creation of SAP system copies provide a remedy here and demonstrably make it possible, in addition to time and cost savings, to increase the process quality of system copying, for example, or to maintain it at a consistently high level. In effect, they free up SAP Basis.
Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.
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.
Storage systems are usually secured in disk arrays by multi-level raid, spatially separated from each other and networked by a storage area network (SAN).
For information on installing and configuring SAP Landscape Management, see the latest SAP documentation on the SAP Help Portal.