SAP RS_GET_BREAKPOINTS Function Module for Determine the breakpoints for an imported program
RS_GET_BREAKPOINTS is a standard rs get breakpoints SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine the breakpoints for an imported program 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 rs get breakpoints FM, simply by entering the name RS_GET_BREAKPOINTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: BREA
Program Name: SAPLBREA
Main Program: SAPLBREA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RS_GET_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 'RS_GET_BREAKPOINTS'"Determine the breakpoints for an imported program.
EXPORTING
PROGRAM = "
* HTTP_DEBUGGING = ' ' "Single-Character Flag
TABLES
SHOWBREAKPOINTS = "
IMPORTING Parameters details for RS_GET_BREAKPOINTS
PROGRAM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
HTTP_DEBUGGING - Single-Character Flag
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for RS_GET_BREAKPOINTS
SHOWBREAKPOINTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RS_GET_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: | ||||
| lv_program | TYPE STRING, " | |||
| lt_showbreakpoints | TYPE STANDARD TABLE OF STRING, " | |||
| lv_http_debugging | TYPE CHAR1. " SPACE |
|   CALL FUNCTION 'RS_GET_BREAKPOINTS' "Determine the breakpoints for an imported program |
| EXPORTING | ||
| PROGRAM | = lv_program | |
| HTTP_DEBUGGING | = lv_http_debugging | |
| TABLES | ||
| SHOWBREAKPOINTS | = lt_showbreakpoints | |
| . " RS_GET_BREAKPOINTS | ||
ABAP code using 7.40 inline data declarations to call FM RS_GET_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.| DATA(ld_http_debugging) | = ' '. | |||
Search for further information about these or an SAP related objects