Contents 1. SAP Architecture 2. SAP Instances 3. SAP Active Servers (SM51) 4. Work process overview (SM50) 5.

Transaction Lock/Unlock (SM01) 6. Users overview/Active users (SM04, AL08) 7. System log (SM21) 8. ABAP Dump (ST22) 9. Database Size / Table space space check (DB02, BRTOOLS) 10. BRTOOLS 11. Client Administration 12. Logical System Creation (SALE) 13. User management (SU01, SUIM,EWZ5, PFCG, SU53,SU24,SU25,SU10) 14. System Profiles (RZ10, RZ11) 15. RFC Destinations setting (SM59) 16. Operation mode Configuration (RZ04, SM63, RZ03) 17. Logon Load balancing (SMLG) 18. Transport Management System (STMS) 19. Spool Administration (SPAD, SP01) 20. Kernel Upgrade 21. Applying Patches using (SPAM, SAINT) 22. Backup and Recovery (DB12) 23. SAP DBA Calendar (DB13) 24. Lock management (SM12) 25. Update Administration 26. CCMS Alert Monitoring (RZ20/RZ21) 27. Trouble Shooting 28. Start and Stop SAP 29. Daily System Check 30. WebAS 31. SAP Net weaver 32. BW Administration 33. Portal User Administration (SSO) 34. ECC fundamentals. 35. Q & A.

1. SAP Architecture

User/Client

Application Layer SD, MM, PP, FI/CO, HR, PS, PM etc. applications are configured here.

BASIS Layer/Middle Layer User Authorization, System Monitoring, Application Tuning, Backup/Recovery, Trouble Shooting etc.

OS Layer OS, CPU, Memory, Database, Hardware etc.

Explanation: When any user tries to access the application like SD, MM, PP, FI/CO, they first touch the application layer which contains the required data and configuration. In order to access the Application, the user has to be authorized, which is done at Middle layer. Similarly if there is an issue for server like at OS, at Database or at Hardware level, then Middle layer people have to identify and direct it to the corresponding responsible person to look at the issue. Because these Middle layer people sit in the middle and look to both sides and trouble shoot the problem at Application level and OS level as per the issue, these people are called BASIS Administrators.

2. SAP Instances SAP instance defines a group of resources such as memory, work processes and so on, usually in support of a single application server or database server within a client/server environment. Application servers share the same memory areas and are controlled by the same dispatcher process. There are 3 types of Instances available in SAP system as defined below. 1. Central Instance (Unique Instance or SID name for a SAP Server) 2. Database Instance (Which contains data with its own SID) 3. Dialog Instance (Used for Load balancing purpose when needed) SAP SID: 3 Alphanumeric Characters except some reserved ones. SID may look like ECP, SCP, BIP like this. System number: System number is the number which differentiates between multiple instances in a single host. System nr varies from 00 -99 (75 and 99 are reserved for TCP/IP use)

Work processes There are different types of work process on which SAP Instance depends to run as described below
Dialog Work process(D) :- Used by frontend users or frontend process every dispatcher requires at least two dialog work processes Backgorund Work process (B) : Used for long running Jobs .At least two for each R/3 system (more than one allowed for each dispatcher) Enqueue Work process (E) :Used for Locking /Unlocking purposes only one enqueue work process is needed for each system Update work process (V1) : Used for critical updates into Database at least one for each R/3 System (more than one allowed for each dispatcher) Update workprocess (V2): Used for normal updates after critical updates Gateway work process (G) : allows communication between R/3, R/2 and external application systems. Spool work process (S) : Used for Printing from SAP at least one process Message Service (M): Used for messaging purpose. The message server (MS or M) communicates between the distributed dispatchers within the R/3 System and is therefore the prerequisite for scalability using several parallelprocessing Application servers.

4. SAP Active Servers (SM51) Execute tcode SM51 at sap command line. It shows the active servers available for the Central Instance if there. See the fig below.

There are five Active Servers in above figure. 5. Work process overview (SM50)

