We have 3 types of client copies

1) Local client copy (SCCL)

2) Remote client copy (SCC9)
3) Client export (SCC7 & SCC8)

What are the prerequisite for SAP Local Client Copy?

Following are the prerequisites for local client copy:
1) Check the source client size: run report RSTABLESIZE for this and check enough space is
available on ur target system.
2) Lock all the users in the source client.(use ewz5)
3) Client copy must be started from the target system, so login into the target system using
sap* and pass.
4) select the profile which u want to copy.
5) Start client copy (local) using SCCL. (Perform test run before starting).
6) Check scc3 for the client copy logs.

1) Local client copy (SCCL)

(LOCAL)- Go to Target client - Client Copy (SCCL)

SCCL - tick on TEST RUN - Schedule as background - background server option - tick on
IMMEDIATELY - tick on NO PRINTER DIALOGE - schedule job -
wizard (RFC Link) - continue - continue - complete .

once again - SCCL for copy.

if coming error for LOCAL CLIENT COPY i.e. FINBTR@......

SAP Profile for CLIENT COPY:

SAP_ALL All Client-Specific Data w/o Change Documents

SAP_APPL Customizing and Application Data w/o Change Docs
SAP_APPX SAP_APPL w/o Authorization Profiles and Roles
SAP_CUST Customizing
SAP_CUSV Customizing and User Variants
SAP_CUSX Customizing w/o Authorization Profiles and Roles
SAP_PROF Only Authorization Profiles and Roles
SAP_RECO Recovery (Only if Source Client = Target Client)
SAP_UCSV Customizing, User Master Records and User Variants
SAP_UCUS Customizing and User Master Records
SAP_UONL User Without Authorization Profiles and Roles
SAP_USER User Master Records and Authorization Profiles

2) Remote client copy (SCC9)

3) Client export (SCC7 & SCC8)

All About Client Copy – Local, Remote,
Import/Export
Client Copy

We can generate a blank client with SCC4.But how to fill the data in the client ?“Answer is the
client copy.”

Client copy means “transferring client specific data” within same instance(SID) or between
different instances(SID).

Client copy can be performed with three different methods -

1. Local client copy.

2. Remote client copy.
3. Client Import/Export.

Below brief details are given about client copy methods.

Local Client Copy :- This method is used to copy client within the same instance (SID).It is done
by T-code SCCL.

 
Remote Client Copy- This method is used to copy client between different instances (SID).It is
performed by T-code SCC9.

Client Import/Export:- This method is used to copy client between different instances(SID).It is

performed by T-code SCC8

 =====

Client Copy Pre-steps

To avoid data inconsistencies there are few pre-steps to be performed before starting client

copy:-

1) Disconnect and lock business users (SU10).You can end the session of active users in the
system through SM04. Once all users are logged out, check that no cancelled or pending
update requests exists in the system.
 2) Suspend all background jobs

 Execute SE38 as given below.

 Fill program name with “BTCTRNS1″ as above figure.

  Press Execute.
3)  For a local copy, system must have enough space in the database or table space.

For remote copy, target system must have enough space in the database or table space. Check
space using Tx DB02.

4) To avoid inconsistencies during client copy users should not be allowed to work in source
client.

5) rdisp/max_wprun_time parameter should be changed to 2000 second as a SAP

recommendation. Although you use parallel processes and schedule job in background, dialog
processes will be used.

Please always follow the suspend /start the jobs before you stop/start SAP.
 
BTCTRNS1 : temporarily suspends all the released jobs in SAP.
 
BTCTRNS2 : It will release all the jobs which are suspended by the earlier report.

Local Client Copy

Local client copy is performed using T-code SCCL.

Scenario:-

 Source Instance & client := DKM-000

 Target Instance & client := DKM-202

Step 1) Create an entry for your new target client using SCC4 . In our scenario, we will create
client 202 in DKM system. Log on to this newly created target client (DKM-202) with user SAP*
and default password pass.

Step 2) Execute T-code SCCL.

Step 3)

 Select your desired profile

 Enter Source client.
 Enter Description

Step 4) By default Client Copy is executed as a single process. Single process will take a lot of
time. We will distribute workload of single process to parallel (multiple) processes which will
reduce time in copying a client.

1. Select Goto from menubar.
2. Select Parallel Process. Parallel processes are used to exploit the capacity of database better

Step 5) Always execute long running processes in background mode rather than
foreground/dialog mode. Infact, some processes run more quickly in background.

 
Step 6) The client copy logs are available in SCC3 . Status – “Successfully Completed” means
client copy is completed.

Remote Client Copy:-

This technique uses Remote function call. You can view RFC from SM59. This technique
depends on the network ,so network connectivity must be strong enough.

Scenario:-

Source Instance & client := BD1-101

Target Instance & client := DKM-202

Step 1) Log on to the target system. Here we will log on to DKM system. Create a new target
client entry (202) using SCC4. Log on to this new target client with user SAP* and default
password “pass“. Here we will log on to DKM-200 system.

Step 2) Execute Transaction Code SCC9.

Step 3) Fill the basic details as per your requirement.

Step 4) Select Parallel Process. Parallel processes are used to exploit the capacity of database
better.

Step 5) Schedule the client copy in background

Step 6) The client copy logs are available in SCC3 as given below.

Client Import/Export

For large database it is recommended to use client import/export instead of remote client
copy.

Scenario:-

Source Instance & client := PKT-300

Target Instance & client := DKM-202
This technique always starts with client export step.

Note:- You must have enough space in the /usr/sap/trans_SID file system to perform the client
export.

How to export client?

