SAP SUSR_SUIM_API_RSUSR200 Function Module for









SUSR_SUIM_API_RSUSR200 is a standard susr suim api rsusr200 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 susr suim api rsusr200 FM, simply by entering the name SUSR_SUIM_API_RSUSR200 into the relevant SAP transaction such as SE37 or SE38.

Function Group: SUSR_SUIM_APIS
Program Name: SAPLSUSR_SUIM_APIS
Main Program: SAPLSUSD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SUSR_SUIM_API_RSUSR200 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_SUIM_API_RSUSR200'"
EXPORTING
* IT_BNAME = "
* IV_LOCKED = "
* IV_UNLOCKED = "
* IV_FAILLOG = 'X' "
* IV_SUCCLOG = 'X' "
* IV_UNUSED = 'X' "
* IV_DIAGUSER = 'X' "
* IV_COMMUSER = 'X' "
* IV_SYSUSER = 'X' "
* IV_SERVUSER = 'X' "
* IV_REFUSER = 'X' "
* IT_CLASS = "
* IV_DEFPASS = 'X' "
* IV_INITPASS = 'X' "
* IV_NOPASS = 'X' "
* IT_SECPOL = "
* IV_DTRDAT = "
* IV_DBCDA1 = "
* IV_VALID = 'X' "
* IV_NOTVALID = 'X' "
* IV_USER_LOCK = "
* IV_PWD_LOCK = "

IMPORTING
ET_USERS = "
RETURN = "

EXCEPTIONS
WRONG_PARAMETER_SET = 1
.



IMPORTING Parameters details for SUSR_SUIM_API_RSUSR200

IT_BNAME -

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

IV_LOCKED -

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

IV_UNLOCKED -

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

IV_FAILLOG -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SUCCLOG -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_UNUSED -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DIAGUSER -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_COMMUSER -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SYSUSER -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SERVUSER -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_REFUSER -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_CLASS -

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

IV_DEFPASS -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_INITPASS -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_NOPASS -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_SECPOL -

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

IV_DTRDAT -

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

IV_DBCDA1 -

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

IV_VALID -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_NOTVALID -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_USER_LOCK -

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

IV_PWD_LOCK -

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

EXPORTING Parameters details for SUSR_SUIM_API_RSUSR200

ET_USERS -

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

RETURN -

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

EXCEPTIONS details

WRONG_PARAMETER_SET -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SUSR_SUIM_API_RSUSR200 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_et_users  TYPE SUSR_T_RSUSR200_ALV, "   
lv_it_bname  TYPE SUSR_T_RANGE_4_XUBNAME, "   
lv_wrong_parameter_set  TYPE SUSR_T_RANGE_4_XUBNAME, "   
lv_iv_locked  TYPE BOOLE_D, "   
lv_iv_unlocked  TYPE BOOLE_D, "   
lv_iv_faillog  TYPE BOOLE_D, "   'X'
lv_iv_succlog  TYPE BOOLE_D, "   'X'
lv_iv_unused  TYPE BOOLE_D, "   'X'
lv_iv_diaguser  TYPE BOOLE_D, "   'X'
lv_iv_commuser  TYPE BOOLE_D, "   'X'
lv_iv_sysuser  TYPE BOOLE_D, "   'X'
lv_iv_servuser  TYPE BOOLE_D, "   'X'
lv_iv_refuser  TYPE BOOLE_D, "   'X'
lv_return  TYPE BAPIRET2_T, "   
lv_it_class  TYPE SUSR_T_SEL_OPT_GROUP, "   
lv_iv_defpass  TYPE BOOLE_D, "   'X'
lv_iv_initpass  TYPE BOOLE_D, "   'X'
lv_iv_nopass  TYPE BOOLE_D, "   'X'
lv_it_secpol  TYPE SUSR_T_SEL_OPT_SECPOL, "   
lv_iv_dtrdat  TYPE I, "   
lv_iv_dbcda1  TYPE I, "   
lv_iv_valid  TYPE BOOLE_D, "   'X'
lv_iv_notvalid  TYPE BOOLE_D, "   'X'
lv_iv_user_lock  TYPE SUIM_LOCK_SEL, "   
lv_iv_pwd_lock  TYPE SUIM_LOCK_SEL. "   

  CALL FUNCTION 'SUSR_SUIM_API_RSUSR200'  "
    EXPORTING
         IT_BNAME = lv_it_bname
         IV_LOCKED = lv_iv_locked
         IV_UNLOCKED = lv_iv_unlocked
         IV_FAILLOG = lv_iv_faillog
         IV_SUCCLOG = lv_iv_succlog
         IV_UNUSED = lv_iv_unused
         IV_DIAGUSER = lv_iv_diaguser
         IV_COMMUSER = lv_iv_commuser
         IV_SYSUSER = lv_iv_sysuser
         IV_SERVUSER = lv_iv_servuser
         IV_REFUSER = lv_iv_refuser
         IT_CLASS = lv_it_class
         IV_DEFPASS = lv_iv_defpass
         IV_INITPASS = lv_iv_initpass
         IV_NOPASS = lv_iv_nopass
         IT_SECPOL = lv_it_secpol
         IV_DTRDAT = lv_iv_dtrdat
         IV_DBCDA1 = lv_iv_dbcda1
         IV_VALID = lv_iv_valid
         IV_NOTVALID = lv_iv_notvalid
         IV_USER_LOCK = lv_iv_user_lock
         IV_PWD_LOCK = lv_iv_pwd_lock
    IMPORTING
         ET_USERS = lv_et_users
         RETURN = lv_return
    EXCEPTIONS
        WRONG_PARAMETER_SET = 1
. " SUSR_SUIM_API_RSUSR200




ABAP code using 7.40 inline data declarations to call FM SUSR_SUIM_API_RSUSR200

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_iv_faillog) = 'X'.
 
DATA(ld_iv_succlog) = 'X'.
 
DATA(ld_iv_unused) = 'X'.
 
DATA(ld_iv_diaguser) = 'X'.
 
DATA(ld_iv_commuser) = 'X'.
 
DATA(ld_iv_sysuser) = 'X'.
 
DATA(ld_iv_servuser) = 'X'.
 
DATA(ld_iv_refuser) = 'X'.
 
 
 
DATA(ld_iv_defpass) = 'X'.
 
DATA(ld_iv_initpass) = 'X'.
 
DATA(ld_iv_nopass) = 'X'.
 
 
 
 
DATA(ld_iv_valid) = 'X'.
 
DATA(ld_iv_notvalid) = 'X'.
 
 
 


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!