SAP system copy On-premises: all involved source/target systems in the company's own data centers - SAP Corner

Direkt zum Seiteninhalt
On-premises: all involved source/target systems in the company's own data centers
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.

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.
Multicloud: the systems involved with different hyperscalers
Depends on the extent of splitting and the degree of parallelization. When importing, the limiting factor is often the index structure.

Unicode conversion: A Unicode target system is built from a non-Unicode source system. Unicode conversion can only be performed using procedures based on R3load.

"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.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page:

You must purchase all required licenses for SAP Landscape Management from SAP.

For a heterogeneous system copy and for homogeneous system copies for which there is no special way for the database used, the source system must be exported.
SAP Corner
Zurück zum Seiteninhalt