Chat now with support
Chat mit Support

Identity Manager 8.1.5 - Administration Guide for Connecting to SAP R/3

Managing SAP R/3 environments Setting up SAP R/3 synchronization Basic data for managing an SAP R/3 environment Basic data for user account administration SAP systems SAP clients SAP user accounts SAP groups, SAP roles, and SAP profiles SAP products Providing system measurement data Reports about SAP systems Configuration parameters for managing an SAP R/3 environment Default project templates for synchronizing an SAP R/3 environment Referenced SAP R/3 table and BAPI calls Example of a schema extension file

Overview of SAP groups, SAP roles, and SAP profiles

To obtain an overview of a group

  1. Select the SAP R/3 | Groups category.
  2. Select the group in the result list.
  3. Select the SAP group overview task.

To obtain an overview of a profile

  1. Select the SAP R/3 | Profiles category.
  2. Select a profile in the result list.
  3. Select the SAP profile overview task.

To obtain an overview of a role

  1. Select the SAP R/3 | Roles category.
  2. Select the role in the result list.
  3. Select the SAP role overview task.

Effectiveness of SAP groups, SAP roles, and SAP profiles

NOTE: In order to easy understanding the behavior is described with respect to SAP groups in this section. It applies in the same way to roles and profiles.
Table 66: Configuration parameters for conditional inheritance
Configuration parameter Effect when set

QER | Structures | Inherite | GroupExclusion

Preprocessor relevant configuration parameter for controlling effectiveness of group memberships. If the parameter is set, memberships can be reduced on the basis of exclusion definitions. Changes to this parameter require the database to be recompiled.

When groups are assigned to user accounts an employee may obtain two or more groups, which are not permitted in this combination. To prevent this, you can declare mutually exclusive groups. To do this, you specify which of the two groups should apply to the user accounts if both are assigned.

It is possible to assign an excluded group at any time either directly, indirectly, or with an IT Shop request. One Identity Manager determines whether the assignment is effective.

NOTE:

  • You cannot define a pair of mutually exclusive groups. That means, the definition "Group A excludes group B" AND "Group B excludes groups A" is not permitted.
  • You must declare each group to be excluded from a group separately. Exclusion definitions cannot be inherited.

The effectiveness of the assignments is mapped in the SAPUserInSAPGrp and BaseTreeHasSAPGrp tables by the XIsInEffect column.

Example of the effect of group memberships
  • Group A is defined with permissions for triggering requests in a client A group B is authorized to make payments. A group C is authorized to check invoices.
  • Group A is assigned through the "Marketing" department, group B through "Finance", and group C through the "Control group" business role.

Clara Harris has a user account in this client. She primarily belongs to the "Marketing" department. The "Control group" business role and the "Finance" department are assigned to her secondarily. Without an exclusion definition, the user account obtains all the permissions of groups A, B, and C.

By using suitable controls, you want to prevent an employee from being able to trigger a request and to pay invoices. That means, groups A, B, and C are mutually exclusive. An employee that checks invoices may not be able to make invoice payments as well. That means, groups B and C are mutually exclusive.

Table 67: Specifying excluded groups (SAPGrpExclusion table)

Effective group

Excluded group

Group A

Group B

Group A

Group C

Group B

Table 68: Effective assignments

Employee

Member in role

Effective group

Ben King

Marketing

Group A

Jan Bloggs

Marketing, finance

Group B

Clara Harris

Marketing, finance, control group

Group C

Jenny Basset

Marketing, control group

Group A, Group C

Only the group C assignment is in effect for Clara Harris. It is published in the target system. If Clara Harris leaves the "control group" business role at a later date, group B also takes effect.

The groups A and C are in effect for Jenny Basset because the groups are not defined as mutually exclusive. If this should not be allowed, define further exclusion for group C.

Table 69: Excluded groups and effective assignments

Employee

Member in role

Assigned group

Excluded group

Effective group

