SAP SYSTEM_DEBUG_BREAKPOINTS Function Module for
SYSTEM_DEBUG_BREAKPOINTS is a standard system debug breakpoints SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 system debug breakpoints FM, simply by entering the name SYSTEM_DEBUG_BREAKPOINTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDBG
Program Name: SAPLSDBG
Main Program: SAPLSDBG
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SYSTEM_DEBUG_BREAKPOINTS 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 'SYSTEM_DEBUG_BREAKPOINTS'".
EXPORTING
* MAIN_PROGRAM = '*' "Main program for which breakpoints are searched for
IMPORTING
BREAKPOINTS_COMPLETE = "
FLAG_SYSTEM_DEBUGGING = "Flag: System Debugging
FLAG_EXCEPTION_OBJECT = "Flag: Exception Object
TABLES
* BREAKPOINTS = "Breakpoints (Include name and line number)
EXCEPTIONS
C_CALL_ERROR = 1 WRONG_PARAMETERS = 2
IMPORTING Parameters details for SYSTEM_DEBUG_BREAKPOINTS
MAIN_PROGRAM - Main program for which breakpoints are searched for
Data type: SY-REPIDDefault: '*'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SYSTEM_DEBUG_BREAKPOINTS
BREAKPOINTS_COMPLETE -
Data type: BREAKPOINTS_COMPLETEOptional: No
Call by Reference: Yes
FLAG_SYSTEM_DEBUGGING - Flag: System Debugging
Data type: ABAP_BOOLOptional: No
Call by Reference: Yes
FLAG_EXCEPTION_OBJECT - Flag: Exception Object
Data type: ABAP_BOOLOptional: No
Call by Reference: Yes
TABLES Parameters details for SYSTEM_DEBUG_BREAKPOINTS
BREAKPOINTS - Breakpoints (Include name and line number)
Data type: BREAKPOINTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
C_CALL_ERROR -
Data type:Optional: No
Call by Reference: Yes
WRONG_PARAMETERS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SYSTEM_DEBUG_BREAKPOINTS 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: | ||||
| lt_breakpoints | TYPE STANDARD TABLE OF BREAKPOINT, " | |||
| lv_c_call_error | TYPE BREAKPOINT, " | |||
| lv_main_program | TYPE SY-REPID, " '*' | |||
| lv_breakpoints_complete | TYPE BREAKPOINTS_COMPLETE, " | |||
| lv_wrong_parameters | TYPE BREAKPOINTS_COMPLETE, " | |||
| lv_flag_system_debugging | TYPE ABAP_BOOL, " | |||
| lv_flag_exception_object | TYPE ABAP_BOOL. " |
|   CALL FUNCTION 'SYSTEM_DEBUG_BREAKPOINTS' " |
| EXPORTING | ||
| MAIN_PROGRAM | = lv_main_program | |
| IMPORTING | ||
| BREAKPOINTS_COMPLETE | = lv_breakpoints_complete | |
| FLAG_SYSTEM_DEBUGGING | = lv_flag_system_debugging | |
| FLAG_EXCEPTION_OBJECT | = lv_flag_exception_object | |
| TABLES | ||
| BREAKPOINTS | = lt_breakpoints | |
| EXCEPTIONS | ||
| C_CALL_ERROR = 1 | ||
| WRONG_PARAMETERS = 2 | ||
| . " SYSTEM_DEBUG_BREAKPOINTS | ||
ABAP code using 7.40 inline data declarations to call FM SYSTEM_DEBUG_BREAKPOINTS
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.| "SELECT single REPID FROM SY INTO @DATA(ld_main_program). | ||||
| DATA(ld_main_program) | = '*'. | |||
Search for further information about these or an SAP related objects