The main purpose of a heterogeneous system copy is to create a copy of an already existing SAP system on the platform where either operating system, or database, or both differ from the operating system/database of the source system. The whole migration process consits of five main steps (described in detail in the system copy documentation). I am working as BASIS Consultant in Cognizant Technology Solutions. This document discusses about the steps to do an E-Sourcing system copy Keywords: SAP, SDN. Answer: The main purpose of a homogeneous system copy is to build a test, demo or training system or to move a system to a new hardware. The difference from a heterogeneous system copy is that both the database and operating system remain the same. 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 and in accordance with best practices.
- Sap Basis Administrator Jobs
- System Copy In Sap Basis Costing
- System Copy In Sap Basis Process
- Sap Basis Tutorial
- System Copy In Sap Basis
- System Copy In Sap Basis Form
Sap Basis Administrator Jobs
Skip to end of metadataGo to start of metadataIf 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:
System Copy In Sap Basis Costing
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
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.
System Copy In Sap Basis Process
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
Sap Basis Tutorial
System copy on HANA:
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
System Copy 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 | replace productive BW system Be aware that a system refresh is a task, during which | replace a productive source system of a BW system Be aware that a system refresh is a task, during which |
create or refresh a non-productive system group | create a new non-productive BW system | Dell latitude e6520 wireless driver download. 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
| 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. |
Restriction concerning system copy without PCA:
- no delta cloning possible
- no renaming of the prefix possible
- ODQMON has to be cleaned-up manually
Comments are closed.