Client Administration

What is a client ?
A client is, by definition, an organizationally and technically self-contained unit
within an SAP system. While all clients in the system access the same repository
objects (programs, tables, and so on; in other words, cross-client data). the Customizing
settings and system master data are largely client-specific.

Client administration, which involves the following tasks:

➔ Creating, changing, and deleting clients
➔ Copying clients within a system
➔ Copying clients across systems

Creating Clients – SCC4

• A client is identified within a system by a unique three-digit code.
• Avoid using letters or special characters when you create new clients because
this limits the functionality of the client to a considerable degree (in relation to
transport management and certain application modules, for example).
• Three clients are reserved in every SAP standard system delivered
: 000. 001, and 066.
These clients are not intended for live operation.
• Before you fill a system with Customizing settings or data,
create a new client (usually client 100).

A new client is normally created using the following two steps:

1. Create a new entry in the client table.
2. Execute a client copy.

You therefore begin by maintaining the client table:

1. Enter Transaction "SCC4" in the command field , and press the I Enter I key
2. The client table is then displayed. Click on DISPLAY <·> CHANGE .
3. In the dialog box that opens, click on CONTINUE .

4. Click the NEW ENTRIES button.

5. Complete the fields in the detailed view for new clients as follows:
• Under CLIENT, enter a client number (for example, 100), and a name (for
example, Customizing client).
• Enter the location name under CITY (for example, New York).
• Under STD CURRENCY, enter a default currency for the client (for example,
USD).
• In the CLIENT ROLE field, select an entry from the drop-down list (for
example, Customizing).
• Select the relevant option from the drop-down list under CROSS-CLIENT
OBJECT CHANGES .
• Select the relevant option from the drop-down list under PROTECTION:
CLIENT COPIER AND COMPARISON TOOL
• If you want to enable the execution of CATT and eCATT runs, select the
ECATT AND CATT OPTION UNDER CATT AND ECATT
RESTRICTIONS.
Finally. click on SAVE .
6. A message appears in the status bar to confirm that the client has been created.
Click on BACK .
7. The client you just created is now also listed in the table.
 • The client is now ready to be used as the target client in a client copy.
• The new client contains no Customizing, master, or application data.
• You therefore need to fill the client with data using a client copy.
• In addition, the new client does not contain any user master records.
• The first time you log on to the client, you therefore use the user SAP* and the
default password "pass".

The SAP* User in New Clients

• The user SAP* and default password pass represent generally recognized logon data,
and this user account also has unrestricted authorizations.
• You should therefore create an actual SAP* user and change the password as soon as
possible.
• Access by this user is only possible if the login/no_automatic_user_sapstar profile
parameter has the value "0".
• As soon as you've created your new client and fin ished the client copy, check whether
the passwords for all system IDs are secure in the new client.

Copying Clients
• You use the client copy function to copy or transport client-specific Customizing
settings or data from a source client into a target client.
• The client copy function doesn't copy any cross·client objects such as ABAP
programs or table structures.
• You can use copy profiles to determine the scope of the data copy, which means
that you don't need to copy all of the data in a client.
• The target client may be in the same or another system.

➢ A copy within the same system is known as a local client copy.

➢ Cross-system copies can be executed either as a remote copy
(using an RFC connection)
➢ or as a client transport using the TMS.

It may take several hours to copy a client because the datasets may be very large in
some cases. You may need up to one day to copy a large client.
For the duration of the copy following must be followed:
• Lock user’s - all users should be locked and
• Suspend Jobs - the scheduling of all background jobs canceled;
otherwise, data inconsistencies may occur in the target client.
• Sufficient Memory :
Note also that the new client requires additional memory in the database.
Make sure that you have sufficient memory in reserve because the client copy is
otherwise very likely to terminate.

Information About Client Copies

• For more information about tools you can use for client copies
refer to SAP Notes 24853 and 552711.
Local Client Copy - SCCL

You perform a client copy to copy a client within the same system.
This is the fastest way to copy a client.

1. To log on to your newly created client, use the SAP* user ID and the password
"pass".

Log On to the Correct Client

It is essential to ensure that you are logged on to the correct target client. Otherwise,
you may unintentionally destroy another client.

2. Enter Transaction "SCCL'' in the command field, and press the I Ent er I

