SAP RS_TOOL_ACCESS_REMOTE Function Module for
RS_TOOL_ACCESS_REMOTE is a standard rs tool access remote 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 rs tool access remote FM, simply by entering the name RS_TOOL_ACCESS_REMOTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEAP
Program Name: SAPLSEAP
Main Program: SAPLSEAP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RS_TOOL_ACCESS_REMOTE 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 'RS_TOOL_ACCESS_REMOTE'".
EXPORTING
OPERATION = "Operation
* OBJECT_NAME = "Object Name
* OBJECT_TYPE = "Object Type
* ENCLOSING_OBJECT = "Program Name
* POSITION = ' ' "Position
* DEVCLASS = "Package
* INCLUDE = "Include
* MONITOR_ACTIVATION = 'X' "
IMPORTING
NEW_NAME = "New Program Name (After Rename)
TABLES
* OBJLIST = "Object List
EXCEPTIONS
NOT_EXECUTED = 1 INVALID_OBJECT_TYPE = 2 UNSPECIFIED_ERROR = 3
IMPORTING Parameters details for RS_TOOL_ACCESS_REMOTE
OPERATION - Operation
Data type: CHAR30Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NAME - Object Name
Data type: EU_LNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_TYPE - Object Type
Data type: SEU_OBJOptional: Yes
Call by Reference: No ( called with pass by value option)
ENCLOSING_OBJECT - Program Name
Data type: SYREPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
POSITION - Position
Data type: EU_NAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DEVCLASS - Package
Data type: TADIR-DEVCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
INCLUDE - Include
Data type: TRDIR-NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
MONITOR_ACTIVATION -
Data type: SY-INPUTDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RS_TOOL_ACCESS_REMOTE
NEW_NAME - New Program Name (After Rename)
Data type: EU_LNAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RS_TOOL_ACCESS_REMOTE
OBJLIST - Object List
Data type: RSEUAPOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_EXECUTED - Application function was not carried out
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_OBJECT_TYPE - Invalid object type
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNSPECIFIED_ERROR - Unknown Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RS_TOOL_ACCESS_REMOTE 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_objlist | TYPE STANDARD TABLE OF RSEUAP, " | |||
| lv_new_name | TYPE EU_LNAME, " | |||
| lv_operation | TYPE CHAR30, " | |||
| lv_not_executed | TYPE CHAR30, " | |||
| lv_object_name | TYPE EU_LNAME, " | |||
| lv_invalid_object_type | TYPE EU_LNAME, " | |||
| lv_object_type | TYPE SEU_OBJ, " | |||
| lv_unspecified_error | TYPE SEU_OBJ, " | |||
| lv_enclosing_object | TYPE SYREPID, " | |||
| lv_position | TYPE EU_NAME, " SPACE | |||
| lv_devclass | TYPE TADIR-DEVCLASS, " | |||
| lv_include | TYPE TRDIR-NAME, " | |||
| lv_monitor_activation | TYPE SY-INPUT. " 'X' |
|   CALL FUNCTION 'RS_TOOL_ACCESS_REMOTE' " |
| EXPORTING | ||
| OPERATION | = lv_operation | |
| OBJECT_NAME | = lv_object_name | |
| OBJECT_TYPE | = lv_object_type | |
| ENCLOSING_OBJECT | = lv_enclosing_object | |
| POSITION | = lv_position | |
| DEVCLASS | = lv_devclass | |
| INCLUDE | = lv_include | |
| MONITOR_ACTIVATION | = lv_monitor_activation | |
| IMPORTING | ||
| NEW_NAME | = lv_new_name | |
| TABLES | ||
| OBJLIST | = lt_objlist | |
| EXCEPTIONS | ||
| NOT_EXECUTED = 1 | ||
| INVALID_OBJECT_TYPE = 2 | ||
| UNSPECIFIED_ERROR = 3 | ||
| . " RS_TOOL_ACCESS_REMOTE | ||
ABAP code using 7.40 inline data declarations to call FM RS_TOOL_ACCESS_REMOTE
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.| DATA(ld_position) | = ' '. | |||
| "SELECT single DEVCLASS FROM TADIR INTO @DATA(ld_devclass). | ||||
| "SELECT single NAME FROM TRDIR INTO @DATA(ld_include). | ||||
| "SELECT single INPUT FROM SY INTO @DATA(ld_monitor_activation). | ||||
| DATA(ld_monitor_activation) | = 'X'. | |||
Search for further information about these or an SAP related objects