SAP F4_RFC_DESTINATIONS Function Module for F4 for Remote Connections









F4_RFC_DESTINATIONS is a standard f4 rfc destinations SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for F4 for Remote Connections 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 f4 rfc destinations FM, simply by entering the name F4_RFC_DESTINATIONS into the relevant SAP transaction such as SE37 or SE38.

Function Group: SEF4
Program Name: SAPLSEF4
Main Program: SAPLSEF4
Appliation area: S
Release date: 09-Mar-1998
Mode(Normal, Remote etc): Normal Function Module
Update:



Function F4_RFC_DESTINATIONS 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 'F4_RFC_DESTINATIONS'"F4 for Remote Connections
EXPORTING
* TYPE = '*' "
* DESTINATION = '*' "

IMPORTING
RESULT = "
.



IMPORTING Parameters details for F4_RFC_DESTINATIONS

TYPE -

Data type: RFCDES-RFCTYPE
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DESTINATION -

Data type: RFCDES-RFCDEST
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for F4_RFC_DESTINATIONS

RESULT -

Data type: RFCDES-RFCDEST
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for F4_RFC_DESTINATIONS 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_type  TYPE RFCDES-RFCTYPE, "   '*'
lv_result  TYPE RFCDES-RFCDEST, "   
lv_destination  TYPE RFCDES-RFCDEST. "   '*'

  CALL FUNCTION 'F4_RFC_DESTINATIONS'  "F4 for Remote Connections
    EXPORTING
         TYPE = lv_type
         DESTINATION = lv_destination
    IMPORTING
         RESULT = lv_result
. " F4_RFC_DESTINATIONS




ABAP code using 7.40 inline data declarations to call FM F4_RFC_DESTINATIONS

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 RFCTYPE FROM RFCDES INTO @DATA(ld_type).
DATA(ld_type) = '*'.
 
"SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_result).
 
"SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_destination).
DATA(ld_destination) = '*'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!