3. On the CLIENT COPY - COPY A CLIENT screen , open the input help
for the SELECTED PROFILE field.

4. Select a copy profile (FOR EXAMPLE, SAP ALL).

The profile determines the type and scope of the data to be copied
(see the DESCRIPTION column). Click on CHOOSE.

5. Enter the number of the source client (for example, "001 ") in the SOURCE CLIENT
field.
You may also need to enter a value in the SOURCE CLIENT USER MASTERS
field, depending on the copy profile selected.
You can specify two different source clients for the data.
 Click the SCHEDULE AS BACKGROUND JOB BUTTON.

6. Click the SCHEDULE JOB button.

7. Enter a start time for the job. The job is scheduled the same way as any other
background process. Choose SAVE
8. The copy options are then displayed.
The activated contents result from the copy profile selected in step 4.
Check the settings. and click on CONTINUE.

9. Scheduling of the copy job is confirmed in a dialog box, which you can close
by choosing CONTINUE

The client copy is executed in the background.

You can monitor the job using Transaction SM37
or
analyze the log in Transaction SCC3 (Client Copy Log)

Local Client Copies Using Transport Requests

A special variant of the local client copy is available with Transaction SCC1 (Client Copy
by Transport Request): With this variant, only the objects included in a specific transport
request are copied from a client into the local target client (in the same system).

This function is useful, for example, in development systems that have a client reserved
exclusively for development, and a separate client for developer testing. Often, the
creation of test cases is not possible in the development client, which means that Customizing
settings must be tested with data in another environment. With Transaction
SCC1, it isn't necessary to transfer every transport request to the test system; an initial
test can be performed in the development system.
Remote Copy – SCC9
• If you want to copy a client into another system (with a different system 10),
perform a remote client copy.
• The RFC interface of the systems involved is used for the remote copy.
• To prepare for the copy. you must therefore create a new client and use
Transaction SM59 to set up an RFC connection to the source system

To do this, follow these steps:

1. Log on to the target system and client.

log On to the Correct Client
Make sure you are logged on to the correct target client . Otherwise, you may unintentionally
destroy another client.

2. Enter Transaction SCC9 in the command field, and press the I En t er I key
On the CLIENT COPY - COPY A CI.IENT SCREEN, open the input help for
the SELECTED PROFILE field.

3. Select a copy profile (FOR EXAMPLE. SAP ALL).

The profile determines the type and scope of the data to be copied.
Click on CHOOSE.
4. Enter the RFC connection to the source system in the SOURCE DESTINATION
field.
The SYSTEM NAME and SOURCE CLIENT fields are filled automatically using
the settings of the RFC connection.
Click the SCHEDULE AS BACKGROUND JOB BUTTON.

5. Click the SCHEDULE JOB button.

6. Enter a start time for the job. The job is scheduled the same way as any other
background process. Choose SAVE
7. The copy options are then displayed.
Check the settings, and click on CONTINUE.

Scheduling of the copy job is confirmed in a dialog box, which you can close by
choosing CONTINUE
When you perform a remote copy, the data are transferred by RFC connection.
This places a corresponding load on the network.
On the other hand, the performance of the copy depends on the dimensions of your
network infrastructure.

Client Copies within a System

Although a remote copy will also work within a system, it is recommended that you use
a local client copy for this purpose instead.

Client Transport – SCC8

The second option for copying a client across systems is a client transport.

This comprises three steps:

1. Client export
2. Client import
3. Import postprocessing

• The client export generates transport files, which are then imported into another
system using the TMS.
• After the import, a postprocessing job must also be run to adapt the copied data
to the new system.
• The client export also allows you to save a client, for example, by burning the
generated files to a CD or using another external storage medium.

To perform the client export, follow these steps:

1. Log on to the source client.

2. Enter Transaction "SCC8" in the command field, and press the I Enter I key
3. On the CLIENT EXPORT screen, open the input help for the SELECTED
PROFILE field.

4. Select a copy profile (for example, SAP ALL). The profile determines the type
and scope of the data to be copied. Click on CHOOSE.
5. Enter the system into which you want the export file to be imported later in the
TARGET SYSTEM field. You may only select selected that are part of the transport
landscape. Click the SCHEDULE AS BACKGROUND JOB button.
~

Selecting the Target System

