Process to migrate configuration data from one BW development system to other

[former_member225699]

Hi SAP Gurus,

We need to migrate configuration data from one BW system DE1 to DE2.. Both systems are SAP net weaver  7.3.

DE1 is BW pre-production system and DE2 is BW DEV.

No transactional  data required.

Please share a document if available.

Kindly, let me know the procedure for Remote Client copy or client export/import with steps.

Also let me know the pre-requisite for these activities.

Thanks,

Avadhesh Sharma

+91 8095226536

[Former Member]

Hi,

Remote Client Copy (SCC9)

Remote client copy is performed in rare situation. When the client copy is done

between two different SAP systems, the copy is called remote client copy.

Before remote client copy is performed, a RFC connection must be set between those

systems using SM59.

1. Check RFC connection is working fine between two systems you want to perform

remote client copy using SM59

2. create client in the target system you want to copy the client

3. login to target client using user SAP* and password PASS

4. execute tcode SCC9 and select the RFC for the source system

5. select the profile you want to copy like SAP_ALL

6. select source client number you want to copy

7. Select source client master data , mostly it is the same client number

8. Now click on schedule as background job.

9. Leave the background server field blank.

10. Click schedule.

11. Select Immediate from next screen.

12. Save the screen.

13. Client copy is scheduled now as a background job and client copy process started.

14. The progress can be monitored using tcode SCC3

Client Export/Import

A client transport consists of two steps:

First a client export extracts client data from the source client

to files at the operating system level. Then the data is imported

from the operating system files into the target client.

To perform a client export, follow these steps:

1. Log on to the source client. From the SAP initial screen,

choose transaction SCC8 (Client Export). Select the data to

be copied using a profile.

2. Indicate the target system to which the client will be copied.

The target system must be defined in TMS as part of the

transport domain.

3. Begin the client export. Because copying is a lengthy

process, use scheduled background processing.

Do not run any other client copy tool before the

data export is finished.

This export process will generate up to three data files at the

operating system level:

• RO< number >: this file contains cross-client data

• RT< number >: this file contains client-specific data

• RX< number >: this file contains SAPscript texts

Depending on the type of data selected through the client

transport profile, the client copy command files added to the

buffer of the target system are as follows:

• <S-SID>KO<number>: this file is for cross-client data

• <S-SID>KT<number>: this file is for client-specific data

• <S-SID>KX<number>: this file is SAPscript texts

The client export change requests are not imported when an

Import all takes place. Therefore, you must import these requests into the target client

using TMS. Choose one of the transport requests of the client transport in the Transport

Management System (TMS). The other transport requests belonging to this client

transport are then automatically added in the correct order.

After the import process has completed, post-import activities are required for object

generation steps. After completing the import, log on to the target client. From the SAP

systems initial screen, choose transaction SCC7

Regards,

Chandu