PROJECT 1 Client Admin
PROJECT 1 Client Admin
PROJECT 1 Client Admin
Databases:
1) Oracle 2) SQL server 3) DB2 4) Sybase 5) Informaix
6) MAX DB
End users:
People who are using for productive work for the company are called as end users.
Named users:
People are working for the client (eg: If client is Airtel, the all Airtel employees are called as
named users).
Concurrent Users:
Users who are login in infrequent time (eg: customers of the client)
Client Administration
What is a client?
What does a client contain?
What are Advantages of client concept?
What are the SAP standard clients?
How to create a client?
How to add a logical system ID to be assigned to a client?
How to do local client copy SCCL or copy one client to another in the same R/3 system?
How to do remote client copy or copy one client to another in different R/3 systems?
How to do Client Import/Export?
How to check the size of the client in SAP?
How to delete a client?
How to lock a client ?
How to Define Default Client in SAP ?
What is the main difference between remote client copy and client export/import in SAP?
Client Tasks
As depicted above 100 and 200 clients exist under one roof. We can
create a number of clients in SAP Application (from 000 to 999)
Step 3)
1. Enter basic details as given below.
Step 4) New client will be there in the list. Here we have created client
100.
Procedure:
As we are doing local client copy (SCCL) source and target instance are same but
Clients are different. In the below
Scenario:
Step 1) Create an entry for your new target client using SCC4. In our scenario, we will
create client 202 in DKM system. Log on to this newly created target client (DKM-202)
with user SAP* and default password pass.
Step 2) Excute T-code SCCL.
Step 3)
Enter Description
Step 4) By default Client Copy is executed as a single process. Single process will take a
lot of time.We will distribute workload of single process to parallel(multiple) processes
which will reduce time in copying a client.
1. Select Goto from menubar.
2. Select Parallel Process.Parallel processes are used to exploit the capacity of
database better
Step 5) Always execute long running processes in background mode rather than
foreground/dialog mode. Infact, some processes run more quickly in background.
Step 6) The client copy logs are available in SCC3 . Status Successfully
Completed means client copy is completed.
1 Check the source client size by enters TC-SE38 and run report rstablesize and check
enough space is available on the target system.
2 Lock all the users in the source client.
3 Client copy must be started from the target system, so login into the target system using
sap* and pass
4 Ensure that transport management system is configured and working fine.
5 Minimum two background jobs should be available, otherwise pause all background
jobs by enter TC-SE38 and run RSBTCTRNS1 report. To reschedule all job back into
normal run RSBTCTRNS2 report.
6 RDDIMPDP job should be run in background, otherwise run report RDDNEWPP.
7 TEMP and TRANS directories should be have three times of client size free space.
8 RFC connections should be established between the servers.
In Remote client copy source and target instance will be different
Scenario:Source Instance & client := BD1-101
(The source client is the client who contains the data to be copied)
Step 1) Log on to the target system. Here we will log on to DKM system. Create a new
target client entry(202) using SCC4. Log on to this new target client with user SAP* and
default password pass.Here we will log on to DKM-200 system.
Step 2) Execute Transaction Code SCC9.
Step 4) Select Parallel Process.Parallel processes are used to exploit the capacity of
database better.
Step 6) The client copy logs are available in SCC3 as given below.
Client Import/Export
For large database it is recommended to use client
import/export instead of remote client copy.
Step 3)
Select profile
Step 5) Once the job is executed data files and co-files of profiles
from PKT systems database are transferred to DKM systems
import buffer.Once we will import request in DKM only then it will be
reflected in database of DKM system.
Depending on the chosen export profile there can be up to 3 transport
requests created :
Step 3) Post import phase:Once the import is done, execute SCC7 to perform the post client
import actions,
Here i am writing the procedure to lock amd unlock a client in SAP,very rarely we need
to use it..But stil u should know so follow these simple steps
1) To lock or unlock a client in R/3 System, run the following function modules in
transaction se37
2. SCCR_LOCK_CLIENT ( to lock the client)
3. SCCR_UNLOCK_CLIENT (to unlock the client)
Run these functions with a client input which is to be locked/unlocked. This function set
flag Client is locked temporarily for client copy in client maintenance menu.The client
will be available for users DDIC and SAP*. If any other user tries to login, system gives
message that Client locked temporarily.
To unlock the client
1. Run transaction SE37
2. Enter the function module as SCCR_UNLOCK_CLIENT
3. press F8 or test run (single run).
4. Specify the client and execute(F8).