What is a derived role?

Q What is a derived role?

A. 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

List R/3 User Types

Q List R/3 User Types

1. Dialog users are used for individual user. Check for expired/initial passwords Possible to change your own password. Check for multiple dialog logon

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

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

4. 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.

What authorization are required to create and maintain user master records?

Q What authorization are required to create and maintain user master records?

A. 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

What is the difference between USOBX_C and USOBT_C?

Q What is the difference between USOBX_C and USOBT_C?

A. 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.

How to create users?

Q How to create users?

A. 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.

Click here for turotial on creating sap user id

List few security Tables

Q List few security Tables

Click here for security tables

SAP Security T-codes

Q. SAP Security T-codes

A. Frequently used security T-codes
SU01 Create/ Change User SU01 Create/ Change User PFCG Maintain RolesSU10 Mass ChangesSU01D Display UserSUIM ReportsST01 TraceSU53 Authorization analysis.

Click here for all Security T-codes