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

Function RFC_TRUSTED_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 'RFC_TRUSTED_CHECK'".
EXPORTING
RFCDEST = "
IMPORTING
TRANSFER_TIME = "
OPERATING_SYS = "
ERROR_MESSAGE = "
IMPORTING Parameters details for RFC_TRUSTED_CHECK
RFCDEST -
Data type: RFCDES-RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RFC_TRUSTED_CHECK
TRANSFER_TIME -
Data type: SY-INDEXOptional: No
Call by Reference: No ( called with pass by value option)
OPERATING_SYS -
Data type: SY-OPSYSOptional: No
Call by Reference: No ( called with pass by value option)
ERROR_MESSAGE -
Data type: SY-LISELOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RFC_TRUSTED_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: | ||||
| lv_rfcdest | TYPE RFCDES-RFCDEST, " | |||
| lv_transfer_time | TYPE SY-INDEX, " | |||
| lv_operating_sys | TYPE SY-OPSYS, " | |||
| lv_error_message | TYPE SY-LISEL. " |
|   CALL FUNCTION 'RFC_TRUSTED_CHECK' " |
| EXPORTING | ||
| RFCDEST | = lv_rfcdest | |
| IMPORTING | ||
| TRANSFER_TIME | = lv_transfer_time | |
| OPERATING_SYS | = lv_operating_sys | |
| ERROR_MESSAGE | = lv_error_message | |
| . " RFC_TRUSTED_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RFC_TRUSTED_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.| "SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_rfcdest). | ||||
| "SELECT single INDEX FROM SY INTO @DATA(ld_transfer_time). | ||||
| "SELECT single OPSYS FROM SY INTO @DATA(ld_operating_sys). | ||||
| "SELECT single LISEL FROM SY INTO @DATA(ld_error_message). | ||||
Search for further information about these or an SAP related objects