Sap basis administrator user guide

Covered :
SAP BASIS Administration and Tuning

1. 1













SAP BASIS Self Document

1) General & Basic Concept in SAP -------------------------2
2) Client Maintenance -------------------------------------------9
3) User Administration ------------------------------------------11
4) Background Process ------------------------------------------16
5) Spool Management -------------------------------------------19
6) Oracle Database ----------------------------------------------20
7) SAP Transport Management System(TSM ) ------------- 25
8) SAP Memory Management ---------------------------------28
9) SAP Security Tables & Report ------------------------------31
10) Monitoring ---------------------------------------------------33
11) Performance-Related Transactions -----------------------43
12) Upgrade the UNIX Kernel ---------------------------------48
13) Support & Packages -----------------------------------------49
14) Utilities- DPMON -----------------------------------------50

2. 2

General & Basic Concept in SAP
1) What is SAP
2) Installation
3) Landscape
4) SAP Work Process
5) SAP Important Directories
6) Start & stop SAP (Using Manual & MMC)
1. What is R/3 and what is basis version?
SAP Basis:
- Provides the runtime environment for all SAP applications
- Optimally embeds the application in the system environment
- Defines a stable architecture framework for system enhancements
- Contains the tools for administering the entire system
- Allows the distribution of resources and system components
- Provides interfaces for decentralized system parts and external products.
An R/3 instance is a group of R/3 services that are started and stopped as a unit (by an
R/3 dispatcher) and have a common instance profile. The name of an R/3 instance is
composed of letters standing for the relevant services, and an instance number which
is unique for each computer.
The services may be D, V, E, B, M, G, or S, which respectively stand for dialogue,
update, enqueue, background, message, gateway, and spool services.
2. What are SAP NETWEAVER, SAP XI, SAP BIW, SAP WAS and SAP BI. What is
difference between these?
SAPNW - Net weaver is a web based technology includes java, based on your
installation choices during software installation. It includes BI/XI/EP and different
level of its configuration.
BI: It is an OLAP (on line analytical processing), which provides a plate form to
collect the data and user extract the data from BI or BW (older version) to analyze it
EP: Enterprise portal provides web based secure access to all the application, services
and information. you can log in to EP using host name: port#/ <service name> and
user name and password
SAP -XI: Exchange Infrastructure is used to establish a cross system connections
between system by different vendors and versions
Web AS: Web Application Server is the platform for ABAP and J2EE stacks in
Netweaver.
3. What is SAP & BASIS
System Application and Product for Data Processing (SAP)
Business Application Software Integrated System(BASIS)
4. Explain Landscape and which LS is Good for SAP environment
Single System ( All in same Server)
Two System ( DEV/QA and PRD)
Three System ( DEV,QA,PRD)
5. Explain about Layer
Presentation Layer ( SAP Client)
Application Layer (Application Servers & Central Database)
Database Layer (DB,Work Process)
6. What Homogeneous SAP System & Heterogeneous SAP System , Give Example
Homogeneous is where all the servers within the SAP cluster are running he same OS
– more specifically , the dB servers and Application servers are running the flavor of
UNIX or WINDOWS NT
Heterogeneous SAP System is conversely …..
7. How to installation sap ecc 6.0
Installing Hardware
Network connections to Systems
Operating System Installation
Database Installation
Partition as per SAP Recommendation
R/3 Installation & Setup
8. Installation Checks

3. 3

9.
10. Check Assistance
UNIX Operating system security and performance
Disk layout
Mirroring
UNIX backup
Network layout
Workload
Security
Dedicated host for R/3
Dedicated file or print servers
Technically Correct Installation: database Requirements
Database version
Database name
Directory names
Mirrored redo log files
Disk layout
R/3 Installation & Setup
R/3 Basis Parameters - UNIX kernel and swap space
Check list OS dependencies
Check tool memlimits
R/3 memory management
Check tool sappfpar
R/3 profile parameters
Transaction RZ10
To check the UNIX kernel parameters relevant for R/3 and the swap space, you
should refer to the check list OS dependencies. You can also use the R/3 tool
/usr/sap/<SID>/SYS/exe/run/memlimits.
This tool checks the following parameters:
Maximum heap size (maximum data segment per process)
Maximum mapped file size
Maximum protectable size
Maximum address space per process
Total available swap space
To check the minimal requirements for the R/3 memory management, run
/usr/sap/<SID>/SYS/exe/run/sappfpar check

4. 4

pf=/usr/sap/<SID>/sys/profile/<instance_profile>. This is a very useful tool,
especially if problems occur during R/3 System startup.
To check R/3 parameters in general, use transaction RZ10, select the profile to be
checked, and choose Check.
Checking the Installation: Further Steps

Once the installation is complete, the administrator must back up the following:
The root file system, which includes the system structure and all configuration files,
such as:
File system size
Logical volume manager configuration
Database configuration data
The RDBMS file systems
i. The initial backup can also include the data file systems.
The database
i. This can be performed with the R/3 CCMS and backup
tools, such as SAPDBA, BRBACKUP, and BRARCHIVE.
External backup tools can also be used if they support the
interface BACKINT.
The following R/3 directories:
i. /usr/sap/<SID>
ii. /<sapmnt>/<SID>
iii. /usr/sap/trans
A backup cycle should also be defined for the various file systems. Since the file
system data does not change very quickly, the backup cycles can be longer than for
the database.
Important Directories
The directory \orant is required on each server with a database client. The
environment variable
ORACLE_HOME points to this directory.
The operating system user <SID>adm requires the following environment
variables:
ORACLE_SID = <SID> (on the database server site)
ORACLE_HOME = \orant on both the database client and server site
SAPDATA_HOME = \oracle\<SID>
SAPDATA<n> = \oracle\<SID>\sapdata<n> for sapdata<n>
11. Explain about SAP Work Process
Dialog - ( Default 300sec , should have at least 2 dialog Work process )
Receives requests from user and passes them to the corresponding work
processes.
Only one dispatcher per application server
Balances the workload between the processes
Buffer management in main memory
Connection with the presentation level
Organization of the communication processes

5. 5

Responsible for the interactive tasks of the R/3 system
Dialog work processes execute only one dialog step at a time and are
immediately freed for the next user request
Constantly switching between users
Reasons for Background Processing Reducing load on dialog work
processes
R/3 WP indicates
 Dw_instance – Unix
 Disp+work - Winows


Update – ( at least one V1 & V2 process R/3 System )
Responsible for making database changes requested by dialog and background
processes
For better performance, this process should be on the database server
Time-critical processes are inside V1 and less critical ones within V2
Error situations in
V1 : changes rolled back and V2 components not executed
V2 : only changes of V2 components rolled back
Enqueue - Exactly 1 process R/3 System
Responsible for the lock management system
Synchronizes database access for the multiple application servers and work
processes
Only one enqueue process per R/3 system to ensure data integrity
Background – at least 2 process R/3 System
Responsible for executing ABAP programs submitted for background execution
Batch jobs schedule the sequence of program execution
Used for running long and time consuming programs
Spool - ( Number of spool processes cannot be changed )
Responsible for formatting the data for printing and passing it to the host spool
system
Only one spool work process allowed per server
Message
Used by different application servers to exchange data and internal messages
Routes messages, such as update or batch job starts, between application servers
One message server per R/3 System
Gateway – ( Transport data information )
Allows communication between R/3, R/2, and external applications
Exchanges large amounts of information between application servers
Gateway can reside on any of the connected systems
SAP Work Process details:
Service No of WP per R/3 System No ‘of WP per R/3 Instance
Message server 1 0 or 1
Enqueue 1 0 or 1
Dialog >=2 >=2
Update(V1/V2) >=1 >=0
Batch >=1 >=0
Spool >=1 R/3 Release 3.1 -> 0 or 1
R/3 Release 4.0 >= 0
Gateway >=1 1

12. How to checks WP & status
SM50
Runing,Waiting,Hold,Killed
13. Different between V1 & V2 Update work process.
Critical & non Critical
14. How to find the Server status & what are they.
Using SM51
Initial,Starting,Active,Passive,Shutdown,Stop
15. Startup Logs and Traces

6. 6


16. MMC(Microsoft Management Console)

17. How many default SAP profile and explain more
SAP_ALL, SAP_APPL, SAP_CUST, SAP_CUSV, SAP_UCSV, SAP_UCUS,
SAP_USR
18. Stopping SAP
Stop R/3 Stopsap r3
Stop DB & all stopsap all & stopsap
Sapdba – shutdown the Database

7. 7




19. SAP Transaction Codes ( Batch details)

/n Skip to the next record if you are processing one batch
input session
/o Generate a session list
/bend Cancel a batch input foreground process
/nend Close all R/3 sessions and logoff
/nxxxx Call transaction xxxx in the same session
/oxxxx Call transaction xxxx in an additional session
/i Delete the current session
/h Turn debug mode on
/$tab Reset all buffers (by System Administrators only)
/$syn c Synchronize instance buffers (by System Administrators
only)

