SAP BM_CHECK_PATH Function Module for Check path
BM_CHECK_PATH is a standard bm check path 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 path 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 bm check path FM, simply by entering the name BM_CHECK_PATH into the relevant SAP transaction such as SE37 or SE38.
Function Group: SF22
Program Name: SAPLSF22
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BM_CHECK_PATH 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 'BM_CHECK_PATH'"Check path.
CHANGING
ERROR_OCCURED = "
TABLES
NODES = "
LINES = "
FUNCTIONS = "
EVENTS = "
ERROR = "
CHANGING Parameters details for BM_CHECK_PATH
ERROR_OCCURED -
Data type: RPYGSGF-ERR_EXISTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BM_CHECK_PATH
NODES -
Data type: BMT_NODESOptional: No
Call by Reference: No ( called with pass by value option)
LINES -
Data type: BMT_LINESOptional: No
Call by Reference: No ( called with pass by value option)
FUNCTIONS -
Data type: BMT_FUNCTIONSOptional: No
Call by Reference: No ( called with pass by value option)
EVENTS -
Data type: BMT_EVENTSOptional: No
Call by Reference: No ( called with pass by value option)
ERROR -
Data type: RPYGSEROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BM_CHECK_PATH 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_nodes | TYPE STANDARD TABLE OF BMT_NODES, " | |||
| lv_error_occured | TYPE RPYGSGF-ERR_EXIST, " | |||
| lt_lines | TYPE STANDARD TABLE OF BMT_LINES, " | |||
| lt_functions | TYPE STANDARD TABLE OF BMT_FUNCTIONS, " | |||
| lt_events | TYPE STANDARD TABLE OF BMT_EVENTS, " | |||
| lt_error | TYPE STANDARD TABLE OF RPYGSER. " |
|   CALL FUNCTION 'BM_CHECK_PATH' "Check path |
| CHANGING | ||
| ERROR_OCCURED | = lv_error_occured | |
| TABLES | ||
| NODES | = lt_nodes | |
| LINES | = lt_lines | |
| FUNCTIONS | = lt_functions | |
| EVENTS | = lt_events | |
| ERROR | = lt_error | |
| . " BM_CHECK_PATH | ||
ABAP code using 7.40 inline data declarations to call FM BM_CHECK_PATH
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 ERR_EXIST FROM RPYGSGF INTO @DATA(ld_error_occured). | ||||
Search for further information about these or an SAP related objects