cancel
Showing results for 
Search instead for 
Did you mean: 

ABAP WD Debugging

Former Member
0 Kudos

Can someone please help me to turn on debugging on ABAP WD.

We recently moved to QA environment, before which I use to do the debugging in Dev without anu problem.

I go thourgh the UTILITY menu and setup debugging from there, is there something that needs to be done from Admin or basis side ?

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

vinay_baji2
Active Participant
0 Kudos

Hi Mkhan,

Apart from what Bala has said above, also do check the id present under utilities->settings->abap editor->debugging.

In some rare cases, there might have been an instance where the users text box might have some other id other then yours.

When this happens, irrespective of you setting the breakpoints, the debugging mode would open for the user id mentioned in that area.

Do look into that possibility too.

Former Member
0 Kudos

Thanks guys,

Thats exactly what I am doing, infact I don't think, or maybe I don't know, that there is any other setting which a WD developer needs to set to bring up the debugger.

Problem here is the admin/basis, I think there is also some kind of setting that needs to happen on the portal side or basis side for me start the debugger.

I don't know what I am missing apart from the settings you have mentioned.

Any help plz!

vinay_baji2
Active Participant
0 Kudos

In case you are debugging a portal running application, then also make sure that the portal is logged in with the same user through which you have set the breakpoint.

The idea with debugging a portal (in case you are not aware of you, or might have overlooked) is

1. First set the breakpoint in the wd abap.

2. Login to portal with the same credentials through which you have kept the breakpoint, and

then execute the view for which you have placed the breakpoint.

Do check if anything else basic has been missed out(like breakpoint set in which method, is the system the same etc). Ideally the debugger should run.

If it still doesnt work, then as a last resort to check the debugger, place a breakpoint in the 'doinit' method of the component controller.

All the best

Answers (1)

Answers (1)

Former Member
0 Kudos

go to utilities - settings- editor - front end editor(new)

settings-debugging - uncheck ip matching,select new debugger and check session breakpoint active immed

utilities - extenal breakpoints - activate/deactivate

then set the external breakpoints

Thanks

Bala Duvvuri