SAP Security User Information System (SUIM)

SAP Security User Information System (SUIM)


SAP User Information System (SUIM) is used to get the information about users, authorizations, roles and profiles in SAP system. we can explicitly search for users with critical authorizations and critical roles.

SUIM is also used for user, authorizations, role and profile comparisons. We can get the list of transaction codes in particular role. SUIM is also used for displaying change documents for users, roles, role assignments, profiles, authorizations and security policies.

Displaying users by their address:

Execute SUIM transaction code and select "users by Address Data" under Users menu 

 Or 

Use report RSUSR002_ADDRESS. Execute this report using SE38 transaction code.

Leave the fields empty and click on execute icon. This will display all the users in the system with their address.

Below is the output that shows the list of users by their address.


Below are the various reports that are used to display the users on various parameters.

RSUSR002 - Users by complex selection criteria
RSUSR006 - Users with unsuccessful logons
RSUSR200 - Users by logon date and password changes
RSUSR008_009_New - Users with critical authorizations

Display roles by complex selection criteria:

Report RSUSR070 is used to determine the roles by complex criteria.

Enter the authorization object and the activity under the "Selection according to authorization values". This will display the list of roles based on the selection criteria.

Use SUIM transaction code or use SE38 and execute report RSUSR070.

Enter the authorization object and the values as shown below.

Below are list of roles displayed as per the selection criteria

RSUSR010 is the report which is used to display the transactions that a user can execute. RSUSR050 report is used for comparing the user, roles, profiles and authorizations with in the same system and also between the different systems.

RSUSR100N is the report which is used for displaying the change documents for users.

Watch the below demo video on how to execute SAP Security programs.





Location: Chicago, IL, USA

Comments

Post a Comment

Popular posts from this blog

SAP Security: Critical Authorization Objects

SAP Security: Critical Authorization Objects 1. S_TABU_DIS: This authorization object enables authorization check for displaying or modifying the table content. For accessing the table data, users use SE16, SM30 or SM31 transaction codes. This object contains two fields, DICBERCLS (authorization group) and ACTCT. 2. S_RFC: This authorization object enables authorization check for remote function call to access program modules (function modules). This authorization object contains three fields, RFC_TYPE, RFC_NAME and ACTCT. 3. S_DATASET: This authorization object enable file access at operating system level. This gives permission to access files from ABAP programs. This object contains three fields, File name, Program and Activity. 4. S_ADMI_FCD: This authorization objects enable access to various administrator activities like system monitoring, spool administration, client creations, update administration etc. This object contains one field, system administration functions. 5. S_DE
Read more

SAP GRC Security Consultant Roles and Responsibilities

SAP GRC Security Consultant Roles and Responsibilities 1. SAP GRC Consultant should have a knowledge on Governance, Risk and Compliance products. 2. Should have a thorough knowledge as well as experience in relation between ERP and GRC systems. 3. Should have an experience in configuring and supporting of GRC components like ARA, ARM, BRM and EAM. 4. GRC consultant should be having good understanding of GRC architecture. 5. Should be having hands on experience in user provisioning, role management, risk analysis, emergency access management and monitoring. 6. Should have experience in pre installation, post installation, connector settings, rule building and MSMP workflows and BRF+ in the ARM and BRM components. 7. Should have experience in end to end implementation of GRC Access Controls. 8. Should have experience in designing and developing the SAP business process. 9. Should be able to gather business requirements and implement the same in the GRC AC modules like ARA, ARM, BRM and E
Read more

SAP Security: How to set auto Logoff for Inactive users in SAP

Image
How to set auto Logoff for Inactive users in SAP SAP provides an options for logging of inactive users in SAP automatically. Inactive means if there is no activity for a specific period of time. By setting the auto logoff improves the security in the SAP system. The auto logoff options is not active in the system by default. This needs to be activated using the profile parameter called rdisp/gui_auto_logout. The value for this parameter should be set in the form of seconds. The inactive users are logout of the system after the specific time period that is set in the parameter. The SAP system doesn't save the data before auto logoff and it does not popup any prompt before auto logoff. Procedure to set the value in the Profile parameter: Execute transaction code RZ10 Select the DEFAULT profile from the selection menu. Select the Extended maintenance and click on change icon. Click on the create parameter icon as shown below. Enter the new parameter name as rdisp/gui_auto_logout and c
Read more