SAP system deployment scenarios
Reliable and fast rework after SAP® system copies
Nowadays, companies are required more than ever to react agilely and flexibly to the demands of the global market. It is not unusual for them to have to introduce new processes and projects particularly quickly and securely for the benefit of their own competitiveness. At the same time, their system landscapes are becoming increasingly complex due to mergers and acquisitions and the use of new technologies.
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.
Technical system copy for the upgrade
On the other hand, such a tool must ensure that traceability or transparency is always available. What happens in the smallest detail during an SAP system copy creation must be visible in whatever form in order to be able to track down possible errors, but also, for example, to optimize the actual copying process or to accelerate it even further, for example by using log files and more.
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.
To shorten the list of activities and to simplify the complete process of a system copy or a system refresh and to save manual activities, you can use "Shortcut for SAP Systems". Several manual activities can be omitted because with "Shortcut for SAP Systems" the system-specific data can be saved before the copy and imported again afterwards - also automated. This reduces the error-proneness that is inevitably caused by manual activities and enormously reduces the time span until the system is available again.
In Release 6.40 and 7.00 the 'NetWeaver 2007 Strategy' can be implemented with manual configuration.
Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date.