SAP TERM_GET_RFC_DESTINATION_CLIEN Function Module for NOTRANSL: Ermitteln des Namens der RFC-Verbindung zum Client
TERM_GET_RFC_DESTINATION_CLIEN is a standard term get rfc destination clien SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Ermitteln des Namens der RFC-Verbindung zum Client 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 term get rfc destination clien FM, simply by entering the name TERM_GET_RFC_DESTINATION_CLIEN into the relevant SAP transaction such as SE37 or SE38.
Function Group: STERM_ATTR
Program Name: SAPLSTERM_ATTR
Main Program: SAPLSTERM_ATTR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TERM_GET_RFC_DESTINATION_CLIEN 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 'TERM_GET_RFC_DESTINATION_CLIEN'"NOTRANSL: Ermitteln des Namens der RFC-Verbindung zum Client.
EXPORTING
SYSTEM_ID = "ABAP System Field: Name of SAP System
IMPORTING
RFC_DESTINATION = "Logical Destination (Specified in Function Call)
IMPORTING Parameters details for TERM_GET_RFC_DESTINATION_CLIEN
SYSTEM_ID - ABAP System Field: Name of SAP System
Data type: SY-SYSIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for TERM_GET_RFC_DESTINATION_CLIEN
RFC_DESTINATION - Logical Destination (Specified in Function Call)
Data type: RFCDES-RFCDESTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for TERM_GET_RFC_DESTINATION_CLIEN 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_system_id | TYPE SY-SYSID, " | |||
| lv_rfc_destination | TYPE RFCDES-RFCDEST. " |
|   CALL FUNCTION 'TERM_GET_RFC_DESTINATION_CLIEN' "NOTRANSL: Ermitteln des Namens der RFC-Verbindung zum Client |
| EXPORTING | ||
| SYSTEM_ID | = lv_system_id | |
| IMPORTING | ||
| RFC_DESTINATION | = lv_rfc_destination | |
| . " TERM_GET_RFC_DESTINATION_CLIEN | ||
ABAP code using 7.40 inline data declarations to call FM TERM_GET_RFC_DESTINATION_CLIEN
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 SYSID FROM SY INTO @DATA(ld_system_id). | ||||
| "SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_rfc_destination). | ||||
Search for further information about these or an SAP related objects