SAP RM_SENDEN_BILD_EBM Function Module for Send screen for data base EBM
RM_SENDEN_BILD_EBM is a standard rm senden bild ebm SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Send screen for data base EBM 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 rm senden bild ebm FM, simply by entering the name RM_SENDEN_BILD_EBM into the relevant SAP transaction such as SE37 or SE38.
Function Group: DEXM
Program Name: SAPLDEXM
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_SENDEN_BILD_EBM 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 'RM_SENDEN_BILD_EBM'"Send screen for data base EBM.
EXPORTING
E0_SELKA = "Indicator: select requests
E0_SELKB = "Indicator: select purchase orders
E0_SELKF = "Indicator: select purchase requisi
E0_SELKK = "Indicator: select contracts
E0_SELKL = "Indicator: select scheduling agree
IMPORTING
E0_SELKA = "Indicator: select requests
E0_SELKB = "Indicator: select purchase orders
E0_SELKF = "Indicator: select purchase requisi
E0_SELKK = "Indicator: select contracts
E0_SELKL = "Indicator: select scheduling agree
E0_START = "
IMPORTING Parameters details for RM_SENDEN_BILD_EBM
E0_SELKA - Indicator: select requests
Data type: RMDB1-SELKAOptional: No
Call by Reference: No ( called with pass by value option)
E0_SELKB - Indicator: select purchase orders
Data type: RMDB1-SELKBOptional: No
Call by Reference: No ( called with pass by value option)
E0_SELKF - Indicator: select purchase requisi
Data type: RMDB1-SELKFOptional: No
Call by Reference: No ( called with pass by value option)
E0_SELKK - Indicator: select contracts
Data type: RMDB1-SELKKOptional: No
Call by Reference: No ( called with pass by value option)
E0_SELKL - Indicator: select scheduling agree
Data type: RMDB1-SELKLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RM_SENDEN_BILD_EBM
E0_SELKA - Indicator: select requests
Data type: RMDB1-SELKAOptional: No
Call by Reference: No ( called with pass by value option)
E0_SELKB - Indicator: select purchase orders
Data type: RMDB1-SELKBOptional: No
Call by Reference: No ( called with pass by value option)
E0_SELKF - Indicator: select purchase requisi
Data type: RMDB1-SELKFOptional: No
Call by Reference: No ( called with pass by value option)
E0_SELKK - Indicator: select contracts
Data type: RMDB1-SELKKOptional: No
Call by Reference: No ( called with pass by value option)
E0_SELKL - Indicator: select scheduling agree
Data type: RMDB1-SELKLOptional: No
Call by Reference: No ( called with pass by value option)
E0_START -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_SENDEN_BILD_EBM 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_e0_selka | TYPE RMDB1-SELKA, " | |||
| lv_e0_selka | TYPE RMDB1-SELKA, " | |||
| lv_e0_selkb | TYPE RMDB1-SELKB, " | |||
| lv_e0_selkb | TYPE RMDB1-SELKB, " | |||
| lv_e0_selkf | TYPE RMDB1-SELKF, " | |||
| lv_e0_selkf | TYPE RMDB1-SELKF, " | |||
| lv_e0_selkk | TYPE RMDB1-SELKK, " | |||
| lv_e0_selkk | TYPE RMDB1-SELKK, " | |||
| lv_e0_selkl | TYPE RMDB1-SELKL, " | |||
| lv_e0_selkl | TYPE RMDB1-SELKL, " | |||
| lv_e0_start | TYPE RMDB1. " |
|   CALL FUNCTION 'RM_SENDEN_BILD_EBM' "Send screen for data base EBM |
| EXPORTING | ||
| E0_SELKA | = lv_e0_selka | |
| E0_SELKB | = lv_e0_selkb | |
| E0_SELKF | = lv_e0_selkf | |
| E0_SELKK | = lv_e0_selkk | |
| E0_SELKL | = lv_e0_selkl | |
| IMPORTING | ||
| E0_SELKA | = lv_e0_selka | |
| E0_SELKB | = lv_e0_selkb | |
| E0_SELKF | = lv_e0_selkf | |
| E0_SELKK | = lv_e0_selkk | |
| E0_SELKL | = lv_e0_selkl | |
| E0_START | = lv_e0_start | |
| . " RM_SENDEN_BILD_EBM | ||
ABAP code using 7.40 inline data declarations to call FM RM_SENDEN_BILD_EBM
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 SELKA FROM RMDB1 INTO @DATA(ld_e0_selka). | ||||
| "SELECT single SELKA FROM RMDB1 INTO @DATA(ld_e0_selka). | ||||
| "SELECT single SELKB FROM RMDB1 INTO @DATA(ld_e0_selkb). | ||||
| "SELECT single SELKB FROM RMDB1 INTO @DATA(ld_e0_selkb). | ||||
| "SELECT single SELKF FROM RMDB1 INTO @DATA(ld_e0_selkf). | ||||
| "SELECT single SELKF FROM RMDB1 INTO @DATA(ld_e0_selkf). | ||||
| "SELECT single SELKK FROM RMDB1 INTO @DATA(ld_e0_selkk). | ||||
| "SELECT single SELKK FROM RMDB1 INTO @DATA(ld_e0_selkk). | ||||
| "SELECT single SELKL FROM RMDB1 INTO @DATA(ld_e0_selkl). | ||||
| "SELECT single SELKL FROM RMDB1 INTO @DATA(ld_e0_selkl). | ||||
Search for further information about these or an SAP related objects