SAP MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F Function Module for wrf_lmvf_asgmt -> bapi_fix_asgmt
MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F is a standard map2e wrf lmvf asgmt to bapi f SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for wrf_lmvf_asgmt -> bapi_fix_asgmt 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 map2e wrf lmvf asgmt to bapi f FM, simply by entering the name MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F into the relevant SAP transaction such as SE37 or SE38.
Function Group: WRF_WPLG
Program Name: SAPLWRF_WPLG
Main Program: SAPLWRF_WPLG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F 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 'MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F'"wrf_lmvf_asgmt -> bapi_fix_asgmt.
EXPORTING
WRF_LMVF_ASGMT = "
CHANGING
BAPI_FIX_ASGMT = "
IMPORTING Parameters details for MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F
WRF_LMVF_ASGMT -
Data type: WRF_LMVF_ASGMTOptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F
BAPI_FIX_ASGMT -
Data type: BAPI_FIX_ASGMTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F 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_bapi_fix_asgmt | TYPE BAPI_FIX_ASGMT, " | |||
| lv_wrf_lmvf_asgmt | TYPE WRF_LMVF_ASGMT. " |
|   CALL FUNCTION 'MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F' "wrf_lmvf_asgmt -> bapi_fix_asgmt |
| EXPORTING | ||
| WRF_LMVF_ASGMT | = lv_wrf_lmvf_asgmt | |
| CHANGING | ||
| BAPI_FIX_ASGMT | = lv_bapi_fix_asgmt | |
| . " MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F | ||
ABAP code using 7.40 inline data declarations to call FM MAP2E_WRF_LMVF_ASGMT_TO_BAPI_F
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