立即与支持人员聊天
与支持团队交流

Identity Manager 8.2.1 - 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 objects Removing a Central User Administration Troubleshooting an SAP R/3 connection 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

Validity period of role assignments

You can enter a validity period for assigning SAP roles to user accounts. If no validity period is given to the role assignments, they are allocated the following validity dates by default:

  • Valid from: 1900-01-01
  • Valid to : 9999-12-31

These role assignments are therefore unlimited.

The SAPUserInSAPRole table contains all role assignments, limited, and unlimited.

The HelperSAPUserInSAPRole table only contains current valid role assignments. The Daily calculation of SAP user accounts assignments to SAP roles schedule controls the calculation of this table.

Detailed information about this topic
Related topics

Assigning the validity period of direct role assignments

Direct assignments can occur in two different ways:

  1. Synchronizing role assignments

    The Valid from and Valid to columns are taken into account in the default mapping. Synchronization writes the validity period of role assignments into the One Identity Manager database.

  2. Direct assignment of SAP roles to user accounts in the Manager

    A validity period can be entered for direct assignment of SAP roles to user accounts. Valid from and Valid to dates are provisioned in the target system.

Related topics

Configuring the validity period of indirect role assignments

When the validity period is calculated, the following configuration parameters are taken into account. These configuration parameters are disabled by default.

  • TargetSystem | SAPR3 | ValidDateHandling | DoNotUsePWODate

    Specifies whether the request's validity period is transferred when role assignments are requested.

    Not set: The request's validity period is transferred. If there is no validity period given, the default values of 1900-01-01 and 9999-12-31 are set.

    Set: The role assignment is unlimited.

  • TargetSystem | SAPR3 | ValidDateHandling | ReuseInheritedDate

    Controls reuse of existing profile assignments if another assignment for the same combination of user account and SAP role is added.

    Set: Existing role assignments are reused if the same assignment is created by different means of inheritance. The following applies:

    • The Valid from date of the existing assignment is in the past.

    • The Valid until date of the existing assignment is 9999-12-31 or the new assignment has the same Valid until date as the existing assignment.

    Any other unlimited assignment or any other assignment with the same Valid until date does not generate a new entry in the SAPUserInSAPRole table. This can reduce the number of entries in the SAPUserInSAPRole table.

    Not set: An entry in the SAPUserInSAPRole table is created for every new role assignment. Existing assignments are not reused.

    NOTE: In databases that are migrated from versions older than 7.0, you may see assignments with a Valid until date of 9998-12-31. This is a valid date for unlimited role assignments, which means that these assignments can also be reused.

  • TargetSystem | SAPR3 | ValidDateHandling | ReuseInheritedDate | UseTodayForInheritedValidFrom

    Specifies the value that indirect role assignments' Valid from date contain when they are added.

    Not set: 1900-01-01

    Set: <today>

    IMPORTANT: Calculating indirect role assignments can become much slower depending on the amount of data to be processed.

    Do not set this configuration parameter if the information about when a role assignment's validity period starts is not absolutely necessary in SAP R/3.

To reuse an existing role assignment:

  • In the Designer, set the TargetSystem | SAPR3 | ValidDateHandling | ReuseInheritedDate configuration parameter.

To set the assignment's date as the first day of the role assignment's validity period

  • In the Designer, set the TargetSystem | SAPR3 | ValidDateHandling | ReuseInheritedDate | UseTodayForInheritedValidFrom configuration parameter.

To prevent the request's validity date being copied to the role assignment

  • In the Designer, set the TargetSystem | SAPR3 | ValidDateHandling | DoNotUsePWODate configuration parameter.

    This adds an unlimited role assignment.

Related topics

Determining the validity period of indirect role assignments

SAP roles that are assigned to departments, cost centers, locations, or business roles are indirectly assigned through them to user accounts. By default, indirect assignments are unlimited. The TargetSystem | SAPR3 | ValidDateHandling configuration parameter is used to determine the validity period of indirect assignments.

You can enter a valid from date if the requests are made in the IT Shop. An entry in SAPUserInSAPRole only exist between the first and last days of the request's validity period. The request's validity period is copied to role assignments under the following prerequisites:

  • The DoNotUsePWODate configuration parameter is not set (default).

  • The SAP role was requested directly.

    - OR -

  • The assignment was created through an assignment request and at the same time a role assignment was requested. BaseTreeHasSAPRole.XOrigin='8' is set for this.

By default, an entry in the SAPUserInSAPRole table is created for every new role assignment. If the same assignment is created by different means of inheritance, the number of entries in the SAPUserInSAPRole table grows rapidly. In this case, if the validity period is identical, the same entries can be reused. Existing role assignments can be reused under the following prerequisites:

  • The ReuseInheritedDate configuration parameter is set.

  • The Valid from date of the existing assignment is in the past.

  • The Valid until date of the existing assignment is 9999-12-31 or the new assignment has the same Valid until date as the existing assignment.

  • Another assignment for the same combination of user account and SAP role is added.

Any other unlimited assignment or any other assignment with the same Valid until date does not generate a new entry in the SAPUserInSAPRole table. The number of entries in the SAPUserInSAPRole table can be reduced in this way.

NOTE: In databases that are migrated from versions older than 7.0, you may see assignments with a Valid until date of 9998-12-31. This is a valid date for unlimited role assignments, which means that these assignments can also be reused.

By default, the first day that indirect assignments are valid is 1900-01-01. This does not tell us when the assignments were created. If you need this information, in the Valid from field, you can enter the date on which the SAP role will be assigned. The date of the assignment is set as the first valid day of the indirect role assignments under the following prerequisites:

  • The ReuseInheritedDate | UseTodayForInheritedValidFrom configuration parameter is set.

    Exception: the DoNotUsePWODate configuration parameter is not set and:

    • The assignment has been requested and the request has a Valid from date.
    • The assignment has been requested and the request has a Valid to date but no Valid from date.

IMPORTANT: Calculating indirect role assignments can become much slower depending on the amount of data to be processed.

Do not set the UseTodayForInheritedValidFrom configuration parameter if the information about the valid from date of the role assignment is not absolutely necessary in SAP R/3!

Detailed information about this topic
Related topics
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级