SAP SALF_RFC_MODIFY_DESTINATION Function Module for









SALF_RFC_MODIFY_DESTINATION is a standard salf rfc modify destination 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 salf rfc modify destination FM, simply by entering the name SALF_RFC_MODIFY_DESTINATION into the relevant SAP transaction such as SE37 or SE38.

Function Group: SALF
Program Name: SAPLSALF
Main Program: SAPLSALF
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SALF_RFC_MODIFY_DESTINATION 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 'SALF_RFC_MODIFY_DESTINATION'"
EXPORTING
DESTINATION = "estination for RFC use
* GWSERVICE = ' ' "Gateway service
* RFCUNICODE = 1 "
* ACTION = 'I' "rocessing mode (see function module doc.)
* AUTHORITY_CHECK = 'X' "M59 AUTHORITY_CHECK active ?
* METHOD = 'R' "Identification of a registered RFC server program
* PROGRAM = ' ' "Program name (complete path)
* SERVER = ' ' "Name of target host
* TRACE = ' ' "Trace ?
* DESCRIPTION = ' ' "Description of RFC connection
* GWHOST = ' ' "Gateway host name

EXCEPTIONS
AUTHORITY_NOT_AVAILABLE = 1 DESTINATION_ALREADY_EXIST = 2 DESTINATION_NOT_EXIST = 3 DESTINATION_ENQUEUE_REJECT = 4 INFORMATION_FAILURE = 5 TRFC_ENTRY_INVALID = 6 INTERNAL_FAILURE = 7
.



IMPORTING Parameters details for SALF_RFC_MODIFY_DESTINATION

DESTINATION - estination for RFC use

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

GWSERVICE - Gateway service

Data type: RFCDISPLAY-RFCGWSERV
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

RFCUNICODE -

Data type: RFCDISPLAY-RFCUNICODE
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACTION - rocessing mode (see function module doc.)

Data type: RFCDISPLAY-RFCTRACE
Default: 'I'
Optional: Yes
Call by Reference: No ( called with pass by value option)

AUTHORITY_CHECK - M59 AUTHORITY_CHECK active ?

Data type: RFCDISPLAY-RFCTRACE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

METHOD - Identification of a registered RFC server program

Data type: RFCDISPLAZ-RFCREGID
Default: 'R'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PROGRAM - Program name (complete path)

Data type: RFCEXEC
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERVER - Name of target host

Data type: RFCHOST
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRACE - Trace ?

Data type: RFCDISPLAY-RFCTRACE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DESCRIPTION - Description of RFC connection

Data type: RFCDOC-RFCDOC1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

GWHOST - Gateway host name

Data type: RFCGWHOST
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

AUTHORITY_NOT_AVAILABLE - No authorization exists

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

DESTINATION_ALREADY_EXIST - Destination already exists

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

DESTINATION_NOT_EXIST - Destination does not exist

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

DESTINATION_ENQUEUE_REJECT - Destination is locked by another user

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

INFORMATION_FAILURE - Parameter (information) not correctly maintained

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

TRFC_ENTRY_INVALID - Inconsistent parameter maintenance for TRFC opti

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

INTERNAL_FAILURE - Internal error

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

Copy and paste ABAP code example for SALF_RFC_MODIFY_DESTINATION 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_destination  TYPE RFCDISPLAY-RFCDEST, "   
lv_authority_not_available  TYPE RFCDISPLAY, "   
lv_gwservice  TYPE RFCDISPLAY-RFCGWSERV, "   SPACE
lv_rfcunicode  TYPE RFCDISPLAY-RFCUNICODE, "   1
lv_action  TYPE RFCDISPLAY-RFCTRACE, "   'I'
lv_destination_already_exist  TYPE RFCDISPLAY, "   
lv_authority_check  TYPE RFCDISPLAY-RFCTRACE, "   'X'
lv_destination_not_exist  TYPE RFCDISPLAY, "   
lv_method  TYPE RFCDISPLAZ-RFCREGID, "   'R'
lv_destination_enqueue_reject  TYPE RFCDISPLAZ, "   
lv_program  TYPE RFCEXEC, "   SPACE
lv_information_failure  TYPE RFCEXEC, "   
lv_server  TYPE RFCHOST, "   SPACE
lv_trfc_entry_invalid  TYPE RFCHOST, "   
lv_trace  TYPE RFCDISPLAY-RFCTRACE, "   SPACE
lv_internal_failure  TYPE RFCDISPLAY, "   
lv_description  TYPE RFCDOC-RFCDOC1, "   SPACE
lv_gwhost  TYPE RFCGWHOST. "   SPACE

  CALL FUNCTION 'SALF_RFC_MODIFY_DESTINATION'  "
    EXPORTING
         DESTINATION = lv_destination
         GWSERVICE = lv_gwservice
         RFCUNICODE = lv_rfcunicode
         ACTION = lv_action
         AUTHORITY_CHECK = lv_authority_check
         METHOD = lv_method
         PROGRAM = lv_program
         SERVER = lv_server
         TRACE = lv_trace
         DESCRIPTION = lv_description
         GWHOST = lv_gwhost
    EXCEPTIONS
        AUTHORITY_NOT_AVAILABLE = 1
        DESTINATION_ALREADY_EXIST = 2
        DESTINATION_NOT_EXIST = 3
        DESTINATION_ENQUEUE_REJECT = 4
        INFORMATION_FAILURE = 5
        TRFC_ENTRY_INVALID = 6
        INTERNAL_FAILURE = 7
. " SALF_RFC_MODIFY_DESTINATION




ABAP code using 7.40 inline data declarations to call FM SALF_RFC_MODIFY_DESTINATION

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 RFCDISPLAY INTO @DATA(ld_destination).
 
 
"SELECT single RFCGWSERV FROM RFCDISPLAY INTO @DATA(ld_gwservice).
DATA(ld_gwservice) = ' '.
 
"SELECT single RFCUNICODE FROM RFCDISPLAY INTO @DATA(ld_rfcunicode).
DATA(ld_rfcunicode) = 1.
 
"SELECT single RFCTRACE FROM RFCDISPLAY INTO @DATA(ld_action).
DATA(ld_action) = 'I'.
 
 
"SELECT single RFCTRACE FROM RFCDISPLAY INTO @DATA(ld_authority_check).
DATA(ld_authority_check) = 'X'.
 
 
"SELECT single RFCREGID FROM RFCDISPLAZ INTO @DATA(ld_method).
DATA(ld_method) = 'R'.
 
 
DATA(ld_program) = ' '.
 
 
DATA(ld_server) = ' '.
 
 
"SELECT single RFCTRACE FROM RFCDISPLAY INTO @DATA(ld_trace).
DATA(ld_trace) = ' '.
 
 
"SELECT single RFCDOC1 FROM RFCDOC INTO @DATA(ld_description).
DATA(ld_description) = ' '.
 
DATA(ld_gwhost) = ' '.
 


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!