SAP SUSR_USER_CHANGE Function Module for









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

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



Function SUSR_USER_CHANGE 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_USER_CHANGE'"
EXPORTING
USER_NAME = "
* CHANGE_UCLASS = ' ' "Character Field Length 1
* MAINT_FOR_OWN_USER_ONLY = ' ' "
* PRODUCTIVE_PWD = ' ' "
* USER_LOGONDATA = "
* PASSWORD = "Password
* DELETE_PASSWORD = "Deactivate Password
* USER_DEFAULTS = "
* USER_ADDRESS = "
* REF_USER = "User Name
* ALIAS = "Internet User Alias
* UCLASS = "

TABLES
* USER_PARAMETERS = "
* UCLASSSYS = "

EXCEPTIONS
USER_NAME_NOT_EXISTS = 1 PASSWORD_NOT_ALLOWED = 2 INTERNAL_ERROR = 3
.



IMPORTING Parameters details for SUSR_USER_CHANGE

USER_NAME -

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

CHANGE_UCLASS - Character Field Length 1

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

MAINT_FOR_OWN_USER_ONLY -

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

PRODUCTIVE_PWD -

Data type: BAPIFLAG-BAPIFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

USER_LOGONDATA -

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

PASSWORD - Password

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

DELETE_PASSWORD - Deactivate Password

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

USER_DEFAULTS -

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

USER_ADDRESS -

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

REF_USER - User Name

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

ALIAS - Internet User Alias

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

UCLASS -

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

TABLES Parameters details for SUSR_USER_CHANGE

USER_PARAMETERS -

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

UCLASSSYS -

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

EXCEPTIONS details

USER_NAME_NOT_EXISTS - User Does Not Exist

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

PASSWORD_NOT_ALLOWED -

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 SUSR_USER_CHANGE 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_user_name  TYPE USR02-BNAME, "   
lt_user_parameters  TYPE STANDARD TABLE OF USTYP_T_PARAMETERS, "   
lv_user_name_not_exists  TYPE USTYP_T_PARAMETERS, "   
lv_change_uclass  TYPE CHAR01, "   SPACE
lv_maint_for_own_user_only  TYPE CHAR01, "   SPACE
lv_productive_pwd  TYPE BAPIFLAG-BAPIFLAG, "   SPACE
lt_uclasssys  TYPE STANDARD TABLE OF BAPIUCLASSSYS, "   
lv_user_logondata  TYPE USLOGOND, "   
lv_password_not_allowed  TYPE USLOGOND, "   
lv_password  TYPE XU400-NEWCODE, "   
lv_internal_error  TYPE XU400, "   
lv_delete_password  TYPE XUMARK, "   
lv_user_defaults  TYPE USDEFAULTS, "   
lv_user_address  TYPE USADDRESS, "   
lv_ref_user  TYPE BAPIREFUS, "   
lv_alias  TYPE BAPIALIAS, "   
lv_uclass  TYPE BAPIUCLASS. "   

  CALL FUNCTION 'SUSR_USER_CHANGE'  "
    EXPORTING
         USER_NAME = lv_user_name
         CHANGE_UCLASS = lv_change_uclass
         MAINT_FOR_OWN_USER_ONLY = lv_maint_for_own_user_only
         PRODUCTIVE_PWD = lv_productive_pwd
         USER_LOGONDATA = lv_user_logondata
         PASSWORD = lv_password
         DELETE_PASSWORD = lv_delete_password
         USER_DEFAULTS = lv_user_defaults
         USER_ADDRESS = lv_user_address
         REF_USER = lv_ref_user
         ALIAS = lv_alias
         UCLASS = lv_uclass
    TABLES
         USER_PARAMETERS = lt_user_parameters
         UCLASSSYS = lt_uclasssys
    EXCEPTIONS
        USER_NAME_NOT_EXISTS = 1
        PASSWORD_NOT_ALLOWED = 2
        INTERNAL_ERROR = 3
. " SUSR_USER_CHANGE




ABAP code using 7.40 inline data declarations to call FM SUSR_USER_CHANGE

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 BNAME FROM USR02 INTO @DATA(ld_user_name).
 
 
 
DATA(ld_change_uclass) = ' '.
 
DATA(ld_maint_for_own_user_only) = ' '.
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_productive_pwd).
DATA(ld_productive_pwd) = ' '.
 
 
 
 
"SELECT single NEWCODE FROM XU400 INTO @DATA(ld_password).
 
 
 
 
 
 
 
 


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!