SAP PRGN_CHECK_RFC_DEST Function Module for









PRGN_CHECK_RFC_DEST is a standard prgn check 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 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 prgn check rfc dest FM, simply by entering the name PRGN_CHECK_RFC_DEST into the relevant SAP transaction such as SE37 or SE38.

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



Function PRGN_CHECK_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 'PRGN_CHECK_RFC_DEST'"
  EXPORTING
   REPLACE_RFC_VARIABLES =  "Customized ('C') or standard menu ('S') flag
   RFC_DESTINATION_NAME =  "Logical Destination (Specified in Function Call)
*  MESSAGE_OUTPUT = 'X' "Customized ('C') or standard menu ('S') flag
*  MINIMAL_RELEASE = '30G' "R/3 System, system release

 IMPORTING
   REPLACED_RFC_DESTINATION =  "Logical Destination (Specified in Function Call)
   TARGET_RELEASE =  "R/3 System, system release
   TARGET_SYSID =  "
   TARGET_CLIENT =  "

EXCEPTIONS
   DESTINATION_DOES_NOT_EXIST = 1    RELEASE_NOT_ACCEPTED = 2
.



IMPORTING Parameters details for PRGN_CHECK_RFC_DEST

REPLACE_RFC_VARIABLES - Customized ('C') or standard menu ('S') flag

Data type: CHAR01
Optional: No
Call by Reference: Yes

RFC_DESTINATION_NAME - Logical Destination (Specified in Function Call)

Data type: RFCDEST
Optional: No
Call by Reference: Yes

MESSAGE_OUTPUT - Customized ('C') or standard menu ('S') flag

Data type: CHAR01
Default: 'X'
Optional: Yes
Call by Reference: Yes

MINIMAL_RELEASE - R/3 System, system release

Data type: SYSAPRL
Default: '30G'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PRGN_CHECK_RFC_DEST

REPLACED_RFC_DESTINATION - Logical Destination (Specified in Function Call)

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

TARGET_RELEASE - R/3 System, system release

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

TARGET_SYSID -

Data type: SYSYSID
Optional: No
Call by Reference: Yes

TARGET_CLIENT -

Data type: SYMANDT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

DESTINATION_DOES_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

RELEASE_NOT_ACCEPTED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PRGN_CHECK_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_replace_rfc_variables  TYPE CHAR01, "   
lv_replaced_rfc_destination  TYPE RFCDEST, "   
lv_destination_does_not_exist  TYPE RFCDEST, "   
lv_target_release  TYPE SYSAPRL, "   
lv_release_not_accepted  TYPE SYSAPRL, "   
lv_rfc_destination_name  TYPE RFCDEST, "   
lv_target_sysid  TYPE SYSYSID, "   
lv_message_output  TYPE CHAR01, "   'X'
lv_target_client  TYPE SYMANDT, "   
lv_minimal_release  TYPE SYSAPRL. "   '30G'

  CALL FUNCTION 'PRGN_CHECK_RFC_DEST'  "
    EXPORTING
         REPLACE_RFC_VARIABLES = lv_replace_rfc_variables
         RFC_DESTINATION_NAME = lv_rfc_destination_name
         MESSAGE_OUTPUT = lv_message_output
         MINIMAL_RELEASE = lv_minimal_release
    IMPORTING
         REPLACED_RFC_DESTINATION = lv_replaced_rfc_destination
         TARGET_RELEASE = lv_target_release
         TARGET_SYSID = lv_target_sysid
         TARGET_CLIENT = lv_target_client
    EXCEPTIONS
        DESTINATION_DOES_NOT_EXIST = 1
        RELEASE_NOT_ACCEPTED = 2
. " PRGN_CHECK_RFC_DEST




ABAP code using 7.40 inline data declarations to call FM PRGN_CHECK_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_message_output) = 'X'.
 
 
DATA(ld_minimal_release) = '30G'.
 


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!