SAP ME_WF_EVENTS_REQ Function Module for NOTRANSL: Auslösen Workflow-Events für Parken und Sichern Bestellanforderu
ME_WF_EVENTS_REQ is a standard me wf events req SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Auslösen Workflow-Events für Parken und Sichern Bestellanforderu 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 me wf events req FM, simply by entering the name ME_WF_EVENTS_REQ into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEWFL
Program Name: SAPLMEWFL
Main Program: SAPLMEWFL
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function ME_WF_EVENTS_REQ 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 'ME_WF_EVENTS_REQ'"NOTRANSL: Auslösen Workflow-Events für Parken und Sichern Bestellanforderu.
EXPORTING
I_EBAN_NEW = "Table Type EBAN
I_EBAN_OLD = "Table Type EBAN
IMPORTING Parameters details for ME_WF_EVENTS_REQ
I_EBAN_NEW - Table Type EBAN
Data type: MEREQ_T_EBANOptional: No
Call by Reference: No ( called with pass by value option)
I_EBAN_OLD - Table Type EBAN
Data type: MEREQ_T_EBANOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_WF_EVENTS_REQ 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_i_eban_new | TYPE MEREQ_T_EBAN, " | |||
| lv_i_eban_old | TYPE MEREQ_T_EBAN. " |
|   CALL FUNCTION 'ME_WF_EVENTS_REQ' "NOTRANSL: Auslösen Workflow-Events für Parken und Sichern Bestellanforderu |
| EXPORTING | ||
| I_EBAN_NEW | = lv_i_eban_new | |
| I_EBAN_OLD | = lv_i_eban_old | |
| . " ME_WF_EVENTS_REQ | ||
ABAP code using 7.40 inline data declarations to call FM ME_WF_EVENTS_REQ
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.Search for further information about these or an SAP related objects