By : Nagar

Q. SAP Security T-codes
Frequently used security T-codes 

SU01    - Create/ Change User SU01 Create/ Change User 
PFCG   - Maintain Roles
SU10    - Mass Changes
SU01D - Display User
SUIM   - Reports
ST01    - Trace
SU53    - Authorization analysis

Q How to create users?
Execute transaction SU01 and fill in all the field. When creating a new user, you must enter an initial password for that user on the Logon data tab. All other data is optional. 

Q What is the difference between USOBX_C and USOBT_C?
The table USOBX_C defines which authorization checks are to be performed within a transaction and which not (despite authority- check command programmed ). This table also determines which authorization checks are maintained in the Profile Generator. 

The table USOBT_C  defines for each transaction and for each authorization object which default values an authorization created from the authorization object should have in the Profile Generator.

Q What authorization are required to create and maintain user master records?
The following authorization objects are required to create and maintain user master records: 

S_USER_GRP: User Master Maintenance: Assign user groups 
S_USER_PRO: User Master Maintenance: Assign authorization profile 
S_USER_AUT: User Master Maintenance: Create and maintain authorizations 

Q List R/3 User Types
Dialog users are used for individual user. Check for expired/initial passwords.  Possible to change your own password. Check for multiple dialog logon 

A Service user - Only user administrators can change the password.  No check for expired/initial passwords. Multiple logon permitted 

System users are not capable of interaction and are used to perform certain system activities, such as background processing, ALE, Workflow, and so on. 

A Reference user is, like a System user, a general, non-personally related, user. Additional authorizations can be assigned within the system using a reference user. A reference user for additional rights can be assigned for every user in the Roles tab. 

Q What is a derived role?

Derived roles refer to roles that already exist. The derived roles inherit the menu structure and the functions included (transactions, reports, Web links, and so on) from the role referenced. A role can only inherit menus and functions if no transaction codes have been assigned to it before. 

The higher-level role passes on its authorizations to the derived role as default values which can be changed afterwards. 
Organizational level definitions are not passed on. They must be created anew in the inheriting role. User assignments are not passed on either. 

Derived roles are an elegant way of maintaining roles that do not differ in their functionality (identical menus and identical 
transactions) but have different characteristics with regard to the organizational level. Follow this link for more info 

Q What is a composite role?
A composite role is a container which can collect several different roles. For reasons of clarity, it does not make sense and is 
therefore not allowed to add composite roles to composite roles.  Composite roles are also called roles. 

Composite roles do not contain authorization data. If you want to change the authorizations (that are represented by a composite role), you must maintain the data for each role of the composite role. 

Creating composite roles makes sense if some of your employees need authorizations from several roles. Instead of adding each user separately to each role required, you can set up a composite role and assign the users to that group. 
The users assigned to a composite role are automatically assigned to the corresponding (elementary) roles during comparison. 

Q What does user compare do?
If you are also using the role to generate authorization profiles, then you should note that the generated profile is not entered in the user master record until the user master records have been compared. You can automate this by scheduling report 
FCG_TIME_DEPENDENCY on a daily.

SAP Basis Reference Books:
SAP Basis Components, System Administration, Security, ALE and iDoc Books

Back to Basis Menu:
SAP BC (Basis Components) Hints and Tips

Return to :-
SAP ABAP/4 Programming, Basis Administration, Configuration Hints and Tips