20. How to Check the WP at OS level in UNIX from SAP
Ps – elf | grep dw … all WP
Ps – elf | grep sapos .. Check the sap OS collector
Ps –elf | grep ms … Message server
21. Different Between Application Server and Central Instance
Central instance: have message server and dialog, update, spool, enque, gateway,
background work processes.
Application server: Have only Dialog, update, spool, gateway and Background work
process.
Note: SAP server has only one message server and Enque server.
22. If there are 4 systems installed SAP, how should I connect all of them in one network
so that I can administrate the 4 systems with one among them as main server(Check
this ans)
After installing an R/3 System, you can use transaction RZ20 to monitor the system.
To monitor all systems of your system landscape centrally from one system, first
customize the alert monitor by choosing Tools > CCMS > Configuration > Alert
monitor or calling transaction RZ21.
Then, to specify the remote systems by System ID and RFC destination (which must
have been created beforehand), choose Technical infrastructure > Create remote
monitoring entry.
Next, to change your monitor definitions (you can only change your own monitors),
Choose Tools > CCMS > Control/Monitoring > Alert monitor or call transaction
RZ20.
Activate the maintenance function by choosing Extras > Activate maintenance
function. Then, double click on the monitor and choose monitoring change. Parameter
R3system defines which systems can be monitored by an alert monitor. Change
parameter R3system from <CURRENT> (only the current R/3 System can be

8. 8

monitored) to <ALL> (all R/3 Systems defined in RZ21 can be monitored). Save the
changes
23. How to do SAP Database startup & shutdown
Startup
Login as adm ( Unix)
Startsap all ( this will startup the SAP DB)
Startsap r3 ( R3 components and services, listener)
Startsap db
Shutdown
Check if there are any users or process executing in the SAP (sm50,sm04 – delete
the session before shutdown)
Stopsap r3
Stopsap db
SAP Startup Profile resides in /sapmnt/<SID>/profile/<SID>_DVEBMGS00
24. How to auto Start SAP on Windows Instance
Use transaction RZ10 to edit your startup profile. Add the following entry:
Autostart = 1
Then save the profile. Next time your server reboots, your SAP instance will come
up automatically!
25. Which is the Kernel Directory in SAP
/usr/sa/sid/sys/exe/run/…..

9. 9


Client Maintenance
1) About Client / Default Clients
2) Create clients
3) Copy and refresh clients
4) Client imports and exports
5) Delete and remove clients
6) Modify change options
26. Basic Information about Client
Clients 000, 001, and 066 are part of the R/3 delivery system.
In Client 000 and 001, there are two special users:
SAP* for initial access to the R/3 System
DDIC for the transport and correction system
To protect SAP* and DDIC from unauthorized access, you must change the initial
passwords for these users in all clients of your R/3 System. We recommend that you
add the user group SUPER to the user master records. This user group can only be
accessed by the super user.
Client 066 is the Early Watch client. Customers must change the initial user password
in their own system.
SAP* is a special user. In addition to the user SAP* that is created in every client
during a client copy, the user SAP* is hard coded into the kernel. The hard coded user
SAP* is exempt from all authorization checks. Do not delete the user master record
from any client in the R/3 system. If the user master record for SAP* is deleted from a
client, the hard coded user can be accessed.
To deactivate the hard coded user SAP*, use the system profile parameter
login/no_automatic_user_sapstar. See SAP Note 68048.
27. What is client in SAP, How do you client Copy
A client is indepent business or a legal unit within an SAP R/3 System. It could be
different independent branches within a company. A client is the highest
organizational unit. Data belonging to one client may not be shared or viewed by
another client.
Type of Client Copy :
SCC1 Client Copy - Special Selections
SCC2 Client transport
SCC3 Client Copy Log
SCC4 Client administration
SCC5 Client Delete
SCC6 Client Import
SCC7 Client Import – Post Processing
SCC8 Client Export
SCC9 Remote Client Copy
SCCL Local Client Copy

28. An example , If you taking one Local client copy , How long it will take to complete
Mini 5 – 8 hr ( depends on data and server configuration)
29. How drop the client in SAP
Using T-code : SCC5
30. What is the difference between client 000 & 001? Why we use client 000 for client
copy, why don’t 001?
000 clients is standard client and contain client independent setting. 000 client contain
simple organizational structure of test company and include all parameter for
application, standard setting
001 client is copy of 000 clients. It is reserve for the activity for preparing the system
for production system.
31. How many Default Client in SAP
000,001,066,SAP*,DDIC,
32. How to lock & unlock a client in SAP
SE37
33. How to move the favorites from one user to another
SE37
Menu _favorites _download (.mnu)

10. 10

Menu_favorites_upload
34. How to changing to titles of SAP Transaction
SE63
Click Transaction  short texts  Transactions
35. How to send popup message to specific user in SAP
SM02 – sends message to all users
SE37  TH_POPUP
36. User Can’t Connect to SAP , where we need to check
Check SAP logon settings, ping the host, Check Message Server & Check the
Dispatcher
37. User Can’t Print , where we need to check
Check SAP User setup, Check SPOOLS, Check Unix queue or Printer Queue
38. How can we maintain SAP PARAMETER?
T-Code:RZ10 /RZ11
39. How to Increasing or Decreasing the Number of Work Processes
Transaction RZ10
On the Edit Profiles screen, select the <SID>_DVEBMGS00_SAP<SID> Profile
40. How to lock SAP Client? Is there any Tcode to lock the particular Client…?
Execute Transaction code SE37.
Enter the Functional Module SCCR_LOCK_CLIENT/SCCR_UNLOCK_CLIENT .
Execute this and enter the client u need to lock.
41. How to change the Work process parameter using which T-code
Rdisp/wp_no_dia - Dialog process
Rdisp/wp_no_vb, Rdisp/wp_no_vb2 – Update process
Rdisp/wp_no_enq – enqueue Process
Rdisp/wp_no_btc - Background Process
Rdisp/wp_no_ spo – Spool process
If you want to change, use Code - RZ10 && Use for Configuration Operation mode
use Rz04
42. How do you kill a Job?
SM37 - select - kill
43. How do you Modifying System Parameters
Log on to any client in the appropriate SAP system.
Go to transaction RZ10.
On the Edit Profiles screen, select the <SID>_DVEBMGS00_SAP<SID> Profile
from the dropdown, or whatever instance profile you need to change. In the Edit
profile section, click the radio button to the left of extended maintenance. Click
the Change button.
On the Maintain R/3 Profile screen, locate the parameter that needs to be changed
in the Parameter name column. Change the matching value under Parameter value
to the new value. Click the Copy button. Click the white arrow on green picture-
icon.
On the Edit Profiles screen, click the Save picture-icon.

11. 11



User Administration
1) Default Users
2) Create users and assign profiles
3) Modify, lock and unlock users
4) Develop authorizations and profiles
5) Important profile parameters –Password
6) User Administration T-Code’s

44. Special SAP R3 Users - SAP* DDIC EARLYWATCH
SAP R/3 installation comes pre-configured with certain special user profiles with
privileged access. These user ID's are SAP*, DDIC and EARLYWATCH
SAP* - Clients 000 and 001 include the default super user ID SAP*. The SAP*
user id comes pre-installed in SAP. It is for this reason that it does not need a
master record. When a SAP installation team is installing SAP, a user master
record is defined for SAP*. The user password for SAP* user id is 06071992. One
small detail which needs to be looked at is in case SAP* user master record is
deleted, the user can use the password SAP* PASS. SAP bypasses all authorization
checks when user logs on again using SAP*.
DDIC - DDIC user id is used to maintain the ABAP/4 dictionary. At the time of
SAP R/3 installation DDIC is created automatically in clients 000 and 001. The
password for user ID DDIC is 19920706. Since, it is a critical user id which can
access R/3 during the new installation, it should be handled carefully. Password for
DDIC user id should be changed immideately. However, this user id should never
be deleted, since same can be used for installation and setup.
EARLYWATCH - EARLYWATCH user id comes standard with client 066 in
SAP. The default password for EARLYWATCH user id is SUPPORT. With
EARLYWATCH user id, one can access the data for monitoring and performance.
Normally, SAP Earlywatch experts work with this user id. Password for
Earlywatch should be changed, howev er, one should never delete the id. One SAP
consultant told me that as a best practice Earlywatch user id should be used only
for Earlywatch functions rather than asa generic user id.
45. How do we reset password for SAP* and DDIC user in SAP R/3 4.0B?
If you cannot log in as SAP*, you can carefully delete it at the database level.
Issue a delete statement against table USR02, which is the one that keeps the
passwords.
Example: delete USR02 where BNAME = 'SAP*' and MANDT='100'
Make sure you delete it only in the desired client.
After this, you will be able to log on as SAP* again with password PASS. Then,
you can change the DDIC password and go from there.
46. What do you know about Default user DDIC?
DDIC - DDIC user id is used to maintain the ABAP/4 dictionary. At the time of
SAP R/3 installation DDIC is created automatically in clients 000 and 001. The
password for user ID DDIC is 19920706. Since, it is a critical user id which can
access R/3 during the new installation, it should be handled carefully. Password for
DDIC user id should be changed immediately. However, this user id should never
be deleted, since same can be used for installation and setup.
47. What is Profile in SAP
A user profile is a set of authorizations that enable user access to certain parts of
the system
48. What is Composite Profile
Group of two or more profiles is called Composite Profile
49. What is Roles
It is combination of profiles, URL’s, Menus, Transactions, Reports, and User
Assignments.
50. Default profile & Instance startup Profile location
<sapglobalHost>/sapmnt/<sid>/sys/profile/default.PFL

