SAP SUSR_GET_ADMIN_USER_LOGIN_INFO Function Module for
SUSR_GET_ADMIN_USER_LOGIN_INFO is a standard susr get admin user login info 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 admin user login info FM, simply by entering the name SUSR_GET_ADMIN_USER_LOGIN_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: SUSO
Program Name: SAPLSUSO
Main Program: SAPLSUSO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SUSR_GET_ADMIN_USER_LOGIN_INFO 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_ADMIN_USER_LOGIN_INFO'".
EXPORTING
* USERID = "User name in user master record
* ALIASNAME = "Internet User Alias
* AUTHORITY_CHECK = "
IMPORTING
USER_ID = "User name in user master record
PASSWORD_STATUS = "Status of the User Password (Values: -2/-1/0/1/2, see Docu)
LOCK_STATUS = "
LAST_LOGON_DATE = "Last logon date
EXCEPTIONS
NOT_AUTHORIZED = 1 NO_USERID_FOR_ALIASNAME = 2 PARAMETER_MISSING = 3 USER_NOT_EXISTS = 4 INTERNAL_ERROR = 5
IMPORTING Parameters details for SUSR_GET_ADMIN_USER_LOGIN_INFO
USERID - User name in user master record
Data type: XUBNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
ALIASNAME - Internet User Alias
Data type: USALIASOptional: Yes
Call by Reference: No ( called with pass by value option)
AUTHORITY_CHECK -
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUSR_GET_ADMIN_USER_LOGIN_INFO
USER_ID - User name in user master record
Data type: XUBNAMEOptional: No
Call by Reference: No ( called with pass by value option)
PASSWORD_STATUS - Status of the User Password (Values: -2/-1/0/1/2, see Docu)
Data type: XUPWDSTATEOptional: No
Call by Reference: No ( called with pass by value option)
LOCK_STATUS -
Data type: XUUFLAGOptional: No
Call by Reference: No ( called with pass by value option)
LAST_LOGON_DATE - Last logon date
Data type: XULDATEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_AUTHORIZED -
Data type:Optional: No
Call by Reference: Yes
NO_USERID_FOR_ALIASNAME -
Data type:Optional: No
Call by Reference: Yes
PARAMETER_MISSING -
Data type:Optional: No
Call by Reference: Yes
USER_NOT_EXISTS -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SUSR_GET_ADMIN_USER_LOGIN_INFO 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_userid | TYPE XUBNAME, " | |||
| lv_user_id | TYPE XUBNAME, " | |||
| lv_not_authorized | TYPE XUBNAME, " | |||
| lv_aliasname | TYPE USALIAS, " | |||
| lv_password_status | TYPE XUPWDSTATE, " | |||
| lv_no_userid_for_aliasname | TYPE XUPWDSTATE, " | |||
| lv_lock_status | TYPE XUUFLAG, " | |||
| lv_authority_check | TYPE CHAR1, " | |||
| lv_parameter_missing | TYPE CHAR1, " | |||
| lv_last_logon_date | TYPE XULDATE, " | |||
| lv_user_not_exists | TYPE XULDATE, " | |||
| lv_internal_error | TYPE XULDATE. " |
|   CALL FUNCTION 'SUSR_GET_ADMIN_USER_LOGIN_INFO' " |
| EXPORTING | ||
| USERID | = lv_userid | |
| ALIASNAME | = lv_aliasname | |
| AUTHORITY_CHECK | = lv_authority_check | |
| IMPORTING | ||
| USER_ID | = lv_user_id | |
| PASSWORD_STATUS | = lv_password_status | |
| LOCK_STATUS | = lv_lock_status | |
| LAST_LOGON_DATE | = lv_last_logon_date | |
| EXCEPTIONS | ||
| NOT_AUTHORIZED = 1 | ||
| NO_USERID_FOR_ALIASNAME = 2 | ||
| PARAMETER_MISSING = 3 | ||
| USER_NOT_EXISTS = 4 | ||
| INTERNAL_ERROR = 5 | ||
| . " SUSR_GET_ADMIN_USER_LOGIN_INFO | ||
ABAP code using 7.40 inline data declarations to call FM SUSR_GET_ADMIN_USER_LOGIN_INFO
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