Jenny Basset

 

Marketing

Group A

 

Group C

 

Control group

Group C

 Group B

Group A

Prerequisites
  • The "QER | Structures | Inherite | GroupExclusion" configuration parameter is set.
  • Mutually exclusive groups, roles, and profiles belong to the same client.

To exclude a group

  1. Select the SAP R/3 | Groups category.
  2. Select the group in the result list.
  3. Select the Exclude groups task.
  4. In the Add assignments pane, assign the groups that are mutually exclusive to the selected group.

    - OR -

    In the Remove assignments pane, remove the groups that are not longer mutually exclusive.

  5. Save the changes.

To exclude roles

  1. Select the SAP R/3 | Roles category.
  2. Select the role in the result list.
  3. Select the Exclude SAP roles task.
  4. In the Add assignments pane, assign the roles that are mutually exclusive to the selected role.

    - OR -

    In the Remove assignments pane, remove the roles that no longer exclude each other.

  5. Save the changes.

To exclude profiles

  1. Select the SAP R/3 | Profiles task.
  2. Select a profile in the result list.
  3. Select the Exclude roles task.
  4. In the Add assignments pane, assign the profiles that are mutually exclusive to the selected profile.

    - OR -

    In the Remove assignments pane, remove the profiles that are no longer mutually exclusive.

  5. Save the changes.

SAP group, SAP role, and SAP profile inheritance based on categories

NOTE: In order to easy understanding the behavior is described with respect to SAP groups in this section. It applies in the same way to roles and profiles.

In One Identity Manager, groups can be selectively inherited by user accounts. For this purpose, the groups and the user accounts are divided into categories. The categories can be freely selected and are specified using a mapping rule. Each category is given a specific position within the template. The mapping rule contains different tables. Use the user account table to specify categories for target system dependent user accounts. In the other tables enter your categories for the target system-dependent groups. Each table contains the Position 1 to Position 31 category positions.

Every user account can be assigned to one or more categories. Each group can also be assigned to one or more categories. The group is inherited by the user account when at least one user account category items matches an assigned group. The group is also inherited by the user account if the group or the user account is not put into categories.

NOTE: Inheritance through categories is only taken into account when groups are assigned indirectly through hierarchical roles. Categories are not taken into account when groups are directly assigned to user accounts.
Table 70: Category examples
Category item Categories for user accounts Categories for groups
1 Default user Default permissions
2 System users System user permissions
3 System administrator System administrator permissions

Figure 5: Example of inheriting through categories.

To use inheritance through categories

  • Define the categories in the client.
    NOTE: If central user administration is implemented, define the categories in the central system as well as in the child system. The same categories must be defined in the child system as in the central system so that groups from a child system can be inherited by user accounts.
  • Assign categories to user accounts through their master data.
  • Assign categories to groups, roles, and profiles through their master data.
Related topics

Assigning extended properties to SAP groups, SAP roles, and SAP profiles

Extended properties are meta objects, such as operating codes, cost codes, or cost accounting areas that cannot be mapped directly in One Identity Manager.

To specify extended properties for a group

  1. Select the SAP R/3 | Groups category.
  2. Select the group in the result list.
  3. Select the Assign extended properties task.
  4. In the Add assignments pane, assign extended properties.

    - OR -

    In the Remove assignments pane, remove extended properties.

  5. Save the changes.

To specify extended properties for a role

  1. Select the SAP R/3 | Roles category.
  2. Select the role in the result list.
  3. Select the Assign extended properties task.
  4. Assign extended properties in Add assignments.

    - OR -

    Remove extended properties in Remove assignments .

  5. Save the changes.

To specify extended properties for a profile

  1. Select the SAP R/3 | Profiles category.
  2. Select a profile in the result list.
  3. Select the Assign extended properties task.
  4. In the Add assignments pane, assign extended properties.

    - OR -

    In the Remove assignments pane, remove extended properties.

  5. Save the changes.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen