Technical system copy for the upgrade
Automatic determination of delta states after SAP system copy/recovery
Fact: BDLS is a kind of "time eater" for system copies (except when using Hana). An important first step is to integrate the BDLS run into the system copy. Once the copy is effectively through, the BDLS is automatically started.
There are various ways to tame this time robber and reduce run times. For example, through parallelization or the automatic generation of secondary indices.
Planning Guide for the Connector for SAP Landscape Management
In SAP, the admin must be happy to build new landscapes so that testing, development and enhancement can take place. In a system copy, the approaches are as colorful and varied as the philosophies of the administrators. The important thing is to think about the target system before building it. After all, after the database is removed and the system is rebuilt, there will be two identical systems on the network.
Typically, the "homogeneous SAP system copy" process involves a large number of manual activities. A certain skill level is required for this, which leads to the fact that usually the employees of the SAP Basis department or external service providers realize the system copy. Depending on the structure and size of the systems, this process can take anywhere from hours to several days. In addition to making the target systems unavailable to operations and project teams, system and landscape copies also block SAP Basis administrators. Other challenges include the varying duration and quality (completeness) of the results depending on the processor, time dependency on the employees performing the work, etc.
Tools such as "Shortcut for SAP Systems" supplement missing functions in the area of SAP system copy.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
Table splitting reduces the risk of losing a lot of time during export in case of an error.
For each package being processed, there is a = line.