SAP Library - Find your answers

Copy users from DEV to PRD

1. Login to the client in your DEV system from where you want to copy.

2. Execute scc8. Select the profile sap_user.
Specify the target system.
Click on 'schedule as background job'.

3. Specify the background server name i.e. the server name where your DEV system is available.

4. Click on 'schedule job' button.
Verify the things and click on 'continue' button.

5. You will have options to specify the start time.
Specify to suit your convenience.
You can see the log in scc3.

6. Login to the destination client and execute scc6.
Specify the request number which was created during scc8.
You need to specify only one request number. Other(s) will be taken automatically.
Click on 'Prepare import'.

Copy a Client into a Stand Alone System

How to copy a client into a stand alone system?

The scenario is I have a 2 system landscape. I want to copy an existing client from DEV to a standalone system for some demo purposes.

There is an option for Client TRANSPORT which will help you perhaps:

A client transport differs from a remote client copy in that it does not use RFC. Like a remote client copy, however, a client transport is used to copy data between different R/3 Systems.

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. Second, the data is imported from the operating systemfiles into the target client.

To perform a client export, proceed as follows:

Log on to the source client. From the R/3 initial screen, choose:

*Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) *Client Transport*(r) *Client Export*. Select the data to be copied using a profile.

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.)

Begin the client export. As copying is a lengthy process, use scheduled background processing. The client export performed in the source system , exports the client data asynchronously bycalling the transport program tp at the operating system level. This export process will generate up to

3 data files at operating system level:

. RT<>; this file contains client-specific data

. RO<>; this file contains Cross-client data

. RX<>; 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

KO; this file is for cross-client data

KT; this file is for client-specific data

KX; this file is also for client-specific data

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. You must import the data in the following order: first cross-client data, then client- specific data.

After the import process has completed, post-import activities are required possible for object generation steps. After completing the import, log on to the target client. From the R/3 initial screen, choose:
*Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) *Client Transport *(r) *ImportEditing*

To display client transport logs, use the Transport Organizer.During client transport, a Repository consistency check can be performed by clicking the RFC system check button in Transaction SCC8. If inconsistencies are detected, a list of the ABAP Dictionary tables definitions missing in the target system is generated. This will help your recognize in advance formal problems that may occur during the import of the source data.

If you want to exclude a table x from copying in client copy run report RSCCEXPT
Goto transaction SA38 , enter the report name and execute. You will see the output screen as

Before doing a client copy, you need to prepare the following :-

1. Find the source client space with the client size custom program which can be implemented using the rel. note:
Find the space of the client - '0118823'. This will give you the size of the source client.

2. If your are on Unix OS, adjust all the file systems according to PRD file system to fit the PRD client in DEV
client based on space requirements also.

3. You can do the client copy by remote or export/import client.
Remote method is not preferred if you are doing a large client copy.
Do a client export/import.

4. To speed up the export/import, use R3trans export/import for the clustered tables.
Please find the rel. notes related to performance improvements for cluster tables in OSS.

5. Do import and post processing.
Note: Export may take 10 to 20 hr. for 50gb of data
import may take 4 days and post import will take 8 to 15 hr. for 50gb of data. And it all depends on
your system performance.

Please refer OSS rel. notes for the few RZ10 parameters which needs to be set for cluster tables to speed up the process.

Note :-

If it is a fresh installation, do this --

1. SCC4 --> Create client no. and fill other details.
2. Logon to the newly created client with SAP* and PASS as password.
3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client .
4. Preferably do a test run initially to check if it can go well.
5. As a care check space in databases.

What are step and procedure to create a client & to take a client copy from source to target.

By: Kavitha.G

If you are copying from same system then flow the below steps:

1. Create the client in Tcode scc4.
2. Before that create a logical System in BD54.
3. Login in the newly created client with
user Name : sap* and password : pass
4. Use the Tcode sccl to copy the client.if you are not familiar with the client copy. Try a test run and then schedule it in background.
5. You can select the needed profile.
6. To view the log files use the tcode scc3.

If you are using different system then create a rfc connection in sm59.test the connection and then continue from the 1st step
You can also import and export a client. Use scc7 for importing from the client and scc8 fro exporting from the source client

What is system refresh when and why it is done?

The system refersh is nothing but the deletion of the client and replacing the data from other client. For example : you have clients 100, 200 and 300. Suppose when you want to refresh the client 100 you remove the client 100 and replace it with 200 0r 300 as per your reqiurement. Mostly the refresh of clients will be happen at the time of development stage.

System Refresh is a simplified term to Client Copy. Client Copy means copying the production client on to the quality to test the real data. As recommend by SAP this need to carried out every 3 months.

The process to carry out the same is as follows:
1. Create a client on quality system using txn scc4
2. Create a RFC between Production system and Quality System (need to create on quality system)
3. Login to the newly created client using sap* and pass as a password
4. Txn sccl to start the client copy. You can test the client copy by selecting the test run option. (test run will estimate the time taken for the activity).

Export them via SCC9, copy profile SAP_USER. This profile copies both roles and user
accounts. Once exported, use STMS to import the transports into the development server.

Use profile SAP_UONL while client copy.

1. Login to the client in your DEV system from where you want to copy.
2. Execute scc8. Select the profile sap_user.
Specify the target system.
Click on 'schedule as background job'.
3. Specify the background server name i.e. the server name where your DEV system is available.
4. Click on 'schedule job' button.
Verify the things and click on 'continue' button.
5. You will have options to specify the start time.
Specify to suit your convenience.
You can see the log in scc3.
6. Login to the destination client and execute scc6.
Specify the request number which was created during scc8.
You need to specify only one request number. Other(s) will be taken automatically.
Click on 'Prepare import'.
7. Specify the target client and click on 'Import'.
Log can be checked in scc3.

If you want to exclude a table x from copying in client copy run report RSCCEXPT
Goto transaction SA38 , enter the report name and execute.

RSCCEXPT - Client Copy Expert Settings

NOTE : Please go through the following note before performing any changes 446485, 557132.

Keyword: BASIS
Title : Client Copy / System refresh