Professional Documents
Culture Documents
Clientadmin PDF
Clientadmin PDF
It is advisable to change the standard password of the above users for security reasons since these
users are the superusers.
Since you should not work in the standard clients (except for administrative purposes), you need
to create a copy of the clients.
The most time is required for physically copying the data because all the client-specific data in
the SAP system has to be copied. When application data is copied in production systems this can
entail a few 100MB and therefore take several hours. When only customizing data is copied, only
up to 150 MB is involved and consequently copying only requires a few hours, depending on the
hardware and system load.
Authorizations
Possible damage resulting from incorrect copying of the client to the target makes it necessary to
possess the following authorizations for the copying process:
S_TABU_CLI allows table maintenance in all clients
S_TABU_DIS allows maintenance of the contents of table CCCFLOW
For copying user master records and user profiles the appropriate authorizations for maintaining
user master records and profiles are required:
S_USER_PRO for the user profile
S_USER_GRP for the user master records
For starters, you can create a copy of client 000. You can also copy clients within the same R/3
system or from other systems
A client is copied in two steps. The first step defines the client in the R/3 system and the second
step fills the client with the data. And only after that the client becomes functional.
When you define a client a role is assigned to it. This role expresses the purposes of the client.
The possible attributes are : Production, Testing, Customizing, Demonstration, Training /
Education and SAP Reference.
Among the basic attributes of a client are the change options of its data and objects
Using the change options attribute the correction and transport system can be stopped in the
clients (No Transport Allowed). This option deactivates the CTS in the client.
For clients in which customizing is performed all changes must be recorded in case they are
transported into other systems (Automatic Recording of Changes). Otherwise Customizing
Organizer will not be activated automatically when a setting is made (Changes Without
Automatic Recording). Such a configuration is suitable for demonstration or training clients.
What you will get is the overview of the clients available in the system.
Click on the change icon to change the display mode.
For example we have created a client 900 which is a copy of client 800.
Click on the New Entries button on the application toolbar to define the client
Figure 1.1
2
3
4
5
6
Figure 1.2
7
You will get the screen as above. (since the entire client definition screen could fit into one screen
shot, two screen shots are used).
When a client is defined, no data is available in the client. By default user SAP* with password
PASS is assigned to it. You need this user to log on to the client in order to copy data from other
clients into it.
Client Copy :
You do a client copy to fill data into the new client. A client can be filled with data in various
ways :
1. You can do a Local Copy where you copy the data into the new client from a client within
the same system
2. You can do a Remote Copy where you copy the data into the new client from a remote system
3. Data can also be filled into the new client from another system by way of transport request
(Client Transport)
To do a client copy into the new client, first login into the new client as SAP* with password
PASS.
Follow the path Tools Administration Administration Client Admin. Client Copy
Local Copy / Remote Copy
Alternatively, you can also use the transaction code SCCL
1
2
3
4
1. These are data profiles that R/3 provides for copying clients. These basically indicate
what kind of data from the source you want to copy into the new client. The scope of the
profile can be seen from the path Profile Display Profile.
2. Specify the source client.
3. Specify source client user masters
4. Use the Test Run option to first test run the execution of the entire procedure. The results
of the test run include an estimate of the data volume to be moved. This helps in
resolving any problems, like for example, problems due to insufficient disk space before
the actual copy run
After specifying the above settings, click on the Execute button or the Execute in Background
button
Depending on the volume of data to copied and the system configuration, this process may take
several hours.
You can also view the copy procedure log. Goto Tools Administration Administration
Client Admin . Copy Logs
Alternatively you can also use transaction code SCC3
After the client copy is over, a log of the copy process is displayed.
A client can only be copied from one R/3 system to another R/3 system if both the R/3 systems are
of the same release.
Before the actual copy, test the RFC connection using the RFC system check button on the
application toolbar. In addition to testing the connection, the R/3 system releases are also checked
Click the Execute button to start the process of copying.
Transaction Code
Menu Path
SCCL
SCC9
Administration
System administration
Administration Client admin. Client copy
Remote copy
Administration System administration
Administration Client admin. Special functions
Copy transport request
Client import
postprocessing
SCC7
Deleting a client
SCC5
Copying logs
SCC3
Administration
System administration
Administration Client admin. Client transport
Client import postprocessing
Administration
System administration
Administration Client admin. Special functions
Delete client
Administration
System administration
Administration Client admin. Copy logs
Client maintenance
SCC4
Client export
Copying
Clients SCCL
within an SAP R/3
System
Copying
Clients SCC9
between 2 Systems
Administration
Administration
maintenance
System administration