SAP SUSR_GET_CHANGED_USERS Function Module for









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

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



Function SUSR_GET_CHANGED_USERS 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_GET_CHANGED_USERS'"
EXPORTING
IV_MODDATE = "
IV_MODTIME = "
IV_OPTION = "
* IV_MODDATE_TO = "
* IV_MODTIME_TO = "

IMPORTING
ET_USERS_CHANGED = "
ET_RETURN = "
.



IMPORTING Parameters details for SUSR_GET_CHANGED_USERS

IV_MODDATE -

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

IV_MODTIME -

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

IV_OPTION -

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

IV_MODDATE_TO -

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

IV_MODTIME_TO -

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

EXPORTING Parameters details for SUSR_GET_CHANGED_USERS

ET_USERS_CHANGED -

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

ET_RETURN -

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

Copy and paste ABAP code example for SUSR_GET_CHANGED_USERS 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_iv_moddate  TYPE XUMODDATE, "   
lv_et_users_changed  TYPE SUID_TT_BNAME, "   
lv_et_return  TYPE BAPIRET2_T, "   
lv_iv_modtime  TYPE XUMODTIME, "   
lv_iv_option  TYPE XUOPTION, "   
lv_iv_moddate_to  TYPE XUMODDATE, "   
lv_iv_modtime_to  TYPE XUMODTIME. "   

  CALL FUNCTION 'SUSR_GET_CHANGED_USERS'  "
    EXPORTING
         IV_MODDATE = lv_iv_moddate
         IV_MODTIME = lv_iv_modtime
         IV_OPTION = lv_iv_option
         IV_MODDATE_TO = lv_iv_moddate_to
         IV_MODTIME_TO = lv_iv_modtime_to
    IMPORTING
         ET_USERS_CHANGED = lv_et_users_changed
         ET_RETURN = lv_et_return
. " SUSR_GET_CHANGED_USERS




ABAP code using 7.40 inline data declarations to call FM SUSR_GET_CHANGED_USERS

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



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!