Delete SAP client

1. Log into the client to delete
2. Go into SCC5 and delete client
3. Log into another client and delete the Client entry in SCC4
4. Reorg database to recover database space.

If you check "on" the little "Delete Entry from T000" checkbox, you can skip step 3.

One other way of deleting a client which could give significant performance gain and save time is at OS level using - R3trans

To delete a client 130, you have to create a command file "del130" with following entries

Clientremove
Client = 130
Select *
Place the command file in /usr/sap/trans/bin
$ cd /usr/sap/trans/bin
$ R3trans –w -u 1
e.g $ R3trans -w del130.log -u 1 del130
To check the progress...
$ tail -f del130

Reorg the database after deleting the client.

What is a SAP client?

OK, we have the concept of a SAP instance, and that instance has a database which contains thousands of tables which contain a whole bunch of rows. After SAP is installed, these tables need to have some base data in order for customization and configuration to begin. Like state abbreviations, country codes, HR titles, etc.

SAP provides a subset of this data so that the Basis team can get in the new instance, add themselves a user ID in client 000 – “our” client - and start the real work. We don’t want to mess this subset of data up so we need to populate it to a “work” place for the Functional Team to do their work. Or several work places.

The base SAP instance comes with two clients: 000 and 066. Forget client 066, it is used by SAP when you get close to GoLive and you want an EarlyWatch report. This is optional and I believe a fee is involved for this service.

All the base or subset data is contained in client 000. Also, client 000 is where the Basis Team does a lot of its maintenance like patching. The Basis Team people are the only implementation members who will ever have access to client 000. You can think of client 000 as the owner of all the client independent data in the SAP instance. Explanation in a minute.

So, in order to let the Functional Team do their own thing without screwing anything up, we create a new client for them. Think of a client as a view of the database. If you log into client 000, you can see all client independent data – like the ABAP programs – and all the data that is dependent on client 000 only. If you log into client 100, you see all client independent data – like the ABAP programs – and all the data that is dependent on client 100. You can’t see the data that is dependent on client 110 while you are logged on to client 100.

Thus the concept of client dependent and client independent data. All rows in some tables are accessible from any client like T000, the Data Dictionary tables, tables that contain the ABAP programs, printers, etc. These are said to be client independent. Data like users, companies, vendors, customers, etc. are client dependent. You have to go into a specific client in order to see this data.

How To Lock SAP Client

1. How to lock the client from logon
2. How to see the all the users connected per day (with the activities they have done and resource utilization)

I cannot answer the first straight away, but the second questions, there are many available SAP transactions.

use STAT very useful and many options available if you use them correctly.

1. I don't know how how to lock the client, but you can lock the system with "tp locksys " and unlock it with "tp unlocksys ". You can also stop the service, but then noone can login including yourself. However, I had problems with tp locksys when applying some Hot Packages and exporting client. It wouldn't work with system locked. I didn't try, but a simple ABAP that locks and unlocks all the users in table usr02 (with exceptions of yourself, SAP*, DDIC... - ofcourse) might be an interesting idea.

2. STAT transaction

You can lock the system thro "tp locksys" (Transport Utility).
Check the other options of "tp" command for locking the specific client under the system thro "tp help".

With this solution I can lock the whole system, but not specified by client.
Send me in more detail....

There's no way to lock a client.
You have to lock all users from loging in of this specified client.
The way you do is by user administration setting the lock.

We can lock a client using SCCR_LOCK_CLIENT and unlock SCCR_UNLOCK_CLIENT functions.

Once we run this functions with a client as input , that client will be locked/unlocked. Actually this function set flag '' Client is locked temporarly for client copy" in client maintanance menu. And the client will be available for users other than DDIC and SAP*. If you try to login in that client as any user , system gives message that ' Client locked temporarly'..

Is there any t-code to lock a client?

There is no direct tcode to lock a client. the easiest way to lock a client is
1. run tcode SE37
2. type function module name - SCCR_LOCK_CLIENT
3. enter the Client No.
4. execute the function module.