12. 12

<sapglobalHost>/sapmnt/<sid>/sys/profile/<sid_instance_hostname>
51. Explain the type of User in SAP
Single user using T-Code: SU01
Mass User using T-Code: SU10
Type of User
a. Dialog ( logon screen user)
b. Communication ( RFC user)
c. System ( Local System user)
d. Service ( Service related)
e. Reference( refer to dialog user only)
52. System Trace for Authorizations
To record authorization checks, use the system trace. To start the system trace,
choose Tools --> Administration--> Monitor --> Traces --> System Trace or use
transaction ST01.
To analyze an authorization failure, call transaction SU53 and determine which
authorizations are required for your task. See SAP Note 66056.
To display all the authorizations contained in your user buffer, call transaction
SU56. If all your authorizations are not displayed by this transaction, check
whether:
Activity groups have been maintained since you last logged on to the R/3
System. To display your new authorizations, log off from the system and then
log on again.
You have received new authorizations through a transport.
The user buffer is too small. Maintain the following R/3 profile parameter:
auth/auth_number_in_user buffer.
53. Which table is having SAP logon user information
USR02 – select mandt, bname, bcode from usr02 where bname =’ ‘;
54. What is the T-code for creation of User Group
SUGR
55. To view locked users in SAP
SU10/SU01
Call SA38 - run RSUSR006
EWZ5
SUIM( User information System  with unsuccessful logons, user address &
Authorization)
56. Suspend/UnSuspend Released ABAP Jobs
BTCTRNS1 - Suspend all Released Jobs
Released Jobs will have the status Released/Susp. in transaction SM37.
BTCTRNS2 - Reverse Suspend for all Released Jobs
57. What is the difference between Sap lock and database lock?
A "SAP lock" is named "enqueue lock", the enqueue is on a much higher level, e.
g. a complete sales document is locked there whereas in the datbase usually only
row locks exist. Since SAP runs on more database than Oracle (thanx god) one
needed to have a mechanism, that is database independent and on a higher level.
58. What is the diff between clients 000 and 001?
Client 000 is the SAP source client, client 001 exists only on certain installations
(e. g. solution Manager).
59. How do you Lock/Unlock user in SAP?
Go to SU01Enter the userID to be locked in the user field and click on lock button
Then you will see the the following screen if the user is already locked.click on the
unlock button at the bottom left of the window and the user will be unlocked.to lock a
user again enter the user id in the user field and click on lock button and you will see
the following screennow press on the lock button to lock the user…you can also lock
the user at database level. login to the system database..then run a query to update the
USR02 table.
To lock an user.
SQL> UPDATE USR02 SET UFLAG = ‘64′ where BNAME=’USERID’ ANDMANDT=’CLIENT’
SQL> COMMIT
To unlock an user use
SQL> UPDATE USR02 SET UFLAG = ‘0′ where BNAME=’USERID’ AND MANDT=’CLIENT’
SQL> COMMIT

60. How to Copying the one user
Use transaction SU01 or, from the System Administration Assistant (transaction
SSAA), choose Entire view  Display Tasks  Running Your System 

13. 13

Additional Administration Tasks SAP System Administration  Users:
Copying a User.
In transaction SU01, enter ADMIN##, choose Copy, then enter the name
BASIS##. Deselect Authorization profiles and Activity groups. Enter a new
password for BASIS## twice and save.
61. Different values of uflag have different meaning UFLAG value
0 - Not locked
16 - Mystery values
32 - Locked by CUA admin
64-Locked by system Administrator
128 - Locked due to incorrect logon attempts or too many failed attempts
192 - A combination of both.
The user is locked by admin and user tries to logon with incorrect passwords and
gets locked ( 192 = 64+128)
62. How to grant roles
To use the Profile Generator, choose Tools - Administration - User Maintenance -
Activity
Groups (User Roles) or call Transaction PFCG.
63. Traffic lights indicate the status of your authorizations:
Green: all authorizations have been maintained
Yellow: some authorizations must still be maintained
Red: organizational levels must be maintained
64. Important Tables for User, Profile, Authorization
History Tables : Users : USH02,USH04
Profile : USH10, AUTH: USH12
Profile Generator Tables:
User Master: USR01 to UST04
Profile: USR10,USR11,USR10S,UST10C
Authorization : USR12,USR13,UST12
Password Exception: US404
65. Backup of Profile / Import
Backup Profile  \usr\sa\<sid>\sys\profile
Choose Edit  Copy profiles & then edit  Paste profile into Backup disk
mkdir backup
Copy default.PFL backup
Cp/copy start_<instance_name>_<hostname> backup
Cp/copy <sid>_<instance_name>_<hostname> backup
Important all profiles at once into the R/3 system
1. RZ10  choose utilities  import profile s  of active servers
66. How to view locked Transaction Code
SE11/SE16 – TSTC
SM01
67. How to check Locks
SM12
68. If Locking the whole system
Using the command tp locksys «SysID» only the user SAP* will be allowed to
login.
The command tp unlocksys «SysID» cancels the lock.
69. How to reset the password
Using T-Code : SU01
70. Disable SAP users to logon multiple times.
RZ10
Login_multi_login_users = set to 1 to active
Login/disable_multi_gui_login = you can put a list of users that should be allow to
logon multiple times
71. Maxi number of SAP session per User
Using RZ10  rdisp/max_alt_modes… default max no’ of session 4.6X is set as
6 session per user
72. Automatically logged off the frontend SAP GUI
RZ11 ( for session level)
Rdisp/gui-auto_logout (in seconds)... if value has 0 , there will be no automatic
log off
73. How to reset SAP* password from Oracle Database
Logon to database

14. 14

Delete from usr02 where bname=’SAP*’ and mandt =’XXX’;
Commit. Now you login to client using SAP* & password is pass
74. Which T-code is to Create Internet User
SU05
75. Explain about SAP role and Profile. Which T-code to use …
PFCG – Role
RZ10 – Profile
76. How to setup the Operation Mode.
T-Code: RZ04
77. Reporting logon information

Worst-case scenario Best-case scenario
Manually log in to each system and
execute one of the following:
Run a script that reaches inside each SAP
database and extracts the user list. To achieve
that we need to:
Tcode SUIM -> User Information
System -> User -> With
Unsuccessful Logons
1. Create a SQL script that can produce the
output we need by querying database table
USR02. This script will be later incorporated
in a batch file.
Tcode SE16 and query table USR02.
2. Create a text file with the SAP server
names, SID database names and database
owners.
Run ABAP report RSUSR006 via
SA38.
3. Create a batch file that loops through the
text file entries and runs the appropriate SQL
statements to produce reports.
Script:
SELECT TOP {Max_Rows_To_Return }
USR02.MANDT as s_CV30, (Mandant) USR02.BNAME as s_SUN,
USR02.USTYP as s_CV31, (User Type) USR02.CLASS as s_CV32, (Group
Type)
USR02.ANAME as s_CV33, (Creator) USR02.ERDAT as s_Creation_Date,
USR02.TRDAT as s_Access_Date,USR02.LTIME as s_Offset,
USR02.PWDCHGDATE as s_Last_Pass_Change
FROM USR02 WHERE USR02.TRDAT = {Current_Date} AND
USR02.LTIME > {Event Time}
ORDER BY USR02.LTIME ASC

78. Explain some important profile parameter for login ( Password)
Password Checks
Login/min_password_ing
Login/min_password_digits
Login/password_expiration_time
Login/disaple_password_login
Multiple login
Login/disable_multi_gui_login
Login_multi_login_users
79. System Profile ParametersValues
Set the minimum password length
login/min_password_lng Default – 3 Permitted 3-8
Require change of password
login/password expiration_time Default- 12 Permitted 1-99
Lock users after incorrect logons
login/fails_to_user lock Default -1 Permitted- 0
Prevent automatic unlocking at midnight
login/failed user auto unlock Default-3 Permitted -1-99
Number of failed logon attempts permitted
login/fails_to_session_end Default- 0 Permitted -1
Preventing multiple dialog user logons
login/disable multi_gui login Default- 0 Permitted- 999
80. Initial Logon Procedure in SAP Clients
Client  000 001 066 New Client
User  SAP* DDIC EarlyWatch SAP*
Initial Password 06071992 19920706 support pass

