Global License
Auditing Services
MEASUREMENT PROGRAM AND
LICENSE ADMINISTRATION WORKBENCH
Version 7.0
Updated Edition, August 2015

2
Copyright 2015 SAP SE. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE. The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5,
System x, System z, System z9, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5,
POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP SE and its affiliated companies
(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

1 SAP License Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Named Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Process Overview: SAP License Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5 Information and Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6 Measurement Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7 Process Overview: System Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8 Classifying Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.1 Classifying Individual Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2 Classifying Users with Reference Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.3 Classifying Users with User Mass Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.4 Classifying Users with Central User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.5 Classifying Users with the User Classification List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.6 Performing Mass Changes of Contractual User Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.7 Migrating Price Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.8 Checking User Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.9 Analyzing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3

4
9 Performing the System Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
10 Consolidating Results and Transferring Results to SAP. . . . . . . . . . . . . . . . . . . . . . . . . 27
11 Evaluation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
11.1 Evaluation Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
11.2 Special Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
12 Measurement Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
12.1 Measurement Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
12.2 Creating the Measurement Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
12.3 SSCR-Registered Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
12.4 Results of Engine Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
13 Definition and Availability of Contractual User Types . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.1 User Types in the mySAP Solution Suite/Business Suite Price List
(mySAP.com Solution Suite Price List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.2 User Types in the mySAP Individual Solutions Price List
(mySAP.com Individual Solutions Price List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.3 User Types in the SAP Software Component (R/3 Enterprise) Price List . . . . . . . . . . . . . . . . . . 34
13.4 Special Module User Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
13.5 Special User Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
13.6 Technical Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
14 LAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
14.1 Prerequisites for Using LAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
14.2 Collecting Measurement Data in the Component System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
15 Process Overview: LAW Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

16 Combining Measurement Data in LAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16.1 Loading System Data from a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16.2 Loading System Data for a Non-SAP System from a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16.3 Transferring Measurement Data to LAW by RFC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16.4 Copying RFC Destinations of SAP Solution Manager 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
16.5 Entering Component Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
16.6 Starting Remote Actions in Component Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
16.7 Deleting a Component System or Measurement Data from LAW . . . . . . . . . . . . . . . . . . . . . . . 47
17 Combining Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
17.1 User Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
17.2 Enhanced Grouping of Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
17.3 Grouping Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
18 Consolidating Contractual User Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
18.1 Consolidation Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
18.2 Correcting User Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
19 Transferring Results to SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Usertype Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
LAW Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5

6
This system measurement guide contains supplementary information about SAP SE’s 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.

SAP® software contains measurement tools that help all systems produce the information necessary for determining usage of the SAP software. This guide describes the procedure for a license audit and how to use the following SAP tools:
• Measurement program
• License administration workbench (LAW)
According to the provisions of the contract, the customer undertakes to support SAP in accordance with SAP’s instructions.
In particular, the customer undertakes to prepare the measurement log no later than four weeks after SAP’s request. The measurement may be carried out 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.
The measurement program is used exclusively to determine the number of users and the used units of SAP products. The results are evaluated according to the terms of your contract.
You classify your users, clients, and systems according to this system measurement guide.
You then consolidate the measurement results of your systems using LAW.
If you have any questions about your SAP software contract or the licensed products, contact your SAP sales executive.
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 customer’s 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 user’s 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).
7

8
1.2 Named Users
A named user is an employee of a customer, of its affiliated companies, or of third-party companies authorized to access the licensed software directly or indirectly, regardless of the technical interface chosen. All employees who use the SAP software require a license and must be set up as dialog users.
SAP is entitled to require that the customer declare the number of external named users and produce a stipulated statement from each external named user concerning compliance with the restrictions applying to licensed use and confidentiality.
1.3 Engines
Engines are software products that are available as options.
Except as otherwise expressly stated, every user who accesses any software engine requires a named user license.
Engine licensing depends on key business metrics such as orders, contracts, contract accounts, and patients treated.
Engines are either pan-industry, such as Payroll Processing within the mySAP™ ERP application, or industry-specific, such as Billing within the SAP for Utilities solutions.
Engines are to be licensed in addition to named users. Named users may access engines to the extent of their licensed user category.

This system measurement guide is valid for all SAP software contracts.
It is based on the functions of the measurement tools (measurement program and LAW) that were revised and enhanced for the SAP NetWeaver® 2004s platform (software component
SAP_BASIS 700).
The functions available in the measurement tools depend on the release of your SAP software component SAP_BASIS.
You can find the details of the software component
SAP_BASIS in the SAP software system by choosing System
→
Status
→
SAP System Data
→
Component Information . The component information is specified in this SAP System
Measurement Guide.
This measurement guide contains all information about the measurement tools for earlier releases.
Some of the functions are also available for earlier releases through support packages and the Note Assistant (SAP Note
428479 from the SAP Notes tool).
The functions available in the measurement tools depend on your SAP software release. The measurement tools are specified in this guide.
Platform
SAP NetWeaver® 2004s
SAP NetWeaver 2004
SAP® Web Application Server 6.20
SAP Web Application Server 6.10
Software Component
SAP_BASIS 700
SAP-BASIS 640
SAP_BASIS 620
SAP_BASIS 610
SAP Basis 4.6D
SAP Basis 4.6C
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.
Table 1: Software Components and Their Associated Platforms
2.1 Availability of Contractual User Types
Classification of contractual user types depends on the price list on which your contract is based. The available contractual user types are available to you in the measurement program.
The user types in the different SAP software price lists, especially those in the mySAP price lists, are available as support packages for releases earlier than SAP R/3 4.6B (SAP Note 428479).
You can obtain further contractual user types for the mySAP
Business Suite family of business applications and individual applications that are not available in the measurement program for your release by doing the following activities:
• Obtaining the user types in a support package
• Downloading and installing the user types individually or as a package on the SAP Support Portal: support.sap.com/licenseauditing
Measurement
→
→
Information about SAP System
User Classification
2.2 Availability of Software Engine Measurement
The measurement program contains counting modules that automatically calculate software engine use (SAP Generic,
New Dimension, and IS add-on products).
Measurement programs for software engines are either shipped with the product or are available for earlier releases through support packages.
You can find an up-to-date overview of the programs for engine measurement currently available on SAP Support Portal support.sap.com/licenseauditing
Measurement
→
→
Engine & Self-Declaration Product
Engine Measurement .
Detailed information on engine measurement is also available on SAP Support Portal, including the following information:
•
Description of metric
• Definition of objects
• Notes on measurement
9

To be able to measure all users in your SAP installation clearly and precisely, your systems, clients, and users must be classified according to current use and the price list they are based on prior to each system measurement. This classification reflects the terms of your contract.
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.
If you convert from a software components contract to a mySAP contract, users that are already classified must be reclassified according to the newly licensed user types.
3.1
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.
For each software product, you must register a separate installation in writing with SAP. SAP then gives you a unique installation number.
3.2 SAP Software System
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.
Note: You can make changes to your system landscape
(deletion, system status, and so on) quickly and easily on the system data maintenance page for customers on
SAP Support Portal at support.sap.com/system-data (SAP Note 94998).
Installation 1 Installation 2
Productive
System
Test
System
Development
Figure 1: Overview of Installations and Systems
Productive
System
Test
System
Training
System
SAP®
Software
Contract
Installation N
Productive
System
Test
System
10

SAP initiates system measurement with the measurement request for your SAP contract. These are the steps for the process:
1.
Your SAP Customer Competence Center location receives an overview of all measurement-relevant installations and systems covered by your contract. You must then take the
2.
3.
following actions:
• Check the provided installation overview and systems
• Forward this measurement plan to the administrators responsible for the installations/systems
Each SAP software system must be measured with the measurement program (see section “7 Process Overview:
System Measurement”). You must take the following actions:
• Activate the price list valid for your contract
• Check the system data and flag the relevant clients
• Classify the users according to how they use the software
(see section “8 Classifying Users”)
• Start system measurement
• Check the results
If you do not need to consolidate the measurement results
4.
5.
using LAW, send the measurement results directly to SAP instead
Consolidate the measurement results with LAW (see section
“14 LAW”). To do so, take the following actions:
• Load the LAW measurement plan into the central LAW system
• Import the measurement results of all systems into LAW
• Group the users using a single criterion
• Consolidate the data and check the results
Send the LAW results directly to SAP
Start measurement program
Activate price list
Customize system data, clients
Classify users via:
• User maintenance
• Reference user
• User mass maintenance
• User classification list
• Mass changes
• Migrating price lists
• Central user administration
Perform system measurement
Check results
User consolidation with license administration workbench?
Yes No Result per system
Select central LAW system
Import system measurement data
Combine users
Consolidate users
Figure 2: Process Overview
Transfer to SAP
Transfer LAW result to SAP
11

You can find current information on the SAP license audit and the SAP measurement tools (measurement program and
LAW) on SAP Support Portal at support.sap.com/licenseauditing .
You can find SAP Notes on the measurement tools on SAP
Support Portal under component XX-SER-LAS.
If you have any questions concerning the SAP measurement tools, create a message under component XX-SER-LAS.
If you have any questions relating to the contract, contact your sales executive or your contact person in the contracts department of your SAP international subsidiary.
You can find the documentation on the measurement program from SAP_BASIS 640 and on LAW on SAP Support
Portal at this location:
SAP NetWeaver help.sap.com
→
→
SAP NetWeaver by Key Capability
Cycle Management
→
SAP Library
→
Solution Life
→
SAP Licenses: System Measurement, License
Administration Workbench.
12

With the measurement program (transaction USMM), you determine the number of users and the chargeable objects of the engines of the SAP software for each system. You use the measurement program exclusively to determine the number of users and the used units of SAP products.
Measurement of the SAP engines takes place in the background.
The measurement program automatically detects the engines used in the system, measures them in the background, and lists them in the measurement log.
Measurement programs for software engines are either shipped with the product or are available for earlier releases through support packages.
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
List of users of measurement program
Price list for managing contractual user types
Mass changes to user types
Price list migration
User classification with reference user
User classification with user maintenance: mass changes (transaction SU10)
Technical user types communication, system, service, and reference excluded from measurement
SAP’s own users automatically excluded from measurement
Standard user classification test in nonproduction clients
Country surcharge for mySAP
Display of the Service Data Control Center (SDCC) transfer status in the measurement program
Display of the number of mobile engine users in the measurement log
Classification help
Entry of remarks on the measurement result
Table 2: Main Functions in the Measurement Program
Release Number
(The function is in the standard offering as of this release.)
SAP® R/3® Release 4.0B
SAP R/3 Release 4.6C
SAP R/3 Release 4.6C
SAP R/3 Release 4.6C
Software component SAP_BASIS 610
Software component SAP_BASIS 610
Software component SAP_BASIS 610
Software component SAP_BASIS 620
Software component SAP_BASIS 620
Software component SAP_BASIS 620
Software component SAP_BASIS 640
Software component SAP_BASIS 640
Software component SAP_BASIS 640
Software component SAP_BASIS 700
13

The following process provides you with an overview of how to prepare for and carry out the system measurement in each of your SAP software systems.
Prerequisites
The following prerequisites are required:
• Authorization S_USER_GRP
• Authorization S_BTCH_JOB
3.
Specify the clients to be measured on the Clients tab page by setting the Included flag for all clients relevant to measurement. In the standard system, clients 000 and 066 are excluded. You can also exclude the following clients from the measurement by removing the Included flag:
Test clients in a production system
Clients that have been copied for test purposes
A client must be included, if license relevant users are created on it, for example users of the ABAP Workbench and/or SAP NetWeaver development tool users.
In SAP R/3 releases from 4.6B to 4.5B (inclusive), select the clients to be excluded. In SAP R/3 3.1I and earlier, specify the clients to be excluded with the Exclude Clients option.
Process
You need to take the following steps:
1.
Start the measurement program (transaction USMM)
2.
by choosing Administration
→
Measurement
Administration
→
System
• For SAP releases earlier than software component
SAP_BASIS 610, use this path: SAP Menu
→
Tools
→
Administration
→
Administration
→
System Measurement
• For SAP releases earlier than SAP R/3 4.6C, use this path:
Tools
→
Administration
Check system data
→
Administration
→
System Measurement
The System data tab page contains information on the system’s unique ID.
• As of SAP R/3 4.0B, a system is automatically identified as productive as soon as one client is identified as productive.
You can change this setting only by using the role of the client in the client administration.
Figure 4: Clients
•
•
•
•
•
•
•
Check system data
Select relevant clients
Activate price list
Classify users
Start system measurement
Check results
Send results to SAP
4.
Activate the price list applicable to your contract by setting the Active flag on the Price lists tab page. The system then displays the user types for the applicable price list on the
User types tab page. The following price lists are available for software component SAP_BASIS 610:
•
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)
• mySAP Individual Solutions price list (mySAP.com
Individual Solutions price list)
Figure 3: SAP® Measurement Program
14

Figure 5: Price Lists
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)
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
→ mation about SAP System Measurement
→
User Classification
Infor-
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 6: User Types
• If you use contractually agreed-upon special users, name them clearly. To do this, select the text of a standard special module user type (such as SPECIAL MODULE TYPE 1) and overwrite it with the name of the contractual user type (for example, automobile manager). Then save your entries. These are then offered as F4 input help in the user classification.
Figure 7: Customizing of Special Module User Types
15

