SAP CALL_PARTNER_MAPPING Function Module for









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

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



Function CALL_PARTNER_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 'CALL_PARTNER_MAPPING'"
EXPORTING
SOURCE = "XML Document
STEPS = "Table of Mapping Steps
PARAMS = "Table of Mapping Parameters
MAPPINGKEY = "Mapping Key

IMPORTING
RESULT = "XML Document
RETURNTEXT = "
RETURNCODE = "
.



IMPORTING Parameters details for CALL_PARTNER_MAPPING

SOURCE - XML Document

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

STEPS - Table of Mapping Steps

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

PARAMS - Table of Mapping Parameters

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

MAPPINGKEY - Mapping Key

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

EXPORTING Parameters details for CALL_PARTNER_MAPPING

RESULT - XML Document

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

RETURNTEXT -

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

RETURNCODE -

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

Copy and paste ABAP code example for CALL_PARTNER_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:
lv_result  TYPE XSTRING, "   
lv_source  TYPE XSTRING, "   
lv_steps  TYPE MPP_MAPPINGSTEP_TAB, "   
lv_returntext  TYPE STRING, "   
lv_params  TYPE MPP_PARAM_TAB, "   
lv_returncode  TYPE STRING, "   
lv_mappingkey  TYPE MPP_MAPPINGKEY. "   

  CALL FUNCTION 'CALL_PARTNER_MAPPING'  "
    EXPORTING
         SOURCE = lv_source
         STEPS = lv_steps
         PARAMS = lv_params
         MAPPINGKEY = lv_mappingkey
    IMPORTING
         RESULT = lv_result
         RETURNTEXT = lv_returntext
         RETURNCODE = lv_returncode
. " CALL_PARTNER_MAPPING




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



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!