Not going into debugging mode..

[Former Member]

Hi experts..

One strange problem......

i had given break-point into the program ...(ALV report.)..but its directly showing the output..

I had cross checked everything whether i had given it at right place or not..

but its not going into debugging mode.. i logout and again login..then also...its not going...

i had written break-point also...but no use..

please help as i had to debugg it.....

[Former Member]

Hi,

I suggest you to use several break-point.

And especialy one at the begining of the treatment.

In my opinion, you break-point is not situated in the treatment code.

Erwan

[Former Member]

I think the control of the program is not going to the point where you have added break-point.

Can you check debugging right from the start of selection or so..

[Former Member]

i think in which line you are giving the breakpoint that is not executing so you are getting the output directly.

put /h in command box and debug that .

regards

shiba dutta

[Former Member]

Hey,

I too this issue.

1) Request your BASIS admin to enable debugging for ur id.

2) Goto Utilities->Settings->ABAP Editor->Debugging and make sure Debugging has been enabled.

Reward points if useful...

Cheers,

Sam

[Former Member]

Hi,

After writing the values in the selection screen, switch on debugging.

Try this way.

Hope it works.

thanks.

[Former Member]

Hi all

I had tried by giving break-point at START of selction but...dont kno..why...its not going into debugging mode..

[Former Member]

Hi!

Before you are starting the run your riport with F8, enter the /h code into your transaction field. This will turn on the debugger mode.

Regards

Tamá

[Former Member]

Hi,

Ensure that you have placed break-point in proper place. I think u have placed the bp on statement which is never executing.

that code area is not execting..

[Former Member]

Hi,

The only case when breakpoint does not work is:- In case of field-exits otherwise if bp is added at a proper place it should stop there.

Thanks

Rahul

[lhardin]

All these years later, this continues to be an issue. This happens frequently enough that it really should be addressed by SAP.

Make sure your code which contains the break-point is on your screen or that your transaction is appropriate ( se38/s24) which will enable context menu for Utilities.

Go to: Utilities=>Settings, Select ABAP Editor tab, then the Debugging sub-tab. In the middle container named "ABAP Debugger", select Classic Debugger. Press Enter.

Execute the code with the break-point. You should hit the break-point now. If not, put BREAK-POINT in the first executable line of your code and repeat. Voila, the break-point will be hit.

I have found that it happens when the debugger is set to "New Debugger". Switching to "Classic Debugger" seems to fix the issue of being able to hit breakpoints. Once that occurs, you can switch back to "New Debugger".

As I do not keep my settings to use the classic debugger, I haven't encountered this problem with it. If you do, maybe switch to new debugger will fix that?