27.04.2013 Views

SAP Basis

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ADM100 Lesson: Trace Options<br />

Lesson:<br />

460<br />

Trace Options<br />

Lesson Duration: 45 minutes<br />

Lesson Overview<br />

In this lesson, you will learn about the different trace options in the <strong>SAP</strong><br />

system. You will perform and evaluate a trace yourself.<br />

Lesson Objectives<br />

After completing this lesson, you will be able to:<br />

• List various trace options<br />

• Perform simple traces in the <strong>SAP</strong> system<br />

The participants are to learn about the most important trace options and<br />

to be able to use them practically.<br />

Business Example<br />

An unexpected, reproducible error situation is occurring in your <strong>SAP</strong><br />

system. As a member of the system administration team, it is your task to<br />

find the cause of the error.<br />

Introduction<br />

You can follow the process of various operations in your <strong>SAP</strong> system<br />

with trace functions. This allows you to monitor the system and isolate<br />

problems that occur. There are two types of trace: the performance trace<br />

and the system trace. You can also use developer traces and the system log<br />

to correct problems. The following trace options exist in the system:<br />

• System log<br />

• Dump analysis<br />

• System trace<br />

• Performance trace<br />

• Developer trace<br />

You can use the System Log (transaction SM21) to detect and correct errors<br />

in your system and its environment. <strong>SAP</strong> application servers record events<br />

and problems in system logs. Every <strong>SAP</strong> application server has a local log<br />

that contains the messages output by this server.<br />

2003/Q3 © 2003 <strong>SAP</strong> AG. All rights reserved. 535

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!