{"id":1025,"date":"2014-07-04T14:49:17","date_gmt":"2014-07-04T13:49:17","guid":{"rendered":"http:\/\/oprsteny.cz\/?p=1025"},"modified":"2014-07-04T14:49:17","modified_gmt":"2014-07-04T13:49:17","slug":"abap-advanced-debugging","status":"publish","type":"post","link":"https:\/\/oprsteny.cz\/?p=1025","title":{"rendered":"ABAP – Advanced debugging"},"content":{"rendered":"

\"SAP\"I believe that most of you know how to debug the basic report or class methods etc.<\/p>\n

But things can\u00a0become complicated\u00a0when\u00a0debugging is needed for a backround job, RFC function module or even some user-exit which is being triggered in an update task. E.g. when you update material master in ECC using MM02, you can’t easily debug all user-exits because they’re triggered in separate process independent on session you are currently running.<\/p>\n

In this article I’d like to present several useful debugging tricks you can use in your more complex scenarios.<\/p>\n

Basic debugging<\/h2>\n
    \n
  1. Put a break-point in your code and execute the program.<\/li>\n
  2. Once the line with break-point is reached, the ABAP Debugger is started automatically.<\/li>\n<\/ol>\n

    Basic debugging using ‘\/h<\/em>‘<\/h2>\n

    When you are in a started transaction\/program and you would like to begin debugging at the moment:<\/p>\n

      \n
    1. Type ‘\/h<\/em>‘ (without the quotes) in the command box and press enter<\/li>\n
    2. Do any action in your program (eg. Save, Display, press F4, …)<\/li>\n
    3. After you do any action which triggers PAI of the screen the ABAP Debugger is started<\/li>\n<\/ol>\n

      Debugging of “Update Task<\/em>“<\/h2>\n

      Debugging of an Update task is not possible with\u00a0normal setup\u00a0and without modification of user settings you are basically not able to debug a program which is started in an update task. To enable debugging of update task:<\/p>\n

        \n
      1. Start basic debugging using ‘\/h<\/em>‘<\/li>\n
      2. When ABAP Debugger is started, go to Top menu -> Settings -> Change Debugger Settings \/ profile (Shift+F1)<\/li>\n
      3. Select check box “Update debugging<\/em>“<\/li>\n
      4. Press F8 to let\u00a0current processing continue and wait until\u00a0the update task is\u00a0started in another window<\/li>\n<\/ol>\n

        Debugging “Queued RFCs<\/em>“<\/h2>\n

        Debugging Queued RFC might become useful e.g. for ECC <-> APO interface\u00a0where a CIF is used and data are sent back and forth using named queue called\u00a0‘*CF’<\/em><\/p>\n

        The outbound debug is easy – this can either be achieved by the Basic\u00a0debugging or by Debugging of an update task (outbound queues).<\/p>\n

        Inbound debugging is a bit harder because the queue is setup to process all incoming requests automatically at the moment of their arrival. To be able to debug inbound queue you have to STOP processing of arriving requests on a specific queue.<\/p>\n

        Debugging “Background tasks<\/em>“<\/h2>\n

        Debugging of a background task is not normally possible because the background task is started in another process (like the update task) so developer is not automatically navigated to the background code during debugging.<\/p>\n

        To enable background debugging:<\/p>\n

          \n
        1. Start basic debugging using ‘\/h<\/em>‘<\/li>\n
        2. When ABAP Debugger is started, go to Top menu -> Settings -> Change Debugger Settings \/ profile (Shift+F1)<\/li>\n
        3. Select check box “TRFC (In Background task):\u00a0Block\u00a0sending”<\/em><\/li>\n
        4. Press F8 to\u00a0let\u00a0current process to finish<\/li>\n
        5. Go to SM58 and find your un-processed background task<\/li>\n
        6. Start its debugging in Top-menu -> Edit -> Debug LUW<\/li>\n<\/ol>\n

          Debugging “Dialog windows<\/em>“<\/h2>\n

          When a dialog window is displayed in SAP you don’t have the command box available. So you are not able to start debugging using the ‘\/h’ command as usually.<\/p>\n

          The trick is in creating a ‘shortcut’ as a flat file in your file system with the following contents:<\/p>\n

          [FUNCTION]\r\n<\/span>Command=\/H\u00a0\r\nTitle=Debugger\r\nType=SystemCommand<\/pre>\n
          To enable debugging of a dialog window just Drag&Drop your prepared flat file on that dialog window and you should notice the message saying that debugging has been switched on.<\/p>\n
          After you perform\u00a0any action on such dialog window the ABAP Debugger is started and you can evaluate the user action results.<\/p>\n
          Debugging as different user<\/h2>\n
          This might become useful when processing e.g. requests from webdynpro which is handled on SAP backend\u00a0by some predefined\u00a0system user.<\/p>\n
          To enable debugging for a different user, go to SE38 (or SE37, SE24 or anythnig else which uses ABAP Editor) in the Top-menu open Utilities -> Settings -> tab ABAP Editor -> sub-tab Debugging -> enter the name of user you would like to use for debugging.<\/p>\n
          Dynamic Breakpoints<\/h2>\n
          Dynamic breakpoints are extremely useful especially in debugging of an update task because the update tasks are started in new sessions where your temporary breakpoints are not kept – so you have to set them again.<\/p>\n
            \n
          1. Once ABAP Debugger is started for the update task you can put breakpoints to your code using Top-menu -> Breakpoints -> Breakpoint at …<\/li>\n
          2. Just select the proper “Breakpoint at …”, eg. Function Module and enter the user-exit name you are going to debug<\/li>\n
          3. Press Enter and F8 to continue running the update task until your user-exit is reached and debugger is available again\u00a0for you in the user-exit<\/li>\n<\/ol>\n
            I personally use it a lot\u00a0when searching for the user-exits\/BAdIs called during the\u00a0program execution: just put new dynamic breakpoint as\u00a0“Breakpoint at Statement” with the following ABAP command<\/p>\n
            CALL CUSTOMER-FUNCTION<\/pre>\n
            Conditional breakpoints<\/h2>\n
            This feature of debugger might become quite handy\u00a0when you need to debug something in a loop and let’s say in its 500th<\/sup> iteration.<\/p>\n
            Without the conditional breakpoint you’d have to do each iteration manually. Using this approach you just set the breakpoint condition (in this case sy-tabix = 500) and you are done:<\/p>\n
            When standard debugger is started press F9 (Create Breakpoint), select desired target (Method, Function module, Program-form) and type your “Free Condition Entry” (e.g. SY-TABIX = 500).<\/p>\n
            External breakpoints<\/h2>\n