Automate SAP system copies
Several advantages at once
When executing a system copy, all tables, processes, databases, etc. are taken into account when copying. Logical system names must also be converted (using the BDLS trasaction code). The process of a system copy usually does not change. If no structural changes have been made to the SAP systems involved, the process is even 100% identical. Due to the very high repeatability of the nevertheless complex process, it is advisable to automate it to a large extent.
Until now, there has been no functional tool for System i to automate and optimize this task. The enormous resource requirements that arise during a refresh of the SAP QA system really cry out for an optimizing software tool. System Copy from Libelle (LSC) reduces the effort required for these work steps. Although a one-time effort is still required, the system landscape is examined so well that the system copy and any subsequent ones are performed literally at the push of a button. The work that is automated by LSC is in the preparation and post-processing of the files as well as the actual system copy.
We take over your SAP system copies as a service
Depends on the extent of splitting and the degree of parallelization. When importing, the limiting factor is often the index structure.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
Different DDLORA* files can be assigned to the R3load packages. The assignment is done by a text file, which is given to the MigrationMonitor as parameter 'ddlMap = mapDDL.txt' and evaluated by it.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
The version history is lost in the process.
On www.sap-corner.de you will also find useful information about SAP basis.
It describes the preparations, the general procedure in the form of a quick guide, the individual steps in detail, typical error situations and the problem-solving procedure.