Basis T Codes

Basis T-Codes
Administration
AL11 Display SAP Directories
OSS1 Logon to Online Service System
SARA Archive Management
SCC3 Copy Analysis Log
SCC4 Client Administration
SCC5 Client Delete
SCC7 Client Import Post-Processing
SCC8 Client Export
SCC9 Remote client copy
SCCL Local Client Copy
SICK Installation Check
SM01 Lock Transactions
SM02 System Messages
SM04 User Overview
SM12 Display and Delete Locks
SM13 Display Update Records
SM14 Update Program Administration
SM21 System Log
SM35 Batch Input Monitoring
SM50 Work Process Overview
SM51 List of SAP Servers
SM56 Number Range Buffer
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SM66 System Wide Work Process Overview
SAINT SAP Add-on Installation Tool
SPAM SAP Patch Manager (SPAM)
SPAU Display modified DE objects
SPDD Display modified DDIC objects
ST11 Display Developer Traces
ST22 ABAP/4 Runtime Error Analysis
SU56 Analyze User Buffer
ALERT MONITORING
AL01 SAP Alert Monitor

AL02 Database alert monitor
AL04 Monitor call distribution
AL05 Monitor current workload
AL16 Local Alert Monitor for Operat.Syst.
AL18 Local File System Monitor
RZ20 CCMS Monitoring
CONFIGURATION
FILE Cross-Client File Names/Paths

RZ04 Maintain Operation Modes and Instances
RZ10 Maintenance of Profile Parameters
RZ11 Profile parameter maintenance
SE93 Maintain Transaction Codes
SM63 Display/Maintain Operating Mode Sets
SPRO Customizing: Initial Screen
DATABASE ADMINISTRATION
DB01 Analyze exclusive lockwaits

DB02 Analyze tables and indexes
DB12 DB Backup Monitor
DB13 DBA Planning Calendar
DB15 Data Archiving: Database Tables
JOBS
SM36 Define Background Job

SM37 Background Job Overview
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
MONITORING
AL08 Current Active Users

OS01 LAN check with ping
RZ01 Job Scheduling Monitor
RZ03 Presentation, Control SAP Instances
ST01 System Trace
ST02 Setups/Tune Buffers
ST04 Select DB activities
ST05 Performance trace
ST06 Operating System Monitor
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)
SPOOL
SP01 Output Controller

SP11 TemSe directory
SP12 TemSe Administration
SPAD Spool Administration
TRANSPORTS
SCC1 Client Copy – Special Selections

SE01 Transport Organizer
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
STMS Transport Management System
USER ADMINISTRATION
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
SMLG Maintain Logon Group
SUPC Profiles for activity groups
SUIM Infosystem Authorizations
SAP Daily System Monitoring
Daily System Monitoring:
SM51 SAP Servers :

1- Check Availability of All Servers
2- Check Process Lists for All Servers for Unusual Processes or Activities (e.g. Extra-long execution times,
too many errored processes, too many sequential reports)
SM66 Global Process Monitor:

1- Check for over-all system process utilization
2- Are Batch id's taking up too many DIA processes
3- Is one user running too many BGD jobs for the same report
4- Is one server being used heavily compared to others
SM21 System Logs:

1- Is there any repetitive errors in the system log
2- Any unusual repetitive failed login attempts
ST22 Short Dumps:

1- Except 'Time-Out' errors, is there any short dumps.
SMLG Logon Groups:

1- Check load distribution (Menu: Goto-->Load Distribution)
2- Are server response times acceptable? (< 2 sec)
3- Is user distribution even among active servers
ST03N Workload Analysis:

1- Check is daily, weekly and monthly totals are being calculated for each server
2- Check for Avg. Dialog Response Times. Is it below 2 secs
SM12 Lock Overview:

1- Check for outdated lock records
2- Verify that these lock records are not actively being used and delete these lock records if they are
obsolete
SM13 Update Records:

1- Check if the 'Update System' is active.
2- If not active, investigate what happened
3- Activate 'Update System' after fixing the problem
4- Review update records of past two days and delete if errored or obsolete
SM37 Background Job log:

1- Check if the are any critical jobs that were canceled
2- Identify/Fix the problem
3- Contact canceled job user for details
4- Reschedule if needed
SP01 Spool Request overview:

1- Check if there unusual number of errors in spool (>100)
2- Check if there are spool request with more then 200 pages
3- Should not be a need to delete any as the daily job should handle, unless too many spools are old.
ST04 Database Activity Monitor:

1- Check 'Data Buffer' and 'Shared Pool Cache' quality
2- Investigate and make suggestions to the team to improve quality of these buffers
DB02 Database Performance:

1- Check 'Current Sizes' to see if any tablespace is above %90
2- Add new datafile to the tablespace if needed
3- Check if there is space-critical objects
4- Check if there is any missing objects in DB or R/3 Data Dictionary
DB16 Database Check, Overview of message:

1- Check if there is any messages
2- Take immediate action to fix the problem
3- Notify the team if there is any parameter changes or assistance needed for Production Systems
DB24 Database Operations Logs:

1- Check if all DB Operations are executed
2- Check if any of the operations generated any errors
3- Fix the problem. Notify team if needed
DB12 Database confirm backup success:

