SAP Function Modules

SRDEBUG_CONTINUE SAP Function module - Continue Remote ABAP-Debugging







SRDEBUG_CONTINUE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SRDEBUG_CONTINUE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: REMOTE_DEBUGGING
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM SRDEBUG_CONTINUE - SRDEBUG CONTINUE





CALL FUNCTION 'SRDEBUG_CONTINUE' "Continue Remote ABAP-Debugging
  EXPORTING
    debug_id =                  " sysuuid_c     Debug-ID
    debug_user =                " sy-uname      User Name
    gui_rfcsi =                 " rfcsi         RFC System Information (See RFC_SYSTEM_INFO Function Module)
  EXCEPTIONS
    INVALID_USERID = 1          "
    CANNOT_SET_BREAKPOINT = 2   "
    CANNOT_UPDATE_HTTP_DEBUG = 3  "
    INTERNAL_ERROR = 4          "
    .  "  SRDEBUG_CONTINUE

ABAP code example for Function Module SRDEBUG_CONTINUE





The ABAP code below is a full code listing to execute function module SRDEBUG_CONTINUE including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).


DATA(ld_debug_id) = 'some text here'.
DATA(ld_debug_user) = 'some text here'.
DATA(ld_gui_rfcsi) = 'some text here'. . CALL FUNCTION 'SRDEBUG_CONTINUE' EXPORTING debug_id = ld_debug_id debug_user = ld_debug_user gui_rfcsi = ld_gui_rfcsi EXCEPTIONS INVALID_USERID = 1 CANNOT_SET_BREAKPOINT = 2 CANNOT_UPDATE_HTTP_DEBUG = 3 INTERNAL_ERROR = 4 . " SRDEBUG_CONTINUE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_debug_id  TYPE SYSUUID_C ,
ld_debug_user  TYPE SY-UNAME ,
ld_gui_rfcsi  TYPE RFCSI .

ld_debug_id = 'some text here'.
ld_debug_user = 'some text here'.
ld_gui_rfcsi = 'some text here'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SRDEBUG_CONTINUE or its description.