Skip to Content


*The ABAPDoc Utility* +ABAPdoc is a tool for generating API documentation in HTML format from Function Modules settings and source code.+ By means of this utility you can generate HTML files containing API information about selected Function Modules. These HTML files can be handy for developers who are using these function modules in their applications. For instance for Java developers who communicate via the JCo with SAP ERP. This utility generates HTML a bit like the JAVAdoc generator does, but however for function modules.  *Introduction to ABAPdoc:* Make a selection for which packages and/or for which function group you want to create the ABAPdoc and set the ABAPdoc settings: image *The result:* Execute the program. The result is HTML files containing information about the API of the selected Function Modules: image
You must be Logged on to comment or reply to a post.
  • This is really great.  I have started on something similar once, but didn’t have the time top finish it.
    I love it, very nice!
  • Hi,
    It’s a cool tool. Thanks for sharing it!

    Unfortunately in release 6.20 I got a syntax error for PARAMETER type string.
    After the following steps it worked fine:
    – define tofolder parameter as char255
    – define a tofolder_string variable as string
    – change value request like this:

      tofolder_string = tofolder.

      CALL METHOD cl_gui_frontend_services=>directory_browse
          window_title         = ‘Select a folder’
          initial_folder       = tofolder_string
          selected_folder      = tofolder_string
          cntl_error           = 1
          error_no_gui         = 2
          not_supported_by_gui = 3
          OTHERS               = 4.

      IF sy-subrc = 0.
        tofolder = tofolder_string.

    It would be useful to make a 620 compatible code also available.

    Best regards,

  • Hello,
    the development is great! I have been looking for something like this very long.

    Thank you very much!

    To use the development with developments in the customer namespace like /custX/ will not work.

    For theses cases the coding has to be adjusted in the method ‘get_function_names’. The parameter ‘lv_fgroup’ contains the program name and the namespace. The namespace has to be separated from the above mentioned parameter and passed to the function module ‘FUNCTION_INCLUDE_CONCATENATE’ as parameter ‘NAMESPACE’.

    Then the coding works also for developments in the customer namespace.

    Regards Matthias