Professional Documents
Culture Documents
Auditing Services
SAP SYSTEM
MEASUREMENT GUIDE
MEASUREMENT PROGRAM AND
LICENSE ADMINISTRATION WORKBENCH
Version 7.0
CONTENTS
1
1.1
1.2
1.3
7
7
8
8
2 Scope of Validity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Availability of Contractual User Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Availability of Software Engine Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Installations, Systems, and System Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1 SAP Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2 SAP Software System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4
Measurement Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8
8.1
8.2
8.3
8.4
8.5
8.6
8.7
8.8
8.9
Classifying Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Classifying Individual Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Classifying Users with Reference Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Classifying Users with User Mass Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Classifying Users with Central User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Classifying Users with the User Classification List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Mass Changes of Contractual User Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating Price Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking User Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Analyzing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
18
18
20
21
21
22
23
24
25
Measurement Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measurement Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the Measurement Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SSCR-Registered Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Results of Engine Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
31
32
32
16
16.1
16.2
16.3
16.4
16.5
16.6
16.7
42
42
42
42
44
45
46
47
17
17.1
17.2
17.3
Combining Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced Grouping of Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Grouping Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
48
50
50
This system measurement guide contains supplementary information about SAP SEs product licensing, providing additional
information about the SAP price list and your SAP software
contract.
If there are any contradictions with the terms of your SAP
software contract, then the terms of your contract and the
SAP price list that your contract is based on apply.
1.1
Use
Use means to activate the processing capabilities of the Software, load, execute, access, employ the Software, or display
information resulting from such capabilities. Use may occur by
way of an interface delivered with or as a part of the Software, a
Licensee or third-party interface, or another intermediary
system.
Use of the SAP software is based on the licensing of named
users and engines.
Use of the software is restricted in principle to the customers
own employees. The customer is entitled to allow access to
programs to employees of its business partners and to
employees of the business partners of its affiliated companies, as
well as to the employees of the affiliated companies, provided the
customer acquired a license for this use.
SAP gives express notice that the accessing of a system by more
than one person using one and the same named user constitutes
a breach.
A named users password may be passed on to another person
only in exceptional cases (if, for example, the named user is
on vacation or is absent due to sickness, or if the employment
relationship with the named user has been terminated).
1.2
Named Users
1.3
Engines
SCOPE OF VALIDITY
2.1
Platform
Software Component
SAP_BASIS 700
SAP-BASIS 640
SAP_BASIS 620
SAP_BASIS 610
SAP_BASIS 46D
SAP_BASIS 46C
For SAP R/3 4.6B and earlier, the software component SAP_BASIS corresponds to the
SAP R/3 software version.
Note: For legal reasons related to your license agreement, changes to SAP installations (deletions, changed
contact persons, and so on) and their assignment to
SAP contracts must be done in writing through your
SAP contracts department.
SAP Installation
An SAP installation is a set of SAP software systems. The SAP software system comprises components (for example, an application
server and a message server) that have direct or indirect access
to one database instance. A database counts as an instance if each
database table appears only once.
3.2
When you measure an installation, you must measure all production and development systems, with the exception of test
systems, Internet demo and evaluation systems (IDESs) and
backup systems.
There are different ways of evaluating measurement results,
depending on the system type.
For each software product, you must register a separate installation in writing with SAP. SAP then gives you a unique installation
number.
SAP
Software
Contract
Installation 2
Installation 1
Productive
System
Test
System
Development
10
Productive
System
Test
System
Installation N
Training
System
Productive
System
Test
System
Check results
User consolidation with
license administration workbench?
Yes
No
Transfer to SAP
Combine users
Consolidate users
Transfer LAW
result to SAP
11
12
MEASUREMENT PROGRAM
You may carry out the measurement only by using the unaltered
tools provided by SAP. The result of the measurement is to be
transmitted to SAP immediately and in unaltered form.
From SAP_BASIS 640 (SAP NetWeaver 2004), information about
system measurement (transaction USMM) is also available in
SAP Library under SAP NetWeaver SAP NetWeaver by
Key Capability Solution Life Cycle Management SAP Licenses: System
Measurement.
You can find up-to-date information about the measurement
program and the programs for engine measurement currently
available on SAP Support Portal at support.sap.com/licenseauditing
Information about SAP System Measurement
Function
Release Number
(The function is in the standard offering as
of this release.)
Technical user types communication, system, service, and reference excluded from
measurement
Display of the Service Data Control Center (SDCC) transfer status in the measurement
program
Classification help
13
3.
Prerequisites
Process
14
Figure 4: Clients
4.
The following price lists are available for SAP R/3 4.6C:
SAP Software Component (R/3 Enterprise) price list
(SW Component price list)
mySAP Solution Suite/Business Suite price list
(mySAP.com Solution Suite price list)
Figure 6: User Types
For releases earlier than SAP R/3 4.6B, the contractual user
types from the various SAP price lists, especially those from
the mySAP.com price list, are available in support packages
(SAP Note 428479).
If you require additional user types for mySAP Business
Suite and individual applications for user classification that
are not yet available in the measurement program for your
release, you can download these individually or as a package
from SAP Support Portal: support.sap.com/licenseauditing Information about SAP System Measurement User Classification
5.
On the User types tab page, set the Activ flag for the relevant
user types.
To keep the list of user types as short as possible, deactivate
the special module and IS user types if you do not have
any contractually defined special module users.
The Activ flag controls the display of selected users in user
classification and input help for user maintenance.
Figure 7: Customizing of Special Module User Types
15
6.
7.
16
9.
10.
11.
12.
13.
14.
15.
17
8
8.1
CLASSIFYING USERS
Classifying Individual Users
You can assign a user type to a user when you create the
user. This is especially useful if you have already
performed a system measurement and have classified all
users that exist when doing so. You also get a useful
overview of the individual user profiles.
Procedure
To classify individual users, take the following actions:
1. Start user maintenance (transaction SU01) by choosing
Tools Administration User Maintenance User
2. Specify a user or an alias, and choose Change, Create, or
Copy. As of software component SAP_BASIS 610, the
contractual user type and the special version are also
copied when you copy a user. Select LicenceData in the
function Copy User.
3. Choose the LicenceData tab page in change mode
4. Use the input help to select the contractual user type.
Alternatively, you can assign a reference user to the
user on the Roles tab page (see section 8.2 Classifying
Users with Reference Users).
5. Save your entries
Figure 8: LicenceData
18
Result
19
8.3
2.
3.
4.
User Maintenance: Mass Changes is well suited to initial user classification. In this way, you can classify users by group, such as by
department or cost center. To avoid accidentally overwriting
correct user types, you should later maintain the user types
using user maintenance or the user list.
Create user
(without classification)
Create HUBER
(Development)
HUBER
WEBER
...
Create MEIER
(Sales)
Create WEBER
(Development)
Jan
User Maintenance:
Mass Changes (SU10)
Mass Change Development
Feb
Create WEBER
Classify WEBER
6.
Create STORK
Classify STORK
May
Perform
system
measurement
5.
Figure 12: Classifying Users with User Maintenance: Mass Changes (1)
Create WILD
Classify WILD
Create STORK
Classify STORK
Figure 11: Strategy for Classifying Users with User Maintenance: Mass Changes
Procedure
20
Figure 13: Classifying Users with User Maintenance: Mass Changes (2)
8.4
Administration
You classify users manually using the simple user list. You can
classify users that have not yet been classified or reclassify users
that have already been classified.
Save your entries. The user list displays all users of your SAP
software system with the assigned contractual user types.
21
8.6
Description
Reference user
Created
Logon
22
Procedure
2.
3.
8.7
Use the input help to specify the previous and the future
user type
Choose Execute
Check the security query, and confirm the mass change.
A message in the status bar confirms the change to the
users.
Migrating Price Lists
After an active price list has changed, you must adjust the
contractual user types (migration). A tool is available in the
measurement program for migrating the contractual user types
in the SAP Software Component (R/3 Enterprise) price list to
user types in the mySAP price lists. You can use this function to
change the old user types to new user types in the current price
list.
You can migrate user types only in the client in which you are
logged on.
Figure 15: Price List Migration
23
8.8
Comment
Classification
Workbench Users
Creator of Objects
Self-Service Users
24
Result
Procedure
The result list for Workbench Users displays all users that changed
the SAP source code in the past 12 months and their classifications.
As a rule, only developers change the SAP source code. Therefore,
check that these users are classified correctly (SAP Note 967539).
The user names are specified for internal use in your organization
so that you can investigate these anomalies and, if necessary,
reclassify the relevant users.
The analysis information is made anonymous both in the
measurement statistics and in the measurement log and transferred to SAP.
8.9
Analyzing Users
Comment
Deleted users
Expired users
Multiple logons
User list
The result lists contain the user names for internal use in your
organization so that you can investigate and remove anomalies.
The analysis information is made anonymous both in the measurement statistics and in the measurement log and transferred
to SAP.
25
26
You must prepare the measurement results for further processing with LAW. You do this using the report RSLAW_PLUGIN,
which supplements the user data and converts it to an LAW file.
27
If you use only one SAP software system, transfer the measurements directly from the measurement program (transaction
USMM) to SAP.
As of SAP R/3 4.0B, you can transfer measurement results
online.
As of software component SAP_BASIS 700, you can use the
comments function (enter a comment or upload a file) to
send additional information about the measurement results
to SAP.
Checking the Transfer Status
You can use the all transfers function to check the status of the
different steps of the system measurement and the data transfer
in the measurement program. More information about checking
the status of the data transfer is available in SAP Note 623201.
Detailed information about checking the transfer status is
available in SAP Library under SAP NetWeaver Library SAP
NetWeaver by Key Capability Solution Life Cycle Management
SAP Licenses System Measurement Process of System Measurement
Checking the Transfer Status.
28
11 EVALUATION INFORMATION
11.1 Evaluation Rules
29
systems to SAP.
The measurement program also counts locked users.
Users whose validity period has expired should note the
following information:
As of SAP R/3 4.0B, the measurement program no longer
counts users whose validity period has expired.
In the case of earlier releases, the measurement program
counts users whose validity period has expired for another
90 days after the expiry date.
As of software component SAP_BASIS 610, the contractual
user type (license data) and the special version can also be
copied when you copy a user.
As of software component SAP_BASIS 620, particular
technical users are automatically excluded from the system
measurement (SAP Note 553606).
Classification of the E-ASL surcharge for users of the Oracle
database ORACLE 7 Runtime is no longer necessary and has
been removed from the measurement program. For earlier
releases, ignore the prompt and deactivate the E-ASL indicator.
SW Component
3.
4.
5.
2.
30
7.
12 MEASUREMENT RESULTS
The measurement program enters the measurement results
in a table, and the previous results are overwritten.
The checks in the measurement program take place in the
background. They determine the following information,
depending on the SAP software release, and present it in the
measurement log:
Deleted users: number of users that have been deleted in the
last week, last four weeks, or last twelve weeks
Users
with expired validity periods: number of users whose
You have measured the system and can now check the results
determined with the client-specific measurement statistics. The
results determined (measured users and engines) are listed by
client in the measurement statistics.
31
32
ID
52
53
54
55
Table 7: Examples of User Types for the mySAP Solution Suite/Business Suite
Price List
13.2 User Types in the mySAP Individual Solutions
Price List (mySAP.com Individual Solutions
Price List)
33
AA
AB
BB
ID
01
Operational
02
Information
04
Basis Only
06
Development Workbench
AX
AY
AZ
BA
71-79
34
Comment
04
Substitute
A substitute user can be created in the SAP software system only for a limited period of time (for example, to cover for an absent
colleague). During this time, this user can use the functions of another user as a substitute. The absent user may not work actively in the
SAP software system during this time. Substitute and substituted users must be created in the same client. The substitute user is free of
charge since the other user has already been evaluated according to the assignment.
11
Multiclient/multisystem
The multiclient/multisystem user is a contractual user type for users that are already classified in another client or system as chargeable
users. Every multiclient/multisystem user that is created in another client or system must be assigned to a chargeable user in the same or
another system, and they may use only the functions of that chargeable user. Since the chargeable user is evaluated according to its
assignment, the multiclient/multisystem user is free of charge.
91
Test
Test users can be created in production systems only in the following instances:
No test system is available
Use is exclusively for production preparation of modules that are not yet productive in the production system.
92
External contact
The user type external contact was deleted from the measurement program by means of a support package (SAP Note 313585).
If necessary, use a relevant special module user and name it unambiguously according to use. Your SAP contact person can answer any
questions you may have.
35
All employees who use SAP software require a license and must
be set up as dialog users. These dialog users are chargeable, and
they have the following benefits:
Individual system access (personalized)
Interaction capability
Ability to check for expired/initial passwords
Option to change their own passwords
Ability to check for multiple dialog logons
Features
Examples/Purpose
Dialog
SAP*
DDIC
SAPCPIC
TMSADM
ITSLOGIN
Communication
Batch-Input
External RFC
CPIC
System
Internal RFC
Background processing
Service
Reference
36
14 LAW
You use LAW to collect and consolidate license-relevant measurement data (users and engines) for the component systems
and the central system (LAW system) in which LAW is run. This
provides system administrators with a better overview, and the
system measurement is simpler and more reliable.
In transaction USMM, SU01, or SU10, you can classify the users
clearly according to their activity in all systems relevant for
measurement; that is, you assign them a contractual user type.
You can then begin LAW.
During the subsequent consolidation in LAW, each persons
users and user types are listed and assigned to one contractual
user type. This virtually eliminates the risk of evaluating a
person more than once: classification as multiclient/multisystem
user is superfluous.
The measurement results of all systems are handled as follows:
Collected and consolidated in the central LAW system.
Consolidation is the automatic analysis and optimization
of the individual user types. It includes the deletion of
redundancies and contained contractual user types.
Sent directly to SAP after release
As a result, an anonymous summary of the same user types
and the engine results of the production clients, as displayed
in the LAW log, is transferred.
SAP R/3
System
Jones
Professional
Miller
Limited
Professional
1 Professional
1 Limited Professional
LAW
SAP R/3
HR System
Jones
Employee
Baker
Employee
2 Employees
Business Info.
Warehouse
System
Jones
Taylor
Professional Professional
2 Professionals
LAW Result
2 Professionals (Jones, Taylor)
1 Limited Professional (Miller)
1 Employee (Baker)
37
Note: The LAW documentation below refers to the first LAW version available for customers. There is a new LAW 2.0
version available with enhanced and improved functionalities. The LAW 2.0 documentation is provided on SAP Support
Portal http://support.sap.com/licenseauditing License Administration Workbench (LAW) Documentation LAW 2.0 Getting started with
the new LAW 2.0
Function
Description
Release Number
(The function is in the
standard offering as of this
release.)
Use consolidation
with LAW
Consolidating central
user master records by
a uniform criterion
Software component
SAP_BASIS 610
LAW interface
Software component
SAP_BASIS 620, SP 42
Software component
SAP_BASIS 640
Software component
SAP_BASIS 640
Electronic LAW
measurement plan
Entering component
systems
Software component
SAP_BASIS 640
Enhanced grouping
of users
Software component
SAP_BASIS 640
Grouping of systems
Enabling partial
consolidation of
groups for example,
group companies
Software component
SAP_BASIS 700
Consolidation result
Providing functions
Software component
for further internal
SAP_BASIS 700
processing for example,
license maintenance
38
Authorizations
LAW System
39
Procedure
Result
40
5.
6.
7.
8.
41
42
Procedure
43
4.
44
5.
6.
Result
5.
6.
45
3.
46
3.
Action
Comment
Start measurement
only
Transfer last
measurement
Test connection
Perform qRFC
analysis
Perform tRFC
analysis
You have already entered the data for the component systems
or transferred the measurement data to LAW.
Deleting a Component System
47
17 COMBINING USERS
You can combine multiple user master records for the same
employee.
The criteria for combination originate from the user maintenance
(transaction SU01) of the source system. As of software component SAP_BASIS 640, you can extend these criteria if necessary,
for example, by using personalization objects.
17.1
User Combination
48
17.1.1
To correct errors that you found when checking the user list,
take the following steps:
1. Repeat the combination of the users, and choose Manual
Combination
If you previously combined the users automatically, the
results of this combination are automatically displayed.
2. Revise the old result, if desired
Result
You have combined the users and can now consolidate the
contractual user types.
49
17.2
50
17.3
Grouping Systems
As of software component SAP_BASIS 700, you can use consolidation groups to consolidate by groups of systems within LAW.
For example, you can evaluate by parts of the company or similar
structures.
The Groups tab page appears, since the option Consolidation in Groups
Possible is activated under Utilities Settings.
Note that if Consolidation in Groups is activated, only some of
the Consolidation Result functions are available. For example, you
cannot enter any licenses.
You can now return to the Systems tab page and start the partial
consolidation in the Control LAW box.
More information about the requirements and procedure
for grouping systems is available in SAP Library under
SAP NetWeaver Library SAP NetWeaver by Key Capability Solution
Life Cycle Management SAP Licenses License Administration
Workbench Overview of the LAW Procedures Grouping Systems.
Operational (01)
EHR User (07)
Operational (01)
Test (91)
Example 2
User B
Substitute (04)
Special Notes
User Combination
Procedure
51
The consolidated results are displayed for each user. The Status
column specifies whether the contractual user types of the
users are consistent, showing the following information:
If the light is green, the contractual user types of the user are
consistent.
If
the light is red, the contractual user types of the user are
inconsistent; that is, special versions and country surcharges
do not match in all systems.
An example of inconsistent contractual user types is as
follows: the user is, for example, classified as operational,
without a special version, and as an information user with
the special version of double byte.
Since you can transfer only results with consistent contractual
user types to SAP, correct the user classification (see section
18.2 Correcting User Classification).
The LAW data is also available to you for internal, automated
processing through the LAW interface (see appendix section
LAW Interface). You can obtain the data in the following ways:
As of software component SAP_BASIS 620, SP42, by using the
report RSLAW_TEST_BAPI
As
of software component SAP_BASIS 640 in LAW, by choosing
Goto Information Systems
52
Comment
Indicator
Combination of User
Types
Individually
In Combination
Total
53
The SDCC or the SDCCN is active (see SAP Note 178631 or 763561).
You have authorizations SDCC_DEV = READ and SDCC_RUN
= READ, WRITE for object S_SDCC, with which you can transfer
data.
54
Procedures
APPENDIX
Usertype Description
Up-to-date and detailed descriptions and definitions of the contractual user types of all SAP price lists are available on SAP Support
Portal
http://support.sap.com/licenseauditing Information about SAP System Measurement User Classification Overview of all available user
types
Contractual user types that are not yet available in the measurement program for your release, you can either obtain in a support
package (SAP Note 428479) or download and install them using a report provided on SAP Support Portal
http://support.sap.com/licenseauditing Information about SAP System Measurement User Classification All usertypes of
SAP_BASIS...
55
LAW Interface
Comment
Function Module
LAWUser
Users in LAW
The object contains all relevant data for an SAP software user in
LAW.
BAPI_LAWUSER_GETLIST
LAWSystem
Systems in LAW
The object contains all relevant data for SAP software in LAW.
BAPI_LAWSYSTEM_GETLIST
LAWEngine
Engines in LAW
The object contains all relevant data for an engine in LAW.
BAPI_LAWENGINE_GETLIST
LAWUserType
BAPI_LAWUTYPE_GETLIST
LAWConsUser
BAPI_LAWCONSUSR_GETLIST
LAWConsEngine
BAPI_LAWCONSENG_GETLIST
LAWConsUserType
BAPI_LAWCONSUTY_GETLIST
56
www.sap.com /contactsap