SAP SRM_CREATE_RFC_WRAPPER Function Module for









SRM_CREATE_RFC_WRAPPER is a standard srm create rfc wrapper 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 srm create rfc wrapper FM, simply by entering the name SRM_CREATE_RFC_WRAPPER into the relevant SAP transaction such as SE37 or SE38.

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



Function SRM_CREATE_RFC_WRAPPER 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 'SRM_CREATE_RFC_WRAPPER'"
EXPORTING
IV_RFCDEST = "
IV_FUNCNAME = "
IV_FUNCNAME_NEW = "
IV_FUNCTION_POOL = "
IV_SHORT_TEXT_POOL = "
IV_DEVCLASS = "
IV_CORRNUM = "
IV_SHORT_TEXT_FM = "

EXCEPTIONS
COMMUNICATION_FAILURE = 1 FUNCTION_NOT_FOUND = 2 FUNCTION_ALREADY_EXISTS = 3 INVALID_FUNCTION_POOL = 4 INVALID_NAME = 5 NO_MODIFY_PERMISSION = 6 NO_SHOW_PERMISSION = 7 ENQUEUE_SYSTEM_FAILURE = 8 CANCELED_IN_CORR = 9
.



IMPORTING Parameters details for SRM_CREATE_RFC_WRAPPER

IV_RFCDEST -

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

IV_FUNCNAME -

Data type: RS38L-NAME
Optional: No
Call by Reference: Yes

IV_FUNCNAME_NEW -

Data type: RS38L-NAME
Optional: No
Call by Reference: Yes

IV_FUNCTION_POOL -

Data type: RSNEWLENG-AREA
Optional: No
Call by Reference: Yes

IV_SHORT_TEXT_POOL -

Data type: TFTIT-STEXT
Optional: No
Call by Reference: Yes

IV_DEVCLASS -

Data type: RS38L-DEVCLASS
Optional: No
Call by Reference: Yes

IV_CORRNUM -

Data type: E071-TRKORR
Optional: No
Call by Reference: Yes

IV_SHORT_TEXT_FM -

Data type: TFTIT-STEXT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

COMMUNICATION_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

FUNCTION_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FUNCTION_ALREADY_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

INVALID_FUNCTION_POOL -

Data type:
Optional: No
Call by Reference: Yes

INVALID_NAME -

Data type:
Optional: No
Call by Reference: Yes

NO_MODIFY_PERMISSION -

Data type:
Optional: No
Call by Reference: Yes

NO_SHOW_PERMISSION -

Data type:
Optional: No
Call by Reference: Yes

ENQUEUE_SYSTEM_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

CANCELED_IN_CORR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SRM_CREATE_RFC_WRAPPER 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_iv_rfcdest  TYPE RFCDEST, "   
lv_communication_failure  TYPE RFCDEST, "   
lv_iv_funcname  TYPE RS38L-NAME, "   
lv_function_not_found  TYPE RS38L, "   
lv_iv_funcname_new  TYPE RS38L-NAME, "   
lv_function_already_exists  TYPE RS38L, "   
lv_iv_function_pool  TYPE RSNEWLENG-AREA, "   
lv_invalid_function_pool  TYPE RSNEWLENG, "   
lv_invalid_name  TYPE RSNEWLENG, "   
lv_iv_short_text_pool  TYPE TFTIT-STEXT, "   
lv_iv_devclass  TYPE RS38L-DEVCLASS, "   
lv_no_modify_permission  TYPE RS38L, "   
lv_iv_corrnum  TYPE E071-TRKORR, "   
lv_no_show_permission  TYPE E071, "   
lv_iv_short_text_fm  TYPE TFTIT-STEXT, "   
lv_enqueue_system_failure  TYPE TFTIT, "   
lv_canceled_in_corr  TYPE TFTIT. "   

  CALL FUNCTION 'SRM_CREATE_RFC_WRAPPER'  "
    EXPORTING
         IV_RFCDEST = lv_iv_rfcdest
         IV_FUNCNAME = lv_iv_funcname
         IV_FUNCNAME_NEW = lv_iv_funcname_new
         IV_FUNCTION_POOL = lv_iv_function_pool
         IV_SHORT_TEXT_POOL = lv_iv_short_text_pool
         IV_DEVCLASS = lv_iv_devclass
         IV_CORRNUM = lv_iv_corrnum
         IV_SHORT_TEXT_FM = lv_iv_short_text_fm
    EXCEPTIONS
        COMMUNICATION_FAILURE = 1
        FUNCTION_NOT_FOUND = 2
        FUNCTION_ALREADY_EXISTS = 3
        INVALID_FUNCTION_POOL = 4
        INVALID_NAME = 5
        NO_MODIFY_PERMISSION = 6
        NO_SHOW_PERMISSION = 7
        ENQUEUE_SYSTEM_FAILURE = 8
        CANCELED_IN_CORR = 9
. " SRM_CREATE_RFC_WRAPPER




ABAP code using 7.40 inline data declarations to call FM SRM_CREATE_RFC_WRAPPER

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 NAME FROM RS38L INTO @DATA(ld_iv_funcname).
 
 
"SELECT single NAME FROM RS38L INTO @DATA(ld_iv_funcname_new).
 
 
"SELECT single AREA FROM RSNEWLENG INTO @DATA(ld_iv_function_pool).
 
 
 
"SELECT single STEXT FROM TFTIT INTO @DATA(ld_iv_short_text_pool).
 
"SELECT single DEVCLASS FROM RS38L INTO @DATA(ld_iv_devclass).
 
 
"SELECT single TRKORR FROM E071 INTO @DATA(ld_iv_corrnum).
 
 
"SELECT single STEXT FROM TFTIT INTO @DATA(ld_iv_short_text_fm).
 
 
 


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!