0% found this document useful (0 votes)
29 views

Client Administration

Uploaded by

Santhosh Menon
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
29 views

Client Administration

Uploaded by

Santhosh Menon
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Client Administration

A client is, in organizational terms, an independent unit in the R/3 System. Each client has its
own data environment and therefore its own master data and transaction data, assigned user
master records and charts of accounts, and specific customizing parameters.

1. Client Overview SCC4


2. Client Creation SCC4
3. Local Client Copy SCCL
4. Remote Client copy SCC9
5. Client Deletion SCC5
6. Client Export SCC8
7. Client Import SCC7

Client Overview (SCC4)

Creation of Client (SCC4)


Execute SCC4 and see the screen below
Click on the change button
Click on “New Entries”
Fill up the tabs as shown below.
Click Save button.
Local Client Copy (SCCL)

Pre-Requisites
1. Make sure you have enough space in PSAP<SID> tablespace to complete the client
copy.
2. Create a client in 3 digit numbers except 000, 001 and 066
3. Check server has enough space to handle client copy before scheduling client copy.
You can check this using tcode DB02.
4. Log in to the new client using SAP* user and password PASS.
5. execute tcode SCCL in SAP command line
6. Select the profile you want to copy to new client, e.g. SAP_ALL
7. Select the source client e.g. 000
8. Select source client master data e.g. 000

9. Now click on schedule as a background job


Click on continue
10. Select the back ground server you want to perform this action, default leave the field
blank.

11. Now click on schedule job


12. Click on “Immediate.”
13. Click the check
14. click Save button.
15. A summary of client copy will be shown in the screen with test run
16. Make sure test mode is not selected at this moment.
17. click on continue

18. now the client copy is scheduled in background

19. Client copy progress can be monitored using tcode SCC3


20. Job can be also seen in SM50

If the client copy fails due to any reason, you can check the log in SCC3.
Once the problem is solved, you can restart the client copy with the same setting in restart
mode.

Remote Client Copy (SCC9)

Remote client copy is performed in rare situations. When the client copy is done between
two different SAP systems, the copy is called remote client copy.
Before remote client copy is performed, an RFC connection must be set between those
systems using SM59.

1. Check RFC connection is working fine between two systems you want to perform
remote client copy using SM59
2. create a client in the target system you want to copy the client
3. login to the target client using user SAP* and password PASS

4. execute tcode SCC9 and select the RFC for the source system
5. select the profile you want to copy like SAP_ALL
6. select the source client number you want to copy
7. Select source client master data, mostly it is the same client number
8. Now click on schedule as a background job.
9. Leave the background server field blank.
10. Click schedule.
11. Select Immediate from the next screen.
12. Save the screen.
13. Client copy is scheduled now as a background job and the client copy process started.
14. The progress can be monitored using tcode SCC3

Client Deletion (SCC5)


Client deletion is performed when the client data is corrupted or client data is no longer
needed to avoid confusion.

1. Don’t delete the client using SCC4 the space occupied by the client can’t be regained
2. login to the client you want to delete
3. run tcode SCC5 in sap command line
4. Tick mark on remove from table T000 to perform a complete removal.
5. Now click on schedule as background job
6. leave the background server blank
7. now click on schedule job
8. click on Immediate
9. click on save
10. Client deletion is started and log can be seen in SCC3

Client Export/Import

A client transport consists of two steps:

First, a client export extracts client data from the source client
to files at the operating system level. Then the data is imported
from the operating system files into the target client.

To perform a client export, follow these steps:

1. Log on to the source client. From the SAP initial screen,


choose transaction SCC8 (Client Export). Select the data to
be copied using a profile.

2. Indicate the target system to which the client will be copied.


The target system must be defined in TMS as part of the
transport domain.

3. Begin the client export. Because copying is a lengthy


process, use scheduled background processing.

Do not run any other client copy tool before the

data export is finished.

This export process will generate up to three data files at the


operating system level:
• RO< number >: this file contains cross-client data
• RT< number >: this file contains client-specific data
• RX< number >: this file contains SAPscript texts
Depending on the type of data selected through the client
transport profile, the client copy command files added to the
the buffer of the target system are as follows:

• <S-SID>KO<number>: this file is for cross-client data


• <S-SID>KT<number>: this file is for client-specific data
• <S-SID>KX<number>: this file is SAPscript texts

