SAP ME_MAPPING Function Module for Mobile Engine: Mapping Client method - application wrapper

Search SAP Function Modules

ME_MAPPING is a standard me mapping SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Mobile Engine: Mapping Client method - application wrapper 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 mapping FM, simply by entering the name ME_MAPPING into the relevant SAP transaction such as SE37 or SE38.

Function Group: BWAF_MW
Program Name: SAPLBWAF_MW
Main Program: SAPLBWAF_MW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ME_MAPPING 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_MAPPING'"Mobile Engine: Mapping Client method - application wrapper
  EXPORTING
   METHOD =  "WAF: Mapping Method Name Function Module

 IMPORTING
   FUNCTION =  "Name des Funktionsbausteins
   RFCDEST =  "logische Destination (Wird bei Funktionsaufruf angegeben)
   SYSRELEASE =  "R/3-System, Release-Stand des R/3-Systems

EXCEPTIONS
   MAPPING_FAILED = 1 

.

IMPORTING Parameters details for ME_MAPPING

METHOD - WAF: Mapping Method Name Function Module

Data type: BWAFMAPP-METHOD
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ME_MAPPING

FUNCTION - Name des Funktionsbausteins

Data type: BWAFMAPP-FUNCTION
Optional: No
Call by Reference: No ( called with pass by value option)

RFCDEST - logische Destination (Wird bei Funktionsaufruf angegeben)

Data type: MEMAPPDEST-RFCDEST
Optional: No
Call by Reference: No ( called with pass by value option)

SYSRELEASE - R/3-System, Release-Stand des R/3-Systems

Data type: MEMAPPDEST-SYSRELEASE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

MAPPING_FAILED - unable to dertermine procedure to be called

Data type:
Optional: No
Call by Reference: Yes

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

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