SAP FDT_START_DEBUGGEE Function Module for FDT: Start Debuggee Session

Search SAP Function Modules

FDT_START_DEBUGGEE is a standard fdt start debuggee SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FDT: Start Debuggee Session 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 fdt start debuggee FM, simply by entering the name FDT_START_DEBUGGEE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FDT_DEBUGGER
Program Name: SAPLFDT_DEBUGGER
Main Program: SAPLFDT_DEBUGGER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FDT_START_DEBUGGEE 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 'FDT_START_DEBUGGEE'"FDT: Start Debuggee Session
  EXPORTING
   IV_SESSION_HANDLE =  "Session Handle (UUID)
*  IV_TIMESTAMP =  "Timestamp for Processing
   IV_FUNCTION_ID =  "Function ID
*  IV_INACTIVE = ABAP_FALSE "True: Inactive function should be debugged
*  IV_EXECUTE_ACTIONS = ABAP_FALSE "True: Execute actions

.

IMPORTING Parameters details for FDT_START_DEBUGGEE

IV_SESSION_HANDLE - Session Handle (UUID)

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

IV_TIMESTAMP - Timestamp for Processing

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

IV_FUNCTION_ID - Function ID

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

IV_INACTIVE - True: Inactive function should be debugged

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

IV_EXECUTE_ACTIONS - True: Execute actions

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

Copy and paste ABAP code example for FDT_START_DEBUGGEE 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.

ABAP code using 7.40 inline data declarations to call FM FDT_START_DEBUGGEE

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.

Search for further information about these or an SAP related objects