The following are the points we observe from SM50 a. No of each work processes like (Dialog, Background, Enqueue, Update, spool ) b. What is the processes id for each work process c. Work process status, running or waiting d. IF any error is there , reported in Err field e. The field CPU show how much CPU time is consumed by the particular work process f. Time: It shows how long the work process is running g. Report: Which report is running currently by that work process h. Client: Specifies the client no for which this process is busy i. User: Specifies which user is running this report. j. Action: What exactly going on during this process k. Table: Which table is accessed during this process The point to concentrate from SM50 is Process Status, time, client and user. If Basis wants to cancel one running Work process then, select the work process by clicking on left check box as selected below Now Go to Process -> Cancel Without Core.

Click on Yes to terminate the process. Now you can see that process is in waiting status. Click on Refresh button to get the updated status.

6. Users overview/Active users (SM04, AL08) SM04: This tcode is used to check the status of users i.e how many users have been logged in, how many sessions a user is working. See the fig below.

From the above figure you can see, the users have logged in into client 300. Check the detail of each line. Take the example of user ALEXANDERA, this user has logged into client 300, from system achamma, executing tcode MIGO, time of login 11:40:28, 5 sessions. Two know more about session , select the user or line and double click on it.

Now if you want to delete one session, select /click on the specific line and click on End Session.

Click Click on

button to come out from the window. button to get most up to date data.

Active Users: Al08 Al08: To know how many users are active in all servers.

7. System log (SM21) To know /to investigate the problems in SAP system, Basis Admin checks the system logs to check the possible errors and the cause of the error. Any system related task are recorded into system logs and can be viewed and analyzed later to trouble shoot the problem. The figure below shows how to select the errors and warnings.

8. ABAP Dump (ST22) When users are working they face some kind of time out problem and any kind of problem for which their work gets terminated. That termination is reported in an area called ABAP dumps. Using ST22, Basis can analyze the errors. ST22 show the today and yesterday all the time. To get more dumps from previous days, you can select the date range.

Database Size / Table space space check (DB02)

Using the tcode DB02, Basis checks the database detail like database size, table space size, free space statistics, no of tables, table space growth, data files associated with tables and lot more. See the Fig shown below which shows over all database detail. To get more updated data, click on refresh button. Remember refreshing this take several mins.

Each time you refresh this screen, look for if any space critical objects are shown in space-critical objects field. Click on Current Sizes to check the tablespace size, utilization , free space available and associated datafiles as shown in Fig below.

To know the associated datafiles: select the tablespace and click on Goto Tablespaces DBA Datafiles button from the menu shortcut above. See the below Fig for datafile information.

To know about tablespace history like now much data load into which tablespace on daily, weekly, Monthly basis, click on tablespace history from the menu bar. Check below Fig for detail of history.

Now from tablespace utilization screen, If tablespace utilization is above 90% , then we have to add datafiles to the specific tablespace to bring it below 90% and will try to keep below 80%. One can only view the tablespace utilization and how many datafiles associated with the tablespace but cant add datafiles. 11. 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 2. Client Creation 3. Local Client Copy 4. Remote Client copy 5. Client Deletion 6. Client Export 7. Client Import Client Overview (SCC4)

SCC4 SCC4 SCCL SCC9 SCC5 SCC8 SCC7

Creation of Client (SCC4) Execute SCC4 and see the screen above. Click on 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 PSAPECP tablespace to complete the client copy. 2. Create a client in 3 digit number 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. Login 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 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 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 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 same setting in restart mode. Remote Client Copy (SCC9) Remote client copy is performed in rare situation. When the client copy is done between two different SAP systems, the copy is called remote client copy.

Before remote client copy is performed, a 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 client in the target system you want to copy the client 3. login to 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 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 background job. 9. Leave the background server field blank. 10. Click schedule. 11. Select Immediate from next screen. 12. Save the screen. 13. Client copy is scheduled now as a background job and 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. Dont delete the client using SCC4 the space occupied by the client cant 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

Administrative Database Operations (DB24) We use this transaction to display the backup logs to get first hand information whether the backup or archives have been completed successfully/ Failed or are in progress.

Oracle Lock monitor (DB01) This tcode is used to check the locks in Oracle.