15. 15

81. User Administration T-Code’s
PFCG Profile Generator (Activity Group Maintenance)
PFUD User Master Data Reconciliation
SU01 User Maintenance
SU01D User Display
SU02 Maintain Authorization Profiles
SU03 Maintain Authorizations
SU05 Maintain Internet users
SU10 User Mass Maintenance
SM19 Security Audit Configuration
SMLG Maintain Logon Group
SUPC Profiles for activity groups
SUIM Info system Authorizations
82. Listing, Adding, Deleting Users ( use with sa38)
To list user’s last login, invoke report RSUSR006.
To check passwords of users SAP* and DDIC in all clients, invoke RSUSR003

16. 16


Background Process

1) What is batch Process?
2) Job priority type
3) Status of the background job
4) Background Process – parameter
5) Background Jobs T-code’s

83. Use of Background Process
Reducing load on dialog work processes
Scheduling Regular Activities
84. How many background job priority type in SAP
High priority – A Class
Medium priority – B Class
Low priority – C Class
85. Type of background job Schedule
The start conditions of a job can be time based or event based.
Time based:
1. Immediate
2. At date/time
3. On a chosen workday (defined as a certain workday per month)
4. All time-based start conditions can be periodic. That is, a job can be
performed at regular, defined time intervals. Days that are not
workdays can be treated as exceptions.
5. Parameter rdisp/btctime specifies the time interval of the job
scheduler.
Event based:
After event (optional parameters can be used to further specify
events)
These can be periodic. That is, the job can be triggered every
time the event occurs.
After job (this can depend on the status of the previous job)
At change of operation mode (for example, between day and
night)
Parameter rdisp/btcname specifies which application server
handles events triggered from within R/3.
86. Status of the background job
The job status can be any of the following:
Scheduled: job is created but has no start condition
Released: job is completely defined and waiting for selection
Ready: job has been selected for execution
Active: job is being executed by a background work process
Finished: the entire job has been successfully executed
Canceled: job terminated with problems
As long as a job has status scheduled or released, it can still be changed.
If execution of a job has already started, its progress can be monitored in the job
log. If the job contains ABAP programs, their output is stored in spool lists.
To create the steps of a new job from an existing job, choose Copy.
87. How to change the background Work process
rdisp/btctime
88. While Transportsystem useing , How many background Work process is required
At least 2 background Work process must be available
89. How many background work processes are configured on your SAP System?
Check in transaction SM66 (choose Select Process, flag status wait) for the number
work processes of type BTC (background).
SM50
90. How many background jobs can you run at the same time?
You can run as many background jobs in parallel as background work processes
are available.
91. How can you check at what intervals the job scheduler runs?
Check parameter rdisp/btctime. This parameter determines the intervals at which
the job scheduler runs. To check the parameter setting, use transaction RZ11 or
report RSPFPAR.

17. 17

92. How can you find out which application server handles events triggered from within
R/3?
Check parameter rdisp/btcname. This parameter determines the application server
for event handling. To check the parameter setting, use transaction RZ11 or report
RSPFPAR.
93. What determines the number of available background work processes?
Initially, parameter rdisp/wp_no_btc determines the number of available
background work processes. You can check the parameter setting using transaction
RZ11 or with Report RSPFPAR.
If you use operation modes (transaction RZ04), this setting can be overwritten.
Use the CCMS Control Panel (transaction RZ03) to check the current operation
mode.
94. Background Jobs T-code’s
SM36 Define Background Job or Choose Tools – CCMS – Jobs ->
SM37 Background Job Overview –Monitoring
SM39 Job Analysis
SM49 Execute External OS commands
SM62 Maintain Events
SM64 Release of an Event
SM65 Background Processing Analysis Tool
SM69 Maintain External OS Commands
95. Can you run background jobs of class A on your R/3 server?
You can run background jobs of class A on any server where background work
processes are running.
96. Can you find out if you have background work processes reserved for class A jobs in
your process overview (transaction SM66) or in your instance profile?
If you have reserved background work processes for class A jobs, this is only
visible in the operation mode definition. To find out if any background processes
have been reserved for Class A jobs, in transaction RZ04 choose
Instances/operation modes and view column BPA.
97. Imagine that you have no available background work processes. Can you make
background work
processes available without restarting your R/3 instance?
You can use transaction RZ04 to define an operation mode with background work
processes.
98. ABAP : Define a job STEPS_## using the Job Wizard. The job should:
Be of class C
Step 1: Execute Report RSPFPAR with variant DISPATCHER
Step 2: Execute external program whoami(check the control flags)
Start in 2 minutes
Ans:
In transaction SM36, start the Job Wizard. Enter job name STEPS_## and
select class C but leave Target server free. Select ABAP program step and as
ABAP program name enter report RSPFPAR with variant DISPATCHER.
As additional step, select External program as a step and enter program name
whoami without additional parameters. As target server, enter the name of your
application server. Check the control flags and save the proposed default
settings.
As start condition, select Date/time and enter the planned start time.
Check whether the job ran successfully as in solution 2.4.
99. Display a list of external commands. What does the command ZKERNEL do?
To display a list of external commands in CCMS from the SAP standard menu,
choose Tools CCMS Jobs External Commands (transaction SM49). To run a
command in the list, select the command and choose Execute.
External command ZKERNEL displays the disp+work (kernel) information.
100. What user event ??????
101. Within CCMS, create a user event MYEVENT_##.
Choose Tools CCMS Jobs Maintain event. Do not modify system event names.
Under User event names, select Maintain and execute. Choose Create. Enter the
event ID MYEVENT_## and a description of the event, then choose Save.
102. Define a job NEXTLINK_## using the Job Wizard. The job should:
Be of class C
Step 1: Execute report RSUSR000
Start after successful run of job created in exercise 4
Check the status of the job in the Job Overview.

18. 18

In transaction SM36, start the Job Wizard. Enter job name NEXTLINK_## and
select class C but leave Target server free. Select ABAP report RSUSR000.
As start condition, select After Job, enter predecessor job name EVENT_## and
select Start if the preceding job ends successfully. Complete the job definition.
Check the job status in transaction SM37. To ensure that your job is listed, select
Expanded job selection and in the field Start after job enter the name of the
predecessor job (or *).

19. 19

Spool Management
1) What is Spool Management in SAP
2) Spool Management Jobs T-code’s
3) Monitoring Spool Management

103. Spool Management
To start the spool administration transaction SPAD, use the System Administration
Assistant. Alternatively, choose Tools  CCMS Spool Spool administration.
You can set an upper limit to the number of spool work processes used for front
end printing using parameter rdisp/wp_no_spo_Fro_max. The default value of the
parameter is 1.
SP01 Administration of spool requests(all clients)
SP0R Same as SP01 (own client)
SPAD Spool administration (all clients)
SPAR Client-dependant spool administration
104.
105. Deleting Spool Space  RSPO0041 or RSPO1041

20. 20


Oracle Database

1) Oracle Directory Structure
2) Important Tablespace names List
3) BRTools details
4) Important Database T-code
5)
106. How to check the Oracle alert file
T-Code ST04 – details analysis Menu – database message log
107. Brtools login
cd d:D:\usr\sap\SER\SYS\exe\run
set sapdata_home =D:\oracle\SER
set oracle_sid=SER
brtools
108. Explain Oracle Directory Structure

109. Which table space, gets filled frequently and we add datafile to that?
PSAPBTABD/I, PSAPSTABD/I, PSCAPLUCD etc.
110. SAP requires tablespace names to have a leading "PSAP" and ending "D" or "I"
(for index).
Type Tablespace Contains Tables Size
Activ
ity
Transaction
Tablespaces
PSAPBTABD Holds SAP Transaction tables
holding order headers, line items,
purchase orders, etc.
Large High
est
PSAPSTABD Master data and transparent tables
with high write activity such as
item master, customer data,
pricing, etc.
Largest High
est
PSAPUSER1D Defined to hold user customization
(customer tables) not defined with
the SAP software.
Depends Depe
nds
PSAPVB0101D &
PSAPVB0102D
- Large Very
high

21. 21

