29-03-2021

System Copy In Sap Basis

SAP HANA system copy can be a time-consuming process for SAP Basis system administrators. Admins spend a considerable amount of time and effort preparing the software environment and going through complicated procedures to ensure that the backup and recovery process is carried out with minimum disruption to the business. If a system copy takes place between systems with same platform (operating system and database system), then it’s called HOMOGENEOUS SYSTEM COPY. Reasons for Copying a SAP System To create a new training system for end-user or project team education To create a DEMO system.

Hope every SAP basis consultants / users do well. May i’m still beginner in SAP Basis world, but i think it is very good to share our knowledge between us. Note: if you get bored of reading long articles, kindly forgive me. One of my big issue i faced in our SAP system in copy clients, some tables not completely copied. Heterogeneous System Copy for SAP Systems Based on SAP release” (in the following called System Copy Guide) to get information on copying SAP WebAS-based components. This documentation was written on the basis of System Copy Guide for WebAS version 6.40 SR1 and for NetWeaver 2004s.

Skip to end of metadataGo to start of metadata

If you copy a system which is connected to a BW system or in case you copy the BW itself or both, several steps has to be considered in order to make sure that the connection between BW and another SAP source system works again after one or both systems have been copied.

System copy with PCA (Post-Copy Automation)

SAP provides an automated solution in order to manage the very complex challenge.

A very good overview is available under the following link:

Sap Basis Classes

and SAP note 1707321

delta queue cloning and renaming of the prefix is only possible with PCA

ODP source system connection and ODQMON: deletion of subcriptions which are pointing to the wrong system and creation of the 'new'subcription to the correct system is possible

PCA is not yet released on BW/4HANA, have a look at SAP note 2570363

System copy without PCA tool

Not all landscapes can be described but the the main steps are also described in SAP note 886102. This consulting note has been created when SAPI source systems are involved. In case of ODP source systems, PCA should be used. Not all steps are not necessary anymore for ODP source systems but additional tasks are necessary e.g. cleanup of ODQMON which is possible by using PCA.

Important is that all steps should be executed in the correct order. Additionally have a look at the recommended note list, which should be implemented in case you need to execute BDLS: KBA 2176213

System copy on HANA:

Run the Report RS_BW_POST_MIGRATION with the Option 12 (create calculation view cubes/infoobjects) and 15 (Adjust Snapshots and AnalyticalIndexe) to create missing calc views and workspaces.

SAP note 886102 is not applicable for BW/4HANA systems! Have a look at SAP note 2570363

According to SAP note 886102:

What do you intend to copy?

Below scenarios only decribe the steps which are necessary for SAPI source system connection. For ODP source system connection, have a look at SAP note 886102

Difference Between System Copy And System Refresh In Sap Basis

entire system group (BW system + SAP Source System	only BW (without connected Source System)	SAP Source System of a BW System
Scenario A1 replace productive system group Be aware that a system refresh is a task, during which productive use of the target system of the copy is not possible. Any end users except the system administrator(s) performing the pre- and post-processing must be excluded from log on and any productive operations must be suspended. This being said, until the system copy and post-processing is finished and verified, the target system is not considered 'productive', regardless the system setting for the client role in table T000. Therefore, this scenario can be identified with scenario A2.	replace productive BW system Be aware that a system refresh is a task, during which productive use of the target system of the copy is not possible. Any end users except the system administrator(s) performing the pre- and post-processing must be excluded from log on and any productive operations must be suspended. This being said, until the system copy and post-processing is finished and verified, the target system is not considered 'productive', regardless the system setting for the client role in table T000. Therefore, this scenario can be identified with scenario B2.	replace a productive source system of a BW system Be aware that a system refresh is a task, during which productive use of the target system of the copy is not possible. Any end users except the system administrator(s) performing the pre- and post-processing must be excluded from log on and any productive operations must be suspended. This being said, until the system copy and post-processing is finished and verified, the target system is not considered 'productive', regardless the system setting for the client role in table T000. Therefore, this scenario can be identified with scenario C2.
create or refresh a non-productive system group	create a new non-productive BW system	create a new non-productive source system
refresh an existing non-productive BW system	refresh an existing non-productive source system
create a non-BW client by copying a BW client	create a new non-productive source system client

Special business requirements

BW client copy is not useful

Reason is that most of the BW tables are client independent (table includes not a client) and therefore most of the tables will not be copied during the copy process.

more information in SAP note 1947388

Source system replacement

It is recommended to create a new connection in BW to the new/refreshed sourcesystem even you want to replace an existing source system connection.

Details are explained in Scenario C2; create a new connection in BW to the new/refreshed sourcesystem

Copying only meta data and customizing settings of BW

new installation is recommended and transporting the dataflow from a different system
OR
liable to pay costs option:
Use SLO (System Landscape Optimization) respectivly SLT (System Landscape Transformation) which provides the possiblity of partly system copy e.g copying of infocubes without data.

Replace a BW source system client

Create a new connection in BW, changing the RFC connection is not enough as BW is working with the logical system name.

Details are explained in Scenario 4

This is also recommended in case you did not copy the client but want to connect a different source system client to your BW.