How To Create Composite Roles In SAP

 How To Create Composite Roles In SAP


We have seen how to create single roles and assigning the roles to user master records. In this blog we will see how to create composite roles and assigning these roles to users in SAP.

Composite roles consists of single roles. One composite role can have multiple single roles. When the composite roles are assigned to users, the single roles with in the composite role gets assigned to user automatically. Composite roles do not contain any authorization data. All the authorizations comes from the single roles.

Composite roles are useful when the user requires authorizations for multiple roles. We can assign one composite role instead of assigning multiple single roles. Composite roles can not be included in another composite role.

Procedure for creating Composite roles:

1. Go to SAP menu-->Administration-->User Maintenance-->Role Maintenance or execute transaction code PFCG

SAP System do not recognize the single role and composite role. So when creating these roles system admin has to make naming convention to distinguish between the single and composite roles.

2. Enter the name of composite role and click on create button.

3. Enter the Description of the composite role and long text. Long text generally includes manager approvals and ticket number.


4. Include the single roles from the list or enter it manually in the Roles tab.


5. Assign the composite role to users under the Users tab. Users can be entered manually or choose from the list. 

6. Click on Save button

Watch my demo video on how 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 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

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