You are on page 1of 10

Client Administration

Client is a business entity or customer, all the business transactions will be done with the help of client.
Note Without a client we cannot login to the system.
Client ranges from 000 to 999. Except 000,001,066 we can create client range upto 999.
where 000,001,066 are standard clients.In which 000 is called as golden client, 001 is called as copy of
golden client and 066 is known as early watch client.
000 contains both client specific and cross client data.
To create Client :
Go to scc4 - It shows the existing clients with the details) - click on change - click on new entries and
specify the client no,city,std currency,and client role and save.
Note:when we create client there wont be any data to get the data login to the client and login with usr
sap* and pass and export pfl sap_user.
Delete client :
Go to scc4 - click on change option- sel the client and click on delete to delete the client

Procedure
1. Log on to the client to be deleted.
2. Choose Administration System administration Administration Client admin. Special Functions
Delete Client.
3. You can also specify whether you want to delete the client from the client administration (T000).
4. Setup the parallel process parameters.
5. Start the deletion.
6. In most databases, space which has become free is only available after a reorganization.

Client Copy

Client Copy Data Types


The client copy can copy the following components of the source client into the target client:
User master data: User master data is only deleted in the target system if a profile with user master
data is copied. Authorization profiles and roles belong to customizing and are therefore always copied
with it. Copying users without authorization profiles is problematic. The copy profile SAP_USER
therefore contains additional authorization profiles and roles.
Customizing: All profiles except SAP_USER contain customizing. Customizing data is generally in
tables with delivery classes C, G, E and S.
Cross-client customizing: Choose a profile with this data type for example when you want to create a
test system which is analogous to the production system, and no system copy is to be made.
Inconsistencies can arise in the target system after transporting cross-client tables. Cross-client
customizing can only be used to create a new system because existing clients can be corrupted by
changes in their context.

Scenario 1: You have just installed the target system. The first step in setting up a client is to import a
client from another system. Since there are no other clients in the system yet, you can also copy the
cross-client customizing settings to ensure that they remain consistent, including those pointing to
cross-client objects.
Scenario 2: You have setup clients in the target system whose data must be retained. Cross-client data
must not be imported into the system. This data would overwrite the existing data, and the customizing
of the other clients in the target system would no longer be consistent. Only the data in the new client
would be consistent. This is why you should not transport cross-client data. The data in the other clients
of the target system is then still usable, and only the new client needs some postprocessing to reconcile
the client-specific Customizing data copied with the cross-client Customizing data of the target system.
Master/transaction (application) data: select this option, for example, if you want to set up a test system
from the production client.
Application data depends on customizing data, so it can only exist consistently together with it.
Application data is therefore always deleted from the target client, exception for copies with
SAP_USER. Application data is generally in tables with delivery class A.
The amount of data and thus the memory required and copy time for productive clients can be
considerable. In this case you should not copy application data, you should create the required test
data e.g. with CATTs (Computer Aided Test Tool).

Displaying Copy Logs


Procedure
1.

Choose Administration System administration Administration Client admin. Copy Logs.

The system displays a list of all client copies in which the logon client was the target client. You can go
to the overviews of the copies in other clients, the Copies from Transport Request" (SCC1) and the
client exports from the system.

1.

When you select a copy, you get a log summary with the following information:
Copy type
Profile
Status
User
Tables where copy problems occurred
Statistical info

Double-click on highlighted entries for further information.


1. For further details of the run, choose Details. You get a selection list in which you can get
information about the copied tables (e.g. runtime and number of entries copied) and the exit programs
from other application components used.
2. If you had tables with copy problems in a local or remote client copy, you can recopy them with
the Recopy Errors function.
3. You can display the original log in the file system with the File Log pushbutton. You can also
display the export and import logs of the main transport request (KT).

TWO TYPES OF CLIENT COPIES :


Local client copy : done between the 2 clients with in the same system.
When client is created it dont have any data.so we need to login with usr sap* and pwd pass and copy
the use sap_usr to create the usr.Because sap_usr is a usr master record..
To do client copy first create a client and login with sap* and pass
In tgt system gve the tran sccl.
Gve the dtls selected pfl,description and in source client (from which client u want to copy).
Sel test run.
Sel the options whether u want to run it in "schedule back ground" or "start immediately".
(If u want to start immediately sel "test run".If u want to schedule background uncheck test run)
After that it verifies the dtls which we have gvn right or not.
Click on resource check.
To view the process(client logs) from scc3.
If we schedule client copy in background it will ask for the background server(Instance name) and
select immediately,no print dialog and click on schedule job.
Remote client copy :
Remote client copy will be done between 2 sap systems with same patch level and version which are in
the landscape.
We need to build RFC connection between 2 systems.
To build RFC connection login to tgt client login with sap* and pass pwd and execute sm59 to build
RFC connection.
After creating RFC connection.Execute scc9 transaction in tgt client and gve the dtls selected
pfl,description,in source destination gve the RFC connection.
Remote client copy is not used to copy repository objects.
To lock a client :
Go to scc4 and under restrictions tab option "locked due to client copy".