You can also enter the name of the system in which you are currently logged on as the
target system. You can subsequently import the relevant transport files into a system
other than the system specified here.

6. Click the SCHEDULE JOB button.

7. Enter a start time for the job. The job is scheduled the same way as any other
background process.
Choose SAVE

8. The copy options are then displayed. Check the settings and click on
CONTINUE.

9. The transport request files created by the export are displayed in a dialog box.

Take note of the file names, and choose CONTINUE

[!]
Scheduling of the copy job is confirmed in a dialog box, which you can close by
choosing CONTINUE
Three fi les are generated by the client export:
➢ <SID>KO<number>: Cross-client data
➢ <SID>KT<number>: Client-specific data
➢ <SID>KX<number>: Texts and forms
These files are saved to your system's transport directory
(<drive>:\usr\sap\trans or lust/sap/trans).
To save the client or transfer it to a system outside of your transport
landscape, you can copy these files and archive them or insert them into the
transport directory of the remote system.
If you specify a system within your transport landscape as the target system for
the client export, the transport requests are displayed in the system's transport
queue after the export is completed. You can then import the transport requests.
To do this, select the requests, and click on IMPORT REQUESTS (~).

log On to the Correct Client

Make sure you are logged on to the correct target client. Otherwise, you may unintentionally
destroy another client.

Now you only need to specify the target client, before starting the transport with
the START IMPORT button.
The client data are then imported into the new client via the transport system. Wait
until the import is completed, and then execute import postprocessing:
1. Log on to the target system and client.
2. Enter Transaction "SCC7" in the command field, and press the I Enter I key
3. Click the SCHEDULE AS BACKGROUND JOB button.
Selecting the Target System
You can also enter the name of the system in which you are currently logged on as the
target system. You can subsequently import the relevant transport files into a system
other than the system specified here.

4. Click the SCHEDULE JOB button.

5. Enter a start time for the job. The job is scheduled the same way as any other
background process .Choose the SAVE button

6. The copy options are then displayed.

Check the settings, and click on CONTINUE.
Scheduling of the copy job is confirmed in a dialog box, which you can close by
choosing CONTINUE

The client transport essentially produces the same result as a remote client copy.
How·ever, whereas the remote copy is significantly faster because it allows for a "live"
data copy, the client export option offers the advantage of being network-independent In
addition, the transport requests generated during the export can be used more than
once, for example, for several remote systems, or as backup files.
Deleting Clients – SCC5
• You can delete clients in Transaction SCC5 (Delete Client).
• If you choose to do so, all client-specific data are deleted from the database.
• To delete a client, it's not enough to merely remove the corresponding entry from
the client table (Transaction SCC4).

To delete a client, you should follow these steps:

1. Log on to the client you want to delete.

log On to the Correct Client

Make sure you are logged on to the correct target client. Otherwise, you may unintentionally
destroy another client.

2. Enter Transaction "SCC5" in the command field , and press the I Enter I key
3. On the DELETE CLIENT screen, activate the DELETE ENTRY FROM T000
Checkbox if you want to delete the table entry from Transaction SCC4 at the same
time as your deletion of the client.
Click on the DELETE IN BACKGROUND button.

4. Click the SCHEDULE JOB button.

5. Enter a start time for the job. The job is scheduled the same way as any other
background process. Choose the SAVE button
6. The copy options are then displayed.
Check the settings. and click on CONTINUE.

Scheduling of the copy job is confirmed in a dialog box, which you can close by
choosing CONTINUE
Following deletion, all client data are permanently lost.
You should therefore only execute this action if you're certain that you no longer
need the client.
If necessary, create a backup copy of the client beforehand using a client export, or
create a full backup of the entire database.

Checking the Client Copy Log – SCC3

You can check the client log to determine the progress and results of the operations
just described:
1. Enter Transaction "SCC3'' in the command field. and press the I Enter! key
2. Use the buttons in the title bar. for example. to display a cross-client view (ALL
CLIENTS button) or to switch to the client exports (EXPORTS button).
3. The detailed view provides additional information. such as the time at which an
error occurred. Double-click on a log entry. or click on CHOOSE to display
the details.

The display works in all clients, which means you don't need to be logged on to
the correct client. If an operation has not yet been completed, it is displayed with
the status EXECUTING. Choose the REFRESH button to refresh the display.