16
6.
7.
If you do not want to further consolidate the measurement results with LAW or transfer them directly, specify the address and fax number of the measurement results recipient on the Addresses tab page
Classify the users
• To be able to measure all users in your SAP software systems clearly and precisely, you must classify your users with the appropriate contractual user type according to current use and the price list the users are based on prior to each system measurement.
• If your contract changes, you must reclassify the users who have already been classified, in accordance with the user types in the new license.
• For security reasons, you can change the user type only in the client in which you are logged on.
• You have the following options for user classification:
– Classify the users individually (see section “8.1 Classifying
Individual Users”)
– Use a reference user (see section “8.2 Classifying Users with Reference Users”)
– Classify the users by group (see section “8.3 Classifying
Users with User Mass Maintenance”)
– Classify the users in central user administration
(see section “8.4 Classifying Users with Central User
Administration”)
– Use the user lists from the system measurement
(see section “8.5 Classifying Users with the User
Classification List”)
– Perform a mass change of the user types (see section
“8.6 Performing Mass Changes of Contractual User
Types”)
– Migrate the price lists (see section “8.7 Migrating Price
Lists”)
For information about the contractual user types, see the section titled “13 Definition and Availability of Contractual
User Types.”
Notes: In production clients, unclassified users count as the standard user type of the respective price list (see section
“11.2 Special Notes.”
As of software component SAP_BASIS 620, unclassified users count as test users in nonproduction clients.
8.
9.
10.
Start the measurement in the measurement program
(transaction USMM) by choosing System Measurement . By choosing this, you automatically also start plausibility checks. See the following sections for more information about the data, criteria, and settings of system measurement:
“11.2 Special Notes,” “11.1 Evaluation Rules,” and
“12 Measurement Results.”
Check the results by using the measurement statistics.
To do this, choose the Measurement Statistics option. If there are discrepancies, you must repeat the steps as of the user classification (step 7, above).
• The measurement statistics contain more data than the measurement log, so that you can more easily investigate discrepancies (see section “8.9 Analyzing Users”).
Check the user classification with the User Data Analyses or
List Classification Help function (see section “8.9 Analyzing
Users”).

11.
12.
To format the finally determined measurement data into a print format, choose the Create Log option on the initial screen of the system measurement. The measurement log contains mainly the same data as the measurement statistics; however, it is made anonymous here and combined systemwide. The log contains the following information:
• Header with date and address data
• System-specific data
• Information and results relevant to the measurement
• Results of background checks
• Measurement results for excluded clients
Specify the external named defined users that communicate with external software products that bundle, temporarily store, or summarize the communication activities, and then forward them to the SAP software installation
13.
14.
15.
If necessary, use the Comments function (enter a comment or upload a file) to send additional information about the measurement results to SAP. This function is available as of software component SAP_BASIS 620.
Transfer the measurement results to SAP, using one of the following techniques:
• If you use only one SAP system, transfer the measurement results directly to SAP (see section “10 Consolidating
Results and Transferring Results to SAP”).
• If you use multiple SAP installations, first consolidate the measurement results of all systems in LAW (see section
“14 LAW”). Then send the consolidated result to SAP.
• As soon as possible after the measurement, transfer the measurement results of the SAP component systems to the central LAW system. This means that the user master records are unlikely to have changed and there are no
(or only a few) differences between the user type statistics of the USMM measurement results of the individual systems and the consolidated results in LAW.
Check the transfer status
17

8.1 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.
2.
Start user maintenance (transaction SU01) by choosing
Tools → Administration → User Maintenance → User
Specify a user or an alias, and choose Change, Create , or
3.
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 .
Choose the LicenceData tab page in change mode
4.
5.
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”).
Save your entries
For SAP R/3 4.6C and earlier, do the following activities:
1.
Start user maintenance (transaction SU01) from the SAP
2.
software menu by choosing Tools
→
Administration
→
Maintenance
→
User
Specify a user or an alias, and choose Change or Create
User
3.
4.
Choose Measurement Data in change mode
Save your entries
In SAP R/3 4.6C and earlier releases, the contractual user type and special version are not copied when you copy a user. The user is initialized with the user type as operational user or mySAP.com Category II/Professional User and must subsequently be maintained manually.
8.2 Classifying Users with Reference Users
A reference user is a general, non-person-specific user. You cannot log on to the SAP software system with a reference user; it serves only for additional assignment of authorizations and license data (SAP Note 313585).
You use reference users, for example, to give Internet users identical authorizations and to create users with identical roles and authorizations.
Figure 8: LicenceData
18

User classification using reference users is available as standard as of software component SAP_BASIS 610 or in support packages for SAP R/3 4.6C and SAP R/3 4.6D.
You can classify your users by assigning a reference user with an appropriate classification. A user can inherit the classification of the reference user if the following is true:
• The user does not have any additional roles or profiles
• The user is not manually classified
Creating a Reference User
To create a reference user, do the following activities:
1.
Create a user in user maintenance (transaction SU01)
2.
On the Logon data tab page, choose the Reference user type and deactivate the password
3.
4.
On the LicenceData tab page, use the input help to select the contractual user type
Save your entries
Assigning Users a Reference User
Assign the relevant classified reference users to your users in user maintenance (transaction SU01) or user mass maintenance
(transaction SU10) on the Roles tab page: Reference user for additional rights .
Result
You have classified the users indirectly using a reference user.
You can use the extended list of the measurement program to display a list of all users that inherit their classification using a particular reference user. To use the extended list, take the following actions:
1.
2.
3.
In system measurement (transaction USMM), choose the
User Classification option
Choose Extended List
Specify the name of the reference user (with the input help),
4.
and choose Execute
Use the extended list in the measurement program to check which classification was used in the measurement (see section
“8.5 Classifying Users with the User Classification List”)
Figure 10: Reference Users in the Extended List
Figure 9: Reference Users
19

