Home/ Questions/Q 121065
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T03:54:39+00:00

I’m a ASP.NET and ABAP developer. For years, I used RFC’s to communicate with

  • 0

I’m a ASP.NET and ABAP developer. For years, I used RFC’s to communicate with ASP.NET using SAP .NET Connector.

During the integrated tests, sometimes we need to debug a RFC that has been called from ASP.ENT, just because the bug we are facing does not happens at SE37.

So, everytime I needed to debug the RFC, I just inserted:

IF <<CONDITION>>. WHILE 1 EQ 1. BREAK-POINT. ENDWHILE. ENDIF.

By doing so, the program gets stuck. Then I go to SM50 and debug it.

I was wondering if there is any other way of doing this, because I don’t like the idea of changing code in order to debug, or implementing some debug control functionality.

So, what do you do when you need to debug RFC’s?

Thanks in advance!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I assume you are using a fairly recent version of sap (4.7+) Do the following:

    • Get the username that makes the RFC call into SAP in ASP
    • Fire up SE37, go to the code section of your RFC
    • Look at the menu on top, click on ‘Utilities’
    • Click on Settings
    • Go for the Debugging tab
    • Fill in the username that will make the call from ASP
    • Click IP Matching (otherwise a debug session appears for every time any user makes the call)
    • Session breakpoint active immediately is nice to click as well
    • Put your external breakpoint where you need it (click the icon with the stop sign and the little man)
    • Test your ASP connector
    • The breakpoint should come into effect, a debug window will pop up
    • You might not have the authorization to do this, if it doesnt work, use SU53 to find out what you’re missing.

    This should work.

    • 0