SAP R/3 Local Client Copy – choose background scheduling parameters

Schedule the client copy in background: Choose source client (000 in our case), profile name (SAP_ALL in this case), background server to run this job. Click on “immediately” to start the job after clicking “OK”.

Screen to Schedule the SAP R/3 client copy in background

Once you click OK, you will see the following verification dialog. Please verify the target client, profile name and source client and make sure they are what you intended. Also verify the source client user. Click continue.

screen to verify the target client, profile name and source client

In the next information screen, you will see “background job was successfully scheduled; log is displayed in SCC3”

background job was successfully scheduled; log is displayed in SCC3

SAP R/3 Local Client Copy – Test Run

Before we start up the actual run of client copy we can test the client copy with two options.


You can change the profile from SAP_ALL (All Client specific data without Change Docs) to a different profile such as SAP_APPL (Customizing and Application Data without Change Docs), SAP_CUST (customizing), SAP_CUSV (Customizing and user Variants), SAP_UCSV (SAP Customizing user master records and user Variants), SAP_UCUS (customizing and user master records), SAP_USER (User master records and Authorization profiles)


Finally click OK and a “Client Copy Verification Dialog Box” will appear as below. Click on Simulation to start the client copy simulation.

Local-Client-Copy Verification

Resource Check

Click this to check resources are sufficient. Such as disk space etc. All the data to be copied will be counted without being read. Using this we can find database free space availability with amount of data going to be copied. Client copy can be done with Dialogue mode or Back ground mode.
Using Dialogue mode the copy will be configured with Dialogue work process and the screen will be locked.
Using background mode a job will be configured with the start condition and runs with the help of back ground work process can be monitored using SM37 Transaction code.


Data to be copied will be read without saving to database. Using this we can find if any inconsistency there in the data to be copied. Click this to simulate client copy. All data from source client is read but not written to target client.

Client Profile

It is a selection Criteria of the data to be copied from the source to target client. There are some client profiles already created by SAP. We have to use required profile as per the data to be copied from source to target client.


SAP_ALL – All client specific data.
SAP_APPL – Application data.
SAP_USER – User master records with authorization data
SAP_CUST – Customizing data
SAP_EXPC – Customizing with cross client data.

SAP R/3 Local Client Copy – transaction code RZ10

Client Copy

000 is a master client which maintains all the data given by SAP. But it will not allow client independent customization. For this reason of implementing software or customization as a part of post installation a new client will be created and copied from 000 with SAP_ALL profile. We have three types of client copy procedures in R/3 Local client Copy Remote Client copy Client Export / Import

Local client Copy

If a client copy held under the same database between two clients, this is called Local Client Copy. This is recommended as a post installation step.


Set a system message about the client copy information with SM02 Lock all users except administrator in source client. Lock can be given by SU10 transaction code. Because in any client copy the source data should not be edited. Cancel all the released background jobs in the source client. Check all table spaces and add data files if any table filled above 85% Create a client using SCC4 transaction and mention client role. Note: In case you are creating a client in PRD system to maintain production data, do not select the client role as production because client role as Production will not allow any client copies within that.


  • Log on to the target client with user id SAP* and password PASS
  • If unable to login with SAP* (in ECC6) use TCODE RZ10 to create a new Default Parameter login/no_automatic_user_sapstar and set the value to 0.
  • Run the transaction SCCL
  • Select a client profile with source client number

SAP R/3 Client Management – what is client independent, client dependent data

What is an R/3 Client? R/3 Client Definition

R/3 Client is defined as an “independent accountable business unit within an R/3 system”. In technical lingo client is a logical unit of R/3 database.

R/3 Data Classification

Data in the R/3 database are classified as two types, Client Independent data and client dependent data.

Client Independent Data – Cross Client Data

Data which can be accessible through entire R/3 database from any client is called as client independent data or cross client data. Ex: screen data, transaction data, repository data and dictionary data.

Client Dependent Data – Client Specific Data

Data which can be accessible through a client in which it was created is called as client dependent data or client specific data. Ex: user data, authorization data, application data. As per above two types, the R/3 client maintains differentiation with respect to client dependent data. A number of clients are created in one R/3 database to maintain differentiation in customization, testing, quality assurance and production data. R/3 client can be identified with three digit numeric number starts from 000 to 999 Default clients

After installation there are three default clients configured in database. Which are (for Non-Ides Software) 000 Master Client 001 Copy of master client 066 Early watch client For IDES Software we have clients 800, 810, 812

SAP Profiles: Default Profile, Start Profile ans Instance Profile

What are SAP Profiles (SAP Basis System Profiles)

SAP Profiles (System Profiles) contain parameters that specify how to startup an instance and how to setup the various variables that define the way the SAP instances and system work.

SAP Profiles

  • Path: <SAPMNT>\<SID>\SYS\profile\
  • Example:D:\usr\sap\DEV\SYS\profile\
  • Only the Central Instance Host file system contains the SAP profiles for all instances.
  • Dialog/regular instance hosts do not have any profiles stored on them.
  • If you have N instances on a SAP system (sharing the same SID) you will see 2*N+1 SAP profiles files and their corresponding backup files if any in the SYS/profile folder.

Default Profile

Name: DEFAULT.PFL Contains global parameters that apply to all instances in the SAP R/3 SID such as:

rdisp/mshost = CHALAKI
rdisp/sna_gateway = CHALAKI
rdisp/sna_gw_service = sapgw00
rslg/collect_daemon/listen_port = 37
rslg/collect_daemon/talk_port = 13
rdisp/bufrefmode = sendon,exeauto
ms/http_port = 8100
dbs/ora/tnsnames = DEV

Start Profile

SAP Start profile Contains starting parameters for the instance. Each instance will have its own start profile.

Naming Convention: START_<INSTANCE NAME>_<Host Name>


Start_Program_02 = immediate $(DIR_EXECUTABLE)\$(_DB) DEV _MS = msg_server.exe
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\DEV_DVEBMGS00_CHALAKI _DW = disp+work.exe
Start_Program_04 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\DEV_DVEBMGS00_CHALAKI

Instance Profile

SAP Instance profile Contains instance specific profile data. Each instance will have its own start profile. Naming Convention: <SID>_<INSTANCE NAME>_<Host Name> example: DEV_DVEBMGS00_CHALAKI

  • Management of work processes
  • Management of Memory Buffers
  • Ports
  • Db Home etc.
rdisp/wp_no_dia = 5
rdisp/wp_no_btc = 1
rdisp/wp_no_vb = 1
rdisp/wp_no_vb2 = 2
rdisp/wp_no_enq = 1
rdisp/wp_no_spo = 1
DIR_TRANS = D:\usr\sap\trans
icm/server_port_0 = PROT=HTTP, PORT=8000, EXTBIND=1
DIR_ORAHOME = D:\oracle\ora92

You can learn more about SAP Profile from SAP Help website portal.

Copyright 2005-2016 KnowledgeHills. Privacy Policy. Contact .