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

Function SUSR_USER_BNAME_FROM_ALIAS 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_BNAME_FROM_ALIAS'".
EXPORTING
ALIAS = "Internet User Alias
IMPORTING
BNAME = "User name in user master record
EXCEPTIONS
NO_BNAME_FOUND = 1
IMPORTING Parameters details for SUSR_USER_BNAME_FROM_ALIAS
ALIAS - Internet User Alias
Data type: BAPIALIASOptional: No
Call by Reference: Yes
EXPORTING Parameters details for SUSR_USER_BNAME_FROM_ALIAS
BNAME - User name in user master record
Data type: BAPIBNAME-BAPIBNAMEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_BNAME_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SUSR_USER_BNAME_FROM_ALIAS 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_alias | TYPE BAPIALIAS, " | |||
| lv_bname | TYPE BAPIBNAME-BAPIBNAME, " | |||
| lv_no_bname_found | TYPE BAPIBNAME. " |
|   CALL FUNCTION 'SUSR_USER_BNAME_FROM_ALIAS' " |
| EXPORTING | ||
| ALIAS | = lv_alias | |
| IMPORTING | ||
| BNAME | = lv_bname | |
| EXCEPTIONS | ||
| NO_BNAME_FOUND = 1 | ||
| . " SUSR_USER_BNAME_FROM_ALIAS | ||
ABAP code using 7.40 inline data declarations to call FM SUSR_USER_BNAME_FROM_ALIAS
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 BAPIBNAME FROM BAPIBNAME INTO @DATA(ld_bname). | ||||
Search for further information about these or an SAP related objects