debugging

[Former Member]

Hi,

During creation order runtime error occurs .this is upgrdation testing of the abap code. what my question is:

1.how to debug the code where it goes for dump

how to check the point where it goes into dump.

2. can u explain me the placing of break points while creating the order.

3. what the function keys f5, f6, f7, f8 will do?

when we have to use that function keys .

4. finally how to find the solution by debugging.

please explain this details by your pratical experiance not by theoritically.

Thank u in advance.

[Former Member]

If the program want to DUMP, u can that using transaciton ST22. Execute that transaction and select the dump left hand corner button. It will take u to another screen. Press the ABAP Editor button and check the place the DUMP as happened.

/h to debugg on.

break <User ID>. Will stop at desired place.

Function F5 - to go step by step

F6 - to skip a perform

f7 - to skip a include

f8 - to execute

In the debugging mode u can the value to the fields. So that u can check whetther u have written a correct code or not.

Check the link

http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

Regards,

Prakash.

[Former Member]

Hi Srisaihari,

<b>>1.how to debug the code where it goes for dump

>how to check the point where it goes into dump.</b>

Click on DEBUGGER button then it willl navigate to you to the statement where dump is causing.

Clik on SAVE button here and rerun the program and based on dump case do changes accordingly.

<b>>3. what the function keys f5, f6, f7, f8 will do?

>when we have to use that function keys .</b>

Following buttons are used to navigate through the program and debugger.

<b>Single step(F5):</b>Executes a single program command.

<b>Execute(F6):</b>Similar to the single step, but when a program calls a subroutine, it executes the whole subroutine unlike single step.

<b>Continue(F8):</b>Executes the program until it is finished or until it finds next breakpoint.

<b>Return(F7):</b>Allows for executing the program instruction up to the end of a routine and stops in the line of code where the subroutine gives back control to the main program.

<b>>>4. finally how to find the solution by debugging.</b>

Click on LONGTEXT button on dump screen, then it will navigate you about the details of dump. You can have a look on ERROR ANALYSIS to get something about the cause for dump. The SOURCE CODE part will give which statement is causing dump. It will have mark >>>> at LINE.

Thanks,

Vinay