Client refresh Prod data to QA - NW2004s

[Former Member]

Hi,

In our landscape CRM,BI,XI and EP components . We wanted to do client refresh from Production data to QA .We are using Widows and MSSQL 2005 database.

We have some doubts, since we have go-live date very soon it would be great help if some one can suggest step by step so that we will save time to complte this task

1. What is the procedure to do client refresh ?

2.What is the post configuration steps for client refresh ? like logical system change , and etc

3.Since we are integrated Portal with CRM and BI in QA after refreshing production data to QA ,is that settings will distrub ?

4. Do i need to do client refresh for all the components CRM,BI,XI or only Source system (CRM) is enough ?

5. We have CRM production system client 990 and logical system BAPCLNT990 , QA CRM client 880 and BAQCLNT880 so once i refresh production client to QA , is QA client will be remain 880 or it will replace as production client990 ?

We have seen some of the SDN docs it will not give complete picture , it would be really great help if you give more

- Kristene

[Former Member]

Hi Kevin,

Thankis for your reply.I have one more issue

After refresh database from production to QA, do i need to reapply license for QA system?

What are thye post activities ?

- Kristene

[clas_hortien]

Hi,

yes, you have to install a new license as the hardware key changed.

The post activities are described in note 151603 in section 8, and can be done by the STM tools (SAP Tools for Microsoft SQL Server) mentioned in this section.

Best regards

Clas

[Former Member]

Hi,

Depends on the profile you use as to what will happen or what data config will be copied.

Note 577778 - Postprocessing after client copy for CRM

Note 757093 - FAQ: Analyzing CRM Client Copy problems

Note 793717 - Client copy into the BW client in Netweaver/mySAP ERP

Note 325470 - Activities after client copy in BW source systems

I dont know Xi so cant answer that one.

Client numbers will remain, as will the logical names - you are importing INTO, not replacing 880 with 990.

Make sure all the transports needed are into the production client prior to the copy as config may well be missing when you bring the client back. (ie anything in QAS not in PRD wont be in QAS when you've done the import - depending on the import/export used).