SAP RFDKSEL_GET_VALUES Function Module for
RFDKSEL_GET_VALUES is a standard rfdksel get values 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 rfdksel get values FM, simply by entering the name RFDKSEL_GET_VALUES into the relevant SAP transaction such as SE37 or SE38.
Function Group: RFDKSEL
Program Name: SAPLRFDKSEL
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RFDKSEL_GET_VALUES 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 'RFDKSEL_GET_VALUES'".
EXPORTING
ID_KOART = "
ID_VARIANT = "
TABLES
ET_ACCOUNTS = "
EXCEPTIONS
INCORRECT_VARIANT = 1
IMPORTING Parameters details for RFDKSEL_GET_VALUES
ID_KOART -
Data type: KOARTOptional: No
Call by Reference: Yes
ID_VARIANT -
Data type: RSVAR-VARIANTOptional: No
Call by Reference: Yes
TABLES Parameters details for RFDKSEL_GET_VALUES
ET_ACCOUNTS -
Data type: RFDKSEL_RESULTOptional: No
Call by Reference: Yes
EXCEPTIONS details
INCORRECT_VARIANT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RFDKSEL_GET_VALUES 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_id_koart | TYPE KOART, " | |||
| lt_et_accounts | TYPE STANDARD TABLE OF RFDKSEL_RESULT, " | |||
| lv_incorrect_variant | TYPE RFDKSEL_RESULT, " | |||
| lv_id_variant | TYPE RSVAR-VARIANT. " |
|   CALL FUNCTION 'RFDKSEL_GET_VALUES' " |
| EXPORTING | ||
| ID_KOART | = lv_id_koart | |
| ID_VARIANT | = lv_id_variant | |
| TABLES | ||
| ET_ACCOUNTS | = lt_et_accounts | |
| EXCEPTIONS | ||
| INCORRECT_VARIANT = 1 | ||
| . " RFDKSEL_GET_VALUES | ||
ABAP code using 7.40 inline data declarations to call FM RFDKSEL_GET_VALUES
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 VARIANT FROM RSVAR INTO @DATA(ld_id_variant). | ||||
Search for further information about these or an SAP related objects