SAP R_FDKUSER_GET_VALUES Function Module for









R_FDKUSER_GET_VALUES is a standard r fdkuser 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 r fdkuser get values FM, simply by entering the name R_FDKUSER_GET_VALUES into the relevant SAP transaction such as SE37 or SE38.

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



Function R_FDKUSER_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 'R_FDKUSER_GET_VALUES'"
EXPORTING
ID_USER = "
ID_ACTION = "
* ID_NO_DIALOG = ' ' "
* ID_A_SEG = ' ' "
* ID_DATESELECT_KEY = 'SAP' "
* ID_CALLBACK_REPID = "
* ID_SET_TITLE_FORM = "
* ID_HEADERLINE = "

TABLES
* IT_DIALOG_FIELDS = "
* IT_CUSTOM_BUTTONS = "
* IT_RESTRICTIONS = "
* ET_ACCOUNTS = "
* ET_SELECTIONS = "

EXCEPTIONS
ACTION_NOT_ALLOWED = 1 INCORRECT_INPUT = 2 EXIT_REQUEST = 3
.



IMPORTING Parameters details for R_FDKUSER_GET_VALUES

ID_USER -

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

ID_ACTION -

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

ID_NO_DIALOG -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

ID_A_SEG -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

ID_DATESELECT_KEY -

Data type: FDKKEYNAME
Default: 'SAP'
Optional: Yes
Call by Reference: Yes

ID_CALLBACK_REPID -

Data type: SY-REPID
Optional: Yes
Call by Reference: Yes

ID_SET_TITLE_FORM -

Data type: EDPERFORM
Optional: Yes
Call by Reference: Yes

ID_HEADERLINE -

Data type: FDKHEADERLINE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for R_FDKUSER_GET_VALUES

IT_DIALOG_FIELDS -

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

IT_CUSTOM_BUTTONS -

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

IT_RESTRICTIONS -

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

ET_ACCOUNTS -

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

ET_SELECTIONS -

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

EXCEPTIONS details

ACTION_NOT_ALLOWED -

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

INCORRECT_INPUT -

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

EXIT_REQUEST -

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

Copy and paste ABAP code example for R_FDKUSER_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_user  TYPE XUBNAME, "   
lt_it_dialog_fields  TYPE STANDARD TABLE OF FDKFIELDS, "   
lv_action_not_allowed  TYPE FDKFIELDS, "   
lv_id_action  TYPE FDKACTION, "   
lv_incorrect_input  TYPE FDKACTION, "   
lt_it_custom_buttons  TYPE STANDARD TABLE OF FDKBUTTONS, "   
lv_exit_request  TYPE FDKBUTTONS, "   
lv_id_no_dialog  TYPE XFELD, "   SPACE
lt_it_restrictions  TYPE STANDARD TABLE OF COSEL, "   
lv_id_a_seg  TYPE XFELD, "   SPACE
lt_et_accounts  TYPE STANDARD TABLE OF FDKACCOUNTS, "   
lt_et_selections  TYPE STANDARD TABLE OF COSEL, "   
lv_id_dateselect_key  TYPE FDKKEYNAME, "   'SAP'
lv_id_callback_repid  TYPE SY-REPID, "   
lv_id_set_title_form  TYPE EDPERFORM, "   
lv_id_headerline  TYPE FDKHEADERLINE. "   

  CALL FUNCTION 'R_FDKUSER_GET_VALUES'  "
    EXPORTING
         ID_USER = lv_id_user
         ID_ACTION = lv_id_action
         ID_NO_DIALOG = lv_id_no_dialog
         ID_A_SEG = lv_id_a_seg
         ID_DATESELECT_KEY = lv_id_dateselect_key
         ID_CALLBACK_REPID = lv_id_callback_repid
         ID_SET_TITLE_FORM = lv_id_set_title_form
         ID_HEADERLINE = lv_id_headerline
    TABLES
         IT_DIALOG_FIELDS = lt_it_dialog_fields
         IT_CUSTOM_BUTTONS = lt_it_custom_buttons
         IT_RESTRICTIONS = lt_it_restrictions
         ET_ACCOUNTS = lt_et_accounts
         ET_SELECTIONS = lt_et_selections
    EXCEPTIONS
        ACTION_NOT_ALLOWED = 1
        INCORRECT_INPUT = 2
        EXIT_REQUEST = 3
. " R_FDKUSER_GET_VALUES




ABAP code using 7.40 inline data declarations to call FM R_FDKUSER_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.

 
 
 
 
 
 
 
DATA(ld_id_no_dialog) = ' '.
 
 
DATA(ld_id_a_seg) = ' '.
 
 
 
DATA(ld_id_dateselect_key) = 'SAP'.
 
"SELECT single REPID FROM SY INTO @DATA(ld_id_callback_repid).
 
 
 


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!