SAP MAP2I_BAPIBEFUN_TO_DF04VD Function Module for
MAP2I_BAPIBEFUN_TO_DF04VD is a standard map2i bapibefun to df04vd SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 map2i bapibefun to df04vd FM, simply by entering the name MAP2I_BAPIBEFUN_TO_DF04VD into the relevant SAP transaction such as SE37 or SE38.
Function Group: BEFUNCT
Program Name: SAPLBEFUNCT
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP2I_BAPIBEFUN_TO_DF04VD 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 'MAP2I_BAPIBEFUN_TO_DF04VD'".
EXPORTING
BAPIBEFUN = "
CHANGING
DF04VD = "
EXCEPTIONS
ERROR_CONVERTING_ISO_CODE = 1
IMPORTING Parameters details for MAP2I_BAPIBEFUN_TO_DF04VD
BAPIBEFUN -
Data type: BAPIBEFUNOptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP2I_BAPIBEFUN_TO_DF04VD
DF04VD -
Data type: BMT_FUNCTIONOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_CONVERTING_ISO_CODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MAP2I_BAPIBEFUN_TO_DF04VD 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_df04vd | TYPE BMT_FUNCTION, " | |||
| lv_bapibefun | TYPE BAPIBEFUN, " | |||
| lv_error_converting_iso_code | TYPE BAPIBEFUN. " |
|   CALL FUNCTION 'MAP2I_BAPIBEFUN_TO_DF04VD' " |
| EXPORTING | ||
| BAPIBEFUN | = lv_bapibefun | |
| CHANGING | ||
| DF04VD | = lv_df04vd | |
| EXCEPTIONS | ||
| ERROR_CONVERTING_ISO_CODE = 1 | ||
| . " MAP2I_BAPIBEFUN_TO_DF04VD | ||
ABAP code using 7.40 inline data declarations to call FM MAP2I_BAPIBEFUN_TO_DF04VD
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