a step by step manual guide with screen shots_ sap basis - daily check list

3/10/2014 HOW TO SAP - A STEP BY STEP MANUAL GUIDE WITH SCREEN SHOTS: SAP Basis - Daily check list

http://howtosap.blogspot.in/2007/12/sap-basis-daily-check-list.html 1/7

HOME

SAP Basis - Daily check list

Basis perform health check daily on the system. Below are the activity most

command check list activity.

SAP Logon Connection Test

1. Double click on all below instance to check if you are able to login.

2. If login were successful, this means server is alive and has no connectivity issue. A new

screen will pop up. See below

Blog Archive

2013 (2)

2012 (5)

2011 (88)

2010 (1)

2009 (17)

2008 (20)

January (20)

How to

Implement

support

packages

Execute

SPAM. Ch...

Step by step

how to

create a

batch file to

replace...

Steps by step

to query

user with

certain

plants us...

Find Role

inside a

Composite

role

Type of

processing

in SAP -

Online and

Batch

Step by step to

create new

job using

SM36

How to

manage

jobs from

AuthorizationTRANSPORTmssql 2008 R2oracle stms unixJOB SPOOLinstallation linux sap

gui sapcar

Search

Latest Blogger Templates

Webdynpro - User session (HTTP/SMTP/..)

closed after timeout

Install new add-on or plugin with SAINT

HOW TO SAP - Perform system trace via ST01

How to configure Sap Logon 720 to update

from server

HOW TO View all parameter in a system with

report RSPARAM

HOW TO SAP - A STEP BY STEP MANUAL GUIDE WITHSCREEN SHOTSA STEP BY STEP MANUAL GUIDE WITH SCREEN SHOTS

Subscribe:

Database

Download Support Pack

EDI IDOCS

PERFORMANCE SPAM

ST03 SUPPORT

PACKAGES configtool

expensive sql grc java

certification abap java

error livecache log

backup password sap

license security solman

sql command visual

admin ABAP AISUSER

BASIS BDLSS BDOCS Batch

CUA SYSTEM EP License

Failed to load administrator

rule f ile GRC support pack

upgrade IGS ITS JOB

SAP_REORG_SPOOL

Master Data New s

Processing RSPARAM

RSPO0041 RZ10 RZ11

SAINT SPID kill Snote

763789

TH_SET_AUTO_LOGOUT

Transaction Profile UME

UPDATE USER

MANAGEMENT USR40

Virtual Admin Window s

2008 activity monitor add-on

authorization trace bex

analyzer big transport truck

change main login screen

tex client copy color

command connectors create

database delete developer



3. Now you are ready to perform the next activity

DB12/DB13 Create and Check backup status for DB2

1. On the command field, key in DB12 and below screen will be displayed. It shows the

summary of the backup status.

2. On command field, enter DB13. This T-code is used to perform backup. You can also

check the backup status.

3. In DB13, select a desired cell which you plan to perform your backup. Double click on

the cell

4. Choose Full database backup to device

5. Backup mode: Offline

6. Device directory: d:backup (this is just a folder which your backup could be stored)

7. Below is a sample picture.

the Job

Overview -

SM37

Type of

Standard

Jobs in SAP

system

User: Creating

User in SAP

STMS - Steps

to perform

transport

News: SAP is

still doing

great!

Deleting

Master Data

- user claim

and vendor

list

Procedure

Cache Hit

Ratio for

database

SAP Basis -

Daily check

list

What is

Authorizatio

n?

How to

troubleshoot

authorizatio

n issue

Job: Error

Print

parameters

for step 1

could not ...

ABAP DUMP:

MESSAGE

TYPE X

BDOC and

IDOC - What

are they?

Steps to

troubleshoot

IDOCS error

status 51

and st...

key estimate I/O cost expiry

date export folder frontend

incorrect (Error Sending

Data) java java performance

by changing log levels jspm