1- Check to see that the previous backup was successful
2- If a backup is currently running check its status
3- If the last backup failed , check the reason correct and resubmit.
ST06 OS Monitor:
1- Click on 'Detailed Analysis menu'
2- Click on 'CPU' in 'Previous Hours' Group
3- Check if at any past hours is > %80
4- Notify Team if there is any such case
The Following are the transaction codes used for the System Monitoring:
SM12:
This Traction is used for Check for Lock Entries. There may be old locks still in place from transactions
that did not release, or from when the user was cut off from the Network. If any lock entries are exist then
we have to check since how long this lock existing. If, this lock existing from more than one day then we
should check that particular User is available or not (By using the Transaction Code AL08). If he is not
available then Delete that lock. Otherwise we should wait 1 or 2 Days.
SM13 :
This Transaction is used for Check for any Errors in Update Records. A failed or “Update Terminate” is an
update to the failed database. These failed Updates occurs when a user entry or transaction is not entered
or Updated in database. And we should check Whether Update is ACTIVE or not. And also we should
check any Update Records are terminated.
SM21 :
This Transaction is used to check System Logs. After hitting the traction we should goto System log-->
Chooseà All Remote System logs, and set Date and time to before the Last log review. And we should
check whether any Errors, Warnings, Security Messages, Database, Abends, Any other different Events
are there.The log is important because unexpected or unknown warnings and errors could indicate a
serious problem.
SM51 :
This Transaction is used to check that all Application Servers are UP. And also This transaction is a
central transaction from which you can select the instance to be monitor.
SM50 :
This Transaction is used to check Work Process Overview and for Systems with out Servers. Here all work
processes with a “Running” or “Waiting” State. If Batch Jobs are not Running, If all the work processes
are in use, this transaction provide a hint of this problem.
ST01 :
This Transaction is used for System Trace. By this transaction we can trace that what are the operations
performed on particular file by particular user on which dates.
ST02 :
This transaction is used for Buffer tuning or Buffer Statistics. And it is used to tune Buffer perameters of
R/3. The Buffer is important because significant buffer swaping reduces performance. Look under
“Swaps” for Red Entries. Regularly check these entries to establish trends and get a feel of the Buffer
behaviour. And in this transaction we should Maintain “Hit Ratio” is in between 90 – 100% for all , and
“Heap Memory” allocated should be “0” , and “Swaps” is 0.
ST03 :
This Transaction is used to Check Work Load Analysis of . Workload Analysis is used to determine System
performance. Check Statistics and Record Trends to get a feel for the System’s Behaviour and
Performance. Understanding the System when it is running well helps us to determine what changes may
need to be made when it is not.
ST04 :
This Transaction is used for Database Performance Analysis. This transaction provides the ability to
Monitor the Database in related to 1) In Shared Pool “SQL Area Get Ratio” should be 90 – 95% 2) In Log
Buffer Allocation Retries / Entries <1% 3) In Data Buffer “Quality” should be in 90 – 95% 4) In Sorts
Disk / Memory <1% 5) In Table Scan & Fetches “Long Table Scans” should maintain as minimum as
possible. And we should check Detailed Analysis then we should hit “Detailed Analysis menu” Button in
this screen. In that we can check Database Overview like “Exclusive Lock Waits” , “Wait Events”, “Buffer
Busy Waits”, “ File System Request”, “ Database Message logs”, “ SQL Requests”, Summery Report for all
activities, etc
ST22 :
This Transaction is used to Analyse ABAP Dumps or Short Dumps. This transaction is also used for
Analyse and Determine why the error occurred and take corrective action. It looks for an excessive
number of dumps, and also dumps of an unusual nature. A ABAP dump is generated when a report or
transaction terminates as a result of a serious error. The system records in the System Log(SM21) and
writes a snapshot of the program terminate to a special table.
DB02 :
This transaction is used to check all table Spaces and Indexes. Here we should check table spaces sizes. If
any table used space is =>99 then we should increase add the space for particular table space. And this
transaction is provides a way to examine database allocation. And this transaction is allows us to monitor
items such as: a) DB Space History b) DB Analysis By this transaction we can view Database history by
Dates and Times.
DB12 :
This Transaction is used to check database Backups. And in this we should we see successful Backups and
Unsuccessful Backups list
AL08 :
This transaction is used to Check the users on the System. This transaction displays User Ids and
Terminal Names who are currently logged on the system.
SM37 :
This transaction is used for Monitoring Background Jobs. Background are batch jobs scheduled to run at
specific time during the day. Here we should check for cancelled jobs. Here If we want to check particular
job then,we should enter the Job Name and enter User name in User name field or ‘*’ and hit execute
Button. And verify that all critical jobs are successful.

Basis T Codes

Uploaded by

Copyright:

Available Formats

Basis T Codes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Basis T Codes

Uploaded by

Copyright:

Available Formats

Basis T-Codes

AL01 SAP Alert Monitor

FILE Cross-Client File Names/Paths

DB01 Analyze exclusive lockwaits

SM36 Define Background Job

AL08 Current Active Users

SP01 Output Controller

SCC1 Client Copy – Special Selections

PFCG Profile Generator (Activity Group Maintenance)

Daily System Monitoring:

SM51 SAP Servers :

SM66 Global Process Monitor:

SM21 System Logs:

ST22 Short Dumps:

SMLG Logon Groups:

ST03N Workload Analysis:

SM12 Lock Overview:

SM13 Update Records:

SM37 Background Job log:

SP01 Spool Request overview:

ST04 Database Activity Monitor:

DB02 Database Performance:

DB16 Database Check, Overview of message:

DB24 Database Operations Logs:

DB12 Database confirm backup success:

You might also like