SAP VARI_USER_VARS_DIALOG Function Module for
VARI_USER_VARS_DIALOG is a standard vari user vars dialog 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 vari user vars dialog FM, simply by entering the name VARI_USER_VARS_DIALOG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SVUV
Program Name: SAPLSVUV
Main Program: SAPLSVUV
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VARI_USER_VARS_DIALOG 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 'VARI_USER_VARS_DIALOG'".
EXPORTING
PARAMID = "
* USER = SY-UNAME "List of Users
* JUST_P_OR_S = ' ' "
* JUST_DISPLAY = ' ' "
* SUPPRESS_MESSAGE = ' ' "
* CALLED_FROM_SELSCREEN = ' ' "
* DESC_SEL = ' ' "
* NAME_PAR = ' ' "
* TEXT_PAR = ' ' "
IMPORTING
SAVE_OR_CANCEL = "
EXCEPTIONS
INVALID_USER = 1 INVALID_PARAMID = 2 ILLEGAL_P_OR_S = 3 OBJECT_LOCKED = 4 ENQUEUE_INTERNAL_ERROR = 5 INTERNAL_ERROR = 6
IMPORTING Parameters details for VARI_USER_VARS_DIALOG
PARAMID -
Data type: TUVID-PARAMIDOptional: No
Call by Reference: No ( called with pass by value option)
USER - List of Users
Data type: TVARUVN-BNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
JUST_P_OR_S -
Data type: VUVVALUES-KINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
JUST_DISPLAY -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SUPPRESS_MESSAGE -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CALLED_FROM_SELSCREEN -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DESC_SEL -
Data type: RSSELINTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NAME_PAR -
Data type: RSSCR-NAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TEXT_PAR -
Data type: RSPARINT-TEXTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for VARI_USER_VARS_DIALOG
SAVE_OR_CANCEL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_USER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_PARAMID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_P_OR_S -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_LOCKED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENQUEUE_INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VARI_USER_VARS_DIALOG 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_paramid | TYPE TUVID-PARAMID, " | |||
| lv_invalid_user | TYPE TUVID, " | |||
| lv_save_or_cancel | TYPE TUVID, " | |||
| lv_user | TYPE TVARUVN-BNAME, " SY-UNAME | |||
| lv_invalid_paramid | TYPE TVARUVN, " | |||
| lv_just_p_or_s | TYPE VUVVALUES-KIND, " SPACE | |||
| lv_illegal_p_or_s | TYPE VUVVALUES, " | |||
| lv_just_display | TYPE VUVVALUES, " SPACE | |||
| lv_object_locked | TYPE VUVVALUES, " | |||
| lv_suppress_message | TYPE VUVVALUES, " SPACE | |||
| lv_enqueue_internal_error | TYPE VUVVALUES, " | |||
| lv_internal_error | TYPE VUVVALUES, " | |||
| lv_called_from_selscreen | TYPE VUVVALUES, " SPACE | |||
| lv_desc_sel | TYPE RSSELINT, " SPACE | |||
| lv_name_par | TYPE RSSCR-NAME, " SPACE | |||
| lv_text_par | TYPE RSPARINT-TEXT. " SPACE |
|   CALL FUNCTION 'VARI_USER_VARS_DIALOG' " |
| EXPORTING | ||
| PARAMID | = lv_paramid | |
| USER | = lv_user | |
| JUST_P_OR_S | = lv_just_p_or_s | |
| JUST_DISPLAY | = lv_just_display | |
| SUPPRESS_MESSAGE | = lv_suppress_message | |
| CALLED_FROM_SELSCREEN | = lv_called_from_selscreen | |
| DESC_SEL | = lv_desc_sel | |
| NAME_PAR | = lv_name_par | |
| TEXT_PAR | = lv_text_par | |
| IMPORTING | ||
| SAVE_OR_CANCEL | = lv_save_or_cancel | |
| EXCEPTIONS | ||
| INVALID_USER = 1 | ||
| INVALID_PARAMID = 2 | ||
| ILLEGAL_P_OR_S = 3 | ||
| OBJECT_LOCKED = 4 | ||
| ENQUEUE_INTERNAL_ERROR = 5 | ||
| INTERNAL_ERROR = 6 | ||
| . " VARI_USER_VARS_DIALOG | ||
ABAP code using 7.40 inline data declarations to call FM VARI_USER_VARS_DIALOG
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 PARAMID FROM TUVID INTO @DATA(ld_paramid). | ||||
| "SELECT single BNAME FROM TVARUVN INTO @DATA(ld_user). | ||||
| DATA(ld_user) | = SY-UNAME. | |||
| "SELECT single KIND FROM VUVVALUES INTO @DATA(ld_just_p_or_s). | ||||
| DATA(ld_just_p_or_s) | = ' '. | |||
| DATA(ld_just_display) | = ' '. | |||
| DATA(ld_suppress_message) | = ' '. | |||
| DATA(ld_called_from_selscreen) | = ' '. | |||
| DATA(ld_desc_sel) | = ' '. | |||
| "SELECT single NAME FROM RSSCR INTO @DATA(ld_name_par). | ||||
| DATA(ld_name_par) | = ' '. | |||
| "SELECT single TEXT FROM RSPARINT INTO @DATA(ld_text_par). | ||||
| DATA(ld_text_par) | = ' '. | |||
Search for further information about these or an SAP related objects