SAP RSEC_USER_INTERFACE Function Module for BI AS: Interface for Processing Authorizations for Reporting Users

Search SAP Function Modules

RSEC_USER_INTERFACE is a standard rsec user interface SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BI AS: Interface for Processing Authorizations for Reporting Users 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 rsec user interface FM, simply by entering the name RSEC_USER_INTERFACE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSEC_SCREENS
Program Name: SAPLRSEC_SCREENS
Main Program: SAPLRSEC_SCREENS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSEC_USER_INTERFACE 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 'RSEC_USER_INTERFACE'"BI AS: Interface for Processing Authorizations for Reporting Users
  EXPORTING
   I_AUTHORIZATION =  "Authorization Name in User Master Maintenance
   I_UNAME =  "User Name in User Master Record
   I_ACTION =  "Activity

EXCEPTIONS
   PARAMS_INCOMPLETE = 1    NOT_AUTHORIZED_FOR_USER = 2    NOT_AUTHORIZED_FOR_AUTH = 3    USER_LOCKED = 4    BAD_ACTION = 5    UNKNOWN_ERROR = 6 

.

IMPORTING Parameters details for RSEC_USER_INTERFACE

I_AUTHORIZATION - Authorization Name in User Master Maintenance

Data type: XUAUTH
Optional: No
Call by Reference: Yes

I_UNAME - User Name in User Master Record

Data type: XUBNAME
Optional: No
Call by Reference: Yes

I_ACTION - Activity

Data type: ACTIV_AUTH
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PARAMS_INCOMPLETE -

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED_FOR_USER -

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED_FOR_AUTH -

Data type:
Optional: No
Call by Reference: Yes

USER_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

BAD_ACTION -

Data type:
Optional: No
Call by Reference: Yes

UNKNOWN_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSEC_USER_INTERFACE 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.

ABAP code using 7.40 inline data declarations to call FM RSEC_USER_INTERFACE

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