27.04.2013 Views

SAP Basis

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ADM100 Lesson: Troubleshooting Procedure<br />

You will run through the steps in the figure “Troubleshooting: Approach”<br />

when troubleshooting.<br />

Figure 172: Troubleshooting: Approach<br />

Isolate the problem area: First attempt to isolate the error. Where does it<br />

occur, when does it occur, and in what context does it occur? “It doesn’t<br />

print”, would be too imprecise here. “Front end printing on front end xyz<br />

does not work with any <strong>SAP</strong> system”, is more exact. If you also know that<br />

front end printing works on other front ends, you have already isolated<br />

the problem.<br />

Problem Analysis: Check the scenario to find out whether all required<br />

settings, and so on are correct. Check the application logs, the system log,<br />

and the traces (the developer traces will usually be helpful here), to see<br />

whether they provide any clues for correcting the error.<br />

Gain additional knowledge: To interpret the results from the first problem<br />

analysis, it is, of course, necessary that you are familiar with the processes<br />

and functions of the area in which the error is occurring. If your experience<br />

and your previous knowledge are insufficient, you can start a search in the<br />

<strong>SAP</strong> Notes and on the <strong>SAP</strong> Service Marketplace with the keywords from<br />

the system log or the trace files. You may find a problem solution here, or<br />

additional information that helps you find and correct the error. If you<br />

have not found any suitable <strong>SAP</strong> Notes or suitable search terms, search<br />

for composite notes for the topic area. In this case, for example, with the<br />

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

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

Saved successfully!

Ooh no, something went wrong!