ABAP debugger begins before my application program

[Former Member]

I'm in ECC at a new organization and previously was on 4.7.

At the new site, when I'm in SE80 and I execute->debugging the application program that I've written, the debugger doesn't start at my program, but instead at a lower-level (SAPLSDBT--LSDBTU01). I don't have system debuggin turned on.

If I set a breakpoint in my app program, then it stops at my breakpoint, but I've not seen this behavior before.  Since I'm new to a new platform, I think I must have some setting turned on (I checked SETTINGS--> DISPLAY AND CHANGE ALL and nothing is checked in that box).

I'm using the classic debugger for now, until I can learn the new debugger.  Any idea what it stopping the debugger at this entry point?

[Former Member]

Hi ,

If lower level of debugging start please press F7 it will stop inside your report while debugging mode go to Breakpoints Tab->Inside two tabs available Breakpoints/Watchpoints Click on breakpoints table see any debug point is set there excluding that you have set in your program then select the column delete it and save it.Hope it will solve the problem.

Ravi Shankar L

[Former Member]

Hi Jeremy,

Problem is weird, try

1) Logging out and logging in again - if issue persists i assume it is some basis setting

2) Go to Classic/New Debugger and delete all breakpoints/watchpoint(if any) and re-execute the se80.

BR,

Ankit.

[Former Member]

To get around this issue, you need to do F7 as suggested by Ravi Shankar.

Reason behind your program not executing directly is shadow system check done by FM UPG_IS_SHADOW_SYSTEM.

Shadow system is like a copy of existing system which is useful during upgrade activity to minimize downtime or resource consumption.

Visit SAP Upgrade Help for further information.

[Former Member]

Hello and thank you for these replies.  I apologize for my slowness getting back to this thread. My e-mail for the SCN changed from the old organization to the new.  Upon Execute-->Debugging from SE80 (i'm using the new debugger now) the debugger first stops at the Report statement, but then an F5 takes me to the lower-level code.  I *can* F7 back up to my application program/report but there doesn't seem to be any breakpoint set in the tab that you mentioned.

[Former Member]

Hi,

That breakpoint is created by me manually while debugger is on..Just put breakpoint at your first line of code in the report after low level code displays please press F7,Hope it will work for you.Thanks.

Regards,

Ravi Shankar L

[Former Member]

Hi Ravi.

Thanks again for the reply.  I can use F7 to get back up to the application program from the lower-level, I was just hoping there was a setting that I could configure that would prevent the debugger from going to the lower-level in the first place.  I will research it more with the link that Manish Kumar posted above as well as asking our Sys Admins.

Thank you all.

Jeremy H.