SAP AMDP_DBG_PROT_CLIENT Function Module for ADT-Simulation: Use Debugger API









AMDP_DBG_PROT_CLIENT is a standard amdp dbg prot client SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ADT-Simulation: Use Debugger API processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for amdp dbg prot client FM, simply by entering the name AMDP_DBG_PROT_CLIENT into the relevant SAP transaction such as SE37 or SE38.

Function Group: AMDP_DBG_PROTOTYPE
Program Name: SAPLAMDP_DBG_PROTOTYPE
Main Program: SAPLAMDP_DBG_PROTOTYPE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled + BasXML supported
Update:



Function AMDP_DBG_PROT_CLIENT pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'AMDP_DBG_PROT_CLIENT'"ADT-Simulation: Use Debugger API
EXPORTING
* IM_SQLCONN = "
* IM_STOP_AT_SQL_EXCEPTION = "
* IM_NONBLOCKING_MODE = "
* IM_FORCED_START = "
* IM_DEBUG = "CHAR01 Type
* IM_FOR_USER = SY-UNAME "
* IM_TMP_DBG = "CHAR01 Type
* IM_HIDE_NATIVE_OBJECTS = "CHAR01 data element for SYST
* IM_STEPIN_DBOBJ_KIND = "
* IM_STEPIN_BREAKPOINTS = "
* IM_STEPIN_RECOMPILES = "
* IM_NO_DBG_CASCADE = "

IMPORTING
EX_MSG = "
EX_DBG_CNTL = "
.



IMPORTING Parameters details for AMDP_DBG_PROT_CLIENT

IM_SQLCONN -

Data type: STRING
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_STOP_AT_SQL_EXCEPTION -

Data type: SYCHAR01
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_NONBLOCKING_MODE -

Data type: SYCHAR01
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_FORCED_START -

Data type: SYCHAR01
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_DEBUG - CHAR01 Type

Data type: SYCHAR01
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_FOR_USER -

Data type: SYUNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_TMP_DBG - CHAR01 Type

Data type: SYCHAR01
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_HIDE_NATIVE_OBJECTS - CHAR01 data element for SYST

Data type: SYCHAR01
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_STEPIN_DBOBJ_KIND -

Data type: D010DBOBJ_KIND
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_STEPIN_BREAKPOINTS -

Data type: XSTRING
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_STEPIN_RECOMPILES -

Data type: XSTRING
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_NO_DBG_CASCADE -

Data type: SYCHAR01
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for AMDP_DBG_PROT_CLIENT

EX_MSG -

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

EX_DBG_CNTL -

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for AMDP_DBG_PROT_CLIENT Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_ex_msg  TYPE STRING, "   
lv_im_sqlconn  TYPE STRING, "   
lv_im_stop_at_sql_exception  TYPE SYCHAR01, "   
lv_im_nonblocking_mode  TYPE SYCHAR01, "   
lv_im_forced_start  TYPE SYCHAR01, "   
lv_im_debug  TYPE SYCHAR01, "   
lv_ex_dbg_cntl  TYPE STRING, "   
lv_im_for_user  TYPE SYUNAME, "   SY-UNAME
lv_im_tmp_dbg  TYPE SYCHAR01, "   
lv_im_hide_native_objects  TYPE SYCHAR01, "   
lv_im_stepin_dbobj_kind  TYPE D010DBOBJ_KIND, "   
lv_im_stepin_breakpoints  TYPE XSTRING, "   
lv_im_stepin_recompiles  TYPE XSTRING, "   
lv_im_no_dbg_cascade  TYPE SYCHAR01. "   

  CALL FUNCTION 'AMDP_DBG_PROT_CLIENT'  "ADT-Simulation: Use Debugger API
    EXPORTING
         IM_SQLCONN = lv_im_sqlconn
         IM_STOP_AT_SQL_EXCEPTION = lv_im_stop_at_sql_exception
         IM_NONBLOCKING_MODE = lv_im_nonblocking_mode
         IM_FORCED_START = lv_im_forced_start
         IM_DEBUG = lv_im_debug
         IM_FOR_USER = lv_im_for_user
         IM_TMP_DBG = lv_im_tmp_dbg
         IM_HIDE_NATIVE_OBJECTS = lv_im_hide_native_objects
         IM_STEPIN_DBOBJ_KIND = lv_im_stepin_dbobj_kind
         IM_STEPIN_BREAKPOINTS = lv_im_stepin_breakpoints
         IM_STEPIN_RECOMPILES = lv_im_stepin_recompiles
         IM_NO_DBG_CASCADE = lv_im_no_dbg_cascade
    IMPORTING
         EX_MSG = lv_ex_msg
         EX_DBG_CNTL = lv_ex_dbg_cntl
. " AMDP_DBG_PROT_CLIENT




ABAP code using 7.40 inline data declarations to call FM AMDP_DBG_PROT_CLIENT

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
DATA(ld_im_for_user) = SY-UNAME.
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!