Step 1) Log on to the target system (DKM). Create an entry for your new target client
using SCC4 .Log on to the source system / source client (PKT).

Step 2) Before you import a Client you need to export. Export is nothing but transferring data
files and co-files from source system’s database to target system’s import buffer. Execute T-
code SCC8.
 Step 3) 

 Select profile
 Choose target system.

Step 4) Schedule the export in background

Step 5) Once the job is executed data files and co-files of profiles from PKT system’s database
are transferred to DKM system’s import buffer. Once we will import request in DKM only then
it will be reflected in database of DKM system.

Depending on the chosen export profile there can be up to 3 transport requests created :

 Request PKTKO00151 will hold the cross client data,

 Request  PKTKT00151 will hold the client dependent data,
 Request  PKTKX00151 will also hold some client dependent data.
How to import the client? 

Step 1) Log on to the newly created target client(DKM-202) using SAP* and password pass.

Step 2) Start the STMS_IMPORT transaction

As shown below, import queue will open

Step 2) Select the transport requests generated by client export .Import theses transport
requests on the target client.

The transport requests should be imported in the following sequence :

1. Request PKTKO00151
2. Request  PKTKT00151
3. Request  PKTKX00151

The system automatically detects these are client export transport requests and automatically
performs the import of the 3 requests.
The import logs can be seen in STMS_IMPORT.

Step 3) Post import phase:- 

Once the import is done, execute SCC7  to perform the post client import actions,

Schedule the post import job in background.

Step 4) Import log will be available in SCC3. Client is successfully  imported.

You might like

Prerequisite of Client Import & Export :

Hi Keat,
 
: Can we assume and say that our whole production client data along with configurations,
workflow, etc etc will   be exported?
 
-- Depending upon the selection of profile, if you select SAP_ALL then YES.
 
: And would there be any limitations with client export import?
 
-- There are certain prerequisites you are suppose to follow before you start the procedure and
once it over follow the Post-processing activity.
 
Prerequisites are below :
 
- Make sure Source and Target systems are running on same support pack level.
 
- Check for table space in target system.
 
- Ensure TMS setup is OK and there is sufficient space in TRANS directory.
 
- Lock all dialog users.
 
- Ensure no BTCs running.
 
- There should be no DB lock and no update errors.
 
Please make sure to perform "Repository consistency check" during Client transport using "RFC
System Check" option in SCC8 , this will detect if any inconsistency is there.
 
Regards,
SUJIT
Hi

Follow the steps as below,

 
Client Export:
-

1. Before export, check the space in /usr/sap/trans

2. Client export using SCC8 and execute in background.
3. If you are exporting SAP_ALL profile, you will get 2 transport requests with
<SID>KT<number>  & <SID>KX<number>
4. Note down the TP requests.
5. Check the job status in SCC3
6. Once the client export is finished, move the data to the target systems /usr/sap/trans   co-
files and data-files
 
Client Import:
-

1. Before starting the import check whether there is sufficient space to hold the new data at
table space level. If needed, extend the table spaces.
2. Add the 2 TP requests to the target systems import Queue via STMS
3. Start importing any one request the other will automatically imported.
4. Check the job status in SCC3
5. Once the import is finished, execute the post processing using SCC7
6. Post process user master records, if you don’t need Production system user IDs....
 
You need to take care of the following things during the activity,
 
1. Check the free space at /usr/sap/trans directory both in source and target system.
2. Check enough table space is available in the target system.
3. Use parallel processing during export and import if your H/W supports - This will speed up
the process.
 
Best regards,
Vinodh.
Client Export : (LIVE Example)
New since Release 4.5: Import by TMS (see below)

Client export:

Up to 3 requests are created, depending on the data selected and available:

1. "DPPKO00003" for transporting cross-client data, if you have selected this

2. "DPPKT00003" for transporting client-specific data
3. "DPPKX00003" for transporting client-specific texts, provided texts are available in this client

When the transport requests have been created successfully, the data is exported asynchronously by
starting the transport program tp at operating system level, and can take several hours, depending on
the data volume. The status of the export can be found using either Transaction SCC3 or Transaction
SE01 and specifying the transport request.

Wait until the data has been successfully exported before you start another client copy or transport
involving the source client.

Client import:

Choose one of the above-named requests to import, in the Transport Management System (transaction
STMS) import overview. Its other transport requests are then selected automatically.

You must post-process with the transaction SCC7 after the import.

When you call the transaction SCC7 in the target system an analysis procedure first determines the
associated transport request and displays its ID "DPPKT00003" with the parameters of this export.
Verify that the correct transport request was selected for import.
If the transport requests are not yet in the import queue in the target system, use the following
commands:

./tp pf=TPPARAM addtobuffer <commfile name> <target sys id> u18

Example:

cd /usr/sap/trans/bin

./tp pf=TPPARAM addtobuffer "DPPKT00003" P11 u18

You can also still import the transport requests directly with the tp.
Do so in the sequence "DPPKO00003", "DPPKT00003", "DPPKX00003".

Example:

./tp pf=TPPARAM import "DPPKT00003" P11 client005 u18

---
Client Import : (LIVE Example)
1. data file & co file paste into Target System (Quality System) from Source System
(Production system)
2. Add : Request into Target System (Quality System)

"DPPKT00003" for transporting client-specific data

"DPPKX00003" for transporting client-specific texts, provided texts are available in this
client

3. Select the Request number “DPPKT00003” & Import request.

4. fdfsf

5. After finish the import request it will show green right tick mark.
6. Then give the t-code SCC7.
7. Scheduled the job in “Background Job”

8. Select the background server & immediately.

9. sfsdsf
10. sfdsf
========