8.3
Classifying Users with User Mass Maintenance
As of software component SAP_BASIS 610, you can classify users with User Maintenance: Mass Changes (transaction SU10).
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.
3.
4.
2.
5.
6.
On the User Maintenance: Mass Changes initial screen, select the users whose user type you want to change
Choose Change
On the LicenceData tab page, choose the contractual user type for the selected users of the group, or assign an appropriate classified reference user to these users
Save your entries. The user classification of the user group is changed.
If you want to create a log of the mass change, choose Mass
Change with Log
Create user
(without classification)
Create HUBER
(Development)
Create MEIER
(Sales)
Create WEBER
(Development)
Jan Feb
Classify user as soon as they are created
Create HUBER
Classify HUBER
Create MEIER
Classify MEIER
Create WEBER
Classify WEBER
User Maintenance:
Mass Changes (SU10)
Mass Change Development
HUBER
WEBER
...
Mass Change
MEIER
...
Sales
Perform system measurement
Classify users as soon as they are created
Create WILD
Classify WILD
Create STORK
Classify STORK
License Audit
Perform system measurement
May
Classify user as soon as they are created
Create WILD
Classify WILD
Create STORK
Classify STORK
Figure 11: Strategy for Classifying Users with User Maintenance: Mass Changes
Procedure
To classify users with user mass maintenance , take the following actions:
1.
Start User Maintenance: Mass Changes (transaction SU10) by choosing Administration
→
System Administration
→
User Maintenance: Mass Changes , and choose the users according to the required criteria, as follows:
• Address data, for example, by room, department, or cost center
• Authorization data, for example, by authorization, role, or profile name
Figure 12: Classifying Users with User Maintenance: Mass Changes (1)
Figure 13: Classifying Users with User Maintenance: Mass Changes (2)
20

8.4
Classifying Users with Central User
Administration
When you use central user administration, you can process the user types in the central system using user maintenance (transaction SU01) or user maintenance (transaction SU10). The following prerequisites are required:
• The central and child systems have release software component
SAP_BASIS 620 or later; SAP Note 704412 is installed.
• In transaction SCUM, maintenance of license data is set to global . This is the default setting in new installations of central user administration. If you implement the support package in multiple systems in your landscape, we recommend that you do not activate global maintenance until you have set the maintenance of license data to global .
• You have copied all of the users, including all data (address data, license data, and so on) from the child systems into the central system.
Then consolidate the measurement results from all systems with LAW (see section “14 LAW”).
8.5
Classifying Users with the
User Classification List
The measurement program generates a list of all users created.
With this user classification list, you can classify your users clearly and effectively. Use the following lists:
• The simple list for manually classifying users
• The extended list for checking classifications (as of software component SAP_BASIS 610)
The extended list of the user classifications is available in a support package (SP) for the following releases: SAP R/3 4.6C
with SP11; SAP R/3 4.6D with SP03.
Classifying Users with the User List
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.
As of software component SAP_BASIS 610, the measurement program automatically excludes non-dialog users from the measurement (SAP Note 553606). They are no longer displayed in the user list (see section “13.7 Technical Users”).
As of software component SAP_BASIS 700, SP 14, non-dialog users are displayed again in the user classification list. It is possible to classify the non-dialog users manually. If they have a manual classification, they are counted as dialog users.
However, if they have no manual classification, they are disregarded in the system measurement.
In releases earlier than software component SAP_BASIS 610, classify the nondialog users accordingly.
To classify users that have not yet been classified, take the following actions:
1.
Start the measurement program (transaction USMM)
2.
3.
Choose User Classification and then Simple List
To display the unclassified users, select the User Type field on
4.
the User Classification screen, choose Edit → Selection Options
(F2), select Single Value , and choose Copy
If appropriate, restrict the selection further using the validity period for Currently Valid Users
5.
6.
7.
8.
Choose Execute
Select the users to be classified in the list
Choose Classify Selected Users
Use the input help to specify the contractual user type.
9.
Save your entries. The user list displays all users of your SAP software system with the assigned contractual user types.
21

Checking Classification with the Extended List
The extended list enables you to see which of the following classifications was included in the measurement:
• Manual user classification
• Classification using a reference user
You can obtain a list of all users that are classified by using a reference user with the extended list in the measurement program.
• Unclassified users
For more information about the extended list, choose
User Classification
→
313585.
Quick Info: Program Documentation or SAP Note
The extended list for user classification is available in support packages for the following releases:
• SAP R/3 4.6C, SP11
• SAP R/3 4.6D, SP03
8.6
Performing Mass Changes of
Contractual User Types
As of SAP R/3 4.6C, you can use the measurement program to perform mass changes of user types of a price list. You can use this function to assign a user type to all users that have not yet been classified and to change the classification of all users of type A to type B. For security reasons, you can change the user type only in the client in which you are logged on.
Mass change of user types is available by download or support package for SAP releases earlier than SAP R/3 4.6C (SAP Note
376252).
Prerequisites
This task requires that you have chosen Environment
→
Mass
Change on the initial screen of the measurement program and that the software is displaying the dialog box System Measurement:
Mass Change of User Types , which offers the following options:
• Classify Non-Maintained Users
• Change Old Classification
For releases earlier than SAP R/3 4.6C, choose Goto
→
Mass Change .
Field
Checked user type
User type (manual)
Reference user
User type (reference user)
Special version (hidden)
Created
Logon
Table 3: Extended List Fields
Description
User type that is relevant for the measurement and that is counted
User who was classified manually (This specification corresponds to that of the Checked User Type field.)
Name of assigned reference user
Contractual user type of the reference user
The relevant special versions for the checked user type, the user type (manual), and the user type (reference user), which are displayed and calculated
Date on which the user was created
Date on which the user last logged on
Figure 14: Mass Change of User Types
22

Classifying Unclassified Users
To classify the unclassified users, take the following steps:
1.
Use the input help to specify the new user type
2.
Choose Execute
3.
Check the security query, and confirm the mass change
A message in the status bar confirms the change to the users.
Changing Old User Classifications
1.
Use the input help to specify the previous and the future user type
2.
Choose Execute
3.
Check the security query, and confirm the mass change.
A message in the status bar confirms the change to the users.
8.7 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.
Procedure
To migrate price lists, take the following actions:
1.
On the initial screen of the measurement program, choose
2.
Environment
→
Migration Price List
The dialog box System measurement: Migration of price lists appears.
3.
Use the input help to specify the new user type for each of the old user types to be changed. If you do not specify a new user type in a row, users with this user type are not migrated.
4.
5.
Choose Execute migration . You receive confirmation that the user type of your user has changed.
Check the new contractual user types of your users
Figure 15: Price List Migration
23

8.8
Checking User Classification
As of software component SAP_BASIS 640, the User Data Analyses or List Classification Help function helps you classify individual user types and provides you with an analysis of the plausibility checks on various users.
On the basis of the user data, the List Classification Help function provides lists of users that access the related functions and objects and shows the current classification. You can use the list to check the classification of the listed users and correct it if necessary. As soon as you are satisfied with the classification of the users, you can perform the measurement again.
Classification help is available for ABAP Workbench and mobile engine users and for checking user types. Classification help for users creating objects and for user self-services is not yet available.
The user lists are made anonymous when the measurement results are transferred. That is, the data is transferred to SAP without the user names.
The List Classification Help function provides you with the options in the “Classification Help Functions” table for checking your user classification.
Function
Workbench Users
Comment
Displays a list of the users that changed the source code in the last 12 months (SAP Note 967539)
Classification
• Development Workbench
User (ID 06)
• mySAP™ Business Suite
Developer (ID 55)
• mySAP <Individual
Solutions> Developer
Mobile Engine Users Displays a list of the users that use mobile engines
SAP® Mobile Engine User
(ID 61)
Creator of Objects
Self-Service Users
Displays a list of the users that create the most objects, such as orders
Not yet available
Displays a list of the users that most frequently execute activities that are not part of the selfservice area, such as maintaining master records
Not yet available
Table 4: Classification Help Functions
Figure 16: Classification Help
Procedure
To check user classification, take the following actions:
1.
In the measurement program (transaction USMM), choose
2.
User Data Analyses or List Classification Help
In the Existing Measurement Data dialog box, the system displays a table of the previous measurements performed, with the number, date, and time of the relevant measurement. The most up-to-date measurement is at the top of the table.
3.
4.
To remove superfluous data from List Classification Help , choose Delete . Ensure that you do not accidentally delete the logs of the measurement that you have transferred to
SAP. If you do, you do not have any reference material if there are queries in the future.
Select the measurement to be checked, and choose the desired list option on the Classification Help tab page, such as
Workbench Users
24

