SAP MDG_TR_GET_RFC_DEST Function Module for Determine RFC Destination for Transport Methods









MDG_TR_GET_RFC_DEST is a standard mdg tr get rfc dest SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine RFC Destination for Transport Methods 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 mdg tr get rfc dest FM, simply by entering the name MDG_TR_GET_RFC_DEST into the relevant SAP transaction such as SE37 or SE38.

Function Group: MDG_TR_TOOLS
Program Name: SAPLMDG_TR_TOOLS
Main Program: SAPLMDG_TR_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MDG_TR_GET_RFC_DEST 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 'MDG_TR_GET_RFC_DEST'"Determine RFC Destination for Transport Methods
EXPORTING
* I_SYSID = SY-SYSID "Name of SAP System
I_MANDT = "Client

IMPORTING
E_RFCDEST = "RFC Destination

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for MDG_TR_GET_RFC_DEST

I_SYSID - Name of SAP System

Data type: SYSYSID
Default: SY-SYSID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MANDT - Client

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

EXPORTING Parameters details for MDG_TR_GET_RFC_DEST

E_RFCDEST - RFC Destination

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

EXCEPTIONS details

NOT_FOUND - RFC destination not found

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

Copy and paste ABAP code example for MDG_TR_GET_RFC_DEST 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_i_sysid  TYPE SYSYSID, "   SY-SYSID
lv_e_rfcdest  TYPE RFCDEST, "   
lv_not_found  TYPE RFCDEST, "   
lv_i_mandt  TYPE SYMANDT. "   

  CALL FUNCTION 'MDG_TR_GET_RFC_DEST'  "Determine RFC Destination for Transport Methods
    EXPORTING
         I_SYSID = lv_i_sysid
         I_MANDT = lv_i_mandt
    IMPORTING
         E_RFCDEST = lv_e_rfcdest
    EXCEPTIONS
        NOT_FOUND = 1
. " MDG_TR_GET_RFC_DEST




ABAP code using 7.40 inline data declarations to call FM MDG_TR_GET_RFC_DEST

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.

DATA(ld_i_sysid) = SY-SYSID.
 
 
 
 


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!