SAP SMSS_RAT_RFCTRANS Function Module for









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

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



Function SMSS_RAT_RFCTRANS 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 'SMSS_RAT_RFCTRANS'"
EXPORTING
CON_NAME = "
OBJNAME = "
* ACTION = '1' "
LOCAL_VERSION = "

IMPORTING
RFC_VERSION = "

TABLES
FIXED = "
VARIANT = "

EXCEPTIONS
SMSS_INTERNAL_ERROR = 1 NO_AUTHORITY = 2
.



IMPORTING Parameters details for SMSS_RAT_RFCTRANS

CON_NAME -

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

OBJNAME -

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

ACTION -

Data type: CHAR1
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOCAL_VERSION -

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

EXPORTING Parameters details for SMSS_RAT_RFCTRANS

RFC_VERSION -

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

TABLES Parameters details for SMSS_RAT_RFCTRANS

FIXED -

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

VARIANT -

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

EXCEPTIONS details

SMSS_INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SMSS_RAT_RFCTRANS 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_fixed  TYPE STANDARD TABLE OF SMSSSERI2, "   
lv_con_name  TYPE MSSCONNDATA-CON_NAME, "   
lv_rfc_version  TYPE MSSCONNDATA-RFC_VERSION, "   
lv_smss_internal_error  TYPE MSSCONNDATA, "   
lv_objname  TYPE SMSSRATTR-OBJNAME, "   
lt_variant  TYPE STANDARD TABLE OF SMSSSERI2, "   
lv_no_authority  TYPE SMSSSERI2, "   
lv_action  TYPE CHAR1, "   '1'
lv_local_version  TYPE MSSCONNDATA-RFC_VERSION. "   

  CALL FUNCTION 'SMSS_RAT_RFCTRANS'  "
    EXPORTING
         CON_NAME = lv_con_name
         OBJNAME = lv_objname
         ACTION = lv_action
         LOCAL_VERSION = lv_local_version
    IMPORTING
         RFC_VERSION = lv_rfc_version
    TABLES
         FIXED = lt_fixed
         VARIANT = lt_variant
    EXCEPTIONS
        SMSS_INTERNAL_ERROR = 1
        NO_AUTHORITY = 2
. " SMSS_RAT_RFCTRANS




ABAP code using 7.40 inline data declarations to call FM SMSS_RAT_RFCTRANS

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 CON_NAME FROM MSSCONNDATA INTO @DATA(ld_con_name).
 
"SELECT single RFC_VERSION FROM MSSCONNDATA INTO @DATA(ld_rfc_version).
 
 
"SELECT single OBJNAME FROM SMSSRATTR INTO @DATA(ld_objname).
 
 
 
DATA(ld_action) = '1'.
 
"SELECT single RFC_VERSION FROM MSSCONNDATA INTO @DATA(ld_local_version).
 


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!