SAP QIST_VALUE_REQUEST_RFCDEST Function Module for NOTRANSL: Auswahl einer RFC-Destination zu einer Auswertemethode
QIST_VALUE_REQUEST_RFCDEST is a standard qist value request rfcdest 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: Auswahl einer RFC-Destination zu einer Auswertemethode 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 qist value request rfcdest FM, simply by entering the name QIST_VALUE_REQUEST_RFCDEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: QIST
Program Name: SAPLQIST
Main Program:
Appliation area: Q
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QIST_VALUE_REQUEST_RFCDEST 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 'QIST_VALUE_REQUEST_RFCDEST'"NOTRANSL: Auswahl einer RFC-Destination zu einer Auswertemethode.
EXPORTING
I_METHOD = "Evaluation method
IMPORTING
E_RFCDEST = "RFC Destination
E_RFCTXT = "Description of RFC connection
EXCEPTIONS
NO_RFCDEST = 1 INVALID_METHOD = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLQIST_001 Generation of Report Header
EXIT_SAPLQIST_002 Generation of Material Data
EXIT_SAPLQIST_003 Generation of Vendor Data
EXIT_SAPLQIST_004 Generation of Characteristic Header
EXIT_SAPLQIST_005 Generation of Quantitative Characteristic
EXIT_SAPLQIST_007 Generation of Sample Header
EXIT_SAPLQIST_008 Generation of Additional Data for Results
EXIT_SAPLQIST_009 Generation of Quantitative Results
EXIT_SAPLQIST_010 Generation of Method Data
IMPORTING Parameters details for QIST_VALUE_REQUEST_RFCDEST
I_METHOD - Evaluation method
Data type: QIMTH-METHODOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for QIST_VALUE_REQUEST_RFCDEST
E_RFCDEST - RFC Destination
Data type: QIMTH-RFC_DESTOptional: No
Call by Reference: No ( called with pass by value option)
E_RFCTXT - Description of RFC connection
Data type: RFCDOC-RFCDOC1Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_RFCDEST - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_METHOD - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for QIST_VALUE_REQUEST_RFCDEST 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_method | TYPE QIMTH-METHOD, " | |||
| lv_e_rfcdest | TYPE QIMTH-RFC_DEST, " | |||
| lv_no_rfcdest | TYPE QIMTH, " | |||
| lv_e_rfctxt | TYPE RFCDOC-RFCDOC1, " | |||
| lv_invalid_method | TYPE RFCDOC. " |
|   CALL FUNCTION 'QIST_VALUE_REQUEST_RFCDEST' "NOTRANSL: Auswahl einer RFC-Destination zu einer Auswertemethode |
| EXPORTING | ||
| I_METHOD | = lv_i_method | |
| IMPORTING | ||
| E_RFCDEST | = lv_e_rfcdest | |
| E_RFCTXT | = lv_e_rfctxt | |
| EXCEPTIONS | ||
| NO_RFCDEST = 1 | ||
| INVALID_METHOD = 2 | ||
| . " QIST_VALUE_REQUEST_RFCDEST | ||
ABAP code using 7.40 inline data declarations to call FM QIST_VALUE_REQUEST_RFCDEST
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 METHOD FROM QIMTH INTO @DATA(ld_i_method). | ||||
| "SELECT single RFC_DEST FROM QIMTH INTO @DATA(ld_e_rfcdest). | ||||
| "SELECT single RFCDOC1 FROM RFCDOC INTO @DATA(ld_e_rfctxt). | ||||
Search for further information about these or an SAP related objects