SAP RFC_MODIFY_TRUSTING_SYSTEM Function Module for
RFC_MODIFY_TRUSTING_SYSTEM is a standard rfc modify trusting system 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 modify trusting system FM, simply by entering the name RFC_MODIFY_TRUSTING_SYSTEM 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_MODIFY_TRUSTING_SYSTEM 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_MODIFY_TRUSTING_SYSTEM'".
EXPORTING
* ACTION = 'M' "
RFCTRUST_ID = "
RFCTRUST_SY = "
* RFCDEST_PREENTRY = 'TRUSTING@' "
* LICENSE_NR = "
IMPORTING
RFCDEST_ENTRY = "
EXCEPTIONS
DESTINATION_NOT_EXIST = 1 AUTHORITY_NOT_AVAILABLE = 2
IMPORTING Parameters details for RFC_MODIFY_TRUSTING_SYSTEM
ACTION -
Data type: RFCDISPLAY-RFCTRACEDefault: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)
RFCTRUST_ID -
Data type: RFCTRUST-RFCTRUSTIDOptional: No
Call by Reference: No ( called with pass by value option)
RFCTRUST_SY -
Data type: RFCTRUST-RFCTRUSTSYOptional: No
Call by Reference: No ( called with pass by value option)
RFCDEST_PREENTRY -
Data type: RFCDES-RFCDESTDefault: 'TRUSTING@'
Optional: Yes
Call by Reference: No ( called with pass by value option)
LICENSE_NR -
Data type: SLIC_INSTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RFC_MODIFY_TRUSTING_SYSTEM
RFCDEST_ENTRY -
Data type: RFCDES-RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DESTINATION_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
AUTHORITY_NOT_AVAILABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RFC_MODIFY_TRUSTING_SYSTEM 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_action | TYPE RFCDISPLAY-RFCTRACE, " 'M' | |||
| lv_rfcdest_entry | TYPE RFCDES-RFCDEST, " | |||
| lv_destination_not_exist | TYPE RFCDES, " | |||
| lv_rfctrust_id | TYPE RFCTRUST-RFCTRUSTID, " | |||
| lv_authority_not_available | TYPE RFCTRUST, " | |||
| lv_rfctrust_sy | TYPE RFCTRUST-RFCTRUSTSY, " | |||
| lv_rfcdest_preentry | TYPE RFCDES-RFCDEST, " 'TRUSTING@' | |||
| lv_license_nr | TYPE SLIC_INST. " |
|   CALL FUNCTION 'RFC_MODIFY_TRUSTING_SYSTEM' " |
| EXPORTING | ||
| ACTION | = lv_action | |
| RFCTRUST_ID | = lv_rfctrust_id | |
| RFCTRUST_SY | = lv_rfctrust_sy | |
| RFCDEST_PREENTRY | = lv_rfcdest_preentry | |
| LICENSE_NR | = lv_license_nr | |
| IMPORTING | ||
| RFCDEST_ENTRY | = lv_rfcdest_entry | |
| EXCEPTIONS | ||
| DESTINATION_NOT_EXIST = 1 | ||
| AUTHORITY_NOT_AVAILABLE = 2 | ||
| . " RFC_MODIFY_TRUSTING_SYSTEM | ||
ABAP code using 7.40 inline data declarations to call FM RFC_MODIFY_TRUSTING_SYSTEM
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 RFCTRACE FROM RFCDISPLAY INTO @DATA(ld_action). | ||||
| DATA(ld_action) | = 'M'. | |||
| "SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_rfcdest_entry). | ||||
| "SELECT single RFCTRUSTID FROM RFCTRUST INTO @DATA(ld_rfctrust_id). | ||||
| "SELECT single RFCTRUSTSY FROM RFCTRUST INTO @DATA(ld_rfctrust_sy). | ||||
| "SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_rfcdest_preentry). | ||||
| DATA(ld_rfcdest_preentry) | = 'TRUSTING@'. | |||
Search for further information about these or an SAP related objects