SAP Administrator Daily Activities

SAP Administrator Daily Activities

SAP DAILY ACTIVITIES

1] Check that all the application servers are up:
sm51 SAP Servers
sm04/al08 Logon Users

2] Check that daily backup are executed without errors
db12 Backup logs: overview

3] 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.

4] Operating system Monitoring
st06

5] Extents monitoring
db02 Database monitoring--Check for max-extents reached

6] Check work-processes(started from sm51)
sm50 Process overview-- All work processes with a running or waiting status.

7] 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.

8] Review workload statistics
st03 Workload analysis of
sto2 tune summary instance

9] Look for any failed updates
sm13 update records

10] check for old locks
sm12 lock entry list

11] Check for spool problems
sp01 spool request screen-- check for spool that are in request for over an hour.

12] Review and resolve dumps
st22 ABAP Dump analysis

13] Checking .trc file in SAP trace directory for block corruption on daily basis.
C:\ORacle\sid\saptrace

14] Archive backup
brarchive -f force -cds -c
Insert the archive backup tape

15] 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

Tcodes used for Daily System Monitoring

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 connectivety tesing if there are other systems also connected to your SAP R/3 system

In db13 look if the jobs have run successfully.

In sm37 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.

Monitor and Administrate 4 SAP Systems

Monitor and Administrate 4 SAP Systems

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.

This should help you:

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 (only the current R/3 System can be monitored) to (all R/3 Systems defined in RZ21 can be monitored). Save the changes.

It will help you monitor & use spome other activities centrally.

Brief Description About SAP Basis Implementation

Brief Description About SAP Basis Implementation

Please give a brief description about implementation process carried out.

There is no standard Implementation process, it purely depends on which methodology person have adopted for implementation. I will give you broad view of implementation project... I am just starting from sizing of the servers ...

1. Identify the no of users and type of users

2. Design the technical system landscape of servers

3. Do the sizing based on users, documents created.

4. Convert your sizing requirement in to Hardware requiremnet

5. Consider the backup procedure also

6. Then start with the setup of development landscape

7. Define client strategy, transport strategy, User management.

8. Fix the support package levels.

9. Tune the system for performence

10. set up the QA systems

11. Define client copy strategy

12. Setup the PROD systems

13. Apply for Pre Golive report

14. Monitor system of db load

15. Apply post golive report