Types of SAP system copy
Differentiation between homogeneous and heterogeneous SAP system copy
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.
To build a target system that can be used for testing, development and training purposes, there are two different approaches: Users can reinstall an SAP system and import all transports and support packages that have also made it into the production system to date. However, when their number reaches the hundreds and thousands, the effort becomes disproportionately high. In addition, the data still has to be imported from the production system, for example via a client copy.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
Easy integration also in the system copy of systems of older releases possible!
The steps to be taken before shutting down the target SAP system can be summarized as follows: Well before performing the upgrade, inform the target system users - especially project managers, developers, and testers - about the planned maintenance work via e-mail, SAP system messages, and/or a message at the system logon. Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible. Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system. After logging users off and locking them out, download system-specific content from the target system database for customization (including security settings, Remote Function Call (RFC) targets, and operating modes).
Table splitting requires 2 tools: R3ta, which determines the WHERE conditions used to access subsets of a table. TableSplitter, which splits the WHERE-conditions determined by R3ta into packages with one or more subsets.
"Shortcut for SAP Systems" can considerably simplify and shorten a number of activities within the scope of a system copy or a system refresh. By using this application in conjunction with the information on system-specific tables from the PCA tool, the system-specific data can be backed up and restored after the system copy / system refresh. As a result, many of the activities mentioned here regarding data backup / restore can be performed much more easily; the creation of screenshots and the subsequent manual restoration of the state documented in this way can then be completely eliminated.
Logical system names must also be converted (using the BDLS trasaction code).
Some useful tips about SAP basis can be found on www.sap-corner.de.
However, the system does not have the same identity in the SAP landscape as it had before the update.