SAP SUSR_USER_AUTH_FOR_OBJ_GET Function Module for Display authorizations (for a specified object) belonging to a user
SUSR_USER_AUTH_FOR_OBJ_GET is a standard susr user auth for obj get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display authorizations (for a specified object) belonging to a user processing and below is the pattern details for this FM, 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 auth for obj get FM, simply by entering the name SUSR_USER_AUTH_FOR_OBJ_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SUSE
Program Name: SAPLSUSE
Main Program: SAPLSUSE
Appliation area: S
Release date: 05-May-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SUSR_USER_AUTH_FOR_OBJ_GET 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_AUTH_FOR_OBJ_GET'"Display authorizations (for a specified object) belonging to a user.
EXPORTING
* NEW_BUFFERING = 3 "Flag for various authorization programs
* MANDANT = SY-MANDT "SAP System, Client Number from Logon
USER_NAME = "User Name in User Master Record
* SEL_OBJECT = "Authorization object for restriction
TABLES
VALUES = "Field values
EXCEPTIONS
USER_NAME_NOT_EXIST = 1 NOT_AUTHORIZED = 2 INTERNAL_ERROR = 3
IMPORTING Parameters details for SUSR_USER_AUTH_FOR_OBJ_GET
NEW_BUFFERING - Flag for various authorization programs
Data type: XUFLAGDefault: 3
Optional: Yes
Call by Reference: No ( called with pass by value option)
MANDANT - SAP System, Client Number from Logon
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
USER_NAME - User Name in User Master Record
Data type: USR02-BNAMEOptional: No
Call by Reference: No ( called with pass by value option)
SEL_OBJECT - Authorization object for restriction
Data type: UST12-OBJCTOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SUSR_USER_AUTH_FOR_OBJ_GET
VALUES - Field values
Data type: USVALUESOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
USER_NAME_NOT_EXIST - User name does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_AUTHORIZED - No authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - 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_AUTH_FOR_OBJ_GET 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_values | TYPE STANDARD TABLE OF USVALUES, " | |||
| lv_new_buffering | TYPE XUFLAG, " 3 | |||
| lv_user_name_not_exist | TYPE XUFLAG, " | |||
| lv_mandant | TYPE SY-MANDT, " SY-MANDT | |||
| lv_not_authorized | TYPE SY, " | |||
| lv_user_name | TYPE USR02-BNAME, " | |||
| lv_internal_error | TYPE USR02, " | |||
| lv_sel_object | TYPE UST12-OBJCT. " |
|   CALL FUNCTION 'SUSR_USER_AUTH_FOR_OBJ_GET' "Display authorizations (for a specified object) belonging to a user |
| EXPORTING | ||
| NEW_BUFFERING | = lv_new_buffering | |
| MANDANT | = lv_mandant | |
| USER_NAME | = lv_user_name | |
| SEL_OBJECT | = lv_sel_object | |
| TABLES | ||
| VALUES | = lt_values | |
| EXCEPTIONS | ||
| USER_NAME_NOT_EXIST = 1 | ||
| NOT_AUTHORIZED = 2 | ||
| INTERNAL_ERROR = 3 | ||
| . " SUSR_USER_AUTH_FOR_OBJ_GET | ||
ABAP code using 7.40 inline data declarations to call FM SUSR_USER_AUTH_FOR_OBJ_GET
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.| DATA(ld_new_buffering) | = 3. | |||
| "SELECT single MANDT FROM SY INTO @DATA(ld_mandant). | ||||
| DATA(ld_mandant) | = SY-MANDT. | |||
| "SELECT single BNAME FROM USR02 INTO @DATA(ld_user_name). | ||||
| "SELECT single OBJCT FROM UST12 INTO @DATA(ld_sel_object). | ||||
Search for further information about these or an SAP related objects