BASIS
Tablespaces
PSAPDICTD ABAP data dictionary (usually
cached in memory due to frequent
reference).
Small Low
PSAPLOADD ABAP report loads and screens. - High
PSAPSOURCEID ABAP report source code and
screens.
- Medi
um
PSAPPROTD A heavy-use tablespace. Spool,
customer, log files, reports and
printouts generated by any SAP
process.
- High
est
System
Tablespaces
PSAPPOOLD System pool tables that SAP
considers too small to be in their
own tables. These are generally
buffered in memory, so they're
accessed at SAP startup time but
not heavily after that.
Small Low
PSAPCLUD Cluster tables used by SAP as
subtables containing LONG RAW
datatypes, which must be
reorganized using Oracle's slower
Export/Import utilities instead of
Oracle's faster CREATE TABLE
AS SELECT command.
Large Medi
um
PSAPDOCUD Contains codument tables,
including SAPscript and SAPfind
tables.
Small Low
PSAPVB0201D &
PSAPVB0202D
-
111. Oracle R/3 Naming Conventions
112.
113. Oracle Directory Structure in R/3

22. 22

114.
115.
116.
117. Oracle DB roles
118.

23. 23

119. How to extend the TBS size using SAP Command / Tool
Using BRSPACE == > brspace –f tsextend





120. How to shutdown the database/ How create new TBS /How to rebuilding Indexes
using SAP ( BRSPACE )
Instance administration:
Start up database
Shut down database
Alter database instance
Alter database parameter
Recreate database
Tablespace administration:
Extend tablespace
Create tablespace
Drop tablespace
Alter tablespace
Alter data file
Move data file
Segment management:
Reorganize tables
Rebuild indexes
Export tables
Import tables
Alter tables
Alter indexes
121. How do we find out the indexes that are to be rebuild?
You can use BRSPACE --> reorganization --> check extents and fragmentation
122. Sample Backup
Brbackup –u system/pass
Brbackup –u / -f force –t online –m all –p initser.sap –v <path>
Brconnect –a / -c –f check
123. How to take Database using Brtool
BRBACKUP - Backs up data files, control files, and online redo log files of the
database
124. How to take the Backsup offline redologs
BRARCHIVE
125. How to restore datafile, controlfile and redo log files
BRRESTORE - Restores data files, control files, and redo log files
126. How to recover database
Using BRRECOVER
127. How to gather statistics and clean up logs
BRCONNECT
New file to be added (file) -f tsextend -f|-file
Raw disk / link target (rawlink) -f tsextend -r|-rawlink
Size of the new file in MB (size) -f tsextend -s|-size
File autoextend mode (autoextend) -f tsextend -a|-autoextend
Maximum file size in MB (maxsize) -f tsextend -m|-maxsize
File increment size in MB (incrsize) -f tsextend -i|-incrsize

24. 24

128. Important Database T-code
DB Performance Monitor - ST04
DB space management - DB02, DB20
DB Backup and Recovery-log - DB12
DB Configuration - DB03, DB21
DB Jobs schedule (DBA Planning Calendar) - DB13, DB24
Alerts - DB16, DB17
Diagnostics - DB6COCKPIT
129. How to see the Table contents
SE16
130. Suspend/UnSuspend Released ABAP Jobs
BTCTRNS1 - Suspend all Released Jobs
Released Jobs will have the status Released/Susp. in transaction
SM37.
BTCTRNS2 - Reverse Suspend for all Released Jobs
131. Archiving data in SAP
Call transaction SARA or choose Tools -> Administration -> Administration ->
Archiving, enter object name <US_PASS>

25. 25

SAP Transport Management System(TMS )
1. SAP TMS Concepts
2. Important Transport Management TCodes
3. SAP How to Step by Step Guide
132. SAP Transport Management System Concepts
SAP's Transport management system represents the centralized change and transport
system CTS for all R/3 systems. SAP introduced transport management systems TMS
from version 4.0 onwards.
One of the main benefits of the new transport management system is that it enables the
SAP administrator to manage all SAP R/3 change requests from one single SAP client.
Centralization of change request results in streamlined change management.
Earlier the transport of objects was done through transaction code SE06. With the
introduction of transport management system, the movement of objects is now controlled
through transaction code STMS.
SAP TMS allows SAP administrators to define transport routes before hand. This
minimizes human intervention in handling transport requests. As a segregation of duties
best practice, access to transport management system transactions should only be
restricted to the Basis team.
Important Transport Management TCodes
SCC1, SCC4 - These are Client Administration transactions which enable user to create
a new client SCC1 and copy data from an existing client to a target client.
SE10 - SE10 represents the transport organizer. It is used to manage and verify transport
requests.
SE11 - SE11 is the ABAP dictionary and is used to manage and release transport
requests.
STMS - The transaction for transport management system, controls the movement of
objects between various SAP systems
SAP How to Step by Step Guide
On the command field, enter STMS. You will see the above screen. Now, click the red color
truck on upper left of the screen.

Double click on the target system. In this case, I ‘ going to transport from Development
server to Production server. I’ll double click on PRD.

26. 26


3. Press refresh once to update the transport list.

4. Click on the ‘transport request que (Ctrl-F6) if you see a green colored arrow. Press ok when a
window popup.
5. Once completed, click on Import request button (Ctrl-F11)
6. Enter your target client. In my case, its client 800.

27. 27


7. Click on option tab and un tick leave transport request in queue for later import. See above
picture. Now click ok.
8. Click ok to confirm when a new windows pop up.
9. Transport has been completed.
133. SAP Transaction Code: STMS
Report used to generate STMS is: SAPLTMSU

28. 28

SAP Memory Management
1) Type of Memory
2) Memory Parameter’s
3) Memory Monitoring
134. SAP Memory Management
Roll Area
Extended Memory
Paging Area
Heap memory


R/3 Memory
1. Physical Memory
2. Virtual Memory
3. Local Memory
4. & Shared Memory / Global Memory

29. 29

135.





136. SAP Roll area parameters
ztta/roll_first : First amount of roll area used in a dialog WP
ztta/roll_area : size of the local SAP Roll area in the work process
rdisp/ROLL_SHM : size of SAP roll Buffer
rdisp/ROLL_MAXFS : size of entire shared SAP roll area

30. 30

137. SAP Extended Memory main parameters :
em/initial_size_MB : size of SAP extended memory allocated when the SAP
instance starts up
em/blocksize_KB : size block which split SAP Extended Memory
ztta/roll_extension : maximum size of a user context in the SAP Extended memory
138. SAP Heap Memory
Area which allocated variably as local memory as required.
Released after a transaction is complete.
139. SAP Heap Memory main parameters :
abap/heap_area_dia : quotas oh SAP heap memory that a dialog process can
allocated.
abap/heap_area_nondia : quotas oh SAP heap memory that a nondialog
process can allocated.
abap/heap_area_total : size that can be allocated in total by all work process.
abap/heaplimit : Workprocess restart limit of heap memory
abap/heaplimit : Workprocess restart limit of heap memory

31. 31


SAP Security Tables & Report
SAP Security Tables
Security – T code  SM18,SM19,SM20,SM20N ( se38 Parameter)

32. 32


SAP Security Reports

33. 33


Monitoring
1) User Monitoring
2) Client Monitoring
3) WP Monitoring
4) DB Monitoring
5) Work Load Monitoring
6) Daily Monitoring
7) Computer Center Management System (CCMS)
8) OS Monitoring
9) Memory Monitoring



140.
141. The alert monitoring framework consists of Data Suppliers (collection methods), Data
Consumers (transaction RZ20, CCMS Monitoring Sets), and the Monitoring Architecture.
This architecture is delivered ready to use with collection methods already created for all
major components in the R/3 System environment. Typical data suppliers already active for

34. 34

reporting include: host operating system, R/3 database, R/3 Systems, instances, and their
related services and components, and API for external components outside the R/3 System.
142. Analysis Methods
143.
All instances displayed in transaction RZ20 have the same structure. They are divided
into the following parts:
Operating system
Database client
R/3 services (R/3 work processes)
R/3 basis system, containing the buffers and memory management
R/3 ABAP
R/3 System log, where important messages are stored
Security
Server configuration
144. R/3 Syslog
145.
Use the analysis tool SM21 to look in more detail at the alerts shown in RZ20

35. 35

The MTE R/3 System log provides information about the different parts of your
R/3 System. To see the log information for a time frame, call transaction SM21.
To view the system log, choose Tools --> Administration --> Monitor --> System
log.
The system log shows various messages, including error messages. Some of these
provide information about, for example, operation mode switches or system start
up. Other log messages show errors that occurred in the system (such as update
errors, deletion of lock entries, or aborted programs).
The R/3 System log provides information about such errors. To analyze these
errors, you must use other analysis tools.
If you use the System Administration Assistant for your daily system checks, it
provides you with direct access to transaction SM21.
146. . R/3 Services
147.
148. The alert monitor uses a color scheme to indicate the severity of each alert
displayed:
Green: component OK
Yellow: warning
Red: problem
White: no data
149. R/3 Basis System
150.
151. DB Monitoring

36. 36

152.
153. Operating System
154.
155. DB Monitoring –ST04

37. 37

156.
157. DB Space Monioring
158.
159. DBA Operation Monitoring – DB24
Choose Tools  CCMS  DB Administration  Operations Monitor

38. 38