The client export change requests are not imported when an


Import all takes place. Therefore, you must import these requests into the target client using
TMS. 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.

After the import process has been completed, post-import activities are required for object
generation steps. After completing the import, log on to the target client. From the SAP
systems initial screen, choose transaction SCC7

Reorganization: Client Deleted. Space still filled up in the Database

Data is deleted from tables when deleting a client. Some databases (for example Oracle and
Informix, but not Adabas D) have the attribute that the space occupied by tables is not
changed when deleting data. The cleared areas within the tables can however be filled with
new data.

soln:

This is the normal behavior of the database and not an error. If new data is stored (creation of
a new client, adding further data to already existing clients), the space of the deleted client is
reused.

If you want to immediately recover the cleared space, you must reorganize the database (or
at least parts of it). There are two reasons for performing reorganization:

 A "large" client with a large amount of data was deleted and this amount of data will
not be added to the system in the foreseeable future.

 After deleting the client, a lot of small areas (individual records) can have been
deleted in the database. These small gaps are not completely recycled. Particularly
after the repeated deletion of clients, the space in the database can be utilized
inefficiently.
Interview Q & A

What is client administration in the SAP system? Why do we use multiple

clients in the SAP system?

A: A client is used in the SAP system for multiple logins on a single instance. You can

create multiple clients on a single instance. It also provides data security as one user with

one client can’t see the data of the other user with another client and also there is no need

to install the software again.

The following are the advantages of client administration in the SAP system:

 Using SAP Clients, the same resources can be shared between multiple users.

 It helps you to manage the SAP system landscape as you can create multiple clients

for DEV, QA, and PROD teams.

 It allows you to share the SAP system with a large number of users.

 We have standard clients in the SAP system.

What are the default clients in the SAP system? How can you create a new client in the
SAP system?

A: The SAP system comes with the following three standard clients:

000 — This is called the master client and is available when you install the R/3 system.

001 — This is a copy of 000 and it comes with a test company. Generally, this client is used
to create new clients.

066 — This is called the SAP Early watch. This is used for diagnostic scans and monitoring
services in the SAP system.

Following are the steps to create a New Client in SAP:

 To create a new client in the SAP system, use the transaction code — SCC4

 To create a new client, enter the following details after clicking on New Entries:
o Client number and name

o City

o Currency, Roles

 Enter your client-specific data and set permission for the clients as per your requirement
and click on save.

From which transaction code you can make system settings modifiable, for example,
namespace modifiable?

A: SE06

How many types of client copies can be done?

A: 3

Which transaction code is used for remote client copy?

A: SCC9

The following condition should be met for remote client copy.

A: SM59 RFC connection should be working between the source and target system.

What are the correct client settings in the Production System?

A: A)No changes allowed


B)No changes to Repository and Customizing
C)Protection level 1:No overwriting

Which table contains a list of all clients?

A: T000

From which transaction code can you create a logical system?

A: SALE.

Which profile is used for

"Client-dependent customizing, copying authorization profiles and deleting SAP


application data but retaining user data"?

A: SAP_CUST.

How many clients are supported technically in an SAP System?


A: 1000.

Which of the following is true for remote client copy?

A.: Data is transferred directly between the source and target client using rfc through a
network connection.

Which transaction codes are used to protect Production Clients against unauthorized
system changes?

A: SE06

SCC4.

Which of the following are repository objects in an AS ABAP-based SAP system?

A: A)Program objects

B)Function group objects

C)Dictionary objects.

Which of these statements regarding clients in ABAP-based SAP Systems are true?

A: Although the system change options (transaction SE06) are set to 'modifiable', you can
restrict changes to repository objects by the client change options (transaction SCC4).

You should not allow the changing of the cross-client customizing within a sandbox client
on the development system.

A: True

Using which transaction code you can delete a client?

A: SCC5.

In which parameter you can set the default client number?

A: login/system_client.

What data is contained in a client?

A: Client-specific customizing, user data, and application data

The data structure of an SAP system consists of:

A: Client-specific data, cross-client customizing, and the Repository


From which transaction code post-processing can be done, after remote client copy?

A: SCC7.

Three transport requests are created during the export/import method of client copy.
Select the correct answer with respective to the description.

A: <sid>KO<No> - For cross client data

You might also like