SAP Security: Authorization Concept

 Authorization Concept in SAP System

Authorization concept in the SAP system is all about protecting programs, transaction codes, reports and other services.  Security Administrators/User Administrators assign any authorizations to users based on this concept. These authorizations determine what actions user can perform in the SAP system.

Transactions or programs are protected by authorization objects, so user requires corresponding authorization objects for executing transactions or programs. Authorization profile is a combination of authorizations which is associated with the role. Role is assigned to users, so the user can then get access to the authorizations.




Overview of the elements of SAP Authorization Objects

1. Authorization Object Class: It is a logical grouping of authorization objects.
Example all authorization objects for class FI starts with “F_” and for class MM starts with "M_".

2. Authorization Object: It is a group of 1 to 10 authorization fields. Authorizations provide access to the actions that any user want to execute. Authorizations are divided based on the object class. For example all the finance related objects are grouped under FI object class, for human recourses it is HR, for sales and distributions it is SD and so on. 
Example S_TABU_DIS, S_USER_PRO, F_BKPF_BUK etc.

Below are the permitted activities for this authorization object.


3. Authorization field: It is a smallest using where an authorization check should be executed.
Example ACTVT, BUKRS, CLASS etc.

4. Single roles: Single role is created using PFCG transaction code. Single roles includes an authorization data like authorization objects, fields and field values. It also contains menu for the user. Single roles are generated in PFCG to get the authorization profiles.

5. Composite roles: It includes more than one single roles. Follow the procedure mentioned in the link to create composite roles.



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