SAP system copy SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE - SAP Basis

Direkt zum Seiteninhalt
SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
Differentiation between homogeneous and heterogeneous SAP system copy
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.

In the case of BSC, sophisticated mechanisms make it possible to exclude configuration errors, since relevant parameter settings are made automatically and according to predefined rules. For example, it is automatically recognized whether the system is an Abap, Java or double-stack system.
Solution Description
Installation continues until the 'Load Data' phase. Here the program waits for successfully exported packages and starts the import as soon as a package has been exported.

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.

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.

In these cases, a single client or the entire SAP system is duplicated.

However, the disadvantages of this procedure are the high memory requirements, the lack of anonymization of the data and the long runtime of the copy process.
SAP BASIS
Zurück zum Seiteninhalt