SAP ISM_CHECK_BREAK Function Module for Check Breakpoint
ISM_CHECK_BREAK is a standard ism check break SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Breakpoint 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 ism check break FM, simply by entering the name ISM_CHECK_BREAK into the relevant SAP transaction such as SE37 or SE38.
Function Group: JY00
Program Name: SAPLJY00
Main Program: SAPLJY00
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_CHECK_BREAK 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 'ISM_CHECK_BREAK'"Check Breakpoint.
EXPORTING
* DEBUG_NAME = "
EXCEPTIONS
DO_BREAK = 1 DO_NOT_BREAK = 2
IMPORTING Parameters details for ISM_CHECK_BREAK
DEBUG_NAME -
Data type: SY-UNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DO_BREAK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DO_NOT_BREAK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_CHECK_BREAK 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_do_break | TYPE STRING, " | |||
| lv_debug_name | TYPE SY-UNAME, " | |||
| lv_do_not_break | TYPE SY. " |
|   CALL FUNCTION 'ISM_CHECK_BREAK' "Check Breakpoint |
| EXPORTING | ||
| DEBUG_NAME | = lv_debug_name | |
| EXCEPTIONS | ||
| DO_BREAK = 1 | ||
| DO_NOT_BREAK = 2 | ||
| . " ISM_CHECK_BREAK | ||
ABAP code using 7.40 inline data declarations to call FM ISM_CHECK_BREAK
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 UNAME FROM SY INTO @DATA(ld_debug_name). | ||||
Search for further information about these or an SAP related objects