Result
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
As of software component SAP_BASIS 640, you receive the results of the plausibility checks for system measurement using the User Analysis function.
As of software component SAP_BASIS 610, however, the results of the plausibility checks are available to you in the measurement statistics.
You have the options found in the “User Analysis Functions” table for evaluating the measurement result.
Procedure
To analyze users, take the following actions:
1.
In the measurement program (transaction USMM), choose
User Data Analyses or List Classification Help . In the Existing
Measurement Data dialog box, the system displays a table
2.
of the previous measurements performed, with the number, date, and time of the relevant measurement. The most up-to-date measurement is at the top of the table.
To remove superfluous data, choose Delete . Ensure that you
3.
do not accidentally delete the logs of the measurement that you have transferred to SAP. If you do, you do not have any reference material if there are queries in the future.
Select the measurement to be checked, and choose the desired list option on the User Analysis tab page, such as
Multiple Logons
Figure 17: User Analysis
Result
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.
Function
Deleted users
Expired users
Logon after expiration
Multiple logons
User list
Comment
Displays a list of users that have been deleted in the last week, last four weeks, or last twelve weeks
Displays a list of users whose validity period expired in the last week, last four weeks, or last twelve weeks before the measurement
Displays a list of users that have logged on to the system after their validity has expired
Displays a list of users for which there were multiple logons to the SAP® software system during the measurement period (see section “1.1 Use”).
Displays a list of users that logged on to a client of the
SAP software system during the measurement period
Table 5: User Analysis Functions
25

The measurement program determines and analyzes the number of users and the used units of the SAP engines in all clients. You can start the report as many times as you like.
The measurement program enters the measurement results in a table, overwriting the previous results.
Procedure
Start the system measurement in the measurement program
(transaction USMM) by choosing System Measurement . By choosing this, you automatically also start plausibility checks.
Take note of any messages before the system measurement, and if necessary, check the related long text.
26

If you use multiple SAP software installations, first consolidate the measurement results of all systems in LAW (see section “14 LAW”).
As of software component SAP_BASIS 640, you can export the measurement data to an LAW file directly in the measurement program by choosing System Measurement
→
Export to LAW File .
Your SAP Customer Competence Center must check the measurement results for SAP contracts with more than one installation and consolidate them with LAW.
The report also serves as a kind of RFC module for communication between remote systems.
As soon as possible after the measurement, transfer the measurement results of the SAP component systems to the central
LAW system. This means that the user master records are unlikely to have changed and there are no (or only a few) differences between the user type statistics of the USMM measurement results of the individual systems and the consolidated results in LAW.
Transferring Measurement Results to the Central LAW System
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.
For SAP releases earlier than software component SAP_BASIS 640, take the following actions:
• Use SAP Note 766822 to migrate the report RSLAW_PLUGIN for the releases in which the report already exists (SAP R/3 4.6C
and 4.6D; SAP Web AS 6.10 and 6.20)
• Use SAP Note 777163 to create the report RSLAW_PLUGIN for the releases in which the report does not exist (SAP R/3 3.1,
4.0B, 4.5B, and 4.6B)
All current and future corrections to the plug-in are based on these two SAP Notes.
Information about creating and activating the report is available in SAP Library under SAP NetWeaver Library
→
SAP NetWeaver by Key Capability
→
Solution Life Cycle Management
SAP Licenses
→
License Administration Workbench
Using LAW, Component Systems .
→
Prerequisites for
→
Figure 18: Export to LAW File: RSLAW_PLUGIN
27

Transferring Measurement Directly to SAP
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
→
NetWeaver by Key Capability
→
SAP
Solution Life Cycle Management
→
SAP Licenses
→
→
System Measurement
Checking the Transfer Status .
→
Process of System Measurement
28

11.1 Evaluation Rules
The following items are important for you to know when reading the measurement results:
• All chargeable users (nonchargeable users are, for example, substitute, test, and multiclient/multisystem users) and engines in the production clients of the system
• The number of ABAP Workbench and/or SAP NetWeaver development tool users in all systems
The relevant number of these users is the total of ABAP
Workbench and/or SAP NetWeaver development tool users in all systems.
If you do not use LAW to consolidate the users, note the following information when classifying users that operate in multiple clients and systems:
• A user must be classified only once in the highest group as a chargeable user in a production system (exception: ABAP
Workbench and/or SAP NetWeaver development tool users – see section “11.2 Special Notes,” for ABAP Workbench and/or
SAP NetWeaver development tool users in nonproduction systems).
• In all other systems, users can then be classified as multiclient/multisystem users (ID 11).
ABAP Workbench and SAP NetWeaver development tool users, in particular, can be created in multiple systems, including nonproduction systems.
Recommendation for Users Operating in Multiple Systems
Use LAW to consolidate employees with multiple user master records in various systems.
• Classify users unambiguously according to their job in all systems; that is, assign the users to a contractual user type.
• During the consolidation that then takes place in LAW, the users for a person are listed and assigned one contractual user type.
This virtually eliminates the risk of evaluating a person more than once; classification as multiclient/multisystem user is superfluous.
29

11.2 Special Notes
Note the following information:
1.
Unclassified users are counted with the standard user type of the respective price list. The standard user type is assigned on the basis of the client’s status. Note the following information about client status:
• If clients have production status, the standard user type from the valid price list is assigned to the as-yet unclassified users.
Activated Price List
SW Component mySAP.com® Solution Suite mySAP.com Individual Solutions
Standard User Type
Operational user (ID 01) mySAP Professional user (ID 52)
All users must be classified or you must specify a standard user type (SAP Note 896872)
Table 6: Standard User Types
2.
• For unclassified users of the mySAP Individual Solutions price list or combinations of active price lists, specify a standard user type for unclassified users. You can obtain this function in a support package (SAP Note 896872).
• As of software component SAP_BASIS 620, SP7, if clients have another status ( nonproduction ), the user type test is assigned to unclassified users as the standard user type.
For ABAP Workbench and/or SAP NetWeaver development tool users in nonproduction systems, if you do not use LAW
(see section “14 LAW”) to consolidate these users, note the following information when classifying people that operate in multiple clients and systems:
• In nonproduction systems, first use mass change to classify all users as test (ID 91).
• Then classify the people who use ABAP Workbench and/ or SAP development tools as chargeable users once, ideally in the central development system. To do so, use the contractual user type of your contract or of the price list on which your contract is based – for example, mySAP
Business Suite Developer (ID 55).
3.
4.
5.
6.
7.
• In all other systems, classify all other users of people already classified as test or multiclient/multisystem users
(ID 11).
• Transfer the measurement results of the nonproduction 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.
30

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 validity period expired in the last week, last four weeks, or last twelve weeks
• Number of users that have logged on to the system after their validity expired
• Number of measured users of the mobile engine
• Highest number of a user’s multiple logons to the system
• List of users by category: shows the distribution of users to the technical user types
• Automatically excluded, SAP technical users: shows the technical users automatically delivered by SAP that are made available free of charge
• Message about recording the engine measurement: outputs a warning if the recording of the data for time-dependent engine measurements began only after the specified measurement period
• As of SAP R/3 4.6C, number and distribution of the users for which a developer key – SAP Software Change Registration
(SSCR) key – was installed
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.
12.1 Measurement Statistics
Check the results using the measurement statistics. To do this, choose the Measurement Statistics option. If there are discrepancies, you must repeat the steps as of the user classification.
The measurement statistics contain more data than the measurement log, so that you can more easily investigate discrepancies.
The results determined (measured users and engines) are listed by client.
Do not send the measurement results to SAP until asked to do so.
12.2 Creating the Measurement Log
To format the finally determined measured data into a print format, choose the Create Log option on the initial screen of the system measurement.
The measurement log contains mainly the same data as the measurement statistics. However, it is made anonymous here and combined systemwide. The following information is included:
• Header with date and address data
• System-specific data
• Information and results relevant to the measurement
• Results of background checks
• Measurement results
• Measurement results for excluded clients
31

12.3 SSCR-Registered Users
As of SAP R/3 4.6C, the measurement result shows the number and distribution of user types that have an SSCR key. An SSCR key is a developer key that, as a rule, is required by ABAP
Workbench users and/or SAP NetWeaver development tool users.
Users for which SSCR keys are used are displayed in the list of users.
12.4 Results of Engine Measurement
SAP ships the measurement modules for the different engines in one of the following ways:
• As integral parts of the SAP software
• In the form of add-ons (SAP industry solutions)
The measurement program automatically recognizes these engines used in the system, counts them in the background, and displays them in the measurement log.
In addition, each named user that accesses an engine must be classified according to its activity.
You can find detailed up-to-date information about engine measurement on SAP Support Portal at support.sap.com/licenseauditing
Measurement
→
Engine & Self-Declaration Product
→
Engine Measurement .
32

