SAP system copy SAP system deployment scenarios - SAP Corner

Direkt zum Seiteninhalt
SAP system deployment scenarios
Planning Guide for the Connector for SAP Landscape Management
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.

Normally, therefore, the target system is created using a copy of the production system. The advantages here are: After the initial setup, data is already available, and users receive a completely identical test environment. 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.
What is System Copy as a Service?
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).

In practice, customers have either built their own tools to make the appropriate configurations, or there are extensive lists of steps to be processed manually. This approach is time-consuming and error-prone.

With "Shortcut for SAP Systems" you get additional functions for the 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.


Once the copy is effectively through, the BDLS is automatically started.

For information on installing and configuring SAP Landscape Management, see the latest SAP documentation on the SAP Help Portal.
SAP Corner
Zurück zum Seiteninhalt