ABAP Debugger does not stop with break point

[gilberto_parga]

Hi guys.

I really don't understand why the ABAP debugger is unable to stop in the breakpoints I set in an include. When I go to VF04 transaction and I select some delivery return as SD document (and I check "delivery-related" box), I can see that data is fetched from VKDFS standard table. The row(s) are set in an alv report. If all is right, when user presses the Save button, the standard program does the billing and deleted the row(s) selected from VKDFS. I am able to set session break points in many code excerpts that are being used by VF04 (like if you set a session BP in the COMMIT WORK instruction that appears in SAPLV60A -> LV60AU05, almost finishing the FM RV_INVOICE_REFRESH - this COMMIT WORK deletes VKDFS physically) and debugger actually stops. Due some troubles with some kind of returns, I should identify the excerpt that indicates the deletion from VKDFS using VF04. And I found with SQL Trace that it happens in the include LV05IF5I. But if I set session breakpoints there, ABAP debugger does not stop. I know this LV05IF5I include has a lot of enhancements were break points cannot be set, but I set my BP in the "normal" code, out from enhancement sections and spots. The debugger does not pass on my break points there anyway.

The component version is SAP ECC 6.0. Any suggestion or idea to debug LV05IF5I is welcomed. Thank you.

[Former Member]

May be you can try with System debugging 'ON'.

[rathishr_nair]

Hi Gilberto,

Please ensure that you have checked the option "Session break point active immediately" in the ABAP debugger settings.

Thanks,

Rathish

Edited by: Rathish R Nair on Mar 23, 2011 6:20 AM

[paul_bakker2]

Hi,

It's possible that this ABAP code is being called in an asynchronous V2 update (ie a separate session that is run later), and so it will not stop in debug. I see that the code refers to the updating of indexes, which is typical V2 fodder.

Also, have you tried setting an 'external' breakpoint (in SE38, use the icon that shows stop sign with a little man next to it) ?

hope this helps

Paul Bakker

hanabi technology

[Former Member]

Hi Gilberto,

if you set a break-point and system can't stop there, then you can see a system log entry (SM21). Can you see system log entries regarding your break-points?

If not, then I think your break-point can't be reached for delivery.

The include is for all orders, deliveríes and billing documents I think.

You can show us the code part where you want to set the break-point!

Regards,

Klaus

[Former Member]

HI,

Please set a external break point and check

[gilberto_parga]

Patije Bakker: your advice was correct, the include LV05IF5I is managed asynchronously. I investigated and I set a feature in the ABAP debugger I did not know: when "normal" debugger appears at any break point, you should go to Settings -> Display / Change debugger settings and activate the "Update Debugging" checkbox in Debug modes. Then, when the program "terminated", a message appeared with text "Update debugging has been launched" and another debugger session was shown. The debugger stops in the include LV05IF5I if i set an external break point there.

Thank you all for all your comments. This question has been answered.