SAP system copy Solution Description

Direkt zum Seiteninhalt
Solution Description
SAP system startup and shutdown, including virtual hosts
Quasi tick boxes instead of time-consuming handling of programming lines, so that the use is also possible for less experienced experts who have never or only few SAP system copies created. And this after little system training.

An SAP system copy is not done in an hour. Due to the large amount of data in an SAP system, the individual steps can take a long time to complete. The export and the import do not always run without errors. Often one is held up by troubleshooting. Of course, the target system must be prepared before the actual copy can be performed: Setting up the server, installing the operating system and database software, downloading and copying the installation media. During the export, the source system cannot be used. Therefore, this task must be planned well and in advance.
Copy only specific data
The third-party providers have adapted their tools to various special areas. For example, the "Clone & Test" tool from Pecaso, which is now part of Accenture, specializes in transferring data from SAP's HR module. In addition to HR data, the "Data Sync Manager" from the provider Epi-Use makes it possible to select additional objects from the areas of accounting and logistics. As with TDMS, "Infoshuttle" from Gamma Enterprise Technologies gives users the option of selecting any data from the SAP system. For transport, the tool uses Idocs, which, however, can only be used to transfer small amounts of test data. SNP's "Data Distillery" can either write extracted data directly into the tables of the target system via RFC or generate an export file that can be imported into target systems multiple times. In the source system, users can select by objects, processes and transactions. Further selection options, for example by organizational units or fiscal year, allow a percentage of the data to be filtered out of the system as consistent test data.

SAP SE is a software company that uses the proprietary programming language ABAP. SAP® landscapes include not only production but also Quality Assurance (QA) systems as well as test and other staging systems. For appropriate and consistent testing and acceptance of changes in programs and processes, SAP recommends the "homogeneous system copy" approach to provide non-production systems with up-to-date data.

There is a useful product for SAP system copy - "Shortcut for SAP Systems".

Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production.

Scenario: We assume that a new training system will be created from the productive system.
SAP Corner
Zurück zum Seiteninhalt