Skip to end of metadata
Go 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:

     http://scn.sap.com/docs/DOC-32414

     http://scn.sap.com/docs/DOC-54097

     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

entire system group (BW system + SAP Source Systemonly 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.

Scenario B1

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.

 

Scenario C1

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.

Scenario A2

create or refresh a non-productive system group

Scenario B2

create a new non-productive BW system

Scenario C2

 create a new non-productive source system

 

Scenario B3

refresh an existing non-productive BW system

Scenario C3

refresh an existing non-productive source system

 

 Scenario B4

create a non-BW client by copying a BW client

Scenario C4

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.

   
   

Restriction concerning system copy without PCA:

  • no delta cloning possible
  • no renaming of the prefix possible
  • ODQMON has to be cleaned-up manually

Connections errors after a system copy

How to check a BW - SAP SAPI source system connection

BDLS - Logical system name conversion

 

8 Comments

  1. Hello Janette,

    Please share your thoughts on this?

    Our BW PRD client is setup different than the Quality client configuration, ie (PRD 400, QAS 300). As you know already, this will overwrite the QAS 300 to make PRD 400.

    My strategy is after the copy is done and QAS now has overwritten 300 and is now 400, 1) create a new client 300 in QAS,

    2) then run DB stat on client 400,

    3) do a local client copy in QAS 400 to the new QAS 300 client

    4) Run BDLS 5) resume BW Post steps, ie RSA1, etc...

    Although it will take time and save the BW team extra headache with residual issues from the wrong client configuration. Please let me know if you think this is a good option or offer other options if not?

  2. Hi,

    it is not recommended to change BW client. Have a look at KBA 1720687.

    best regards,

  3. Thank you for your timely response Janette for providing the note. Being that the system copy had already taken place and that QAS 300 was overwritten in the process, which is now PRD 400, can you clarify what  the note actually suggesting in relation to system copy cases like this?

     Does it mean to not change the client after the copy?  

     I understand that BW operates on a single client. However, the BW PRD and QAS clients were not setup with the same numbers and its causing extra steps the BW team have to take beyond standard BW post copy steps. Can you provide another KBA, SNOTE, or document with this scenario please?

     

     

  4. Hi,

    If possible do not change the client and keep client 400 of the productive system. A BW client copy will copy nearly nothing as most of the tables are client independent.

    best regards,

    Janette

  5. Thank you again Janette. We'll keep it as 400 and follow the post copy steps and do the necessary to record the extra steps as needed.

  6. Former Member

    Hello Janette, here we will make a copy of source system for BW QAS  (ie ERP PRD -> ERP QAS), and I think I should apply the C3 scenario. Does this scenario also work for ODP source systems? Thanks 

  7. Former Member

    Janette, another question, if there is a connection between the BWQAS -> ERPQAS, and then a copy of the BW source system is made (example: ERP PRD -> ERP QAS), but the QAS ERP client changes, ie ERP QAS300 → ERP QAS400, it is posible to use the C3 scenario? Thanks.

  8. Hi,

    the steps described in scenario C are for SAPI source system and are not necessary for ODP source systems

    • RSAP_BIW_DISCONNECT not necessary as there is no entry in RSBASIDOC in the sourcesystem
    • RSSM_OLTP_INIT_DELTA_UPDATE only relevant for delta uploads using infopackages

    For ODP source systems ODP queue is relevant and therefore the old 'subscriptions have to be deleted' and new subscriptions have to be created by starting the DTP for example.