160.
161. DBA Alert Monitoring – RZ20
162.
163. System Configuration
RZ10  Maintain profile Parameter
RZ11  profile Parameter Maintenance
RZ12  maintain RFC Server group Assignment
164. Remote System Monitoring

39. 39



After installing an R/3 System, you can use transaction RZ20 to monitor the
system. To monitor all systems of your system landscape centrally from one
system, first customize the alert monitor by choosing Tools  CCMS 
Configuration  Alert monitor or calling transaction RZ21. Then, to specify the
remote systems by System ID and RFC destination (which must have been created
beforehand), choose Technical infrastructure ® Create remote monitoring entry.
Next, to change your monitor definitions (you can only change your own
monitors), choose Tools -> CCMS -> Control/Monitoring -> Alert monitor or call
transaction RZ20. Activate the maintenance function by choosing Extras ®
Activate maintenance function.
Then, double-click on the monitor and choose Monitoring change. Parameter
R3system defines which systems can be monitored by an alert monitor. Change
parameter R3system from <CURRENT> (only the current R/3 System can be
monitored) to <ALL> (all R/3 Systems defined in RZ21 can be monitored). Save
the changes.
165. How to check that all the application server are up
SM51 – SAP Server
SM04/Al08 - logon users
166. Monitor Work processes on the system
SM50, SM51, SM66
167. To check that daily backup are executed without errors
DB12 – backup log overview
168. How do you check the Background Job
T-Code:SM37,RZ01
169. OS Monitoring
ST06
170. How can delete old logs with T-Code
SM20
171. DB object extents monitoring - check for max extents reached
DB02 or brspace tools
172. How to find the table use by a transaction
Using T-Code:SE49
173. How to check Memory usage in SAP
T-CODE:ST02.ST03,RZ10
174. How to configure the Printer and check
T-Code: SPAD,SP01,SM50,SU01
175. How to Tracing a User’s Activity
Using T-Code: SM19
176. Which table is having Tablespace size information in SAP
RSORAT01
177. Which table is having Table Extent information in SAP
RSORATC5
178. How to monitor the work load

40. 40

Transaction ST03
179. How to find long running job,, how do you analyzes
Use transaction SE30.
180. How to Check for any failed Updates
SM13
181. How to Reviewing cancelled Jobs
SM37
182. Sending System Message
Using with SM04
183. Which table for finding all activities?
TACT in sm30
184. After analysing ST02, how can we calculate the value of the parameter profile to
be increased (in RZ10)
sappfpar check pf=\\usr\sap\trans\tpparam
(or)
sappfpar check pf=\\usr\sap\trans\tp_domain_<sid>
185. Computer Center Management System (CCMS)
Choose  Tools – CCMS
Manages the entire system - database, application, operating system
Collection of tools and utilities which allow you to monitor and manage the R/3
system
Allows monitoring of multiple R/3 systems
Comes FREE with each SAP system
Starting and stopping instances
Monitoring and analyzing workload
Alert capabilities
Operation modes and work process automatic reconfiguration
Instance profile checking and maintenance
Logon load balancing
186. CRITICAL TASKS – Monitoring
Check daily backup (DB12)
Check all A/s is Up (SM51)
Check the CCMS Alert Monitor (RZ20)
Check for any failed Updates (SM13)
Check System Log (SM21)
Reviewing cancelled Jobs (SM37)
Checking Locks (SM12)
Check for Users on the System (SM04/AL08)
Check for Spool Problems (SP01)
Check Job Log (SM35)
Review and Resolve dumps (ST22)
Review Workload Statistics (ST03)
Review buffer statistics (ST02)
Review of DB error logs (AL02/ST04)
Review of O/S logs (AL16/OS06)
187. Alert Monitoring T-Code’s
AL01 SAP Alert Monitor
AL02 Database alert monitor
AL04 Monitor call distribution

41. 41

AL05 Monitor current workload
AL16 Local Alert Monitor for Operating System.
AL18 Local File System Monitor
RZ20 CCMS Monitoring
188. Configuration T-Code’s
FILE Cross-Client File Names/Paths
RZ04 Maintain Operation Modes and Instances –
1. Create Operation Mode
2. Define Instance
3. Maintain Work process distribution for the Instance
RZ10 Maintenance of Profile Parameters
1. Instance Profile, Default, Start profile
2. Import /Maintain profiles
RZ11 Profile parameter maintenance
SE93 Maintain Transaction Codes
SM63 Display/Maintain Operating Mode Sets – Maintain Time table
SPRO Customizing: Initial Screen
SWU3 Consistency check: Customizing
189. Database Administration T-Code’s
DB01 Analyze exclusive lock waits
DB02 Analyze tables and indexes
DB12 DB Backup Monitor
DB13 DBA Planning Calendar – Assign Backup
DB15 Data Archiving: Database Tables
190. System Monitoring
AL08 Current Active Users
AL11 SAP Directories or STUN
OS01 LAN check with ping
RZ01 Job Scheduling Monitor
ST01 System Trace
ST02 Setups/Tune Buffers
ST04 Select DB activities
ST05 Performance trace
ST06 Operating System Monitor( CPU Utilization)
ST06->details analysis menu->snapshot analysis->top CPU from there, start to
narrow down
ST10 Table call statistics
ST03 Performance, SAP Statistics, Workload
ST07 Application monitor
STAT Local transaction statistics
STUN Performance Monitoring (not available in R/3 4.6x)
SM21 Check System Log
STAD Statistics Display for all System
191. Monitoring Hardware
ST06
OS07
SM51
192. Daily monitoring TCodes:
AL08 Current Active Users
SM12 Display and Delete Locks
SM13 Display Update Records
SM21 System Log ( view R/3 syslog for both online & offline )
SM50 Work Process Overview
SM51 List of SAP Servers
SM66 System Wide Work Process Overview
ST22 ABAP/4 Runtime Error Analysis ( ABAP Dump Analysis)
ST01 System Trace
SE30 ABAP Trace
ST02 Setups/Tune Buffers
ST04 Select DB activities
ST05 Performance trace(SQL)

42. 42

ST06 Operating System Monitor
ST10 Table call statistics
ST03 Performance, SAP Statistics, Workload
SU56 Analyze User Buffer
193. Transport Management System:
STMS Transport Management System
SE01 Transport and Correction System
SE06 Set Up Workbench Organizer
SE07 CTS Status Display
SE09 Workbench Organizer
SE10 Customizing Organizer
SE11 ABAP/4 Dictionary Maintenance
SE16 Data Browser
SE80 Repository Browser
SM30 Call View Maintenance
SM31 Table Maintenance
194. SSAA( System Administrator Assistant)
Single point of Control for the entire System Land scape
Periodic tables
Occasional tasks
Performance-Related Transactions by System Layer
1. Performance-Related Transactions
2. System Maintenance Jobs
3. Table Maintenance
4. ABAP Programs for Checks and Cleanup
5. SAP Workload Analysis
6. SAP Administrator Daily Activities
SAPs Early Watch online diagnosis and analysis service provides a performance
report based on over 100 screens available from SAPGUI and other utilities (
SAPDBA utility no longer available on SAP 6.40).
This table repeats what is shown by specifying a SAP Transaction code or a one of these
menu paths:
o Tools > Administration > Monitor > Performance (abbreviated as "TAMP >")
o Tools > CCMS > Control/Monitoring > Performance menu
Layer TSTC Menu Path Items
Network ST08 - Network Monitor
ST09 - Network Alert Monitor
SM58 - Asynchronous RFC error log
Requests SM13 - Display update requests and resolve
errors
SM59 - Display or maintain RFC destinations
Instances RZ02 - Network graphics for R/3 instances
RZ04 - Maintain R/3 instances
Servers SM51 - List of servers
RZ03 - Control Panel for operation modes and
server status
OS SM02 - Display SAP System Messages
SM21 - System Log
SM69 - Maintain external operating-system
commands
SM49 - Execute external operating-system
commands.
ST06 TAMP > Operating Operating System Monitor reports load

43. 43