Client Deletion :
scc5 is used to delete the client.

Procedure
1.Log on to the client to be deleted.
2.Choose Administration System administration Administration Client admin. Special Functions
Delete Client.

3.You can also specify whether you want to delete the client from the client administration (T000).
4.Setup the parallel process parameters.
5.Start the deletion.
6.In most databases, space which has become free is only available after a reorganization.

Transporting Clients Between Systems


The client copier can copy a client into another system, which can be on a different platform. You can
change the client number.
You are no longer required to transport clients before you can copy them between systems. You can
make a remote copy instead. You may still want to use the transport tool for the following reasons:
There is no LAN connection.
The data is to be buffered.
So the transport functionality is still supported.
All languages in the source system are transported according to the settings of the transport tool. All
languages are selected by default.
Codepage conversions are performed automatically, as far as technically possible.

Procedure
A client transport comprises three steps
1. Client export (SCC8)
1. Choose Administration System administration Administration Client admin. Client transport Client
export.
2. Select a copy profile.
Up to three transport requests are created, depending on the selected copy profile and the existing
data. The transport request for texts is e.g. only created if the source client contains customer texts.

Transport

Description

KO

cross-client data

KT

client-specific data

KX

texts and forms

The data export is performed automatically asynchronously. The output of the export includes the
names of the transport requests that are to be imported.
The data export is asynchronous and still runs if SCC8 has already finished. Do not run any other client

copy tool before the data export is finished. You can check the status of the export with the transaction
SE01. Display the logs for the request KT.
2. Import transport requests into the target client (STMS)
Choose one of the transport requests of the client transport in the Transport Management System
(TMS). The other transport requests belonging to this client transport are then automatically added in
the correct order.
Import these transport requests into the target client.
3. client import postprocessing (SCC7)
You need to perform postprocessing activities to adapt the runtime environment to the current state of
the data.
Choose Administration System administration Administration Client admin. Client transport Import
editing.
Client import postprocessing is always necessary and must be performed in the target client after the
import of the transport requests.
It may be technically possible to start the transaction SCC7 in the source client, but you should not do
so because it may cause data loss. You should protect the source client from overwriting by the client
copy tools by choosing protection level 1 in transaction SCC4.
Do not use the same client as the source for several copies or client transports at the same time.
Ensure that the data export has finished before another client copy or client transport, by examining the
export log of the transport request.
SCC1 :
To transport the client objects with transport request.

Difference between sccl and scc1 :


sccl only profiles will be copied between 2 clients with in the same system.
scc1 copy done with in the same system between 2 clients with transport request.
Client Export and Import :
The client export and import is done between 2 systems which are not connected.
STMS configuration needs to be there.
User like sap* can not perforem client copy.
To do client copy login with usr like ddic and 000 client.
In the source system execute scc8 (Export)
It asks for the profile,description and Target system id.
Click on start immediately.

It will show the details what ever the detais that yo u have gvn.
Click on continue.
It will create requests depend upon the profile selected.
It will generate the files in usr/sap/trans/cofiles(K) and data(R) directory
After that we need to go the import system and copy the Export system files (data and cofiles) in the
Import system cofiles and data directory.
After that we need to login to the import system and execute stms_import - click on import
overview(truck).
Here the files which ae generated in Export system are displayed in Import system under requests.
Select the request and clcik on import.
Scc7 is the post installation activity.

Copying Clients between Systems

Prerequisite
The same product is installed, with the same release, in both systems.
All components in these systems, including add-ons, have the same development status.
If you experience problems copying from another system, see the SAP note 557132.

Procedure
1. Choose Administration System Administration Administration Client Admin. Client Copy Remote
Copy.
2. Select a copy profile.
3. Enter the RFC destination.
4. Make an RFC system comparison if necessary.
5. Setup the parallel process parameters.
6. Start the Copy.
The client copier can copy a client into another system. The systems can be on different platforms. You
can change the client number.
When you copy a client from one system to another, the data is transferred directly via the RFC
interface - there is no intermediate storage on hard disk.
Codepage conversions are performed automatically, as far as technically possible.
Do not use the same client as the source for several copies or client transports at the same time.

