SAP BM_FUN_ASS_MODIFY Function Module for Add to/change diagram
BM_FUN_ASS_MODIFY is a standard bm fun ass modify SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Add to/change diagram 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 fun ass modify FM, simply by entering the name BM_FUN_ASS_MODIFY into the relevant SAP transaction such as SE37 or SE38.
Function Group: SF11
Program Name: SAPLSF11
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BM_FUN_ASS_MODIFY 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_FUN_ASS_MODIFY'"Add to/change diagram.
EXPORTING
MODE = "
* NO_DIALOG = ' ' "
* CICO_REQUEST_NO = ' ' "
* DEVCLASS = "
DIAGRAM_INFO = "
NODES = "
* LINES = "
* LINEPOINTS = "
IMPORTING
ERROR_OCCURED = "
PROCESSING_STATUS = "
TABLES
* ERRORS = "
EXCEPTIONS
DB_FAULT = 1
IMPORTING Parameters details for BM_FUN_ASS_MODIFY
MODE -
Data type: RPYGSGF-MODEOptional: No
Call by Reference: No ( called with pass by value option)
NO_DIALOG -
Data type: BMT_FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CICO_REQUEST_NO -
Data type: RPYGSGF-CICO_REQNODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DEVCLASS -
Data type: RPYGSCO-DEVCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
DIAGRAM_INFO -
Data type: BMT_DIAGRAM_INFOOptional: No
Call by Reference: No ( called with pass by value option)
NODES -
Data type: BMT_NODESOptional: No
Call by Reference: Yes
LINES -
Data type: BMT_LINESOptional: Yes
Call by Reference: Yes
LINEPOINTS -
Data type: BMT_LINEPOINTSOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BM_FUN_ASS_MODIFY
ERROR_OCCURED -
Data type: RPYGSGF-ERR_EXISTOptional: No
Call by Reference: No ( called with pass by value option)
PROCESSING_STATUS -
Data type: RPYGSGF-PROC_STATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BM_FUN_ASS_MODIFY
ERRORS -
Data type: RPYGSEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DB_FAULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BM_FUN_ASS_MODIFY 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_mode | TYPE RPYGSGF-MODE, " | |||
| lt_errors | TYPE STANDARD TABLE OF RPYGSER, " | |||
| lv_db_fault | TYPE RPYGSER, " | |||
| lv_error_occured | TYPE RPYGSGF-ERR_EXIST, " | |||
| lv_no_dialog | TYPE BMT_FLAG, " SPACE | |||
| lv_processing_status | TYPE RPYGSGF-PROC_STAT, " | |||
| lv_cico_request_no | TYPE RPYGSGF-CICO_REQNO, " SPACE | |||
| lv_devclass | TYPE RPYGSCO-DEVCLASS, " | |||
| lv_diagram_info | TYPE BMT_DIAGRAM_INFO, " | |||
| lv_nodes | TYPE BMT_NODES, " | |||
| lv_lines | TYPE BMT_LINES, " | |||
| lv_linepoints | TYPE BMT_LINEPOINTS. " |
|   CALL FUNCTION 'BM_FUN_ASS_MODIFY' "Add to/change diagram |
| EXPORTING | ||
| MODE | = lv_mode | |
| NO_DIALOG | = lv_no_dialog | |
| CICO_REQUEST_NO | = lv_cico_request_no | |
| DEVCLASS | = lv_devclass | |
| DIAGRAM_INFO | = lv_diagram_info | |
| NODES | = lv_nodes | |
| LINES | = lv_lines | |
| LINEPOINTS | = lv_linepoints | |
| IMPORTING | ||
| ERROR_OCCURED | = lv_error_occured | |
| PROCESSING_STATUS | = lv_processing_status | |
| TABLES | ||
| ERRORS | = lt_errors | |
| EXCEPTIONS | ||
| DB_FAULT = 1 | ||
| . " BM_FUN_ASS_MODIFY | ||
ABAP code using 7.40 inline data declarations to call FM BM_FUN_ASS_MODIFY
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 MODE FROM RPYGSGF INTO @DATA(ld_mode). | ||||
| "SELECT single ERR_EXIST FROM RPYGSGF INTO @DATA(ld_error_occured). | ||||
| DATA(ld_no_dialog) | = ' '. | |||
| "SELECT single PROC_STAT FROM RPYGSGF INTO @DATA(ld_processing_status). | ||||
| "SELECT single CICO_REQNO FROM RPYGSGF INTO @DATA(ld_cico_request_no). | ||||
| DATA(ld_cico_request_no) | = ' '. | |||
| "SELECT single DEVCLASS FROM RPYGSCO INTO @DATA(ld_devclass). | ||||
Search for further information about these or an SAP related objects