{"id":472,"date":"2011-10-29T16:00:12","date_gmt":"2011-10-29T16:00:12","guid":{"rendered":"http:\/\/sapsecurityanalyst.com\/WP\/?page_id=472"},"modified":"2021-06-28T05:15:42","modified_gmt":"2021-06-28T05:15:42","slug":"roles","status":"publish","type":"page","link":"https:\/\/sapsecurityanalyst.com\/WP\/general-disclaimer\/roles\/","title":{"rendered":"Roles"},"content":{"rendered":"


\nIn this post we have discussed about concepts of SAP Roles and Profiles.\u00a0As we discussed earlier, roles are like containers which contain authorization objects, tcodes etc. Roles are created via PFCG tcode and when roles are generated, we get authorization profiles.<\/span>
\n<\/span>
\n
\nThese roles are added to users via SU01 tcode or PFCG tcode. When they get added with a proper validity period, the authorization profiles get assigned to users. These authorization profiles provide the necessary authorization.
\n<\/span>
\n
\nBelow screenshot shows user to role assignment options via SU01 and PFCG tcodes respectively:
\n<\/span>
\n
\n\"\"
\n<\/a>
\n
\nLet us create a role using PFCG:<\/span><\/span>
\n
\nLet us name the role as ZTEST123 (As a good practice, we should always use names which begin with Y or Z while creating any role). Click on “Single Role” button to create a single role (We will discuss about various role types later).\u00a0Let the role description be “Test role”.
\n<\/span>
\n In the next screen, we see various tabs: Description, Menu, Authorization, User etc.<\/span><\/p>\n

 <\/p>\n

<\/p>\n

In the Description Tab, on the right side there is a text box labelled as “Derive from Role”. This text box comes into picture when the role being created is a derived role of some master role. We will discuss about this in details when we go through various role types.<\/span>
\n
\n At the bottom of the description tab, there is a “Long Text” field. This field is not a mandatory field, but we should use this to maintain information related to role creation tickets and role updation reasons etc. This will be helpful for audit purpose.
\n<\/span>
\n
\n\"\"
\n<\/a>
\n
\nThe next tab is “Menu<\/strong>” Tab.<\/span>
\n<\/span>
\n In this tab, we get the option to assign tcodes to roles. Apart from tcodes, we can also add reports, queries, URLs etc.
\n<\/span>
\n Let us add tcodes-su56, su01, va03, su56 to the role.
\n<\/span>
\n To do this, click on “Transaction” button in the Menu Tab and add the tcodes in the “Assign Transactions” dialog window.
\n<\/span>
\n
\n\"\"<\/a><\/p>\n


\n<\/a><\/p>\n

Next we come to the next tab-“Authorizations”. It is from this tab that gives the option to maintain authorizations and generate profile.<\/span><\/p>\n

<\/span><\/p>\n

In the “Authorizations” tab screen, we find options to maintain “Profile Name” and “Maintain Authorization Data and Maintain Profiles”. See below figure:<\/span><\/p>\n

<\/a><\/p>\n


\n\"\"
\n<\/a>
\nIn the label “Profile Name” we can give our own profile name (as I have given ztest123) or we can leave it blank. In case we leave it blank, the system will automatically create a profile name with naming convention “T-<First and Last character of SID>xxxxxx<\/span>“<\/span>
\n
\nNext we need to maintain authorization data and generate profile. For this we can either click on either “Change Authorization Data” or “Expert Mode for Profile Generation”.<\/span>
\n
\nNote: Expert Mode is mandatory when a SU24 change is made. We will discuss about Expert mode in details when we discuss SU24 later.<\/span>
\n
\n After we get in the next screen-to maintain authorization data, click on Utilities->Technical names on<\/strong><\/span>
\n<\/span>
\n
\n\"\"
\n<\/a>
\n
\nThis option helps us to see the technical names of authorization objects and authorization classes.<\/span>
\n<\/span>
\n
\n\"\"<\/a><\/p>\n


\n<\/a>
\nIn the above screen we maintain authorization for roles. After the authorizations are maintained, we generate the profile using “Generate” button at the top or by pressing “Shift+F5”.<\/span><\/span><\/p>\n

<\/span>
\n