Showing posts with label t-code. Show all posts
Showing posts with label t-code. Show all posts

Monday 28 October 2013

SAP SECURITY INTERVIEW QUESTIONS & ANSWERS -2

SAP SECURITY INTERVIEW QUESTIONS & ANSWERS  

1.Please explain the personalization tab within a role. 

Personalization is a way to save information that could be common to users, I meant to a user role...  E.g. you can create SAP queries and manage authorizations by user groups. Now this information can be stored in the personalization tab of the role.  (I supposed that it is a way for SAP to address his ambiguity of its concept of user group and roles: is "usergroup" a grouping of people sharing the same access or is it the role who is the grouping of people sharing the same access)

2.Is there a table for authorizations where I can quickly see the values entered in a group of fields?  

In particular I am looking to find the field values for P_ORGIN across a number of authorization profiles, without having to drill down on each profile and authorization.
AGR_1251 will give you some reasonable info.

3.How can I do a mass delete of the roles without deleting the new roles ? 

There is a SAP delivered report that you can copy, remove the system type check and run. To do a landscape with delete, enter the roles to be deleted in a transport, run the delete program or manually delete and then release the transport and import them into all clients and systems.
It is called: AGR_DELETE_ALL_ACTIVITY_GROUPS.
To used it, you need to tweak/debug & replace the code as it has a check that ensure it is deleting SAP delivered roles only. Once you get past that little bit, it works well.

4.Someone has deleted users in our system, and I am eager to find out who. Is there a table where this is logged? 

Debug or use RSUSR100 to find the info's.
Run transaction SUIM and down its Change documents.

5.How to insert missing authorization? 

su53 is the best transaction with which we can find the missing authorizations.and we can insert those missing authorization through pfcg.

6.What is the difference between role and a profile? 

Role and profile go hand in hand. Profile is bought in by a role. Role is used as a template,  where you can add T-codes, reports..Profile is one which gives the user authorization.  When you create a role, a profile is automatically created.

7.What profile versions? 

Profile versions are nothing but when u modifies a profile parameter through a RZ10 and generates a new profile is created with a different version and it is stored in the database.

8.What is the use of role templates? 

User role templates are predefined activity groups in SAP consisting of transactions, reports and web addresses.

9.What is the different between single role & composite role? 

A role is a container that collects the transaction and generates the associated profile.  A composite roles is a container which can collect several different roles

10.Is it possible to change role template? How? 

Yes, we can change a user role template.  There are exactly three ways in which we can work with user role templates
- we can use it as they are delivered in sap
- we can modify them as per our needs through pfcg
- we can create them from scratch.

For all the above specified we have to use pfcg transaction to maintain them.

Thursday 10 October 2013

SU24 Concept

                                                  SU24 Concept


Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships between the particular transaction and its authorization objects. It is possible to add or subtract the checks performed in the transaction by changing the appropriate flag.
The benefit of transaction SU24 occurs when transactions are added to or deleted from Role Groups using the Profile Generator.
When new transactions are added, the Profile Generator will add all authorization values maintained in SU24 for the transaction(s).
When deleting transaction the Profile Generator will remove all authorization values that are maintained in SU24 for the transaction.
Activities performed:
Check/Maintain Authorization Values
Addition of Authorization Object to tcode
Deletion of Authorization Object from tcode.


Check Ind.
Proposal
Meaning
Explanation
Check
YS
Check /Maintained
The object will be inserted along with the values in the role.  The object will be checked along with the values during runtime of the transaction.
Check
NO
Check
This object will not be inserted into the roles. A check on the object along with the values will be done during the runtime of the transaction
Do not Check
NO
Do Not Check
The object will not be inserted into the roles and there will not be any check performed
during runtime of the transaction



Status Texts for authorizations

Standard: All field values in the subordinate levels of the hierarchy are unchanged from the SAP defaults
Maintained: At least one field in the subordinate levels of the hierarchy was empty by default and has since been filled with a value
Changed: The proposed value for at least one field in the subordinate levels of the hierarchy has been changed from the SAP default value.
Manual: You maintained at least one authorization in the subordinate hierarchy levels manually (it was not proposed by the Profile Generator).