kernel lc10 license lock user

log configuration log ful

maintenance migration

monitor netw eaver nw a

nw di object

outofMemoryError output

device type parameter

permission pfcg plugin

popup printer purge

putserlet register server

program renew portal

certif icate report restart

restore retention period rfc

rfcexec sap logon 7.20

sapgui saplogon

saplogon.ini scc8 scc9 sccl

scot script search printer

host sent message server

settings shd0 sm59 snc

snote sost sound

notif ication spad st01 stad

step by step installation

guide stms hang stop

transport system trace table

program table tcode tcpip

connection transport button

disable uncar unlock user

upgrade upload protected

area user session user type

vv33 w eb dispatcher

w ebdynpro timeout xml

configuration f ile



DB02 Check Database size for DB2

1. Use DB02 to check DB size

2. Database current size (GB) is Total DB size - Free space

SM50 Check if instance is running on all servers

1. All work process is either running or waiting and none are stopped except CPIC



(interprocess communication)

2. Make sure not all dialog work process are used up, otherwise other user cannot make

any transaction.

3. Alternatively you can use SMLG to check whether system respond is good or bad.

RZ20 Check filling degree of spool used numbers

1. Click on SAP CCMS Monitor Templates

2. Click on SPOOL System

3. System Wide > Spool > SpoolNumbers > UsedNumebrs

4. If value greater then 80% in spool numbers - will lead to system wait until spool

reorganisation is done



SM13 Check if update is active

1. Enter SM13 and make sure UPDATE SYSTEM STATUS : Update is active.

2. Make sure client = *, User =* and status = All, Press F8 to execute

3. Click on any entry with error

4. You may have to dig deeper (SM21, ST22, DB02, etc) and work with functional expert to

resolve the issue

SM12 Check lock entries with long duration

1. Type SM12 in command field

2. Client = *

3. User name = *

4. Click list.



Its important to notice all values under the time column show the current time. Jobs with

earlier date should be immediately investigated. These locks are problematic because it

prevents access or changes to the locked records.

ST22 Check and analyze SAP ABAP short Dumps

An ABAP dump (AKA short dump) is generated when a report or transaction terminates as

the result of a serious error. The system records the error in the system log. SM21 and

write a snapshot (dump) of the program terminiation to a special table (SNAP). This

transaction can also be called from the system log (SM21). ABAP dump is used to analyze

and determine why the error occured and take corrective action

(no print screen - currenly my SAP has no Runtime errors)

Once Runtime errors is displayed

1. Double click on the entries

2. A detail analysis on the error will be displayed

3. Dump contains the follow information

- Why program has been terminted

- What caused the program termination

- Where in the program code the termination occured

- What you can do to correct the error

- The values of the relevant system fields when the program terminated

- The calls or events that was active when the program terminated

- Any other programs that are affected

SM21 Check and analyze SAP system log for any critical log entries (hourly)

1. Type SM21 into command field

2. Enter the relevant details and execute

3. Look for unusual entries.



HOW TO CHECKSIZE OF A CLIENTNote 118823 - CC-ADMIN: Size ...

Job: Error Printparameters forstep 1 could not befound

Steps totroubleshootIDOCS error status51 and status 68

Newer Post Older Post

4. Double click on the entries for more information

Lastly, a few more userful transaction

1. SM37 - Check and analyze failed background jobs

2. SP01 - Check SPOOL for errors

3. ST06 - CPU & Memory Utilization

4. ST03 - Check for database performance and response time

5. ST11 - Check for core file entries

You might also like:

Linkwithin

Labels: BASIS, PERFORMANCE

Home

Copyright (c) 2011 HOW TO SAP - A STEP BY STEP MANUAL GUIDE WITH SCREEN SHOTS. Designed by Tech Blogger Template

Web Hosting Review s, Government Jobs in India, Students stock photography

a step by step manual guide with screen shots_ sap basis - daily check list

Documents