System > Local on the CPU and the physical main
memory. (such as what is reported by
Unix command lsattr -E1 sys0).
ST07 TAMP > Operating
System > Remote
Application Monitor reports load on the
CPU and the physical main memory by
application.
App Server ST02 TAMP >
Setups/Buffers
R/3 Memory Configuration Monitor
(also known as the function Setups &
Tune Buffers). Its Tune Summary
reports load on R/3 buffers and other
memory areas. Buffer hit ratio = Buffer
object reads / logical requests. poor
Buffer Quality = saved database calls /
(database calls + saved database calls)
STAT - Single statistics records on the
application server.
Work Processes SM66 CCMS >
Control/monitoring
> Work process
overview or
TAMP >
Exceptions/Users >
Active users > All
processes.
System wide Work Process Overview
SM50 TAMP > System
monitoring >
Services > Process
Overview
Local work process load (CPU
utilization).
Shows the currently executing WPs on
a dialog instance.
ST03 Workload
distribution
Monitor
A technical analysis uses this monitor
to identify and analyze problems in the
database, R/3 memory management, or
R/3 buffers.
An application analysis uses this
monitor to identify and analyze
transactions, programs, and users that
place a heavy load on the system.
DB AL02 - Oracle Database Monitor
ST04 CCMS screen that
displays Oracle
database activity.
+ alert log
Database Performance Monitor
displays load on the database buffers,
database locks, wait situations, read
and write access to hard disks, and SQL
statements.
DB02 CCMS >
Control/Monitoring
> Performance
Menu > Database >
Tables/Indexes >
Database
Allocation > Detail
Analysis
(consistency check)
Analyze tables and indexes (missing
database objects and space
requirements). Database
Performance:Database Allocation
monitor, Check Table Within SQL
Server, the DBCC CHECKDB
command locks user tables, indexes
and system tables when running. It is
very I/O intensive and should therefore
not be run during normal operation, but
at times when the system load is low.
For more information, see SAP Note
142731 DBCC Checks of SQL Server.
DB12 CCMS > DB
Administration >
Backup logs >
CCMS Monitoring
Tool > Backup
history > Logs
Overview of backup logs (DBA
protocols). In Backup Restore
Information list, find the largest
transaction log backup. Select a row
and then History info to find the
number of pages backed-up. Calculate

44. 44

Backup. how much free space is left on the
transaction log disk by subtracting the
amount of space used in the transaction
log is the number of dumped pages,
multiplied by 8 KB. The SAP log file is
initially created with a default size of 1
GB, with the smallest disk normally 9
GB.
DB Tables AL12 - Display table buffer (buffer
synchronization)
DB05 - Table analysis
DB20 - Generate tables statistics
ST10 TAMP >
Setup/Buffers >
Calls
Table Access Statistics
SE16 - Data Browser for displaying table
contents.
SM31 - SAP Table Maintenance
SE13 STUN >
Setup/Buffers >
Buffers > Goto >
Current local data
> Table buffers >
Single record
To specify whether or not a table
should be buffered.
DB SQL ST05 System > Utilities
> SQL Trace
Start, stop, or view SQL Trace
enqueue trace, or RFC trace within
ABAP programs for detailed analysis.
ST11 - Display developer traces. – Check
Core files
SE30 - ABAP Trace
ST22 - ABAP runtime error analysis and dump
listings
ST01 - R/3 System trace
Locks & Enqueues SM01 - Lock Transactions
SM12 - Display and delete R/3 enqueues
SMLG provides average response times of the overall system. ST03N provides response
times.
195. System Maintenance Jobs (Scheduling of system maintenance jobs)

Job Description
RSBTCDEL Clean the old background job records
RSDBCREO Clean batch input session log
RSPO0041 Removing old spooling objects
RSSNAPDL Clean the old ABAP error dumps
196. Table Maintenance ( use SA38 or Choose system service)
To copy tables across clients, invoke RSCLTCOP
To make table adjustments across clients, RSAVGL00
To invoke the Substitution/Validation utility, invoke RGUGBR00
To transport SAP script files across systems, RSTXSCRP
To release batch-input sessions automatically. RSBDCSUB
RSORATC5- Check the table Extent or DB02
RSORAT01- Check Tablespace Size/ Extent
RSMI3001 – deleting cancelled Update Records
RSPO0041 – Obsolete spool Objects

45. 45

RSPO0043 – Spool lists Which are remnants of cancelled by job
RSUSR003 Check the passwords of users SAP* and DDIC in all clients
RSUSR006 List users last login
197. ABAP Programs for Checks and Cleanup( use SA38 or Choose system service )
RSBTCDEL Delete background logs
RSPO1041 Delete old spool requests
RSPO1043 Check consistency of spool DB
RSBDCREO Reorganize BI folders and logs
RSSNAPDL Delete ABAP short dumps
RSSTAT60 Reorganize table MONI
RSORA811 Delete old brbackup / brarchive (not all databases)
RSORASNP Reorganize logs SNAP and STAT$
RSCOLL00 Performance monitor collector run
Program that starts tool dispatching for CCMS Monitoring Architecure
Collector of Performance Database (CCMS) •
Program for Reorganization of Performance Database (CCMS) •

These programs must be scheduled using transaction RZ21 ã SAP AG 1999
We recommend that you schedule these reports to run periodically.
SAP Workload Analysis
198. Performance Analysis


In order to perform analysis of a SAP software component the component should start without an
error and there should be spare work processes available to run the analysis.If there are no work
processes available then use the program dpmon at the operating system level which will give the
same output as the work process overview.
Workload Analysis (tcode ST03 or ST03N)
Menu Path
Tools=> Administration=> Monitor=> Performance=> Workload=> Analysis
Problem Analysis
High database time i.e. more than 40% (database time =
response time – wait time)
Check using tcode STAT / STAD if buffer
reload then check ST10 for Table Access
Statistics if OK, then use ST05 for SQL
trace analysis.
Roll wait time more than 200 mseconds Check using tcode ST05 for RFC trace
GUI time more than 200 mseconds Check for networks bottlenecks
Load time more than 50 mseconds Check the program buffer, maybe the
program buffer too small
Roll out or roll in time more than 20 mseconds Check SAP memory, problem cold be with
SAP extended memory or SAP roll buffer
Programs with high CPU time i.e. >40% Check ABAP program tcode SE30
Work Process Overview SM50 / SM66
Menu Path
Tools=> Administration=> Monitor=> Performance=> Exceptions / Users=> Active Users=> All processes
Work Processes with status running
Direct read, Sequential read, Insert,
Update, Delete or Commit
Check databse locks tcode DB01, if exclusive lock wait, check
process holding the lock.
Load Report or semaphore 1 SAP program buffer too small
Roll in, Roll out or semaphore 6 Check SAP memory problems due to extended memory or roll
buffer
Work processes with status stopped
Reason PRIV Check SAP memory problems due to extended memory or roll

46. 46

buffer
Reason CPIC Test RFC destination using tcode SM59
Work process with status complete Save the work process trace file and restart work process
Operating System Monitor ST06
High CPU load i.e. idle avarage <35%
SAP work process causing the high CPU
load?
SM50 SM66 Check ABAP trace using tcode SE30
Database processes causing high CPU
load?
ST04 Check expensive SQL statement
External processes causing high CPU
load?
Postpone the process to off peak hours
File system cache >10% of RAM Reduce file system cache
SAP Memory Configuration Monitor ST02
SAP extended memory >80% Enlarge the SAP extended memory
Individual users consuming a lot of
memory
Check user action
Many buffer swaps Enlarge the related buffer
ztta/roll_first >1024 ztta/roll_first=1
Table Access Statistics ST10
Invalidations for buffered tables If required deactivate buffering
Large buffer size for buffered tables If required deactivate buffering
Many rows affected for buffered tables If required deactivate buffering
Many total ABAP processor requests for non-buffered
tables
If required activate buffering


SAP Administrator Daily Activities
199. Check that all the application servers are up:
SM51  SAP Servers
SM04/Al08  Logon Users
200. Check that daily backup are executed without errors
DB12 Backup logs: overview
201. SAP standard background jobs are running successfully. Review for cancelled
and critical jobs.
SM37 Background jobs--- Check for successful completion of jobs. Enter * in
user-id field and verify that all critical successful jobs and review any cancelled
jobs.
202. Operating system Monitoring
ST06
203. Extents monitoring
DB02 Database monitoring--Check for max-extents reached
204. Check work-processes(started from sm51)
SM50 Process overview-- All work processes with a running or waiting status.
205. Check system log
SM21 System log-- Set date and time to before the last log review. Check for
errors ,warning, security, message-bends, database events.
206. Review workload statistics
ST03 Workload analysis of <sid>
ST02 tune summary instance
207. Look for any failed updates
SM13 update records
208. Check for old locks
SM12 lock entry list
209. Check for spool problems
SP01 spool request screen-- check for spool that are in request for over an hour.
210. Review and resolve dumps
ST22 ABAP Dump analysis

47. 47

