SAP MAP2E_MVKE_TO_BAPIMATMVK Function Module for NOTRANSL: mvke -> bapimatmvk

Search SAP Function Modules

MAP2E_MVKE_TO_BAPIMATMVK is a standard map2e mvke to bapimatmvk 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: mvke -> bapimatmvk 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 mvke to bapimatmvk FM, simply by entering the name MAP2E_MVKE_TO_BAPIMATMVK into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM1
Program Name: SAPLCRM1
Main Program: SAPLCRM1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP2E_MVKE_TO_BAPIMATMVK 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_MVKE_TO_BAPIMATMVK'"NOTRANSL: mvke -> bapimatmvk
  EXPORTING
   MVKE =  "

CHANGING
   BAPIMATMVK =  "

.

IMPORTING Parameters details for MAP2E_MVKE_TO_BAPIMATMVK

MVKE -

Data type: MVKE
Optional: No
Call by Reference: Yes

CHANGING Parameters details for MAP2E_MVKE_TO_BAPIMATMVK

BAPIMATMVK -

Data type: BAPIMATMVK
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MAP2E_MVKE_TO_BAPIMATMVK 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.

ABAP code using 7.40 inline data declarations to call FM MAP2E_MVKE_TO_BAPIMATMVK

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