Classify your users according to their activity, based on their authorization and the contractual agreement and in accordance with the price list on which your SAP contract is based. Note the following information:
• As of software component SAP_BASIS 610, the contractual user types are listed for each price list on the User Types tab page.
• As of SAP R/3 4.6C, the selected price list controls the available contractual user types.
• The contractual user types are available to you as an F4 Help selection list for SAP releases earlier than SAP R/3 4.6B.
13.1 User Types in the mySAP Solution
Suite/Business Suite Price List
(mySAP.com Solution Suite Price List)
A detailed description and definition of the contractual user types of mySAP.com Solution Suite are available at the following locations:
• In the appendix under “User Types in mySAP Solution
Suite/Business Suite Price List”
• On SAP Support Portal at support.sap.com/licenseauditing
→
Information about SAP System Measurement
→
User Classification
Overview of all available user types
→
• Users without classification in production systems count as mySAP Professional (ID 52) users.
For further contractual user types for mySAP Business
Suite and individual applications that are not available in the measurement program for your release, note the following information:
• You can obtain contractual user types in a support package.
• You can download and install contractual user types individually or as a package on SAP Support Portal at support.sap.com/licenseauditing
SAP System Measurement
→
Information about
→
User Classification
54
55
ID
52
53
Contractual User Type mySAP Professional (Cat. II) mySAP Limited Prof. (Cat. III) mySAP Employee (Cat. IV) mySAP Business Suite Developer
Table 7: Examples of User Types for the mySAP Solution Suite/Business Suite
Price List
For measurement of contractual user types that may not yet be included in your measurement program, use the special module user types by arrangement with your contact person at SAP for system measurement.
• Specify or overwrite the available special module user types with the appropriate name.
13.2 User Types in the mySAP Individual Solutions
Price List (mySAP.com Individual Solutions
Price List)
A detailed description and definition of the contractual user types of the mySAP.com Individual Solutions price list are available at the following locations:
• In the appendix under “User Types in mySAP Individual
Solutions Price List”
• On SAP Support Portal at support.sap.com/licenseauditing
→
Information about SAP System Measurement
→
User Classification
Overview of all available user types
→
33

• Classify all valid users according to the licensed mySAP solution. An error message appears for unclassified users.
• For unclassified users of the mySAP Individual Solutions price list, you can specify a standard user type for unclassified users.
You can obtain this function in a support package (SAP Note
896872).
ID
AA
AB
BB
AX
AY
AZ
BA
Contractual User Type mySAP™ CRM Professional mySAP CRM Limited Professional mySAP CRM Developer mySAP ERP Professional mySAP ERP Limited Professional mySAP ERP Employee mySAP ERP Developer
Table 8: Examples of Contractual User Types for the mySAP Individual
Solutions Price List
13.3 User Types in the SAP Software Component
(R/3 Enterprise) Price List
A detailed description and definition of the contractual user types of the SAP Software Component price list are available in the following locations:
• In the appendix under “User Types in the SAP Software
Component (R/3 Enterprise) Price List”
• On SAP Support Portal at support.sap.com/licenseauditing
→
Information about SAP System Measurement
→
User Classification
Overview of all available user types
→
• Users without classification in production systems count as operational (ID 01) users.
ID
01
02
04
06
Contractual User Type
Operational
Information
Basis Only
Development Workbench
Table 9: Examples of Contractual User Types for Software Component
(R/3 Enterprise) Price List
• IS users are users who use industry-specific components and for whom an individual contractual rule holds (IS user types 81 through 85). Overwrite the IS users used and name them clearly.
13.4 Special Module User Types
Special module user types are available to you regardless of the active price list.
Special module users are users for whom a special individual contractual rule holds.
• These user types are permitted only if appropriate contractual agreements with SAP are in place or by arrangement with your contact person for system measurement at SAP.
• Overwrite the special module users used and name them clearly.
If these user types are used without contractual agreement or by arrangement, these users count as unclassified users, depending on the underlying price list, and evaluated with the standard user type of the relevant price list.
ID
71-79
Contractual User Type
Special module types 1 to 9
Table 10: Special Module User Types
34

13.5 Special User Types
Special user types do not depend on the activated price list.
Type ID Contractual User Type
04
11
91
92
Substitute
Multiclient/multisystem
Test
External contact
Comment
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.
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.
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.
The classification of test users must be agreed on with SAP.
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.
Table 11: Special User Types
35

13.6 Technical Users
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
As of software component SAP_BASIS 610, the measurement program counts only the dialog users created in the system.
The measurement program excludes SAP’s own and technical users from the measurement, provided that they are not classified manually.
The measurement program counts the technical user types for releases earlier than software component SAP_BASIS 610.
Classify them manually as test users (SAP Notes 327917 and
553606).
The measurement log lists the following information:
•
The automatically excluded SAP technical users for each client
•
The users for each category, according to the technical users type (see table “Technical User Types”)
Technical User Type
Dialog
Features
SAP-internal, technical user
Communication Cross-system activities, not capable of interaction
System
Service
Reference
System-dependent and system-internal activities, not capable of interaction
System access (anonymous) used jointly by different users, not capable of interaction
Tool for extending authorization, logon not possible
Table 12: Technical User Types
Examples/Purpose
SAP*
DDIC
SAPCPIC
TMSADM
ITSLOGIN
Batch-Input
External RFC
CPIC
Internal RFC
Background processing
Anonymous system access (Internet user)
Internet users with identical authorizations
36

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 person’s 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.
The LAW data is available to you for internal, automated processing through the LAW interface – for example, for internal cost allocation for the licenses.
SAP® R/3®
System
Jones
Professional
Miller
Limited
Professional
1 Professional
1 Limited Professional
LAW
Figure 19: LAW Strategy
SAP R/3
HR System
Jones
Employee
Baker
Employee
Jones
Professional
Taylor
Professional
2 Employees
Business Info.
Warehouse
System
2 Professionals
LAW Result
2 Professionals (Jones, Taylor)
1 Limited Professional (Miller)
1 Employee (Baker)
Detailed information about LAW and its functions are available in SAP Library under SAP NetWeaver Library
→
SAP NetWeaver by Key Capability
→
Solution Life Cycle Management
→
SAP Licenses
→
License Administration Workbench .
37

The LAW screen consists of two large subscreens:
• Control LAW
– You can call all steps for user consolidation in sequence here.
– As an alternative, you can, as of software component
SAP_BASIS 640, use the functions of the tab pages to transfer the measurement data – for example, for the RFC transfer of data.
• Tab pages
The tab pages provide an overview of the systems for which data has already been imported into LAW or for which you must still transfer data. The significantly enhanced functions for transferring measurement data from the component systems are also available to you here as of software component
SAP_BASIS 640. The following functions are included:
– Systems (imported systems)
– Inbox, Messages (as of software component SAP_BASIS 640)
– Result, Groups (as of software component SAP_BASIS 700)
Figure 20: LAW
This guide is based on the functions of LAW that were revised and enhanced for SAP NetWeaver 2004s (software component
SAP_BASIS 700). It also contains all information for earlier releases. Some of the functions are also available for earlier releases in support packages and the Note Assistant.
Function Description Release Number
Use consolidation with LAW
Consolidating central user master records by a uniform criterion
(The function is in the standard offering as of this release.)
Software component
SAP_BASIS 610
LAW interface Using BAPI® or XML
RFC connection LAW/ component systems
SAP® Solution Manager 4.0
Copying the RFC destination
Electronic LAW measurement plan
Enhanced grouping of users
Starting remote actions in component systems
Entering component systems
Using multiple criteria, personalization objects, and so on
Grouping of systems
Consolidation result
Software component
SAP_BASIS 620, SP 42
Software component
SAP_BASIS 640
Software component
SAP_BASIS 640
Software component
SAP_BASIS 640
Software component
SAP_BASIS 640
Enabling partial consolidation of groups – for example, group companies
Providing functions for further internal processing – for example, license maintenance
Software component
SAP_BASIS 700
Software component
SAP_BASIS 700
Table 13: Overview of the Main Functions of LAW
14.1 Prerequisites for Using LAW
For you to be able to use LAW, the prerequisites listed below must be fulfilled.
Authorizations
You must have authorization for authorization object
S_USER_GRP, ACTVT = 03 (display). For transferring the results, you also require the authorizations SDCC_DEV = READ and
SDCC_RUN = READ, WRITE for object S_SDCC.
38
→
→
2
0
→
2
0

LAW System
Note the following information about the LAW system:
• You have defined a system as the central system. The release of this LAW system is SAP R/3 4.6C SP30 or later. The support package level must be current.
• Transaction LICENSE_ADMIN or SLAW exists in the LAW system. As of software component SAP_BASIS 610, transaction
LICENSE_ADMIN is included as standard. As of SAP NetWeaver
2004, transaction SLAW is also included as standard.
• For security reasons, if you do not already use software component SAP_BASIS 640, use a separate system to make the upgrade easier.
We recommend operating LAW on SAP Solution Manager 4.0
or later, because the existing infrastructure of RFC connections can be used there.
Component Systems
Note the following information about component systems:
• The component system release is SAP R/3 3.1I.
• The report RSLAW_PLUGIN exists in the component systems to collect the measurement data.
The report RSLAW_PLUGIN is the plug-in for LAW and forms the interfaces between the central LAW system and the connected component systems. It must be used for formatting the measurement results and transferring them from the component system to LAW.
As of software component SAP_BASIS 640, the report also serves as a kind of RFC module for communication between remote systems. To use the new functions of LAW and the future corrections for earlier releases, take the following actions:
– Use SAP Note 766822 to migrate the report RSLAW_PLUGIN for the releases in which it already exists (SAP R/3 4.6C and
4.6D, SAP Web AS 6.10 and 6.20)
– Use SAP Note 777163 to create the report RSLAW_PLUGIN for the releases in which it does not exist (SAP R/3 3.1, 4.0B,
4.5B, and 4.6B)
All current and future corrections to the plug-in are based on these two SAP Notes.
Information about creating and activating the report is available in SAP Library under SAP NetWeaver Library
→
SAP NetWeaver by Key Capability
→
Solution Life Cycle Management
→
SAP Licenses
→
License Administration Workbench for Using LAW, Component Systems .
→
Prerequisites
User Data
The user master records need a uniform criterion, such as the same user ID (alternatively, first and last name, e-mail address, telephone number, and so on).
Availability of Data to be Evaluated
You have determined the measurement-relevant data for the component systems and the LAW system as follows:
• You have classified the user master records in every relevant system in accordance with the activities of the users in the system.
• You have run the system measurement (transaction USMM) in every measurement-relevant system (see section
“6 Measurement Program”).
14.2 Collecting Measurement Data in the
Component System
You can collect the measurement results directly in each component system and take the following actions:
• Save the data in a local file, which you load from the central system
• Send the data to the central system by RFC (as of software component SAP_BASIS 640)
• Alternatively, start the report for the component system from the central system (see section “16.6 Starting Remote
Actions in Component Systems”).
Information about collecting measurement data in the component system is available in SAP Library under
SAP NetWeaver Library
→
SAP NetWeaver by Key Capability
→
Solution Life Cycle Management
→
SAP Licenses
→
License
Administration Workbench
Component System .
→
Collecting Measurement Data in the
39

