Kontakt

Ansicht
Dokumentation

RSUSR_SYSINFO_LICENSE - License Data

RSUSR_SYSINFO_LICENSE - License Data

CPI1466 during Backup   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Program RSUSR_SYSINFO_LICENSE makes it possible to call and display user types from the systems of a CUA or from the local system. In the SUIM tree, the report for the CUA tree can be reached via the 'cross-system information (central user administration)' folder. For the local system, you can find the report via the 'User' folder as variant SAP&_LOCAL of report RSUSR_SYSINFO_LICENSE.

Integration

Prerequisites

To acquire the license types on the license audit side, the new functionality from SAP Note 1307693 must be available in all relevant systems.

If the report should be called in the central CUA, the following condition must be met:

The RFC user in the called child system of the CUA has the authorizations for authorization object S_RFC with function groups SUNI and SLIM_REMOTE_USERTYPES.
If this condition is not met, only the target state (values in the central CUA) is displayed in the result list in the designated columns.

As of the following Support Package releases, the prerequisite functionality is contained in your systems:

o,,SAPKB70019

o,,SAPKB70104

o,,SAPKB71008

o,,SAPKB71103

Features

Selection

Standard Variants

SAP&_LOCAL Local license audit for users

Output

In the 'Contractual User Type (USMM)' column, the relevant effective user types for the local or selected system(s) are displayed. The user types of the central CUA or the child systems are displayed in the 'Contractual User Type (CUA)'. With the default variant SAP&_LOCAL, the user types defined with transaction SU01 are displayed in the 'Contractual User Type (Local)’ column.

If the child system cannot be reached by RFC, a warning to this effect is displayed in the application log.

If the child system can be reached, but the new function module 'SLIM_IF_LIST_USERTYPES' does not exist there (see SAP Note 1307693) or the RFC user does not have authorization for function group SLIM_REMOTE_USERTYPES, a warning to this effect is also displayed in the application log.

Despite distribution parameter for the license data being set “globally” (transaction SCUM), the user type settings of a user for a particular child system can still differ from the data maintained in the central CUA. To be able to recognize this kind of "inconsistency", the 'Contractual User Type (CUA)' displays the values maintained for the user both in the central system and and in the child system.

The following rules also apply:

General:

Users are irrelevant for the license audit if one of the following conditions applies:

1. They are technical users that have not been explicitly manually classified. For these users, the message ‘Technical user without classification’ is displayed.

2. The user does not exist in the system in question, is no longer valid or is a user of type “reference user”, this type not being classifiable. For these users, the message 'User is irrelevant for license audits' is displayed in the 'Contractual User Type (USMM)' column.


For more information about relevance of users for license audits, see component XX-SER-LAS.

For users directly in the local or central system, the following applies:

If no user type has been defined for a user in transaction SU01, the default user type is displayed. In this case, there is no value is displayed for the user in the ‘Contractual User Type (CUA)’ or ‘Contractual User Type (Local)’ column.

For child systems, the following applies:

1. If there is not value displayed in the 'Contractual User Type (CUA)' or 'Contractual User Type (Local)' column:

  • The user has not had a user type assigned to it from the central CUA.
    The user displayed in the 'Contractual User Type (USMM)' column is either the default user type in this child system or is a user type assigned locally in the child system using USMM.
  • In the latter case, the license data for these users should be transferred from the child system to the central system again using transaction SCUG.

2. If values are displayed in the ‘Contractual User Type (USMM)' and 'Contractual User Type (CUA)’ columns, but these are not the same:

  • The IDoc containing the change of user type for this user has either not arrived in the child system yet or has not been processed there yet.
  • The user type has been changed locally.

Activities

Example






Fill RESBD Structure from EBP Component Structure   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 5067 Date: 20240601 Time: 092554     sap01-206 ( 91 ms )