SAP RSSDK_LOGSYS_REMOTE_CHECK Function Module for SDK remote to check the source system still existing in SDK infoserver
RSSDK_LOGSYS_REMOTE_CHECK is a standard rssdk logsys remote check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SDK remote to check the source system still existing in SDK infoserver processing and below is the pattern details for this FM, 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 rssdk logsys remote check FM, simply by entering the name RSSDK_LOGSYS_REMOTE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSSDK_REMOTE
Program Name: SAPLRSSDK_REMOTE
Main Program: SAPLRSSDK_REMOTE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RSSDK_LOGSYS_REMOTE_CHECK 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 'RSSDK_LOGSYS_REMOTE_CHECK'"SDK remote to check the source system still existing in SDK infoserver.
EXPORTING
I_QSYSTEMNAME = "Source System
TABLES
E_T_MSG = " Handing over of messages
IMPORTING Parameters details for RSSDK_LOGSYS_REMOTE_CHECK
I_QSYSTEMNAME - Source System
Data type: RSSDK_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RSSDK_LOGSYS_REMOTE_CHECK
E_T_MSG - Handing over of messages
Data type: RSPC_T_MSGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSSDK_LOGSYS_REMOTE_CHECK 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_e_t_msg | TYPE STANDARD TABLE OF RSPC_T_MSG, " | |||
| lv_i_qsystemname | TYPE RSSDK_NAME. " |
|   CALL FUNCTION 'RSSDK_LOGSYS_REMOTE_CHECK' "SDK remote to check the source system still existing in SDK infoserver |
| EXPORTING | ||
| I_QSYSTEMNAME | = lv_i_qsystemname | |
| TABLES | ||
| E_T_MSG | = lt_e_t_msg | |
| . " RSSDK_LOGSYS_REMOTE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RSSDK_LOGSYS_REMOTE_CHECK
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