Procedure
To collect measurement data in the component system, take the following actions:
1.
Start the report RSLAW_PLUGIN in the measurement program (transaction USMM) by choosing System
Measurement
→
Export to LAW File , or start the corresponding report that you have created (using transaction SA38)
2.
3.
To transfer the data by RFC, first maintain the RFC destination of the central LAW system. Select Maintain
RFC Destination for Central LAW System , and choose Execute .
A dialog window on which you enter the name of the
RFC destination appears.
Choose the type of data transfer and then Execute . You have the following options:
• By download to a file: Saves the measurement data to a local file that you specify in the accompanying dialog box
• By e-mail to an address: Allows you to send the measurement data to one or more e-mail addresses if the system is connected to an e-mail server
• By RFC to the central LAW system: Sends the measurement data to the central system. You can choose whether you send the data by RFC or qRFC.
• By function module: Allows you to specify your own function module for postprocessing the measurement data – see the online documentation in the program
RSLAW_PLUGIN (I button)
• By scheduling of a background job for license measurement and for transfer of the data to LAW
Result
You have collected the license-relevant data from the component system and can perform the next step, which depends on which of the following options you have chosen:
• Combining the measurement data in LAW if you want to transfer the data to LAW by RFC
• Loading system data from a file if you saved the data to a local file
Figure 21: Export to LAW File: RSLAW_PLUGIN
40

After you have performed the system measurement in the component systems and in the LAW system, you can evaluate and consolidate the measurement data centrally in LAW. To consolidate the measurement results with LAW, you must perform the steps below in the order in which they are listed:
1.
Combine the measurement data of all component systems and of the central system in LAW (see section “16 Combining
Measurement Data in LAW”)
2.
Combine the users, and then check the user list (see section
“17 Combining Users”)
3.
4.
Correct and amend the combined users manually, if necessary
Consolidate the data and check the results using the results list and the Result tab page (see section “18 Consolidating
Contractual User Types”)
5.
6.
7.
8.
If necessary, correct the user classification of the users in the original system (see section “18.2 Correcting User
Classification”)
Transfer the consolidated data to SAP, and then check the list of all transfers (see section “19 Transferring Results to
SAP”)
Use BAPI to utilize the LAW data for additional internal processing (see appendix section “LAW Interface”)
Group the systems so that you can perform partial consolidations later (see section “17.3 Grouping Systems”)
41

You have the following options for transferring the data of the component systems and central system to LAW:
• You load the data for each component system from a local file and transfer the central system’s data with the LAW system data function in step 1 of the Control LAW box.
• As of software component SAP_BASIS 640, you can transfer the measurement data of the component systems and of the central system by RFC. Significantly enhanced functions for transferring data from the systems are available.
You can also import data for non-SAP systems in your system landscape into LAW (see section “16.2 Loading System Data for a
Non-SAP System from a File”)
16.2 Loading System Data for a Non-SAP System from a File
If you have non-SAP systems in your system landscape from which the users use the SAP system indirectly through interfaces (for example, with an RFC user), you can also use
LAW as the central measurement system for these systems.
To do this, collect the data required by LAW in a characterseparated values (CSV) file. Use the report RSLAW_IMPORT_
EXTERNAL_DATA to convert it into a system identifier (SID) text file that can be read by LAW, and then automatically load it into LAW.
16.1 Loading System Data from a File
You import the measurement files of the component systems and the data of the LAW system into LAW as follows:
1.
2.
Call LAW (transaction SLAW or LICENSE_ADMIN)
To import the files with the measurement data for the
3.
component systems, choose the option Component System Data in the Control LAW box
To import the measurement data for the LAW system, choose the LAW System Data option in the Control LAW box
Information about the requirements and procedure is available in SAP Library under SAP NetWeaver Library
→
SAP NetWeaver by Key Capability
SAP Licenses
→
→
Solution Life Cycle Management
→
License Administration Workbench
→
Overview of the
LAW Procedures
→
Combining the Measurement Data in the LAW
Loading System Data for a Non-SAP System from a File .
→
Result
The data of the systems relevant for the measurement is displayed on the Systems tab page in the Measurement Results view. For more detailed information about a system, double-click the corresponding line.
In the next step, you combine the users (see section
“17 Combining Users”).
16.3 Transferring Measurement Data to LAW by RFC
As of software component SAP_BASIS 640, you have the following options for transferring measurement data to the central LAW system by RFC:
• You can start the measurement in the component system, and transfer the data with the report RSLAW_PLUGIN .
• You can start the measurement in the component system from the central system. You then transfer the measurement data to the central system by RFC or initiate its transfer from the central system (see section “16.6 Starting Remote
Actions in Component Systems”).
To protect data, LAW triggers only the request for the data to be sent by RFC. The component system then creates a separate
RFC connection to the configured central LAW system for the data transfer.
42

• As of software component SAP_BASIS 640, you can load the system data from a file. If you receive the SAP measurement request by e-mail, SAP sends you the electronic LAW measurement plan with the measurement request. The measurement plan contains the system data (system number, installation number, hardware key, and system ID).
The LAW measurement plan is the basis of every consolidated measurement. Your SAP contact person at License Auditing
Services can send it to you on request. Alternatively, you can also enter the measurement plan manually in exceptional cases.
Prerequisites
Note the following prerequisites:
• The report RSLAW_PLUGIN (version 5.0 and later) exists in the central LAW system and the component systems.
• There is a functioning RFC infrastructure between the central
LAW system and the component systems. If they exist, you can use the RFC destinations of SAP Solution Manager
(version 4.0 and later) for this purpose.
• You have made the RFC destination for the LAW system known in the component system.
Procedure
To transfer measurement data to LAW by RFC, take the following actions:
1.
Load the LAW measurement plan , and maintain the RFC destinations of your component systems and of the central
2.
3.
system
Start the measurement in the component systems and in the central system
To transfer the measurement data to the central LAW
4.
system, select the systems with the status new on the Inbox tab page for which you want to transfer measurement data and choose Transfer Measurement(s) .
All selected measurements with the status new are transferred directly to LAW. This is indicated on the Systems tab page in the Measurement Results Overview with a green traffic light. A red traffic light, on the other hand, indicates that you have not yet transferred the measurement results for the relevant system.
On the Messages tab page, you can display a log of all actions so you can react to possible errors.
• The functions of the application log are available to you here – in particular, the button New Selection . You can use it to specify the period for which the log entries are to be displayed.
Result
The data of the systems relevant for the measurement is displayed on the Systems tab page in the Measurement Results Overview . For more information about a system, double-click the corresponding line.
More information about transferring measurement data to LAW by RFC is available in SAP Library under SAP
NetWeaver Library
→
Cycle Management
→
→
SAP NetWeaver by Key Capability
SAP Licenses
→
→
Solution Life
License Administration Workbench
Transferring Measurement Data to the LAW by RFC .
In the next step of the Control LAW box, you combine the users
(see section “17 Combining Users”).
43

16.4 Copying RFC Destinations of SAP Solution
Manager 4.0
As of software component SAP_BASIS 640, you can copy the
RFC destinations from the system landscape of SAP Solution
Manager into LAW and reuse them.
Prerequisites
You have configured the system landscape of SAP Solution
Manager 4.0.
Procedure
To copy RFC destinations of SAP Solution Manager 4.0, take the following actions:
1.
In transaction SLAW, switch to the Maintain RFC Data view on the Systems tab page
2.
3.
Choose Add RFC Destinations . The Transfer RFC Destinations from
Solution Manager screen appears. If this function is not displayed, no system landscape has been maintained, or SAP Solution
Manager is not available in this system.
Select the RFC destinations for the component systems to be copied. Ensure that only one RFC destination is selected for each system. Note the following information:
• If there is exactly one destination for each component system, you can copy these in one step.
• If multiple destinations exist, you need to select exactly one to be copied. To do this, select the relevant check box.
If the tree display of the systems and their destinations is displayed, all destinations that can probably be used are selected (check boxes). If destinations are already assigned to individual systems, these are specified and highlighted in color.
4.
5.
6.
The program uses the assigned icons to indicate the status of the individual systems and destinations. (The quick info in the program provides details.) The destinations for a system are displayed (expanded) only if there are problems or if the assignment is not unique. If there is long text for a message, the message is displayed as a link.
Choose Save Destinations to copy the selected RFC destinations, and if applicable, overwrite the existing destinations.
Any communication errors that are displayed might be only temporary. You can therefore always copy all destinations without restrictions.
Check the usability of the selected destinations by choosing
Check Destinations
Call the problem-identification log by choosing Display Log .
If the program identifies problems during the data collection or a check, it records this in the log.
Result
You have copied the RFC destinations of SAP Solution
Manager 4.0.
44

