Client Copy – Local, Remote & Import / Export
In SAP administration, client management is a vital task
performed regularly by SAP Basis consultants. One of the core functions of this
is the SAP Client Copy process. Whether you’re a student learning SAP, a
job seeker aiming for a Basis role, or an SAP administrator handling live
systems, understanding how client copy works is essential. This article
provides a complete overview of client copy types: Local, Remote, and
Export/Import, with practical examples, step-by-step descriptions, and
use-case relevance.
SAP 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 -
Local client copy.
Remote client copy.
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.
ClientCopysameSID
Remote Client Copy-This method is used to copy client between different instances(SID).It is
performed by T-code SCC9.
ClientCopyDifferentSID
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 tablespace .
For remote copy, target system must have enough space in the database or tablespace. 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.
Local Client Copy
Local client copy is performed using Tcode 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) Excute 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.
Select Goto from menubar.
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
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 :
Request PKTKO00151
Request PKTKT00151
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.
What is a Client in SAP?
A client in SAP is a self-contained business entity
with its own data, user master records, and settings. It acts like a separate
environment within the same SAP system. Different clients can be used for
development, testing, or production purposes.
Examples:
- Client
100 – Development
- Client
200 – Quality
- Client
300 – Production
What is SAP Client Copy?
SAP Client Copy is the process of copying data from
one client to another within the same system (local), across systems (remote),
or using a transport directory (import/export). It helps in replicating
environments, testing configurations, and maintaining system consistency.
Types of Client Copy in SAP
Local Client Copy
What It Is
Local client copy means copying data between clients within
the same SAP system.
Common Transaction Code: SCCL
Use Cases
- Creating
a test client from the development client
- Creating
a copy for sandbox or training
Steps:
- Login
to target client (new or empty)
- Run
transaction SCCL
- Select
profile (e.g., SAP_ALL, SAP_CUST, SAP_USER)
- Enter
source client and execute
Remote Client Copy
What It Is
Remote client copy involves copying client data from one
SAP system to another over RFC (Remote Function Call).
Common Transaction Code: SCC9
Use Cases
- Copying
data from development system to quality system
- Testing
configurations before go-live
Prerequisites:
- RFC
connection between systems must be established
- Background
jobs must be configured
Steps:
- Login
to target client in the target system
- Run SCC9
- Enter
RFC destination and source client
- Choose
profile and start the copy
Visit for latest Job Vacancies and News indianinQ8.com
Client Export / Import
What It Is
Export/import allows client copy via transport files,
useful when RFC is not possible.
Common Transaction Codes:
- Export:
SCC8
- Import:
STMS (Transport Management System)
Use Cases
- Moving
client between isolated environments
- Backing
up and restoring specific client data
Steps:
Export Side (Source System):
- Run SCC8
to export client using a selected profile
- This
creates transport files in /usr/sap/trans
Import Side (Target System):
- Use STMS
to import the transport requests
- Post-import
steps include executing transaction SCC7 to finalize client import
Benefits of SAP Client Copy
|
Benefit
|
Description
|
|
Environment Replication
|
Quickly clone client settings and data for testing or
training
|
|
Flexible Options
|
Choose between local, remote, or file-based based on
system setup
|
|
Secure Data Movement
|
Maintains consistency while copying data between
environments
|
|
Useful for Upgrade Testing
|
Validate configuration or master data after system upgrade
|
|
Saves Manual Effort
|
Reduces time and errors vs. manually configuring clients
|
Important Tips
- Always
perform a client backup before starting
- Use
correct copy profiles like SAP_ALL (full), SAP_CUST (customizing
only), or SAP_USER (user data only)
- Perform
copy in dialog or background mode based on system load
- Run SCC3
to monitor client copy logs and verify success
- Lock
the client during large operations to avoid user disruptions
Kuwait bus routes and numbers, bus route kuwait CityBus, KPTC, KGL Mowsalat. find Kuwait’s public transport Muscat خط الحافلات الكويت.
Who Should Learn This?
Students
- Helps
understand SAP Basis landscape and real-world administration tasks
Job Seekers
- Frequently
asked in SAP Basis and system admin interviews
- Demonstrates
hands-on knowledge of system management
Employees
- Required
when setting up test environments or refreshing data
- Ensures
secure and error-free data replication
Top 5 FAQs About SAP Client Copy
|
Question
|
Answer
|
|
What is the difference between local and remote copy?
|
Local is within the same system; remote is between two SAP
systems
|
|
What is the safest profile to use for a full client copy?
|
SAP_ALL copies everything including user and configuration
data
|
|
Can client copy be reversed?
|
No direct rollback; always take a backup before initiating
the copy
|
|
How do I monitor client copy progress?
|
Use transaction SCC3 to view logs and status
|
|
What’s the use of SCC7 in client import?
|
Finalizes the import and applies post-copy steps in the
target client
|
SAP client copy, SAP local client copy, remote client copy
SAP, SAP client export import, SCCL SAP, SCC9 SAP, SCC8 SAP, SAP basis client
copy steps, SAP client copy best practices.
.jpg)
No comments: