SAP system copy Consideration of additional QA clients - SAP Corner

Direkt zum Seiteninhalt
Consideration of additional QA clients
Automatic determination of delta states after SAP system copy/recovery
Strategy as of NetWeaver 2007: Prerequisite: in the case of a Unicode conversion, conversion must be performed during export. If the target database can be built with unsorted unloaded data, all packages are automatically unloaded unsorted. R3load ensures that tables that must always be unloaded sorted are unloaded sorted.

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.
SAP system copies and the DSGVO
Unsorted unloading: - By default, R3load sorts table data by primary key before export. This requires time and resources in the source system. Under certain conditions, this sorting can be omitted.

In order to check whether the usable settings are correctly adjusted, especially in the case of large databases, the runtimes are automatically logged during the BDLS. Based on these results, it is possible to analyze how the runtime can be further optimized. By the way, BDLS reports and optimization options are displayed in the BSC GUI, including modification options.

With "Shortcut for SAP Systems", a mature and yet very cost-effective product is available that offers useful functions for system copies. For example, SAP system users can be backed up and restored. Likewise, system-specific tables can be backed up before the system copy and restored after the system copy. And all this can also be automated.

The website www.sap-corner.de offers many useful information about SAP basis.


Connected to this are at least two computers, also spatially separated.

The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
SAP Corner
Zurück zum Seiteninhalt