16.5 Entering Component Systems
As of software component SAP_BASIS 640, you can either load the data for the component systems from a file (LAW measurement plan) or, in exceptional cases, include it manually.
With an Electronic LAW Measurement Plan
If you have an electronic LAW measurement plan, take the following steps:
1.
2.
3.
Start LAW
Switch to the Maintain RFC Data view on the Systems tab page
To load the system data from the file, choose Load Measurement Plan
• A dialog box appears, in which you specify the local file to be loaded. All system data of your component systems to be measured and the central system are displayed in
4.
LAW in this way.
• If system data – that is, an old LAW measurement plan – already exists, LAW compares the plans and copies the manually added data, such as the RFC destination. However, it does not delete any component systems when doing so. You must always perform the deletion manually.
Add the name of the RFC destination for each system, and if necessary, replace the default name of the report
RSLAW_PLUGIN with the actual report name used in the relevant system. You can specify the RFC destination NONE for the central system.
• Perform a function, such as Refresh , after the input so that your data can be transferred and checked.
5.
6.
To compare the system identification data with the data from the component systems and to fetch and add missing data (release and system status), select all systems and choose Check System Overview by RFC .
If the function could not be executed or inconsistencies were found (for system number, installation number, and so on), the traffic light is red, and an icon is displayed in the Info column, with which you can display more detailed information. You must manually clean inconsistencies displayed with a red traffic light by taking the following actions:
• Delete the relevant line, and choose Add New System
• Enter the correct data in the dialog box
• If the checks ran successfully, the traffic lights are green.
Save the system overview
Information about the procedures, checks, and status are available in SAP Library under SAP NetWeaver Library
→
SAP NetWeaver by Key Capability
→
Solution Life Cycle Management
→
SAP Licenses
→
License Administration Workbench
→ the LAW Procedures
→
Overview of
Combining the Measurement Data in the LAW
→
Transferring Measurement Data to the LAW by RFC
→
Entering
Component Systems paragraph With an Electronic Measurement Plan .
45

Without an Electronic LAW Measurement Plan
If you need to add to the electronic LAW measurement plan, perform the following steps for each system to be added:
1.
Use the Add New System function to enter the data for each individual system. If you do not specify a system number,
2.
LAW assigns a temporary system number.
To compare the system identification data with the data from the component system and to fetch and add missing data (release and system status), select the system and choose
Check System Overview by RFC. You must have set up the RFC connections for this.
If the function could not be executed or inconsistencies were found (for system number, installation number, and so on), the traffic light is red, and an icon is displayed in the Info column, with which you can display more detailed information. You must manually clean inconsistencies displayed with a red traffic light by taking the following actions:
• Delete the relevant line, and choose Add New System
• Enter the correct data in the dialog box
3.
If the checks ran successfully, the traffic lights are green.
Save the system overview
16.6 Starting Remote Actions in Component Systems
To start remote actions in component systems, do the following activities:
1.
2.
Start LAW (transaction SLAW)
Switch to the Remote Actions view on the Systems tab page.
The status display of the traffic lights is independent of the status display in the Maintain RFC Data view and has the following meanings:
• Gray: No action has yet been started.
• Yellow: An action has been started but not yet finished.
• Green: The last action was successfully executed.
• Red: The last action was not successfully executed.
3.
If the status is red, there is an icon in the Info column, with which you can display the associated error text.
Select the component system to be measured, and under measurement tools, choose, for example, the action Start and
Transfer Measurement
• You can start only one action for each component system.
If you start a new action before an action is completed, the system displays a warning. If you ignore this warning, the new action replaces the previous action. If a response is still received from the component system for the previous action, it is ignored. That is, it does not change the status, although measurement data that still arrives may be saved in the in-box.
46

Action
Start and transfer measurement
Comment
This starts the measurement in the component system, waits for the end of the measurement, and transfers the measurement results to the central LAW system. The results are available on the Inbox tab page.
Start measurement only
Transfer last measurement
Test connection
Perform qRFC analysis
Perform tRFC analysis
Note: This function always starts asynchronously and is not available for component systems with SAP® software releases earlier then SAP R/3® 3.1.
This starts the measurement in the component system. This corresponds to measurement with the local transaction
USMM.
This instructs the component system to transfer the most recent available measurement to the central LAW system.
This corresponds to sending a measurement by RFC with the report RSLAW_PLUGIN .
This checks the RFC infrastructure. RFC communication to the component system is created for this test, which in turn creates RFC communication back to the central LAW system.
This branches to the qRFC monitor. The status of the asynchronous RFC requests is displayed there, and you can analyze possible problems. All remote actions, with the exception of the Check System Overview by RFC function, take place asynchronously as qRFC.
This branches to the tRFC monitor. The status of the transactional RFC requests is displayed there, and you can analyze possible problems.
Table 14: Possible Actions in the Component System
16.7 Deleting a Component System or
Measurement Data from LAW
In LAW, you can either completely delete one or more component systems from the overview or delete only the measurement data of these systems.
Prerequisites
You have already entered the data for the component systems or transferred the measurement data to LAW.
Deleting a Component System
To delete a component system, do the following activities:
1.
Start LAW (transaction SLAW)
2.
On the Systems tab page, choose the Delete Systems function in the Maintain RFC Data view or Remote Actions view
3.
Select the systems to be deleted.
The selected systems are removed from the central LAW system with all of their data.
Deleting Only Measurement Data
To delete only measurement data, do the following activities:
1.
Start LAW (transaction SLAW)
2.
3.
Choose the Systems tab page in the Measurement Results overview
Select the systems for which you want to delete data
4.
Choose the Delete Measurements function
• The measurement data for all selected systems is deleted from the central LAW system.
• On the Inbox tab page, the Delete Measurements function means only that the measurement data that has not yet been transferred into LAW is deleted from the in-box.
47

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
To combine users, do the following activities:
1.
Call LAW (transaction SLAW or LICENSE_ADMIN)
2.
In the Control LAW box, choose the second option, Combine
Users.
The system displays the Combine the Users dialog box.
3.
In the dialog box, choose whether you want to combine your users automatically or manually
We recommend that you first automatically combine the users and then, if necessary, manually correct or amend the combined users.
A manual correction is required if, for example, different spellings of the user name are used in different systems (for example, in system A “Benita Hartmann” and, in system B, “Hartmann,
Benita” or “HARTMANN”).
Choose the grouping criterion/criteria best suited to your situation – for example, the criterion user name if your users have the same user name in all systems. (If you are using central user administration, this is automatically the case.)
Automatic combination offers the following criteria:
• User name
• Last name and first name
• Account number
• E-mail address
• Telephone number
The system displays the message Users successfully combined in the status line.
For manual combination , the system displays the Combine Users Manually screen. Depending on whether you have imported new users from new systems into LAW, choose one of the following options when filling out this selection screen:
• If you have not imported any users from new systems into
LAW, you do not need to make any entries on this screen, but you should choose Execute to combine all imported systems automatically.
• If you have just imported the data for a new system into LAW and had earlier already automatically combined the data for the previous systems, you must now automatically combine the users of the new system by the same criteria. To do this, set the Automatically Assign by indicator on the Combine Users
Manually screen, and choose the criteria for the combination.
Then choose Execute .
In both cases, the screen Combine Users Manually appears. You should now take the following actions:
• Select all user master records of an employee
• Choose Group Selected
After you have combined all user master records for an employee, you can specify the contractual user type to be licensed
(see section “18 Consolidating Contractual User Types”).
48

17.1.1
Displaying the User Combination
To check the combination of the users, choose the Display User
List option in the Control LAW box. The user list provides the following information about the user and the systems in which it is created.
User details , which include the following information:
• User name, first name, and last name
• Contractual user type and special version surcharge
• Account number, the date the user was created, and the date of last logon
Additional user details, as of software component SAP_BASIS
700, include the following information:
• E-mail address, telephone number, and cost center
• Category (production and test), classification (manual, reference, and so on), and country surcharge
• Personalization objects
System details , which include the following information:
• Installation number, system name, client, and hardware key
Additional system details, as of software component SAP_BASIS
700, include the following information:
• System number
The LAW data is 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
17.1.2
Correcting the User Combination
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
2.
Combination
• If you previously combined the users automatically, the results of this combination are automatically displayed.
Revise the old result, if desired
Result
You have combined the users and can now consolidate the contractual user types.
Figure 22: Criteria for Combining Users
49

