Top 33 Sap Grc Interview Questions You Must Prepare 21.Apr.2024

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.

The ‘PFCG_TIME_DEPENDENCY’ background report only cleans up the profiles (that is, it does not clean up the roles in the system). Alternatively, you may use transaction ‘PFUD’.

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.

Yes, we can change a user role template.  There are exactly three ways in which we can work with user role templates

  1. we can use it as they are delivered in sap
  2. we can modify them as per our needs through pfcg
  3. we can create them from scratch.

The table buffers are in the shared memory. Buffering the tables increases performance when accessing the data records contained in the table. Table buffers and table entries are ignored during startup. A user buffer is a buffer from which the data of a user master record is loaded when the user logs on. The user buffer has different setting options with regard to the ‘auth/new_buffering’ parameter.

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.

This is done when ever role is already assigned to users and changes are done in that role. In order to get the changes adjusted in the roles, user comparision is done.

Also during indirect asssignment of roles to user using t codes Po13 and po10, we have to to do user comparision, so that the roles get reflected in the SU01 record of user.

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.

First copy the master role using PFCG to a role with new name you wish to have. Then you have to generate the role. Now open each derived role and delete the menu. Once the menus are removed it will let you put new inheritance. You can put the name of the new master role you created. This will help you keep the same derived role name and also the same profile name. Once the new roles are done you can transport it. The transport automatically includes the Parent roles.

Collection of rules is nothing but rule set. There is a default rule set in GRC called Global Rule Set.

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.

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)

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

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.

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

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

Just to say all the t-codes which can affect roles and user master records are critical ones. SU01, PFCG, RZ10, RZ11, SU21, SU03, Sm37 are some of critical t-codes.

Below are critical objects:


If changes are to be reflected immediately, user comparison is recommended.

prerequisites are follows before assigning sap_all to any user .

1.enabling the audit log —- using sm19 tcode.
2.retreving the audit log—–using sm20 tcode.

this process follows when your not implementing grc in your system.

Background: When defining authorizations using Profile Generator, the table USOBX_C defines which authorization checks should occur within a transaction and which authorization checks should be maintained in the PG. You determine the authorization checks that can be maintained in the PG using Check Indicators. It is a Check Table for Table USOBT_C.

In USOBX_C there are 4 Check Indicators.

@CM (Check/Maintain)

  1. An authority check is carried out against this object.
  2. The PG creates an authorization for this object and field values are displayed for changing.
  3. Default values for this authorization can be maintained.

@C (Check)

  1. An authority check is carried out against this object.
  2. The PG does not create an authorization for this object, so field values are not displayed.
  3. No default values can be maintained for this authorization.

@N (No check)

  1. The authority check against this object is disabled.
  2. The PG does not create an authorization for this object, so field values are not displayed.
  3. No default values can be maintained for this authorization.

@U (Unmaintained)

  1. No check indicator is set.
  2. An authority check is always carried out against this object.
  3. The PG does not create an authorization for this object, so field values are not displayed.
  4. No default values can be maintained for this authorization.

Authorization values may contain wildcards; however, the system ignores everything after the wildcard. Therefore, A*B is the same as A*.

GRC Landscape is 2 system landscape, @SAP GRC DEV @SAP GRC PRD in GRC there is no Quality system.

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

The Profile Generator creates roles. It is important that suitable user roles, and not profiles, are entered manually in transaction ‘SU01′. The system should enter the profiles for this user automatically.

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

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

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.


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.

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.

A maximum of 150 authorizations fit into a profile. If the number of authorizations exceeds this marker, the Profile Generator will automatically create more profiles for the role. A profile name consists of twelve (12) characters and the first ten (10) may be changed when generated for the first time.

Generally this task is done PFCG_TIME_DEPENDENCY background job which runs once daily so that roles are adjusted after running this report.

Change documents cannot be displayed in transaction ‘SUIM’ after they are transported to the production system because we do not have the ‘befor input’ method for the transport. This means that if changes are made, the ‘USR10′ table is filled with the current values and writes the old values to the ‘USH10′ table beforehand. The difference between both tables is then calculated and the value for the change documents is determined as a result. However, this does not work when change documents are transported to the production system. The ‘USR10′ table is automatically filled with the current values for the transport and there is no option for filling the ‘USH10′ table in advance (for the history) because we do not have a ‘befor input’ method to fill the ‘USH10′ table in advance for the transport.