RFC_GET_SYSTEM_INFO SAP Function module

RFC_GET_SYSTEM_INFO is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name RFC_GET_SYSTEM_INFO into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CRFC
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM RFC_GET_SYSTEM_INFO - RFC GET SYSTEM INFO

CALL FUNCTION 'RFC_GET_SYSTEM_INFO' "
  EXPORTING
    destination =               " string        Logical Destination (Specified in Function Call)
  IMPORTING
    rfcsi_export =              " rfcsi         RFC system info (see RFC_SYSTEM_INFO_functionmodule)
    rfc_login_complete =        " sy-debug      Internal
    dialog_user_type =          " sy-debug      Internal
    current_resources =         " sy-index      Loops, Current Loop Pass
    maximal_resources =         " sy-index      Loops, Current Loop Pass
    recommended_delay =         " sy-index      Loops, Current Loop Pass
    dest_communication_message =   " char120
    dest_system_message =       " char120
  EXCEPTIONS
    AUTHORITY_NOT_AVAILABLE = 1  "
    .  "  RFC_GET_SYSTEM_INFO

ABAP code example for Function Module RFC_GET_SYSTEM_INFO

The ABAP code below is a full code listing to execute function module RFC_GET_SYSTEM_INFO including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_rfcsi_export  
 
 TYPE RFCSI
,
ld_rfc_login_complete  
 
 TYPE SY-DEBUG
,
ld_dialog_user_type  
 
 TYPE SY-DEBUG
,
ld_current_resources  
 
 TYPE SY-INDEX
,
ld_maximal_resources  
 
 TYPE SY-INDEX
,
ld_recommended_delay  
 
 TYPE SY-INDEX
,
ld_dest_communication_message  
 
 TYPE CHAR120
,
ld_dest_system_message  
 
 TYPE CHAR120
.


DATA(ld_destination) = 'Check type of data required'.
.

CALL FUNCTION 'RFC_GET_SYSTEM_INFO'
  EXPORTING
    destination =                ld_destination
  IMPORTING
    rfcsi_export =               ld_rfcsi_export
    rfc_login_complete =         ld_rfc_login_complete
    dialog_user_type =           ld_dialog_user_type
    current_resources =          ld_current_resources
    maximal_resources =          ld_maximal_resources
    recommended_delay =          ld_recommended_delay
    dest_communication_message =    ld_dest_communication_message
    dest_system_message =        ld_dest_system_message
  EXCEPTIONS
    AUTHORITY_NOT_AVAILABLE =    1
    .  "  RFC_GET_SYSTEM_INFO

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_rfcsi_export
 
 TYPE RFCSI ,
ld_destination
 
 TYPE STRING ,
ld_rfc_login_complete
 
 TYPE SY-DEBUG ,
ld_dialog_user_type
 
 TYPE SY-DEBUG ,
ld_current_resources
 
 TYPE SY-INDEX ,
ld_maximal_resources
 
 TYPE SY-INDEX ,
ld_recommended_delay
 
 TYPE SY-INDEX ,
ld_dest_communication_message
 
 TYPE CHAR120 ,
ld_dest_system_message
 
 TYPE CHAR120 .


ld_destination = 'Check type of data required'.