17.2
Enhanced Grouping of Users
As of software component SAP_BASIS 640, you can extend the existing criteria for combining users to then group the users as follows:
• By more than one criterion, such as name and telephone number
• By personalization objects
• By a combination of both
You can create your individual user groupings with personalization objects, which are available as of SAP R/3 4.6C.
When grouping, you will find that grouping fields are displayed only if personalization data exists in LAW. The number of these fields corresponds to the number of different personalization objects but is restricted to a maximum of five.
Note the following information:
• If you are using personalization objects, these must be maintained in all systems and for all users. Otherwise, grouping is incomplete.
• Enhanced grouping, especially with personalization objects, is significantly more expensive and time-consuming. You should therefore use the enhanced extended grouping only if you absolutely require it – for example, if you are consolidating using more than one criterion.
More information about using personalization objects is available in SAP Library under SAP NetWeaver Library
→
SAP NetWeaver by Key Capability
→
Solution Life Cycle Management
→
SAP Licenses
LAW Procedures
→
→
License Administration Workbench
→
Combining Users
→
Overview of the
Extended Grouping of User .
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
→
Life Cycle Management
→
Workbench
→
SAP NetWeaver by Key Capability
SAP Licenses
→
Overview of the LAW Procedures
→
→
Solution
License Administration
Grouping Systems .
50

With this procedure, you consolidate the contractual user types of the individual users. LAW takes into account that certain contractual user types are already included in others. This means that licenses are required only for the user’s overall contractual user type.
Example 1
User A
Operational (01)
EHR User (07)
Test (91)
Overall Contractual User Type
Operational (01)
Example 2
User B mySAP Professional (52) mySAP Employee (54)
Substitute (04)
Overall Contractual User Type mySAP Professional (52)
Special Notes
If a clear contractual user type cannot be determined for a user, the contractual user types are indicated as a user combination .
For example, the user is classified as a developer user and a professional user, or special combinations exist.
Example 3
User C mySAP Professional (52)
Test (91)
User Combination mySAP Professional (52)
Special Module User (71) Special Module User (71)
Procedure
To consolidate contractual user types, take the following actions:
1.
Call LAW (transaction SLAW or LICENSE_ADMIN)
2.
To start the consolidation, choose the Start Consolidation option in the Control LAW box. A dialog box appears in which you can choose to schedule consolidation as a background job.
Note the following information:
• If you consolidate only a few groups instead of all LAW data, the status light is yellow.
• If you receive the message No consolidation groups were determined .
Perform the function anyway?
, you can either specify one or more groups to be consolidated on the Groups tab page or choose
3.
Continue to consolidate all data in LAW.
• If you receive the message Country surcharges and special versions must be the same in all systems , correct the user classification and restart the consolidation.
Choose Display Results .
The Result of the User Consolidation screen appears. Depending on the SAP release of the LAW system, you can display the following list of consolidated results:
• Consolidated users: compressed list that shows only one line for each group
4.
This list is the default list in the delivered system. With software component SAP_BASIS 700, you can display the following lists of consolidated results by choosing Change
Display :
• Consolidated users: errors: list of the consolidation errors in which only the consolidation groups that could not be consolidated are displayed. You can select this list as the default list by choosing Utilities
→
Settings option Only Display Errors in Consolidation List .
and then the
• Grouped users: complete list with all users
By double-clicking a line, display a detailed list of the relevant group. This detailed list contains all attributes for the individual users of this group (explanation of the user’s grouping).
51

18.1 Consolidation Result
As of software component SAP_BASIS 700, the Result tab page shows the result of the last (current) user consolidation.
You can enter and save different types of information; for example, you can maintain existing licenses and save them in the archive.
The table is divided into upper and lower parts (indicated by different colors). The upper part shows only individual user types, while the lower part contains all consolidated user-type combinations. If there are no user-type combinations, the lower part is not displayed.
Figure 23: Result List of User Consolidation
Result
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
Column
Indicator
Combination of User
Types
Individually
In Combination
Comment
Shows whether the row is for stand-alone users or users created by an upgrade
Specifies a user type or a combination of user types that was determined during the consolidation and for which the numbers that follow the item apply
Shows the number of users with this type or this type combination
Shows the additional number of users of this type that have resulted from type combinations (only in the upper part of the table).
Total
Licensed (only without group consolidation)
Balance (only without group consolidation)
The totals in this column are calculated purely arithmetically on the basis of the combinations found and do not take into account special features of contracts in any way.
You can change the values at any time in change mode and therefore adjust them to the applicable contractual conditions.
Shows the total of the user types individually measured and found in combination (total of the two previous columns)
Lets you display or enter the number of existing licenses for each user type
Shows the difference between existing and measured licenses
Table 15: Columns of the Results Table
52

The following functions are available in the list of results:
Display types as ID/text
This function switches the display in the Combinations column between the description of the user types and special versions
(text) and the identifier (ID).
Maintain existing licenses
This function switches the table to change mode, so that the fields of the column in the upper part of the columns Licensed and In Combination become ready for input. You can enter the number of existing licenses for the individual types.
Save licenses in archive
The function has two tasks. First, it saves the maintained licenses so that you do not always have to reenter them. It also saves the result of the current consolidation, so that you can display it again at a later time. At every save, you need to enter a description.
This description makes it easier for you to select the results you want later from all of the saved results. The date and time are automatically added at every save.
Fetch licenses from archive
As soon as consolidation results have been saved and therefore exist in the archive, you can use this function to retrieve and display a particular result. You select the desired result in a dialog box. Although you lose the current display when you do this, you can save the display first.
To display the current consolidation result again, call the Result tab page again. When you do so, the maintained licenses from the most recently saved archive are automatically transferred to the display. If user types that did not previously exist have been added as a result of new measurement data, you can perform the maintenance of existing licenses for these types.
Delete licenses from the archive
This function deletes saved consolidation results from the archive using a selection dialog box.
Figure 24: Result of User Consolidation
18.2 Correcting User Classification
If you find errors in the results display during the classification of a user, you can correct these only in the source system.
Procedure
To correct the user classification, take the following actions:
1.
Correct the user classification in the source system, and
2.
restart system measurement (transaction USMM)
Collect the measurement data in the component system
3.
4.
Delete the relevant system in LAW
Import the corrected measurement data, and repeat the following procedures:
• Combine users
• Consolidate the contractual user types
Result
You can transfer the corrected results to SAP.
53

After you have consolidated the data, transfer the results to SAP.
LAW currently supports two procedures: the Service Data Control Center (SDCC) and the new Service Data Control Center
(called SDCCN; see SAP Note 861753). The data is transferred anonymously, as displayed in the LAW log (fax log) .
You can also create comments about the measurement data using the Comments push button. These are also transferred to
SAP.
Procedures
The following procedures are required:
1.
Call LAW (transaction SLAW or LICENSE_ADMIN)
2.
To transfer the files with the measurement data to SAP, choose the option Transfer Directly to SAP in the Control LAW box
3.
4.
If you have created comments, you can now use a dialog box to determine whether you want to send these to SAP unchanged
To display the list of all transfers, choose the Display Transfers option in the Control LAW box. The transfer log displays the status of all transfer requests.
To display the data as it is transferred to SAP, call the LAW log
(fax log). To do this, choose Measurement Data
→
LAW Log
→
Create LAW Log .
Send Results
→
Prerequisites
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

Usertype Description
Up-to-date and detailed descriptions and definitions of the contractual user types of all SAP price lists are available on
→
→
→
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
→
→
→
55

LAW Interface
As of software component SAP_BASIS 620, Support Package 42, the LAW data is available to you for internal, automated processing through the LAW interface – for example, for internal cost allocation for the licenses.
The LAW interface is a collection of function modules with which you can access the information stored in LAW with read access.
Seven business objects and the corresponding BAPI programming interfaces have been defined for this read-only access. The BAPI programming interfaces provide either one or several tables, or an XML document.
You receive a detailed selection of LAW data in the LAW system that you can use for internal processing. You can obtain the data in one of the following ways:
• As of software component SAP_BASIS 610, by using the report
RSLAW_TEST_BAPI
• As of software component SAP_BASIS 640 in LAW, by choosing
Goto
→
Information Systems
Information about the LAW interface, business objects, function modules, and BAPI interfaces are available in
SAP Library under SAP NetWeaver Library
→
Key Capability
→
SAP NetWeaver by
Solution Life Cycle Management
→
SAP Licenses
→
License Administration Workbench
→
LAW Interface .
More information is available in the documentation for function modules in the BAPI Explorer (transaction BAPI) on the Hierarchy tab page under Basis
→
Security .
LAW Business Objects
Object
LAWUser
LAWSystem
LAWEngine
LAWUserType
LAWConsUser
LAWConsEngine
LAWConsUserType
Comment
Users in LAW
The object contains all relevant data for an SAP® software user in
LAW.
Systems in LAW
The object contains all relevant data for SAP software in LAW.
Engines in LAW
The object contains all relevant data for an engine in LAW.
User types in LAW
The object contains all relevant data for an SAP software user type (license type) in LAW.
Consolidated users in LAW
The object contains all relevant data for a consolidated SAP software user in LAW.
Consolidated engines in LAW
The object contains all relevant data for a consolidated engine in LAW.
Consolidated user types in LAW
The object contains all relevant data for a consolidated SAP software user type in LAW. User types with their special versions and surcharges are consolidated to one common user type, where possible.
Function Module
BAPI_LAWUSER_GETLIST
BAPI_LAWSYSTEM_GETLIST
BAPI_LAWENGINE_GETLIST
BAPI_LAWUTYPE_GETLIST
BAPI_LAWCONSUSR_GETLIST
BAPI_LAWCONSENG_GETLIST
BAPI_LAWCONSUTY_GETLIST
56

50 053 697 (06/10)