SAP Basis Tech Supports

Symptom

There is no program to determine license data in a Central User Administration (CUA) across all the systems.

Other terms

SUIM, CUA, Central User Administration, RFC, Remote Function Call

Reason and Prerequisites

This problem occurs because a function is missing.

Solution

Use the Note Assistant to implement the correction instructions or import the relevant Support Package.
Caution:
If you want to use the Note Assistant to implement the corrections, you must first perform manual tasks (create Dictionary objects). The attached PDF document describes the properties of the new objects.
The text symbols and the report RSUSR_SYSINFO_LICENSE that is added to the SUIM tree are delivered as a Support Package only.

Program description

The new program RSUSR_SYSINFO_LICENSE provides the option to call and display user types from the systems of a CUA.

Caution:

The requirements are as follows:
To obtain the license types of the license audit, the new functions that are contained in Note 1307693 must be available in all affected systems.The RFC user in the CUA child system that was called has an authorization for the authorization object S_RFC with the function groups SUNI and SLIM_REMOTE_USERTYPES.

If these prerequisites are not met, the result list displays only the target state (values that are available in the central system) in the relevant columns.
As of the following Support Package levels, the required functions are contained in your systems:
SAPKB70019SAPKB70104SAPKB71008SAPKB71103
Explanations for result list:

The”Contractual User Type”column displays the effective local user types from each individual system.
If the child system cannot be accessed using RFC, the system issues a relevant warning in the application log.
If the child system can be accessed, but the new function module SLIM_IF_LIST_USERTYPES does not exist in this system (see Note 1307693) or the RFC user does not have an authorization for the function group SLIM_REMOTE_USERTYPES, a relevant warning is issued in the application log as well.
Even if you set the distribution parameters for the license data to “Global” (transaction SCUM), the user type settings of a user for a specific child system may differ from the relevant data that is maintained in the central system. To recognize inconsistencies of this type, the”Value in CUA Central”column additionally outputs the value that is maintained for the user and the child system in the central system.
For the two columns “Contractual User Type” and “Value in CUA Central”, the column set of the ALV list includes the related columns with the technical values for the user type. They are named “ID: Contractual User Type” and “ID: Contractual User Type in CUA Central”. They are not displayed in the standard settings of the result list.
Furthermore, the following rules apply:
General:
Users are irrelevant for the license audit if one of the following conditions applies:
1. Technical users are involved that were not classified in an explicitly manual manner.2. The user does not exist in the affected system; the user is not valid in the relevant validity period or is a reference user, which can generally not be classified.

For these users, the system issues the message”User is for Licence Measurement irrelevant”in the “Contractual User Type” column.
More information about the user relevance for the license audit is available under the component XX-SER-LAS.
For users that are directly in the central system, the following applies:
If no user type has been defined for a user in transaction SU01, the system displays the standard user type. You can recognize these cases by the fact that the”Value in CUA Central”column does not display any value for these users.
For users in child systems, the following applies:
1. If the”Value in CUA Central”column does not display any value:The central system has not assigned a user type to this user.
The user type that is output in the”Contractual User Type”column for this, is the standard user type in this child system or was assigned locally in the child system using USMM.
If the latter is the case, you must use transaction SCUG to transfer the license data for these users to the central system again.2. If the”Contractual User Type”and”Value in CUA Central”columns display values, but the values differ:The IDoc that contains the user type change for this user has not yet been transferred to the child system or has not yet been processed.The user type was changed locally.