SAP CHECK_MAPPING Function Module for









CHECK_MAPPING is a standard check mapping 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 check mapping FM, simply by entering the name CHECK_MAPPING into the relevant SAP transaction such as SE37 or SE38.

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



Function CHECK_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 'CHECK_MAPPING'"
EXPORTING
MAPPING_FUNCTION = "
* SOURCE_STRUCTURE = "
* DESTINATION_STRUCTURE = "

TABLES
E_FMAP = "
.



IMPORTING Parameters details for CHECK_MAPPING

MAPPING_FUNCTION -

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

SOURCE_STRUCTURE -

Data type: DFIES-TABNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

DESTINATION_STRUCTURE -

Data type: DFIES-TABNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for CHECK_MAPPING

E_FMAP -

Data type: CRMFDMAP
Optional: No
Call by Reference: No ( called with pass by value option)

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

DATA:
lt_e_fmap  TYPE STANDARD TABLE OF CRMFDMAP, "   
lv_mapping_function  TYPE TFDIR-FUNCNAME, "   
lv_source_structure  TYPE DFIES-TABNAME, "   
lv_destination_structure  TYPE DFIES-TABNAME. "   

  CALL FUNCTION 'CHECK_MAPPING'  "
    EXPORTING
         MAPPING_FUNCTION = lv_mapping_function
         SOURCE_STRUCTURE = lv_source_structure
         DESTINATION_STRUCTURE = lv_destination_structure
    TABLES
         E_FMAP = lt_e_fmap
. " CHECK_MAPPING




ABAP code using 7.40 inline data declarations to call FM CHECK_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.

 
"SELECT single FUNCNAME FROM TFDIR INTO @DATA(ld_mapping_function).
 
"SELECT single TABNAME FROM DFIES INTO @DATA(ld_source_structure).
 
"SELECT single TABNAME FROM DFIES INTO @DATA(ld_destination_structure).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!