Skip to Content
avatar image
Former Member

External Breakpoints

Hi Everyone,

I am not sure if this should be posted in the ABAP forums or Basis forum. I finally decided to post in the ABAP Forums as i thought ABAPers would be having a better idea of what the issue is .

I need to debug a function module. I am not sure what calls this function module, the only thing I am sure of is that it is called when clicking a button in BSP. Previously, I used to debug Webdynpro code by using "External Breakpoints". However, I was not able to find any option to enable external breakpoints.

I was just wondering, if the external breakpoints option could be restricted via Basis authorizations. If so, how could I enable them. Also, Also, is there any way i can get the debug screen after i run the BSP application.

Thanks in advance for any help and suggestions.

Cheers,

Mz

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jan 18, 2011 at 07:34 AM

    Hi All,

    I have been trying to resolve my issue but no avail. Here are a few things that I have found out.

    1. I got SAP_ALL profile for my user ID. So, it could not be an issue with authorization.

    2. When I placed an infinite loop and tried to debug via SM50, i got an error "Error while retreiving data from the server. The Server Message is : RFC Debugging only possible with dialogue user, error key : RFC_ERROR_SYSTEM_FAILURE"

    My user ID is a dialog user in the system. So cannot be that.

    3. In Utilities-> Setting-> ABAP Editor -> Debugging, I have Set my User ID, checked the Actv. checkbox and unchecked the IP Matching Checkbox.

    I might be wrong but, could this issue be caused due to the USER ID specified in the RFC. Right now the HTTP Connection to external System is specified with a user ID ALEREMOTE.

    Best Regards,

    Mazin

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      @ Arani : Thanks for your suggestion, unfortunately, we are currently on SAP_BASIS 640 and not 7 😔

      @ Matt : I think that i made a big blunder of asking something very very stupid. 😔

      Guys : Here is the story after my detailed (and painful) analysis and I am not too proud of myself.

      1. External debugging still does not work. We have no clue as to why. Neither me nor any of My ABAP, Basis colleagues know whats wrong. We ruled out authorization issues, because we tried even after assigning SAP_ALL.

      2. I tried the workaround suggested : Place an infinite loop at the point at which debug is required and then debug from SM50. This worked like a charm and i was able to debug until i reached the point where a FM was called with a parameter CPR_LOGSYS.

      3. (Here comes the really stupid part) CPR_LOGSYS was an RFC destination. We were actually calling a FM of another client, so obviously we were not able to debug.... even though both clients are in the same server...

      4. Since workaround worked, i was able to find most of what i was looking for...

      Please post comments if you have any. I would be closing this thread tomorrow. 😀

      Cheers,

      Mz

  • avatar image
    Former Member
    Dec 27, 2010 at 10:27 AM

    Hi,

    even you can try to debug the BSP in R/3 also.

    try this way..

    First put the break point in the FM and next ..

    go to se80

    slect BSP application

    and select the program and double and execute and enter the value then the Break point will trigger.

    Prabhudas

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      1)when executing go with /h and start the debugging mode...

      2)Break-Points and Break-points at function module,and enter ur function module name.. and press F8

  • avatar image
    Former Member
    Dec 29, 2010 at 06:55 AM

    Create a shortcut for debugger.

    Procedure to create shortcut.

    Click on Generate shortcut button.

    Create New SAP shortcut pop up window will appear.

    Tile : Debug.

    Type : system command (select the system command option)

    Command : /h

    The remaining options are default.

    Now a shortcut will be created in SAP Logon pad Shortcut tab

    You can drag that shortcut Debug to your desktop a shortcut is created in desktop.

    Now you can drag that Debug to any window of SAP you wish to Debug.

    You can also place that Debug on a pop up window also.

    Add comment
    10|10000 characters needed characters exceeded

    • There is a SAP note that gives a few things to check to trigger external debugging - unfortunately I don't know the note number. :}

      One thing that often works for me is to go to transaction SICF. Hit the execute button then navigate to Edit->Debugging->Activate Debugging. Click the Activate button.

      Cheers

      Graham Robbo