Copying Clients Within a System Copy Profile


You can use copy profiles that make it easier for you to select and combine the components you want

to copy. SAP delivers the following copy profiles in the table below. The customizing and application
data is deleted in the target client before copying for all profiles except SAP_USER. This is technically
unavoidable.
Copy profile overview (general)
Copy

Description

profile
SAP_U

Users, user roles and authorization profiles are

SER

copied. The client is not reset.

SAP_U

User without authorization profile and role

ONL
SAP_P

Only authorization profile and roles

ROF
SAP_C

Client-specific customizing including authorization

UST

profile is copied. The application data is deleted,


the user data is retained.

SAP_C

SAP_CUST with variants

USV
SAP_U

SAP_CUST with user master data

CUS
SAP_U

SAP_UCUS with variants

CSV
SAP_A

All client data except change documents (see note

LL

180949) and local data is copied.

SAP_A

SAP_ALL without user master data

PPL
SAP_A

SAP_ALL without authorization profile and roles

APX

Additional copy profiles for client transports (SSC8 with cross-client customizing)
Copy

Description

profile
SAP_EX

SAP_UCSV with cross-client

BC

customizing

SAP_EX

SAP_ALL with cross-client

PA

customizing

SAP_EX

SAP_CUSV with cross-client

PC

customizing

Additional copy profiles for remote copies (SCC9)


Since Basis Release 6.10, the following profiles exist. They correspond to the SAP_EX profiles. These
profiles are only available in systems with no protected clients. You can see the existing clients and
their settings with the transaction SCC4.
Copy

Description

profil
e
SAP

SAP_UCSV with

_RM

cross-client

BC

customizing

SAP

SAP_ALL with cross-

_RM

client customizing

PA
SAP

SAP_CUSV with

_RM

cross-client

PC

customizing

Special profiles (SCC8 & SCC9 only)


S This profile is
A only for
P recovering an
_

accidentally

R deleted client
E (see note
C 31496). It
O contains local
tables of
delivery classes
L and W and the
change
documents, as
well as
SAP_ALL.

Copying Clients Within a System


Procedure :

Copying Clients Within the Same System


1. Choose Administration System administration Administration Client admin. Client Copy Local
Copy.
2. Select a copy profile.
3. Enter the source client.
If you are copying users with other data, you can select a separate source client for the user. The
authorization profiles are still copied with the customizing.
If the selected profile and source client are to be your standard values, choose Profile Save Profile
Instance.
4. Setup the parallel process parameters.
5. Start the Copy.
Improving client copy performance: Excluding data
You can improve the performance of the client copy by, for example, by excluding tables or packages,
with Edit Expert Settings.
You can exclude tables from the client copy, for example if they are not relevant for the target client, in
the Tables tab. For further information about excluding tables from the client copy, choose the Help
button in the expert settings.
For further information about expert settings in the client copy, see the SAP note 446485.

Comparing Cross-System Users, Authorizations, Roles, and Profiles


(RSUSR050)
You can use this procedure to compare two user master records, roles (including composite roles),
profiles, or authorizations in the same system or different systems in the User Information System. You
define the name of the RFC destination with transaction SM59.
When comparing composite roles, you receive as the result a list of the single roles and then below
this, a comparison of the authorization objects.
This example describes how you can compare two users (the procedure is the same for roles, profiles,
or authorizations). The master records are resolved to authorization field level and compared.

Procedure
1. Start the user information system (transaction SUIM).
2. Expand the Comparisons node.
3. Choose the Execute function in the From Users line.
4. In the User A and User B fields, enter the names of the users to be compared.
5. To compare users in different systems, choose the Across Systems button.

To compare a user of the current system with a user from another system, enter the user name
for user A and the RFC destination and the user name for user B. You can use the input help to select
from the available RFC destinations.

To compare a user from another system A with a user from a further system B from the current system,
enter the RFC destinations of these systems in the fields RFC Destination for System A and RFC Destination for
System B.

6. Choose Execute.
The system displays the Comparisons screen, on which a comparison of the two users is displayed.
This is divided into same values, different objects, same values, and different values. In the case of
different objects, only the user for which an authorization object is displayed has the object. Different
values means that although both users have authorizations for the same object, the values are
different. Same values means that both the authorization object and the authorization values of the two
users match.
To display documentation for an authorization object, select the object and choose
Documentation.
To display a sorted comparison of the values by authorization fields, select the relevant line and
choose Select.