SAP SUSR_DDL_USERS_BY_AUTHVALUES Function Module for Users by Authorization Values
SUSR_DDL_USERS_BY_AUTHVALUES is a standard susr ddl users by authvalues SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Users by Authorization Values 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 susr ddl users by authvalues FM, simply by entering the name SUSR_DDL_USERS_BY_AUTHVALUES into the relevant SAP transaction such as SE37 or SE38.
Function Group: SUSR_DDL_QUERIES
Program Name: SAPLSUSR_DDL_QUERIES
Main Program: SAPLSUSR_DDL_QUERIES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SUSR_DDL_USERS_BY_AUTHVALUES 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 'SUSR_DDL_USERS_BY_AUTHVALUES'"Users by Authorization Values.
EXPORTING
ID_SUSO = "Authorization Object
* ID_FLD5 = "Authorization Field
* ID_VAL5 = "Authorization Value
* ID_FLD6 = "Authorization Field
* ID_VAL6 = "Authorization Value
* ID_FLD7 = "Authorization Field
* ID_VAL7 = "Authorization Value
* ID_FLD8 = "Authorization Field
* ID_VAL8 = "Authorization Value
* ID_FLD9 = "Authorization Field
* ID_VAL9 = "Authorization Value
* ID_FLD1 = "Authorization Field
* ID_FLD0 = "Authorization Field
* ID_VAL0 = "Authorization Value
* ID_VAL1 = "Authorization Value
* ID_FLD2 = "Authorization Field
* ID_VAL2 = "Authorization Value
* ID_FLD3 = "Authorization Field
* ID_VAL3 = "Authorization Value
* ID_FLD4 = "Authorization Field
* ID_VAL4 = "Authorization Value
IMPORTING
ET_MESSAGES = "Table with BAPI Return Information
ET_USERS = "Table type for user name
IMPORTING Parameters details for SUSR_DDL_USERS_BY_AUTHVALUES
ID_SUSO - Authorization Object
Data type: XUOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
ID_FLD5 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL5 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FLD6 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL6 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FLD7 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL7 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FLD8 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL8 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FLD9 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL9 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FLD1 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FLD0 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL0 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL1 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FLD2 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL2 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FLD3 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL3 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FLD4 - Authorization Field
Data type: XUFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VAL4 - Authorization Value
Data type: XUVALOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUSR_DDL_USERS_BY_AUTHVALUES
ET_MESSAGES - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
ET_USERS - Table type for user name
Data type: SUSR_USERNAME_TOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUSR_DDL_USERS_BY_AUTHVALUES 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_suso | TYPE XUOBJECT, " | |||
| lv_et_messages | TYPE BAPIRETTAB, " | |||
| lv_id_fld5 | TYPE XUFIELD, " | |||
| lv_id_val5 | TYPE XUVAL, " | |||
| lv_id_fld6 | TYPE XUFIELD, " | |||
| lv_id_val6 | TYPE XUVAL, " | |||
| lv_id_fld7 | TYPE XUFIELD, " | |||
| lv_id_val7 | TYPE XUVAL, " | |||
| lv_id_fld8 | TYPE XUFIELD, " | |||
| lv_id_val8 | TYPE XUVAL, " | |||
| lv_id_fld9 | TYPE XUFIELD, " | |||
| lv_id_val9 | TYPE XUVAL, " | |||
| lv_id_fld1 | TYPE XUFIELD, " | |||
| lv_et_users | TYPE SUSR_USERNAME_T, " | |||
| lv_id_fld0 | TYPE XUFIELD, " | |||
| lv_id_val0 | TYPE XUVAL, " | |||
| lv_id_val1 | TYPE XUVAL, " | |||
| lv_id_fld2 | TYPE XUFIELD, " | |||
| lv_id_val2 | TYPE XUVAL, " | |||
| lv_id_fld3 | TYPE XUFIELD, " | |||
| lv_id_val3 | TYPE XUVAL, " | |||
| lv_id_fld4 | TYPE XUFIELD, " | |||
| lv_id_val4 | TYPE XUVAL. " |
|   CALL FUNCTION 'SUSR_DDL_USERS_BY_AUTHVALUES' "Users by Authorization Values |
| EXPORTING | ||
| ID_SUSO | = lv_id_suso | |
| ID_FLD5 | = lv_id_fld5 | |
| ID_VAL5 | = lv_id_val5 | |
| ID_FLD6 | = lv_id_fld6 | |
| ID_VAL6 | = lv_id_val6 | |
| ID_FLD7 | = lv_id_fld7 | |
| ID_VAL7 | = lv_id_val7 | |
| ID_FLD8 | = lv_id_fld8 | |
| ID_VAL8 | = lv_id_val8 | |
| ID_FLD9 | = lv_id_fld9 | |
| ID_VAL9 | = lv_id_val9 | |
| ID_FLD1 | = lv_id_fld1 | |
| ID_FLD0 | = lv_id_fld0 | |
| ID_VAL0 | = lv_id_val0 | |
| ID_VAL1 | = lv_id_val1 | |
| ID_FLD2 | = lv_id_fld2 | |
| ID_VAL2 | = lv_id_val2 | |
| ID_FLD3 | = lv_id_fld3 | |
| ID_VAL3 | = lv_id_val3 | |
| ID_FLD4 | = lv_id_fld4 | |
| ID_VAL4 | = lv_id_val4 | |
| IMPORTING | ||
| ET_MESSAGES | = lv_et_messages | |
| ET_USERS | = lv_et_users | |
| . " SUSR_DDL_USERS_BY_AUTHVALUES | ||
ABAP code using 7.40 inline data declarations to call FM SUSR_DDL_USERS_BY_AUTHVALUES
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.Search for further information about these or an SAP related objects