Proper way to delete a SAP client!!!

Proper way to delete a SAP client

Here goes:

1. log into the client to delete
2. go into SCC5 and delete client
3. log into another client and delete entry with SCC4
4. reorg database to recover database space.

Actually, 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 XXX, you have to create a command file "delXXX" with following entries

Clientremove
Client = XXX
Select *

Place the command file in /usr/sap/trans/bin

$ cd /usr/sap/trans/bin

$ R3trans –w -u 1

e.g $ R3trans -w del200.log -u 1 delXXX

To check the progress...

$ tail -f delXXX


Reorg the database post client delete

Changing the SAPGUI Logo on the Right Hand Side

Steps to change the default SAP IMAGE on the right hand column of the screen :-

Transaction code - SMW0
X - Binary data for WebRFC application
Hit Enter
Click Execute
Click Settings -> Maintain MIME types
Click the Create button
Fill in :- TYPE : image/gif EXTENSION : .GIF
Click Save
Click Back to the Binary data for WebRFC
Click Create
Fill in :- Obj. name : ZXXXX.GIF Description :
Company Logo
Click Import and specify the filename where your
GIF file is
located.File type is BIN. Finish press the
Transfer button.
If successful, your logo will be shown in the
Binary data for
WebRFC.
Transaction code SM30 - Table/View - SSM_CUST
Click Maintain
Click New Entries
Name Value to be set
START_IMAGE ZXXXX.GIF
RESIZE_IMAGE NO
Logoff and Login again

Step by Step Procedure to copy a Client to the Remote SAP Server.

Step by Step Procedure to copy a Client to the Remote SAP Server.

•Logon to destination SAP server
•Use Transaction Code SCC4
•Go to change mode
•Create a new client, assign client number & description as per request
•Logoff from current client.
•Login to newly created client in destination SAP server using the following credentials :

i. Client Number : Newly created one
ii. User Id : SAP*
iii. Password : PASS



•Use Transaction Code SM59 to create a RFC Connection for client copy if does not exist already.
•RFC Connection should have Target Server as Destination and the test results should say “Connection test OK”
•Use SCC9 Transaction code to go to client copy screen.
•Give profile as per the request.
•Select RFC destination created for the purpose for the source client to client copy
•Use Transaction code SCC3 for monitoring the progress of client copy
___________________________________________________________________

Golden rules for CLIENT Copies

1. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data.

2. Application data (transactional and master) should not be copied without copying configuration data.

3. Client copy requires a valid client as the destination client. Make sure that the client exists in T000 table and you can logon to that client.

4. The transport system and the transport management system of 4.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance.

5. When you copy a client from one system to another, client-independent tables should only be copied if they are not yet modified in the target system.

6. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place.

7. Always check the database space before performing a client copy.

8. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system.

9. RSCLICHK program should be run in the target system remotely before doing a client export. This program will give information about the missing definitions from the data dictionary in the target. After executing this program and getting successful results you can ensure that the client copy will have no problems. In case some tables are different; you can use SE11 to compare and adjust the table structure in both the system before the client copy. A remote test client copy also can be executed to know the differences between source client and target client.

10. If you are not in release 2.2 then do not use R3trans to copy a client.

Add information to your logon screen

Follow these steps to add information to your logon screen:
1. Run tcode --> SE61
2. In the data element field --> ZLOGIN_SCREEN_INFO
3. Document Class --> Select General Text
4. Click create
5. Prag format --> Standard

@6K@ 000 SAP Standard Client
@ 100 Sanbox Client
@GS@ 200 Training & Quality Client
@4A@ 300 Customizing Client

6. To locate the icon code: tcode BIBS --> Element --> Icon Overview


You may also output icons at the beginning of lines by using an icon code (for example, @1D@ for the STOP icon). You can get a list of icon codes from Report RSTXICON. Pay attention to the codes with two '@' symbols displayed by the report. You cannot include text symbols. The 'include indicator' cannot be used for this function. SUBHINT here. These can be used on system messages as well.