211. Checking .trc file in SAP trace directory for block corruption on daily basis.
C:\ORacle\sid\saptrace
212. Archive backup
brarchive -f force -cds -c
Insert the archive backup tape
213. Review NT system logs for problem
NT system log- look 4 errors or failures
NT security log- failed logon 2 sap servers
NT Application log -look 4 errors or failures
214. Tcodes used for Daily System Monitoring
After running daily system monitoring transaction, what should we check for:
In ST22 look for the core dumps if any and report to the respective consultants and
try to know why it happened.
In SM21 try to check for errors.
In SP01 try to see if any spool jobs have failed.
In ST02 look if any swaps are happening, swaps are not good for performance.
In ST04 look for Database alert logs and Performance.
In ST03 look for ratio hits.
In SM59 look for connectivity testing, if there are other systems also connected to
your SAP R/3 system
In DB13sm37 look for any cancelled scheduled job and take action appropriately.
In SM12 look for any pending locks from the previous days.
In SM13 look for any hanged updates, or updates pending for long or updates in
PRIV mode.
215. UNIX commands used for SAP administration:
stopsap/startsap for stopping/starting SAP+ DB, stopsap r3/startsap r3 for
stopping/starting R3
Cdpro for checking the profiles path SAPMNT/<SID>/profile
Cdexe for checking the kernel folder
find . -name filename -print for checking the file in the present directory
dpmon pf= <Instance profile path>, jcmon pf=<instance profile path>
df -k, bdf for checking all file system usages; df -k ., bdf. for individual file usages
ls -lrt for listing of files according to the date modified
du -a | sort -k 1n,1 for sorting the files in a recursive manner.
rm < file> for removing file, gzip <file> for zipping the file.
Ps -ef is to check the how many running process and Kill any running process
gunzip to unzip file
tar -xvzf file name to run the zip folder of file content
mv move from one path to another
Rf remove forcifully any file
du -axm | sort -m | more


Upgrade the UNIX Kernel

1) What is Kernal
2) How to Upgrade SAP Kernal
3) Applying SP4 to Windows 2000 Server

216. Update SAP Kernel in UNIX based
1. Login as root
2. Make new backup directory
1. cd /
2. mkdir SIDkernel_10102007
3. Create latest kernel backup
3. cp -pr /sapmnt/SID/exe/* /SIDkernel_10102007
4. Compare the original kernel and the backup
4. du -sk /sapmnt/SID/exe/ à 840413 /sapmnt/SID/exe
5. du -sk /SIDkernel_10102007 à 841992 /SIDkernel_10102007
5. Make new shadow kernel directory
6. cd /
7. mkdir newkernel_175
6. Copy the new downloaded kernel files into /newkernel_175
7. Unpack the new downloaded kernel in folder /newkernel_175

48. 48

8. SAPCAR -xvf SAPEXE_175-20000221.SAR
9. SAPCAR -xvf SAPEXEDB_175-20000223.SAR
8. Login as sidadm
9. Stop the SAP System
10. stopsap
10. Stop saposcol
11. saposcol -k
11. Login as root
12. Go to the current kernel directory
12. cd /sapmnt/SID/exe
13. Copy all extracted support packages into this folder
13. cp -pr /newkernel_175/*/sapmnt/SID/exe
14. Copy back the original file saproot.sh into this folder.
14. cp -p /SIDkernel_10102007/saproot.sh /sapmnt/SID/exe
15. Go to the current kernel directory
15. cd /sapmnt/SID/exe
16. Then run: ./saproot.sh SID
16. Login as sidadm
17. Start the saposcol service
17. saposcol
18. Start the SAP system
18. Startsap
217. Applying SP4 to Windows 2000 Server
You need to download a newer SAP kernel. You will need an OSS ID and
password to access http://service.sap.com/patches. And you will need to know
what R/3 version, database, and OS you currently use.
Once you are at the patches website, you will need to click in the navigation tree:
R/3 -> R/3 + ?Release number? -> Binary patches ->
SAP Kernel + ?Release number? + 32-Bit -> NT/I386.
Download everything from the database section and everything from the database
independent section.
One of the files you downloaded should start with SAPCAR and end with a *.exe.
Rename this file to SAPCAR.EXE and place it in the c:\winnt\system32 directory.
Go to \usr\sap\<SID>\SYS\exe\run and backup the entire directory to some other
directory -
I usually create a \usr\sap\<SID>\SYS\exe\backup_run directory. Make sure SAP is
down, the database is down, the TNS listener is down, and the SAPOSCOL is
down before you do this.
Uncompress all the files you downloaded by opening a DOS box and typing:
SAPCAR -xvf <file name>.CAR
All files ending with .SAR or .CAR must be uncompressed. All the extracted files
need to be moved to the \usr\sap\<SID>\SYS\exe\run AFTER that directory has
been completely backed up.
Once everything has been downloaded, uncompressed, and moved into the exe\run
directory, you can start the SAPOSCOL, the listener and the database services
again. And then you should be able to start SAP. If there are any application servers
for this database instance, the SAP software will update those kernels on startup.
If the SAP instance STILL does not come back up, you can take down everything
again and restore the exe\run directory with your backup copy. Nothing will have
been damaged.

Support & Packages
1) SPAU, SPDD & SNOTES
2) How to Patch SAP J2ee Stack
3) How to Patch SAP JAVA Applications

218. SPAU and SPDD
Transaction SPDD is based on the Release Level imported during an upgrade.
During the upgrade process there may gave been Data Dictionary changes that
need to be reconciled prior to the completion of the upgrade process. SPDD is used
to correct these objects which will then create a transport to be used during the
Upgrade progression process to QA and Production.
SPAU on the either hand is used to reconcile repository objects that have been
modified by either the customer, SAP or an SAP partner. So basically the functions
of transaction SPDD are identical to that of SPAU.

49. 49

SPAU - is used for Repository Objects Upgradation.
SPDD - For Data Dictionary Objects Up gradation
219. What are SNOTES ? How to apply them in SAP ?
The name of the transaction is SNOTE. A "note" in general is a hint,
documentation, error/bug description and may contain code corrections, that are
applied with the transaction SNOTE.
220. What is OSS ?
OSS is the old name of the nowadays "sapnet" which contains everything you need
to run SAP a program, patches, installation/upgrade documentation etc.
221. What is the correct use of SPAM, SAINT, SPAD and SPDD transactions. When
should we use each?
SPAM is for installing support packages, SAINT is used to install new addons.
SPAD is for creating printers (I assume you meant SPAU) and SPDD is for
adjusting modification to dictionary objects.
222. Is it possible to update Support Release packages from OS level?
No - you can import them but the full process will require additional steps the tools
"tp" and "R3trans" are not aware of. The way is to use SPAM - but SPAM has the
possibility to schedule those imports in the background.
223. How to Patch SAP J2ee Stack ?
Read the release notes of packages and do the home work (very Important)
2. Download the Support Packs from the SAP Market Place
2.a. CTRLSAPDBnn_0-20000nnn.SAR
2.b. J2EERTnn_0-20000nnn.SAR
2.c. J2EERTOSnn_0-20000nnn.SAR
2.d. SAPINSTnn_0-20000nnn.SAR
2.e. SAPCAR (optional, but necessary because what you have might not be the
latest)
3. Create a Temporary File System, and
4. Extract SAPINST* and CTRL* SAR Files
5. Extract OS Independent (J2EERTnn_0-20000nnn.SAR) and apply First and then
extract the OS Dependent Files and apply. The Order is important.
6. J2ee Engine patching would either be required to be done by sapinst or by SDM
or JSPM tools. The details will be mentioned in the release notes.
7. First patch the Central Instance, when you run the sapinst
a. The patching should be done first for the Central Instance
i. The Option “Import Support Package nn”, when you run the sapinst.
2.
b. Only then patch the Dialog instance
1. Choose the option “Support Package nn – Dialog Instance Update”
6 Restart the j2ee engine.
7 Check the status from the URL http://hostname:javaport/ -> “System Information”
224. How to Patch SAP JAVA Applications ?
This is deployed using the tools SDM.
(/usr/sap/SID/instance/program/RemoteGui.sh) The default password for the SDM
tool is “sdm”. In Offline Deployment, the Java instance has to be stopped before
SDM is started while in online deployment it can be deployed online.
Sometimes the files come with the extension filename.sca.zip just rename the file as
filename.sca (or sda) and then deploy.
JAVA Application Server sometimes requires SAPINST tool to apply the patches,
Then
1. Stop all instances of SAP except the CI

50. 50

2. Deactivate all server process except one (server0 should alone be active)
3. Make the instance in SAFE mode from Config Tool.
4. Start Patching using the sapinst tool, possibly by keeping the instance in SAFE
Mode.
5. Start Patching the Java application in CI.
6. Start Patching applications for other server nodes.

Utilities- DPMON
225. DPMON
Dpmon: This tool allows to checks SAP’s process & to find out which one is
killing the performance . Especially useful when it is possible anymore to log to
your system.
Displays parts of the system without login.
Displaying the Queue Statistics
226. Monitoring SAP work processes via OS command
These are examples using Solaris and windows environment.
On Windows:
E:
cd E:\usr\sap\ser\sys\profile
dpmon pf=CRD_DVEBMGS01_JKTGRHXSAPC1
(execute "dpmon pf=SID_hostname_SYSNR")
On Solaris:
cd /sapmnt/EXX/profile
dpmon pf=EXX_DVEBMGS01_sapprod
Dpmon has several functionalities the same as transaction SM50 via SAPGUI.
227. Sample output for dpmon

228.
With dpmon we can stop workprocess, kill workprocess, or enable restart flag.