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

Function SUSR_USER_BUFFER_AFTER_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_BUFFER_AFTER_CHANGE'".
EXPORTING
* CLIENT = "
* USERNAME = "User name in user master record
* PROFILE = "
* IV_COMMIT_CONTROL = IF_IDENTITY=>CO_FALSE "
IMPORTING
NEW_BUFFERING = "
SUBRC = "Return Value, Return Value After ABAP Statements
TABLES
* USERS = "R/3 System, Client Number from Logon
* USERS_OUT = "
IMPORTING Parameters details for SUSR_USER_BUFFER_AFTER_CHANGE
CLIENT -
Data type: T000-MANDTOptional: Yes
Call by Reference: No ( called with pass by value option)
USERNAME - User name in user master record
Data type: USR02-BNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
PROFILE -
Data type: UST04-PROFILEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_COMMIT_CONTROL -
Data type: SESF_BOOLEANDefault: IF_IDENTITY=>CO_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUSR_USER_BUFFER_AFTER_CHANGE
NEW_BUFFERING -
Data type: UST04-PROFILEOptional: No
Call by Reference: No ( called with pass by value option)
SUBRC - Return Value, Return Value After ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SUSR_USER_BUFFER_AFTER_CHANGE
USERS - R/3 System, Client Number from Logon
Data type: USDELETEOptional: Yes
Call by Reference: Yes
USERS_OUT -
Data type: USRBF3Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SUSR_USER_BUFFER_AFTER_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: | ||||
| lt_users | TYPE STANDARD TABLE OF USDELETE, " | |||
| lv_client | TYPE T000-MANDT, " | |||
| lv_new_buffering | TYPE UST04-PROFILE, " | |||
| lv_subrc | TYPE SY-SUBRC, " | |||
| lv_username | TYPE USR02-BNAME, " | |||
| lt_users_out | TYPE STANDARD TABLE OF USRBF3, " | |||
| lv_profile | TYPE UST04-PROFILE, " | |||
| lv_iv_commit_control | TYPE SESF_BOOLEAN. " IF_IDENTITY=>CO_FALSE |
|   CALL FUNCTION 'SUSR_USER_BUFFER_AFTER_CHANGE' " |
| EXPORTING | ||
| CLIENT | = lv_client | |
| USERNAME | = lv_username | |
| PROFILE | = lv_profile | |
| IV_COMMIT_CONTROL | = lv_iv_commit_control | |
| IMPORTING | ||
| NEW_BUFFERING | = lv_new_buffering | |
| SUBRC | = lv_subrc | |
| TABLES | ||
| USERS | = lt_users | |
| USERS_OUT | = lt_users_out | |
| . " SUSR_USER_BUFFER_AFTER_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM SUSR_USER_BUFFER_AFTER_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 MANDT FROM T000 INTO @DATA(ld_client). | ||||
| "SELECT single PROFILE FROM UST04 INTO @DATA(ld_new_buffering). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_subrc). | ||||
| "SELECT single BNAME FROM USR02 INTO @DATA(ld_username). | ||||
| "SELECT single PROFILE FROM UST04 INTO @DATA(ld_profile). | ||||
| DATA(ld_iv_commit_control) | = IF_IDENTITY=>CO_FALSE. | |||
Search for further information about these or an SAP related objects