ABAP TIP -How to easily find out the point which causes error.

Chapter 102

How to easily find out the point which causes error.

Source : http://abapjoy.blogspot.com

It’s really not easy to find out the error point in standard program with debugging. There is a possibility that the error message would be contained in the message statement, but in many cases, since the error description is maintained in the message class, it’s not available to search with the error message.

There are several ways to find out the error point.

Let’s learn the easiest way.

Like below image, there is a error message after you enter the sales order number which does not exist in VA03.

 

Double-click the status bar having a error message. There will be a new popup detailed screen.

Message no. V1302

V1 means message class,

302 manes message number.

You can display the error description after selecting message class via t-code:se91.

Let’s activate the debugging add the /h in command field.

You need to create the watch point with the variable of message class and message no.

There are the 2 watchpoint created in the tab Break/Watchpoint.

IF you press the F8  icon, the program execute until it meets the message and stop at the point.

This point is where the error is occurred.

There is more simple way to find out the error message point.

It’s just that you need to use the breakpoint at features in debugger. If you just enter the ‘MESSAGE’ command, you can also find out the error point.