SAP /SAPSLL/PARTNER_FUNCTION_MAP Function Module for









/SAPSLL/PARTNER_FUNCTION_MAP is a standard /sapsll/partner function map 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 /sapsll/partner function map FM, simply by entering the name /SAPSLL/PARTNER_FUNCTION_MAP into the relevant SAP transaction such as SE37 or SE38.

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



Function /SAPSLL/PARTNER_FUNCTION_MAP 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 '/SAPSLL/PARTNER_FUNCTION_MAP'"
  EXPORTING
   IV_PVWVS =  "
   IV_GRVSY =  "
   IV_LOGSYS =  "
*  IS_DEBUG =  "

 IMPORTING
   EV_PAFCT =  "
   EV_PVWEX =  "
.



IMPORTING Parameters details for /SAPSLL/PARTNER_FUNCTION_MAP

IV_PVWVS -

Data type: /SAPSLL/PVWVS
Optional: No
Call by Reference: Yes

IV_GRVSY -

Data type: /SAPSLL/GRVSY
Optional: No
Call by Reference: Yes

IV_LOGSYS -

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

IS_DEBUG -

Data type: /SAPSLL/DEBUG_S
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for /SAPSLL/PARTNER_FUNCTION_MAP

EV_PAFCT -

Data type: /SAPSLL/PAFCT
Optional: No
Call by Reference: Yes

EV_PVWEX -

Data type: /SAPSLL/PVWEX
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /SAPSLL/PARTNER_FUNCTION_MAP 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_ev_pafct  TYPE /SAPSLL/PAFCT, "   
lv_iv_pvwvs  TYPE /SAPSLL/PVWVS, "   
lv_ev_pvwex  TYPE /SAPSLL/PVWEX, "   
lv_iv_grvsy  TYPE /SAPSLL/GRVSY, "   
lv_iv_logsys  TYPE LOGSYS, "   
lv_is_debug  TYPE /SAPSLL/DEBUG_S. "   

  CALL FUNCTION '/SAPSLL/PARTNER_FUNCTION_MAP'  "
    EXPORTING
         IV_PVWVS = lv_iv_pvwvs
         IV_GRVSY = lv_iv_grvsy
         IV_LOGSYS = lv_iv_logsys
         IS_DEBUG = lv_is_debug
    IMPORTING
         EV_PAFCT = lv_ev_pafct
         EV_PVWEX = lv_ev_pvwex
. " /SAPSLL/PARTNER_FUNCTION_MAP




ABAP code using 7.40 inline data declarations to call FM /SAPSLL/PARTNER_FUNCTION_MAP

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!