sap system measurement

7/29/2019 SAP System Measurement

http://slidepdf.com/reader/full/sap-system-measurement 1/40

System MeasurementGuide

VERSION 6.10

SAP License Audit



© Copyright 2002 SAP AG. 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 AG. The information contained herein may be changed

without prior notice.

Some software products marketed by SAP AG and its distri-

butors contain proprietary software components of other soft-

ware vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word ®, PowerPoint® and

SQL Server® are registered trademarks of Microsoft

Corporation.

IBM®

, DB2®

, OS/2®

, DB2/6000®

, Parallel Sysplex®

, MVS/ESA®

,RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are regis-

tered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM

are registered trademarks of Informix Software Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks

of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®,

MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other

Citrix product names referenced herein are trademarks of

Citrix Systems, Inc.

HTML, DHTML, XML, XHTML 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.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP BusinessWorkflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,

Management Cockpit, mySAP, mySAP.com, and other SAP

products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of

SAP AG in Germany and in several other countries all over

the world. MarketSet and Enterprise Buyer are jointly owned

trademarks of SAP Markets and Commerce One. All other

product and service names mentioned are the trademarks of

their respective owners.

2



1. SAP License Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2 Named users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.3 Software engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2. Scope of validity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 Availability of user types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.2 Availability of software engine measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3. Installations, systems and system types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1 SAP Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.2 SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4. Process description of system measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5. System Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.1 System data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.2 Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.3 Price lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.4 User types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.5 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6. Classifying users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

6.1 Classifying users via User Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

6.2 Classifying users via Reference Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

6.3 Classifying users via User Maintenance: Mass Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

6.4 Classifying users via the user list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6.5 Mass changes to user types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6.6 Price list migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

7. Valuation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7.1 Contracts with special database licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7.2 Special notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

8. Definition and availability of user types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

8.1 User types in the mySAP.com Solution Suite Price List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

8.2 User types in the mySAP.com Individual Solutions Price List . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

8.3 User types in the SAP Software Component Price List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

8.4 Special user types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

8.5 Technical users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3

CONTENTS



9. Performing the system measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

9.1 Creating the measurement log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

9.2 SSCR-registered users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

9.3 Results of engine measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

9.4 Measurement statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

10. Transferring the measurement results to SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

11. Support with system measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

12. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

12.1 Functions available in the measurement program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

12.2 Functions available for user classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

12.3 User types in mySAP.com Solution Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

12.4 User types in mySAP.com Individual Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

12.5 User types in the SAP Software Component Price List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4



5

SAP® software contains a measurement program, which helps

all systems produce the information necessary for determining

usage for the installation. This guide describes how to go about

License Audit and how to use the measurement program.

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 not later than four weeks after SAP's

request. The measurement shall be carried out using only the

unaltered tools provided by SAP. The result of the measure-

ment 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. Theresults are evaluated according to the terms of your contract.

You classify your users, clients, and systems according to this

guide. If you have any questions, contact your sales executive.

1.1 USAGE

Usage of SAP software is based on the licensing of named users

and of software products such as engines. Licensing is based on

the utilization of the software independent of the technical

interface chosen to access functions and data.

SAP gives express notice that the accessing of a system by morethan one person using one and the same named user shall con-

stitute a breach and that this also applies in respect of access by

technical systems and their users. If SAP observes such a breach

in connection with system measurement, SAP shall by way of

damages charge and invoice the appropriate amount for the

continuation of such use in accordance with the then current

List of Prices and Conditions.

1.2 NAMED USERS

A named user is an employee of a customer, of its affiliates, or

of third-party companies authorized to access, directly or indi-

rectly, the licensed software, independent of the technical

interface chosen.

Named users include technical systems that exchange informa-

tion with the SAP system, and their users. Both direct and indi-

rect access and usage is counted. Direct access means that the

user communicates with a system upstream from the SAP soft-

ware that bundles, temporarily stores, or summarizes commu-

nication activities and transmits them to the SAP software

installation.

1.3 SOFTWARE ENGINES

A software engine is an optional piece of software that has to belicensed separately. Software engines are priced based on key

business metrics such as orders, contracts, contract accounts,

patients treated, and so on.

Software engines are to be licensed in addition to named users.

This means that users accessing a software engine must be

licensed as named users too.

1. SAP® LICENSE AUDIT



6

This system measurement guide is valid for all SAP contracts.

It is based on the functions of the measurement program that

were revised and extended for SAP Web Application Server (AS)

6.10.

Some of the functions are also available for earlier releases

through Support Packages. Some of the changes compared to

the measurement program for release 4.6C are:

See the appendix for an overview of the functions available inthe measurement program for each release version.

2.1 AVAILABILITY OF USER TYPES

Classification of user types depends on the price list on which

your contract is based. With SAP Web AS 6.10, user types in the

following price lists are available:• SAP Software Component Products Price List

(SW Component Price List)• mySAP.com® Solution Suite Price List

(mySAP.com® Solution Suite)• mySAP.com® Individual Solutions Price List

(mySAP.com® Individual Solutions)

2.2 AVAILABILITY OF SOFTWARE ENGINE

MEASUREMENT

A software engine is an optional piece of software that has to be

licensed separately. Authorization for named users is also

required.

The measurement program in SAP Web AS 6.10 contains

counting modules for automatically calculating software

engine usage (SAP Generic, SAP 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. For information on currently available meas-

urement programs for software engines, go to SAP Service

Marketplace, at http://service.sap.com/licenseauditing.

2. SCOPE OF VALIDITY

senigneerawtf osf ognitnuoC• 01USf onoitcennoC•

CCDSaivref snartataD• tsilresuehtotsnoisnetxE•



7

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 usage and the price list they are based on,

prior to each system measurement. This classification reflects

the terms of your contract.

If you convert from a software component contract to a

mySAP.com contract, users that are already classif ied must be

reclassified according to the newly licensed user types.

3.1 SAP INSTALLATION

An SAP installation is a combination of SAP systems. These sys-

tems have to be installed on homogeneous platforms (database,

operating system, and hardware). An SAP installation consists

of a maximum of eight SAP systems, usually one production

system plus test systems, training systems, and developmentsystems.

A maximum of one production system can run under an

installation. If you have other production systems, ask for a

new installation from your SAP contracts department.

For each software product, you must register a separate installa-

tion in writing with SAP. SAP will then give you a unique

installation number.

3.2 SAP SYSTEM

An SAP system comprises components (application server,

message server) that have direct or indirect access to one data-

base instance. A database instance is defined as an instance in

which each database table appears only once.

When an installation is measured, all systems (including devel-

opment and test systems) must be measured with the exception

only of IDES and backup systems.

Measurement results are evaluated in different ways, depending

on system type. You can make changes in your systemlandscape quickly and easily in SAP Service Marketplace at

http://service.sap.com/licensekey (Note 94998).

3. INSTALLATIONS, SYSTEMS AND SYSTEM TYPES

INDIVIDUALCONTRACT

SINGLEINSTALLATION

INSTALLATION 1 INSTALLATION 2 INSTALLATION N

PRODUCTIONSYSTEM

TESTSYSTEM

DEVELOPMENTSYSTEM

SAP CONTRACT(VALUE OR VOLUME

CONTRACT)

SEVERALINSTALLATIONS

PRODUCTIONSYSTEM

TESTSYSTEM

TRAININGSYSTEM

PRODUCTIONSYSTEM

TESTSYSTEM

Fig.: Installations and Systems



8

SAP initiates system measurement through the measurement

request. The Customer Competence Center or central SAP

contact person receive:• The system measurement letter• The current installation and system overview• The system measurement documentation

The Customer Competence Center checks the installation

overview and forwards the measurement request to the contact

persons for the individual installations. It then collects the indi-

vidual system measurement results and sends them all, by the

set deadline, to the SAP contact person for system

measurement.

Contact your sales executive if you have any questions on con-

tracts or products licensed.

4. PROCESS DESCRIPTION OF SYSTEM MEASUREMENT

• Installation overview• System landscape• Documentation

• Technical Support for themeasurement

• Inbox for online/LAW transfer

• Evaluation

→ Check the request andinstallation/system over-

view

→ Distribute request anddocumentation to therelevant installation sites

✓ Start measurementprogram

✓ Select price list

✓ Classify user types

✓ Measure all systems

✓ Create Fax log

✓ Return measurementresults to CCC

Measurement Request Installations/System overview

Support Support

CUSTOMERCOMPETENCE

CENTER

INSTALLATION/SYSTEM

→ Check the measurementresults

→ Consolidate overall results with LAW

→ Transfer consolidatedresult to SAP, LAS

License Auditing Services LAS

ACCOUNT MANAGER

• Contract

Transfer MeasurementResults toSAP, LAS

Transfer measure-ment results toCCC

Fig.: License Audit Process



9

Open the measurement program through transaction USMM

or the path:

SAP Menu→ Tools→ Administration→ Administration→ System

Measurement

For SAP releases lower than SAP Basis 4.6C:

Tools→ Administration→ Administration→ System Measurement

You can perform the measurement only if you have

S_USER_GRP authorization.

Fig.: System measurement program

Choose at least one active price list, depending on your SAP

contract. Before starting the system measurement, you should

check and maintain the settings described below.

5.1 SYSTEM DATA

The system data contains information on the system's unique

ID. It must be checked at the start of the measurement, and

changed if necessary.

Fig.: System data

5.2 CLIENTS

All clients in a system except client 000 (SAP Client) and client

066 (EarlyWatch Client) are measured. Other clients can be

excluded from measurement in the following cases:• A test client is created in a production system.• A client that has been copied for test purposes.

Fig.: Clients

5. SYSTEM MEASUREMENT

1. Choose price list

2. Check and maintain settings

3. Classifying users

4. Perform system measurement

5. Creating measurement log

From Release 4.0B, a system isautomatically labeled productive if atleast one client is set to productive.

This setting can then only be chan-ged via the client status.

The clients000 (SAP Reference) and066 (EarlyWatch)are automatically excluded when themeasurement log is created.



10

Procedure for excluding clients

For Release SAP Basis 4.6C and above:• Check the selected live clients.• Remove the Included flag for the clients that are to be

excluded.

For Release SAP Basis 4.6B and lower:• Select the clients to be excluded.

For Release SAP Basis 3.I and lower:• In the option Exclude clients, enter the clients to be

excluded.

5.3 PRICE LISTS

The activated price list controls the user types for classification

that are offered in F4 help. Activate the price list valid for yourcontract.

For SAP Web AS 6.10, the following price lists are available:• SAP Software Component Price List• mySAP.com Solution Suite Price List• mySAP.com Individual Solutions Price List

Fig.: Price lists

From SAP Basis 4.6C, the following price lists are offered in the

standard software:• SW Components Price List• mySAP.com Price List

For releases lower than SAP Basis 4.6B, the user types from the

various SAP price lists, especially those from the mySAP.com

Price List, are available as Support Packages (Note 428479).

For information on user types, see section 8 Definition and

availability of user types.

While system measurement is taking place, corresponding

plausibility checks are run.

5.4 USER TYPES

The tab page User types contains in a drop-down list of all user

types assigned to the activated price list.

For SAP Web AS 6.10

The active indicator controls the display of selected users in

User classification and Input help for User Maintenance.• Activate the relevant user types

Fig.: User types

SAP Web AS 6.10:

Activate the user types relevant for theuser classification



11

Special modules and IS users

As of SAP Basis 4.0B, you can describe exactly the contractual

special module and IS user types. The default setting for the

users Special module type 1-5 and IS user type 81-85 is Active.

Fig.: Customizing Special Module and the IS-Users

• Overwrite the relevant entry with the name of your contrac-

tual user type, and save the data.• Deactivate the special module and IS user types if you do not

have any contractually defined special users.

5.5 ADDRESSES

Enter the address and fax number of the recipient of the

measurement.

For individual contracts and master agreements, send the

measurement results straight to your contact person for system

measurement at SAP.

For SAP contracts (R/3 value, volume, mySAP.com contracts)

give the address and fax number of your Customer

Competence Center as the measurement recipient.

Your Customer Competence Center gathers and checks the

measurement results before forwarding them to SAP.

Fig.: Addresses

• Mark the user type• Overwrite with the

contractual description• Activate the user type



12

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 usage and the price list they are based on,

prior to each system measurement. SAP Web AS 6.10 provides

you with numerous options for user classification.

For user classification, we recommend proceeding according to

the user classification strategy in the diagram below.

Fig.: Strategy for user classification

For the first measurement, if no users are classified yet, use theUser Maintenance: Mass Changes (SU10). All new users should then

be classified as soon as they are created.

6.1 CLASSIFYING USERS VIA USER MAINTENANCE

If you classify users via User Maintenance, you get a useful

overview of the individual user profiles. You can assign user

types when you create the user.

Open User Maintenance through transaction SU01 or by choosing

SAP Menu→ Administration→ System administration→ User

Maintenance→ Users

Enter an existing user name or alias, and choose Change, orenter a new user name and choose→ Create.

The screen Maintain user appears.

For SAP Web AS 6.10

1. Choose Maintain user →Measurement data or select tab

→LicenseData.

2. Maintain the contractual user type, and assign the user a

special version if necessary.

3. Save your entries and continue with user classification.

Fig.: License data

6. CLASSIFYING USERS

Create User (without classification)

Classify user as soonas created

Classify users as soonas they are created

Classify users as soonas they are created

F O R S A P W e b A S 6 . 1

0

S A P B a s i s 4 . 6

D a n d l o w e r

Create HUBER(Development) Create WILD

Classify WILD

Create WILDClassify WILD

Create HUBER

Classify HUBER

Create STORK

Classify STORK

Create WEBER

Classify WEBER

Create MEIER

Classify MEIER

Create MEIER(Sales)

Create WEBER(Development)

User Maintenance:Mass Changes (SU10)

Perform systemmeasurement

Performsystem

measurement

Mass Change Development HUBERWEBER

...

Mass Change SalesMEIER

...

Create STORK Classify STORK

License AuditJan 2002 Feb 2002 May 2002

With SAP Web AS 6.10,License data has its own tabpage.

The measurement program counts users without classifi-

cation as either Operational users or as mySAP.com

Category II/Professional users, depending on which price

list is activated. In the standard system, a user is not

assigned to a special version.



13

As of SAP Web AS 6.10, the contractual user type and the

special version are also copied when a user is copied.• In the function Copy user, select License data.

For Release SAP Basis 4.6C

Open User Maintenance via transaction SU01 or by choosing

SAP Menu→ Tools→ Administration→ User Maintenance→ Users

For SAP Basis Releases below 4.6C

Open User Maintenance via transaction SU01 or by choosing

Tools→ Administration→ User Maintenance→ Users

• Enter an existing user name or alias and choose Change, or

enter a new user name and choose Create. The screen

Maintain User appears.

1. Choose Maintain User →Measurement data2. Choose the user types that correspond to your contract,

and a special version if necessary.

3. Save your entries and continue with user classification.

For releases lower than SAP Web AS 6.10, the contractual user

type and the special version are not copied when a user is

copied. The user is initialized with the type Operational user or

mySAP.com Category II/Professional user, and must subse-

quently be maintained manually.

6.2 CLASSIFYING USERS VIA REFERENCE USERS

For user maintenance, SAP Web AS 6.10 provides you with the

user type Reference for user classification in the standard system.

A reference user is a general, non person-specif ic user. You can-

not log on with a reference user – it serves only for additional

assignment of authorizations and license data (Note 313585).

It is easy to assign many authorizations using reference users.

All users derived from the reference user inherit its user classi-

fication if • No additional roles and profiles are created, and • The dependent dialog users are not manually classified.

Reference users are used, for example, to give Internet users

identical authorizations and to create users with identical roles

and authorizations. In the Roles tab page, you can specify a ref-erence user for additional permissions for dialog users. In gen-

eral, the application controls the assignment of reference users.

User classification via reference users is available through

Support Packages for SAP Basis 4.6D and 4.6C.



14

Creating a Reference User

To create and maintain a reference user, proceed as follows:

1. Activate the User Maintenance function and create a new user.

The screen Maintain user appears.

2. In the Logon data tab page, choose the user type Reference.

3. Define further authorizations if required.

4. In the License data tab page, assign the Contractual user type to the

reference user, and save your entries.

Assigning reference user for dialog users

In the Roles tab page, you can create a reference user for

additional permissions for dialog users.

To assign a dialog user a reference user, proceed as follows:

1. Activate the User Maintenance function.

2. Enter an existing user name or alias and choose Change, orenter a new user name and choose Create. The screen

Maintain user appears.

3. In the Roles tab page, enter Reference user for additional roles

and save.

Displaying reference users in the measurement program

For an overview of all users that get their classification from a

reference user, choose the Extended list in the measurement pro-

gram.

To display the dialog users that have inherited their

classification from a reference user, proceed as follows:

1. Activate the System measurement function (transaction

USMM) and choose→ User classification. The screen User classifi-

cation appears.

2. In the toolbar, choose→ Extended list

3. Enter the name of the reference user and execute the

function.The User classification screen appears, with the list

of users

Fig.: User Classification: Extended List

Explanation of the extended list

Fig.: Assign Reference user

nmuloC noitanalpxE

epytresustluseR rof tnavelerd nad etnuocsitahtepytresU

.tnemerusaem

)launam(epytresU osla;yllaunamd eif issalcsawresUred nusemocyllacitamotua .e p yt r esust luseR

resuecneref eR .resuecneref erd engissaf oemaN ehtotsd nopserrocepytresustluseR ehT

f iresuecneref erehtf oepytresud egnissaneebtonevahsresud evired eht•

selif orpd naselorlanoitid d aynaad engissaneebsahresuecneref ereht•

epytresU resuecneref erehtf oepytresulautcartnoC

snoisrevlaicepS )ned d ih( ehtroF ,e p yt r esust luseR eht )launam( e p yt r esU ehtd na e p yt r esU erasnoisrevlaicepseht,.ylgnid roccad etaluclacd nad etneserper



15

6.3 CLASSIFYING USERS VIA USER MAINTENANCE:

MASS CHANGES

With SAP Web AS 6.10, you can classify your users via User

Maintenance: Mass Change. User groups are determined using

different criteria:• Address data (such as department and cost center)• Authorization data (such as user profiles and roles)

For initial user classification, use User Maintenance:

Mass Change to avoid overwriting correct user types by mistake,

subsequent maintenance of user types should be done via

User Maintenance or the user list.

Open User Maintenance: Mass Change through transaction SU10 or

by choosing:

SAP Menu→ Administration→ System administration→ User Maintenance→ User Maintenance: Mass Change

To select a user group according to, for example, department,

choose Address data

• In the screen Select user according to address, enter the data

required, and execute. A list of assigned users is displayed.• Select the assigned users, and choose→ Copy. The screen

User Maintenance: Mass changes initial screen appears, with the

selected users.

Fig.: User Mass Changes

• On the User Maintenance screen, choose Change.• In the License data tab page, choose the User type acc. to contract for

the user group, and save changes. A confirmation prompt

about the number of users to be changed appears.• If you want to create a log of the mass change, choose mass

change with log.

The user classification of the user group is changed.

Fig.: Mass Change Initial Screen



16

6.4 CLASSIFYING USERS VIA THE USER LIST

The measurement program generates a list of all users created.

With this user list, you can classify your users clearly and effec-

tively.

SAP Web AS 6.10 provides two lists:• The Simple list for manual classification of dialog and system

users.• The Extended list for checking classifications.

User classification with the Simple list

You can classify dialog and system users manually with the

simple list (standard setting). Here, you can• Classify users that have not yet been classified • Reclassify users that have already been classified.

To classify users that have not yet been classif ied, proceed asfollows:

1. Open the measurement program (transaction USMM) and,

in the System measurement screen, choose User classification.

The User classification dialog box appears.

2. Copy the settings Displaying unclassified users.

3. Restrict the validity period to Users currently valid, and exe-

cute the function. The User classification screen appears,

with the user list. Here, you can either

– Classify the users individually, or

– Select and classify several at a time.

Assigning user types according to contract

As of SAP Web AS 6.10, input help (F4) for the user type accord-

ing to contract contains only the user types on the User types tab

page that are activated (5.4 User types)

1. Call up the data relevant for measurement by double-click-

ing on the selected user(s).

2. In the screen Measurement-relevant data for user , choose the user

types from the relevant price list.

For an overview of user types according to contract, choose

input help (F4).

3. Save your entries.

Fig.: Contractual User Type

Special versions

If special versions are used within your installation, classify the

users with the corresponding special version. In the standard

system, users are not assigned special versions:

When classification is completed, the user list shows all users of

your SAP system along with their assigned user types.

SSCR (SAP SoftwareChange Registration), indica-tes all users for which thedeveloper key is used (9.2SSCR-registered users)

From SAP Basis 4.6C, the validity periodof the user is included in the user list

etyB-elbuoD• keerG•

cibarA• egrahcrus%05•

cilliryC• egrahcrus%001•

Fig.: User Classification



17

User classification with the Extended list

With SAP Web AS 6.10, you can check your user classification

using the Extended list. This enables you to see which classifica-

tion was included in the measurement:• Manual user classification,• Users classified through reference users• Unclassified users

For detailed information on the Extended list , choose i

Program documentation. For more information, see Note

313585.

The Extended list for user classif ication is available for the

following Basis releases through Support Packages:• SAP Basis 4.6C with SP11• SAP Basis 4.6D with SP03

6.5 MASS CHANGES TO USER TYPES

As of release SAP Basis 4.6C, the measurement program

supports the mass change and migration of user types. For

security reasons, the mass change and migration of user types

is possible only in the clients that you are logged on to.

Mass changes to user types

As of SAP Basis Release 4.6C, the measurement program can

be used to make mass changes to user types from a price list.

With this function you can• Assign a user type to all users that have not yet been

classified.• Change the classification of all type A users to type B.

From the initial screen of the measurement program, choose

Environment →Mass change to display the dialog box Mass change of

user types. Select the radio button alongside the option you

require.

Classifying non-maintained users

1. Enter the new user type in the input field (input help F4).

2. Execute the mass change.

3. Check the confirmation prompt and confirm the mass

change.

4. The adjustment of the user is confirmed in the status bar.

Fig.: System Measurement Mass Change of User Types

Changing old classifications

1. Enter the Old user type and the New user type in the input fields

(input help F4).

2. Execute the mass change.

3. Check the confirmation prompt and confirm the mass

change.

4. The adjustment of the user is confirmed in the status bar.



18

6.6 PRICE LIST MIGRATION

When the active price list is changed, the user types have to be

adjusted. A tool is available in the measurement program for

migrating the user types in the SAP Software Component Price

List to user types in the mySAP.com Price List. This function

allows you to change the old user types to the new user types in

the current price list. It is possible to migrate user types only in

the clients that you are logged on to.

From the initial screen of the measurement program, choose

Environment →Migration price list to display the dialog box

System measurement: Migration Price List.

1. Enter the new user type in the input field (input help F4).

2. Execute the migration. You receive confirmation that the

user type of your user has changed.

3. Check the new classification of your user.

Fig.: Migration of Price Lists



19

The following are important for valuation of measurement

results:

1. All chargeable* users and engines in the live client in the

production system

2. The number of ABAP Workbench users in all systems. The

relevant number here is therefore the total of ABAP

Workbench users in all systems.

System-independent users

If you do not use the License Administration Workbench for

user consolidation, you should note the following when classi-

fying users that operate in several 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 users – see below).•

In all other systems, it can then be classified as a multi-client/multi-system user.

ABAP Workbench users in particular are created in several

systems. Classify these users accordingly.

7.1 CONTRACTS WITH SPECIAL DATABASE LICENSES

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 older releases, ignore the prompt and deactivate the E-ASL

indicator.

7.2 SPECIAL NOTES

• Depending on the price list activated, the measurement

program counts non-classified users as either

– Operational users or

– mySAP.com Category II/Professional users.

• ABAP Workbench users for test and development systems

(mySAP.com Price List):

1. From Release 4.6C, first use mass change to classify all your

users in test and development systems as Test users

(see 6.5 Mass changes to user types).

2. Then classify your ABAP Workbench users as mySAP.com

Category II/Professional users and start the system

measurement.

For releases lower than 4.6C, get in touch with your contactperson for system measurement at SAP.

• The measurement program also counts locked users.

• As of SAP Release 4.0B, the measurement program no longer

counts users whose validity date has passed. In the case of

earlier releases, the measurement program counts users

whose validity date has passed for another 90 days after the

expiry date.

• For releases lower than SAP Web AS 6.10:When a user is copied, the user type and special version are

not copied.

The user is initialized as an Operational user or a

mySAP.com Category II/Professional user, and must then be main-

tained manually.

7. VALUATION RULES

* Examples of non chargeable users are substitute, test, and multi-client users.



20

Classify your users in accordance both with the terms of your

contract and with their authorizations and their meaning

according to the price list that they are based on.

The user types in the different SAP price lists, especially those

in the mySAP.com Price List, are available as Support Packages

for releases lower than 4.6B (Note 428479).

For measurement of user types that are not yet included in

your measurement program, use the following special module

user types by arrangement with your contact person at SAP for

system measurement:• Name or overwrite the existing special module user types

with the correct description.• Use the special module user types to clearly classify your

users.

For measurement of mySAP.com users with releases lower than

SAP Basis 4.0B, see Note 359271 or get in touch with your SAP

contact person for system measurement.

8.1 USER TYPES IN THE mySAP.com SOLUTION SUITE

PRICE LIST

For detailed descriptions and definitions of the user types in the

mySAP.com Solution Suite Price List, special user types, and

examples, see the appendix to this document, 12.3. User types

in the mySAP.com Solution Suite. Non-classified users arecounted as mySAP.com Category II/Professional users.

User types in the mySAP.com Solution Suite Price List

Special module user types

The user types named below are only valid if agreed in the

terms of the contract with SAP, or by agreement with your

contact person at SAP for system measurement.

If these user types are used although not covered by the

contract, the valuation rules for user type mySAP.com Category

II/Professional apply.• Special module type 1 to 9

8.2 USER TYPES IN THE mySAP.com INDIVIDUAL

SOLUTIONS PRICE LIST


mySAP.com Individual Solutions Price List, and examples, see

the appendix to this document, 12.4 User types in mySAP.com

Individual Solutions. User types in the mySAP.com IndividualSolutions Price List.

User types in the mySAP.com Individual Solutions Price

List

8. DEFINITION AND AVAILABILITY OF USER TYPES

IyrogetaCmoc.PASym / IIIyrogetaCmoc.PASymlanoissef orPd etimiL

yrogetaCmoc.PASymlanoissef orP/ II

/ VIyrogetaCmoc.PASymeeyolpmE

lanoissef orPMR CPASym lanoissef orPR HPASym

d etimiLMR CPASymlanoissef orP

lanoissef orPd etimiLR HPASym

lanoissef orPMCSPASym eeyolpmER HPASym

d etimiLMCSPASymlanoissef orP

lanoissef orPslaicnaniFPASym

lanoissef orP.corP-EPASym d etimiLslaicnaniFPASymlanoissef orP

d etimiL.corP-EPASymlanoissef orP

lanoissef orPIBPASym

eeyolpmE.corP-EPASym lanoissef orPd etimiLIBPASym

lanoissef orPMLPPASym eeyolpmEecalpkroWPASym

d etimiLMLPPASym

lanoissef orP

lanoissef orPMFCPASym

rennalPytid iuqiLMFCPASym



21

Classify all valid users according to the licensed mySAP.com

solution. For the measurement of mySAP.com Individual

Solutions, there is no standard user type that the system can

use for non-classified users.

8.3 USER TYPES IN THE SAP SOFTWARE COMPONENT

PRICE LIST


SAP Software Component Price List, SAP New Dimension

Products, special user types, and examples, see the appendix to

this document (12.5 User types in the SAP Software Compo-

nent Price List).

Users without any classification are counted as Operational users.

User types of SAP R/3 General Function blocks

Users of New Dimension components

Examples:• SAP APO: G.ATP user type• SAP CFM TA (Transaction Manager) user type.

Special module and IS-user types

The following user types are permitted only if appropriate con-

tractual agreements with SAP are in place, or by arrangement

with your contact person for system measurement at SAP.

If these user types are used although not covered by the

contract, the valuation rules for user type Operational user

apply.• Special module type 1 to 9• IS-USER TYPE 81 to 85

resulanoitarepO *snoitamrif noC/ snoitisiuqeR

resunoitamrof nI *ylno-sisaB

resuhcnebkroWtnempoleveD *R HesirpretnE

* Restricted user authorization, see appendix (12.5 User types in the SAP R/3

General Function blocks).



22

8.4 SPECIAL USER TYPES

DIpyT epytresU noitinif eD

40 etutitsbuS ot,elpmaxerof (emitf od oirepd etimilarof ylnometsysPASehtnid etaercebnacresuetutitsbusA

asa,resurehtonaf osnoitcnuf ehtesunacresusiht,emitsihtgniruD.)eugaelloctnesbanarof revoc.emitsihtgnirud metsysPASehtniylevitcakrowtonyamresu”tnesba“ehT.etutitsbus

.tneilcemasehtnid etaercebtsumsresud etutitsbusd naetutitsbuS

ehtotgnid roccad etaulaveneebyd aerlasahresurehtoehtecnisegrahcf oeerf siresuetutitsbusehT.tnemngissa

11 metsys-/ tneilc-itluM elbaegrahcsametsysrotneilcenonid eif issalcyd aerlaeratahtsresurof siresumetsys-/ tneilc-itlumehTaotd engissaebtsummetsysrotneilcanid etaercsitahtresumetsys-/ tneilc-itlumyrevE.sresu

.metsystahtf osnoitcnuf ehttsomtaesuyamd na,metsysrehtonaroemasehtniresuelbaegrahc

f oeerf siresumetsys-/ tneilc-itlumeht,tnemngissastiotgnid roccad etaulavesiresuelbaegrahcehtecniS.egrahc

19 tseT :secnatsnigniwollof ehtniylnosmetsysnoitcud orpnid etaercebnacsresutseT

elbaliavasimetsystsetoN • ehtnievitcud orpteytoneratahtselud omf onoitareperpevitcud orprof ylevisulcxesiegasU•

.PAShtiwd eergaebtsumsresutsetf onoitacif issalcehT

29

tcatnoclanretxE tI.)tenretnIehtmorf yllausu(yllacitamotuad etaerceratahtsresurof sitcatnoclanretxEepytresuehTtahtsresurof ylnosi

eesnecilPASehtotgnolebtonoD•.niahceulavehtf otraptonerA•

.eesnecilPASehtotstnacilpparof osremotsuceraohwsresud ne:selpmaxE

:eraepytresusihtrof airetircehTDN Atnemngissaresuecneref ersahresuehT•

DN Aselif orpON sahresuehT•)585313etoN (selorON sahresuehT•



23

8.5 TECHNICAL USERS

As of SAP Web AS 6.10, the measurement program counts only

the dialog users created in the system. These dialog users are

chargeable, and their features include:• Individual system access (personalized)• Interaction capability• Check for expired/initial passwords• Option to change their own passwords• Check for multiple dialog logons

The following technical user types are counted by releases

lower than SAP Web AS 6.10, and must be manually classified as

in the table below:

Users include technical systems that exchange information

with the system, and their users. A license is required for any

direct access or use.

Direct access means that the user is communicating with a sys-

tem upstream from the SAP software that bundles, temporarily

stores, or summarizes communication activities and transfers

them to the SAP software installation.

In the case of indirect usage of SAP software, you should

provide us separately with the number of external named users.

sepytresulacinhceT serutaeF esopruP/selpmaxE noitacif issalC

resugolaiD resulacinhcet,lanretni-PAS *PAS•CIDD•

CIPCPAS•MDASMT•N IGOLSTI•

resutseT

noitacinummoC ton,seitivitcametsys-ssorCnoitcaretnif oelbapac

tupnihctaB•CFR lanretxE•

CIPC•

resutseT

metsyS -metsysd natned neped -metsySf oelbapacton,seitivitcalanretni

noitcaretni

CFR lanretnI•gnissecorpd nuorkcaB•

resutseT

ecivreS d esu)suomynona(sseccametsySton,sresutneref f id ybyltnio j

noitcaretnif oelbapac

)resuretnI(sseccametsyssumynonA• resutseT

ecneref eR ;noitazirohtuagnid netxerof looTelbissoptonnogol

snoitazirohtualacitned ihtiwsresutenretnI• resutseT

For more information, see Note 327917.

Technical system access

SAP gives express notice that the accessing of a system by

more than one person using one and the same named

user shall constitute a breach, and that this also applies

to access by technical systems and their users.



24

The measurement program determines and analyzes the num-

ber 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 meas-

urement results are entered in a table and the previous results

are overwritten.

From SAP Basis Release 4.6B, the system measurement of users

is performed in the foreground. The SAP engines are measured

in the background.

With SAP Web AS 6.10, the checks in the measurement program

have been enhanced and extended. These checks run in the

background and determine the following information, which is

presented in the measurement log:• Number of deleted users•

Number of users whose validity has expired • Number of users that have logged on after their validity

expired • Highest number of a user's multiple logons to the system.

Once you have classified the users, start the system

measurement. From the initial screen System measurement , choose

System measurement .

Fig.: Start system measurement

9.1 CREATING THE MEASUREMENT LOG

In the initial screen System measurement, choose Create log.

The Measurement log FAX appears, containing the data relevant

for measurement.

The report helps prepare the most recently determined meas-

urement data in fax format, and contains the following data:• Header with date and address details• System-specific data• Information and results relevant to the measurement• Results of background checks• Measurement results for excluded clients

9.2 SSCR-REGISTERED USERS

From release 4.6C, the number and distribution of user types

for which the developer key (SAP Software Change Registra-

tion, SSCR key) is used is displayed in the measurement results.

Developer keys (SSCR) are required by ABAP Workbench users.

ABAP Workbench users are usually classified as Development

Workbench users or mySAP.com Category II/Professional.

Users for which developer keys are used are displayed in the list

of users.

9. PERFORMING THE SYSTEM MEASUREMENT

Send the measurement logs, depending on your contract

type to your Customer Competence Center or your con-

tact person for system measurement at SAP.

1. Start system measurement

2. Create measurement log (report)

3. Check measurement statistics



25

9.3 RESULTS OF ENGINE MEASUREMENT

Measurement modules for the different engines are shipped

either• As integral parts of the SAP software, or• In the form of add-ons (SAP industry solutions)

These engines used in the system are• automatically recognized,• counted in the background, and • displayed in the measurement log by the measurement

program.

In addition, each named user that accesses an engine must be

classified according to its activity.

For up-to-date information on the availability of engine meas-urement, see the System Measurement Engines directory at:

http://service.sap.com/licenseauditing.

9.4 MEASUREMENT STATISTICS

In the measurement statistics, the results found (measured

users, engines) are listed per client.

This client-specific overview of the measurement results helps

you to check them. Do not send the measurement results to

SAP until asked to do so.



26

The online transfer of measurement results for individual con-

tracts and SAP contracts with no more than one installation is

possible.

The measurement results for SAP contracts with more than

one installation must be checked and consolidated by your

Customer Competence Center.

For SAP contracts with more than one installation, you can use

the consolidation tool License Administration Workbench

(LAW) for this. For information on LAW, see the SAP Service

Marketplace: http://service.sap.com/licenseauditing.

SDCC transfer procedure

With SAP Web AS 6.10 the measurement results are transferred

online using the Service Data Control Center (SDCC)procedure. You must have at least version 2.1 of the SDCC in

your system.

Fig.: Transfer to SAP

For previous SAP Releases up to and including SAP Basis 4.0B,

the SDCC procedure is available through Support Packages. For

further technical information, see Note 314672.

To transfer measurement data to SAP online, proceed as

follows:

Open the measurement program (transaction USMM) and,

from the System measurement screen, choose Send to SAP

1. When the confirmation prompt appears, confirm with Yes.

In the status bar, the system displays the message that the

transfer has been successfully scheduled.

2. To check the status of the transfer, choose All transfers

The system displays the status of all measurement transfers.

Fig.: Status data transfer

TRANSFER PROCEDURE WITHOUT SDCC

As of SAP Basis Release 4.0B, you can transfer measurement

results online. For SAP releases without SDCC, data transfer

must be started manually after the data has been released in

the measurement program (transaction SCUI: Transfer data).

10. TRANSFERRING THE MEASUREMENT RESULTS TO SAP

Transfer of the measurement data to SAP

Detailed list of all transfers

Measurement number and status oftransfer

The measurement number of the transfer

clearly identifies the transferred measure-ment results.



27

You can find current notes on the measurement program in

SAP Service Marketplace under component XX-SER-LAS. If

you have any questions concerning the measurement program,

create a message in SAP Service Marketplace 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 depart-

ment of your SAP subsidiary.

You can get up-to-date information on system measurement

(license auditing), the online version of this documentation,

and a selection of Best Practices for System Measurement

under: http://service.sap.com/licenseauditing

11. SUPPORT WITH SYSTEM MEASUREMENT



28

12.1 FUNCTIONS AVAILABLE IN THE MEASUREMENT PROGRAM

This overview covers the functions in the standard measurement program.

Some of the functions are also available for earlier releases through Support Packages and add-ons (Note 428479).

If you have any questions, get in touch with your contact person at SAP for system measurement.

12. APPENDIX

esaeleRsisaBPAS tsilecirP sepytresuelbaliavA

I1.3otpU tnenopmoCerawtf oSPAS )noitamrof nI,lanoitarepO,elpmaxerof (sepytresud rad natS5-1sresuelud omlaicepS

B0.4morF tnenopmoCerawtf oSPAS 58-18sresuSI,5-1sresuelud omlaicepS,sepytresud rad natS

C6.4morF tnenopmoCerawtf oSPAS 58-18sresuSI,9-1sresuelud omlaicepS,sepytresud rad natSsepytresunoisnemiDweN

etiuSnoituloSmoc.PASym VI-IseirogetaCmoc.PASym

01.6morF tnenopmoCerawtf oSPAS ,58-18sresuSI,9-1sresuelud omlaicepS,sepytresud rad natSsepytresunoisnemiDweN

etiuSnoituloSmoc.PASym IyrogetaClanoissef orP/ IIyrogetaC

lanretxE/ IIIyrogetaCeeyolpmE/ VIyrogetaC

snoituloSlaud ivid nImoc.PASym snoitulosd naseirogetacresurepsresumoc.PASymlanoissef orPd etimiL.corP-EPASym,lanoissef orP.corP-EPASym,elpmaxerof (

)eeyolpmE.corP-EPASym



29

12.2 FUNCTIONS AVAILABLE FOR USER CLASSIFICATION

noitcasnart/emaN noitadnemmocer-noitacif issalC sadeppihSmorf dradnats

rof egakcaPtroppuSsAesaeler

troppuSegakcaP

10US/ ecnanetniamresU rof rotnemerusaemtneuqesbuS

:segnahcssamtuohtiwsesaelerd etaercerasresunehW

F0.3sisaBPAS - -

tnemerusaemf osresuf otsiLMMSU/ margorp

snoitacif issalc'sresullaf oweivrevO B0.4sisaBPAS - -

ecneref eR aivecnanetniamresU10US/ sresu

snoitazirohtualacitned ihtiwsresU 01.6sisaBPAS D6.4C6.4 11C64BK PAS30D64BK PAS

ssaM:ecnanetniamresU01US/ egnahc

rof tnemerusaemtsrif nOspuorgresuf onoitacif issalc

01.6sisaBPAS - -

resuf oegnahcssaMMMSU/ sepyt resuf oegnahcssaMMMSU/ sepyt

epytmorf noitacif issalcresuegnahCBepytotA

C6.4sisaBPAS )R H(I1.3B6.4B5.4B0.4I1.3 27I13HK PAS95B04HK PA83B54HK PA62B64BK PA

27I13EK PA

MMSU/ noitargimtsilecirP sahtsilecirpretf asepytresutsu jd Ad egnahcneeb

C6.4sisaBPAS - -



30

12.3 USER TYPES IN THE mySAP.com SOLUTION SUITE

Prerequisite: The mySAP.com Solution Suite price list has been activated (5.3 Price lists).

The user types in the mySAP.com Price List are available through Support Packages for SAP Releases earlier then 4.6B (Note 428479).

For measurement of mySAP.com users for SAP releases without mySAP.com user types in the measurement program, see Note

359271 or get in touch with your contact person at SAP for system measurement.

Named users in the mySAP.com Solution Suite

epyTDI

epytresU noitinif eD

15 *IyrogetaCmoc.PASym mrof repnacohwytilibisnopsertnemeganamenilhtiwresUd emaN asiepytresusihTehT.erawtf osehtybd etroppusselorgnikam-noisiced d nagninnalpehtf oenotsaelta

.esnecilIIyrogetaCared nud etnargsthgirehtsed ulcniesnecilresuIyrogetaC

25 / IIyrogetaCmoc.PASymlanoissef orP

smrof repohwresUd emaN asiresulanoissef orProIIyrogetaCmoc.PASymAlanoissef orProIIyrogetaCmoc.PASymehT.erawtf osehtybd etroppusselorlanoitarepo

d etimiL/ IIIyrogetaCmoc.PASymared nud etnargsthgirehtsed ulcniesnecilresu.esnecillanoissef orP

35 / IIIyrogetaCmoc.PASymlanoissef orPd etimiL

smrof repohwresUd emaN asiresulanoissef orPd etimiL/ IIIyrogetaCmoc.PASymA.erawtf osehtybd etroppusselorlanoitarepod etcirtser

d etimiL/ IIIyrogetaCmoc.PASymsad eif issalcebnacseitrapd rihtf oseeyolpmeyllaicepsEeratahtselorrosnoitcnuf ynamrof reptonod yehtd ed ivorp,sresulanoissef orP

.)elpmaxerof ,stnatlusnoc(seeyolpmes'remotsucehtybd emrof repyllamron

sthgirehtsed ulcniesnecilresulanoissef orPd etimiL/ IIIyrogetaCmoc.PASymehT.esnecileeyolpmE/ VIyrogetaCmoc.PASymared nud etnarg

45 / VIyrogetaCmoc.PASymeeyolpmE

eeyolpmesmrof repohwresUd emaN asiresueeyolpmE/ IVyrogetaCmoc.PASymAmoc.PASymhcaE.erawtf osehtybd etroppusselor)cif iceps-bo jnon(d etalerecivres-f les

nwos'laud ivid nihcusrof yleloserawtf osehtsseccayamresueeyolpmE/ IVyrogetaC.slaud ivid nirehtof of lahebnororof tond nasesoprup

* if licensed



31

Special module user types (mySAP.com Solution Suite)

The following user types are permitted only if appropriate contractual agreements with SAP are in place, or by arrangement with

your contact person at SAP for system measurement.

Examples of user classification (mySAP.com Solution Suite)

Users with developer keys (SSCR keys) who exclusively perform repairs and emergency functions can be classified as Test users.

DIepyT epytresU noitinif eD

97-17 9ot1epytelud omlaicepS tonsnoitcnuf PASlaicepsesuohwslaud ivid nierasresuelud omlaicepSlautcartnoclaud ivid ninamohwrof d nametsysd rad natsehtnid eniatnoc

.ylraelcmehtemand na,d esusresuelud omlaicepsehtetirwrevO.sd lohelur

moc.PASymehtmorf snoitulossesuohwresuA...etiuSnoituloS

epytresugniwollof ehtotdengissaebotsi...

PASlanretxegnid ulcni,sresuhcnebkroWPABAsksattnempoleved htiwstnatlusnoc

lanoissef orP/ IIyrogetaCmoc.PASym

,egakcapetelpmocmoc.PASymehtniselorlanoitarepOpihsnoitaleR remotsuCPASym:elpmaxerof

slaicnaniFPASym,tnemeganaM


d nayllanoisaccoerawtf osmoc.PASymesuohwsresUepocsd etcirtserhtiw

lanoissef orPd etimiL/ IIIyrogetaCmoc.PASym

)stnatlusnocton(seinapmocytrap-d rihtf oseeyolpmE lanoissef orPd etimiL/ IIIyrogetaCmoc.PASym

·f o)ecivreS-f leSeeyolpmE(esulanosrepylevisulcxEtnemerucorP-EPASym•

secruoseR namuHPASym•ecalpkroWPASym•

eeyolpmE/ VIyrogetaCmoc.PASym

)syekR CSS(syekrepoleved htiwsresU .sresuhcnebkroWPABArof d esuylnoyllausuera)R CSS(syekrepoleveD

.lanoissef orP/ IIyrogetaCmoc.PASymsad eif issalcerasresuesehT

gnizimotsuchtiwstnatlusnoclanretnirolanretxEsksat


.smetsysrostneilclarevesnikrowotevahohwsresU asapuorgtsehgihehtniecnod eif issalcsiresueht,metsys/ stneilcniamehtnI.resuelbaegrahc

-/ tneilC-itluMasad eif issalcebnehtnacresueht,smetsysd nastneilcrehtonI.resumetsyS



32

12.4 USER TYPES IN mySAP.com INDIVIDUAL SOLUTIONS

Prerequisite: The mySAP.com Individual Solutions Price List has been activated (5.3 Price lists).

The user types in the mySAP.com Price List are available through Support Packages for SAP Releases lower than 4.6B (Note 428479).

For measurement of mySAP.com users for SAP releases without mySAP.com user types in the measurement program, see Note

359271 or get in touch with your contact person for system measurement at SAP.

Classify all valid users. Note that measurement of the mySAP.com Individual Solutions Price List includes no standard user types for

non-classified users.

Named Users in mySAP.com Individual Solutions (1)


AA lanoissef orPMR CPASym resUd emaN asiresulanoissef orPtnemeganaMnoitaleR remotsuCPASymA

.erawtf osehtybd etroppusselorMR Clanoitareposmrof repohw

BA lanoissef orPd etimiLMR CPASym d emaN asiresulanoissef orPd etimiLtnemeganaMnoitaleR remotsuCPASymAybd etroppusepocsd etcirtserahtiwselorMR Clanoitareposmrof repohwresU

.erawtf oseht

CA lanoissef orPMCSPASym ohwresUd emaN asiresulanoissef orPtnemeganaMniahCylppuSPASymA.erawtf osehtybd etroppusselorMCSlanoitareposmrof rep

DA lanoissef orPd etimiLMCSPASym resUd emaN asiresulanoissef orPd etimiLtnemeganaMniahCylppuSPASymAehtybd etroppusepocsd etcirtserahtiwselorMCSlanoitareposmrof repohw

.erawtf os

EA lanoissef orP.corP-EPASym smrof repohwresUd emaN asiresulanoissef orPtnemerucorP-EPASymA.erawtf osehtybd etroppusselortnemerucorp-elanoitarepo

FA lanoissef orPd etimiL.corP-EPASym ohwresUd emaN asiresulanoissef orPd etimiLtnemerucorP-EPASymAybd etroppusepocsd etcirtserahtiwselortnemerucorp-elanoitareposmrof rep

.erawtf oseht

GA eeyolpmE.corP-EPASym smrof repohwresUd emaN asiresueeyolpmEtnemerucorP-EPASymAybd etroppustnemerucorp-eni)cif iceps-ytivitcanon(selorecivres-f leseeyolpme

.erawtf osehtrof tond nasesoprupnwos'laud ivid nihcusrof erawtf osehtsseccayamresusihT

.slaud ivid nirehtof of lahebnoro

HA lanoissef orPMLPPASym ohwresUd emaN asiresulanoissef orPtnemeganaMelcycef iLtcud orPPASymA

.erawtf osehtybd etroppusselorMLPlanoitareposmrof rep



33

Named Users in mySAP.com Individual Solutions (2)


IA lanoissef orPd etimiLMLPPASym resUd emaN asiresulanoissef orPd etimiLtnemeganaMelcycef iLtcud orPPASymA ehtybd etroppusepocsd etcirtserahtiwselorMLPlanoitareposmrof repohw.erawtf os

K A lanoissef orPR HPASym smrof repohwresUd emaN asiresulanoissef orPsecruoseR namuHPASymA.erawtf osehtybd etroppusselorR Hlanoitarepo

LA lanoissef orPd etimiLR HPASym ohwresUd emaN asiresulanoissef orPd etimiLsecruoseR namuHPASymA.erawtf osehtybd etroppusepocsd etcirtserahtiwselorR Hlanoitareposmrof rep

MA eeyolpmER HPASym smrof repohwresUd emaN asiresueeyolpmEsecruoseR namuHPASymAsecruoseR namuHPASymni)cif iceps-ytivitcanon(selorecivres-f leseeyolpme

s'laud iv-id nihcusrof erawtf osehtsseccayamresusihT.erawtf osehtybd etroppus.slaud ivid nirehtof of lahebnororof tond nasesoprupnwo

N A lanoissef orPslaicnaniFPASym lanoitareposmrof repohwresUd emaN asiresulanoissef orPslaicnaniFPASymA.erawtf osehtybd etroppusselorslaicnaniFPASym

OA d etimiLslaicnaniFPASymlanoissef orP

smrof repohwresUd emaN asiresulanoissef orPd etimiLslaicnaniFPASymAehtybd etroppusepocsd etcirtserahtiwselorsecruoseR namuHlanoitarepo

.erawtf os

PA lanoissef orPIBPASym smrof repohwresUd emaN asiresulanoissef orPecnegilletnIssenisuBPASymA.erawtf osehtybd etroppusselorecnegilletnIssenisuBlanoitarepo

R A lanoissef orPd etimiLIBPASym ohwresUd emaN asiresulanoissef orPd etimiLecnegilletnIssenisuBPASymAybd etroppusepocsd etcirtserahtiwselorecnegilletnIssenisuBlanoitareposmrof rep

.erawtf oseht

SA eeyolpmEecalpkroWPASym -f leseeyolpmesmrof repohwresUd emaN asiresueeyolpmEecalpkroWPASymAehtybd etroppusecalpkroWPASymni)cif iceps-ytivitcanon(selorecivres

d nasesoprupnwos'laud ivid nihcusrof erawtf osehtsseccayamresusihT.erawtf os.slaud ivid nirehtof of lahebnororof ton

TA lanoissef orPMFCPASym ohwresUd emaN asiresulanoissef orPtnemeganaMecnaniFetaroproCPASymAehtybd etroppusselortnemeganaMecnaniFetaroproClanoitareposmrof rep

.erawtf os

UA rennalPytid iuqiLMFCPASym resulanoissef orPd etimiLrennalPytid iuqiLtnemeganaMecnaniFetaroproCPASymAhtiwselorrennalPytid iuqiLMFClanoitareposmrof repohwresUd emaN asi

.erawtf osehtybd etroppusepocsd etcirtser



34

Special module user types (mySAP.com Individual Solutions)



Examples of user classification (mySAP.com Individual Solutions)


DIepyT epytresU

97-17 9ot1epytelud omlaicepS

moc.PASymehtmorf snoitulossesuohwresuA...etiuSnoituloS

epytresugniwollof ehtotdengissaebotsi...

hcnebkroWPABA noitulosmoc.PASymehtf oeman+lanoissef orP

pihsnoitaleR remotsuCPASymniselorlanoitarepOtnemeganaM

lanoissef orPMR CPASym

remotsuCPASymniselorlanoitarepod etcirtseR tnemeganaMpihsnoitaleR

lanoissef orPd etimiLMR CPASym

secruoseR namuHmoc.PASymniselorlanoitarepO lanoissef orPR HPASym

namuHmoc.PASymniselorlanoitarepod etcirtseR secruoseR

lanoissef orPd etimiLR HPASym

namuHmoc.PASymnoitulosehtsseccaohwsresUsesoprupnworiehtrof ylevisulcxesecruoseR

eeyolpmER HPASym

htiwstnatlusnocPASlanretnirolanretxE

sksattnempoleved

noitulosmoc.PASymehtf oeman+lanoissef orP

)syekR CSS(syekrepoleved htiwsresU esehT.sresuhcnebkroWPABArof d esuylnoyllausuera)R CSS(syekrepoleveD.lanoissef orP/ IIyrogetaCmoc.PASymsad eif issalcerasresu

gnizimotsuchtiwstnatlusnoclanretnirolanretxEsksat

noitulosmoc.PASymehtf oeman+lanoissef orP

.smetsysrostneilclarevesnikrowotevahohwsresU asapuorgtsehgihehtniecnod eif issalcsiresueht,metsys/ stneilcniamehtnIasad eif issalcebnehtnacresueht,smetsysd nastneilcrehtonI.resuelbaegrahc

.resumetsyS-/ tneilC-itluM



35

12.5 USER TYPES IN THE SAP SOFTWARE COMPONENT PRICE LIST

Prerequisite: The SAP Software Component Price List has been activated (5.3 Price lists).

User types in SAP R/3 General Function blocks


10 lanoitarepO oterawtf osd esnecilehtsseccaotd ezirohtualaud ivid ninasiresu)PO(lanoitarepOnAekamoslanacresusihT.snoitcasnarterawtf osPASeteled d na,etad pu,d aer,etaerc,etucexe

.esabatad ehtotsegnahc

20 noitamrof nI yleloserawtf osd esnecilehtsseccaotd ezirohtualaud ivid ninasiresu)N I(noitamrof nInAatad gnitsixeotsegnahcynaekamtonnacresusihT.snoitcasnartPASylno-d aermrof repot

.atad wenynad d aro

30 snoitamrif noC/ snoitisiuqeR d esnecilehtsseccaotd ezirohtualaud ivid ninasiresu)R / A(snoitamrif noC/ snoitisiuqeR A·f oesoprupehtrof yleloserawtf os

)MM(noitisiuqeresahcrupgnittimbuS•)PP(snoitamrif nocred rogniretnE•

50 ylnO-sisaB ehtrof yleloserawtf osd esnecilehtsseccaotd ezirohtualaud ivid ninasiresuylnO-sisaBA ·:snoitcasnartgniwollof ehtgnitucexef oesoprupgnivihcralacitpognid ulcni,tnemeganamtnemucoD•

erawtf osehtf onoitartsinimd ad nagnirotinoM•d esnecilehtnid eniatnocsnoitcasnartllA•

.snoitcnuf secruoseR namuHylelossnoitcasnartresuR H/ ecif f OesirpretnEllA•

sesoprupnwos´laud ivid niehtrof SId esnecilehtnid eniatnocsnoitcasnartllA•

tinuselasehtsagnolsa,snoitcnuf eraChtlaeH.sresuH-SItonsi

snoitacilpparof tnemnorivneemitnurehtesuotd ezirohtuasiresuylnO-sisaBehT.esuoh-nid epoleved

60 hcnebkroWtnempoleveD PABAehtesuotd ezirohtualaud ivid ninasiresu)WD(hcnebkroWtnempoleveDA .snoitinif ed wolf krowetaercotd eriuqersinoitazirohtuaresuhcnebkroWPABA.hcnebkroW.noitallatsnirepd eif issalcebtsumresuWDenotsaeltA

70 R HesirpretnE d esnecilehtsseccaotd ezirohtualaud ivid ninasiresu)R HE(R H/ ecif f OesirpretnEnA·:snoitcasnartgniwollof ehtgnitucexef oesoprupehtrof yleloserawtf os

,ecnanetniamsd rocereeyolpmE•,yrtneecnad nettad naemiteeyolpmE•

troperesnepxed nagninnalplevarteeyolpmE•,gnillif

yrotcerid eeyolpmE•,noitartsigergniniarteeyolpmE•

,stnemsitrevd abo jlanretnI•,snoitcnuf rad nelaC•

,snoitisiuqeresahcrupcif iceps-eeyolpmE•

gnilif tnemucod gnid ulcniliam-E•

hcusrof ylelossnoitcasnartevobaehtetucexeyamresuR H/ ecif f OesirpretnEhcaEs´laud ivid ni ,sesoprupnwo rehtof of lahebnororof snoitcasnartetucexetonyamd na

slaud ivid ni



36

User types in SAP New Dimension Products (1)


02 PTA.G:OPAPAS otd ezirohtualaud ivid ninasiresu)PTA.G-OPA(esimorP-ot-elbaliavAlabolGOPAnA.PTAlabolGssecca

12 SD/ PP:OPAPAS :sseccaotd ezirohtualaud ivid ninasiresu)SD/ PP-OPA(rennalPnoitcud orPOPAnA,tipkcoCniahCylppuS•

,gnilud ehcSd eliateDd nagninnalPnoitcud orP•PTAlabolG•

22 PCS:OPAPAS :sseccaotd ezirohtualaud ivid ninasiresu)PCS-OPA(rennalPniahCylppuSOPAnA,gninnalPd nameD•

,tnemyolpeDd nagninnalPkrowteN ylppuS•,tipkcoCniahCylppuS•

.gnilud ehcS-eR red rokcaB/ d liub-ot-raelC•

22 PCS:OPAPAS sseccaotd ezirohtualaud ivid ninasiresu)PCS-OPA(rennalPniahCylppuSOPAnA,gninnalPd nameD•

,tnemyolpeDd nagninnalPkrowteN ylppuS•,tipkcoCniahCylppuS•

gnilud ehcS-eR red rokcaB/ d liub-ot-raelC•

32 LLOC:OPAPAS :sseccaotd ezirohtualaud ivid ninasiresu)LLOC-OPA(rennalPevitaroballoCOPAnA,gninnalPd nameDevitaroballoC•

,gninnalPylppuSevitaroballoC•,tnemerucorPevitaroballoC•

gnired neT/ gninnalPnoitatropsnarTevitaroballoC•

42 PT:OPAPAS sseccaotd ezirohtualaud ivid ninasiresu)PT-OPA(rennalPnoitatropsnarTOPAnAnoitatropsnarTevitaroballoCgnid ulcnignilud ehcSelciheVd natipkcoCniahCylppuS

gnired neT/ gninnalP

52 resahcruP:.corPB2BPAS f oeeyolpme(laud ivid ninasiresu)PBB(esahcruPtnemerucorPssenisuB-ot-ssenisuBAremotsucehtybd ezirohtua)seitrapd rihtniahcylppuselbaif itned iro,setailif f a,eesnecil

laicremmocrof tiesud natcud orpssenisuB-ot-ssenisuBPASd esnecilehtsseccaot .)POekil(sesoprup

resuesahcruP)PBE(noitid Elanoissef orPreyuBesirpretnEoslaeeS

62 renoitisiuqeR :.corPB2BPAS f oeeyolpme(laud ivid ninasiresunoitisiuqeR tnemerucorPssenisuB-ot-ssenisuBAremotsucehtybd ezirohtua)seitrapd rihtniahcylppuselbaif itned iro,setailif f a,eesnecil

hcusrof ylelostiesud natcud orpssenisuB-ot-ssenisuBPASd esnecilehtsseccaot.)R HEekil(sesoprupnwos'laud ivid ni

resunoitisiuqeR )PBE(noitid Elanoissef orPreyuBesirpretnEoslaeeS

03 WBPAS ,eesnecilf oeeyolpme(laud ivid ninasiresu)WB(esuoheraWnoitamrof nIssenisuBAelbaif itned iro,setailif f a



37


52 resahcruP:.corPB2BPAS f oeeyolpme(laud ivid ninasiresu)PBB(esahcruPtnemerucorPssenisuB-ot-ssenisuBAremotsucehtybd ezirohtua)seitrapd rihtniahcylppuselbaif itned iro,setailif f a,eesnecil

laicremmocrof tiesud natcud orpssenisuB-ot-ssenisuBPASd esnecilehtsseccaot.)POekil(sesoprup

resuesahcruP)PBE(noitid Elanoissef orPreyuBesirpretnEoslaeeS

62 renoitisiuqeR :.corPB2BPAS f oeeyolpme(laud ivid ninasiresunoitisiuqeR tnemerucorPssenisuB-ot-ssenisuBAremotsucehtybd ezirohtua)seitrapd rihtniahcylppuselbaif itned iro,setailif f a,eesnecil

hcusrof ylelostiesud natcud orpssenisuB-ot-ssenisuBPASd esnecilehtsseccaot.)R HEekil(sesoprupnwos'laud ivid ni

resunoitisiuqeR )PBE(noitid Elanoissef orPreyuBesirpretnEoslaeeS

03 WBPAS ,eesnecilf oeeyolpme(laud ivid ninasiresu)WB(esuoheraWnoitamrof nIssenisuBAsseccaotremotsucehtybd ezirohtua)seitrapd rihtniahcylppuselbaif itned iro,setailif f a

.tcud orpesuoheraWnoitamrof nIssenisuBPASd esnecileht

43 IIyrogetaCMR CPAS resUd emaN asiresuIIyrogetaC)MR C(tnemeganaMpihsnoitaleR remotsuCPASnA.erawtf osehtybd etroppusselorMR Clanoitareposetucexeohw

IIIyrogetaCMR Cared nud etnargsthgirehtsed ulcniesnecilIIyrogetaCMR CehT.esnecil

53 IIIyrogetaCMR CPAS lanoitarepo,d etcirtsersetucexeohwresUd emaN asiresuIIIyrogetaCMR CPASnAerawtf osehtybd etroppusselorMR C

d eif issalcebnac)ytrapd rihtd ezirohtua(ynapmocytrap-d rihtaf oseeyolpmeyllaicepsE.sresuIIIyrogetaCMR CPASsa

83 MESPAS ,eesnecilf oeeyolpme(laud ivid ninasiresu)MES(tnemeganaMesirpretnEcigetartSAsseccaotremotsucehtybd ezirohtua)seitrapd rihtniahcylppuselbaif itned iro,setailif f a

tcud orpMESPASd esnecileht

04 )PO.lcni(MT:MFCPAS si)MT:MFCPAS(reganaMnoitcasnarTtnemeganaMecnaniFetaroproCPASf oresuA.MFCnisnoitcasnarTlaicnaniFetucexeotd ezirohtua

14 )MTMFC.lcni(R M:MFCPAS tekraMesuotd ezirohtuasi)R M:MFCPAS(rezylanAksiR tekraMMFCPASf oresuA.sisylanAksiR

24 )MTMFC.lcni(R C:MFCPAS tid erCesuotd ezirohtuasi)R C:MFCPAS(rezylanAksiR tid erCMFCPASf oresuA.ksiR

44 )MTMFC.lcni(AP:MFCPAS oilof troPesuotd ezirohtuasi)AP:MFCPAS(rezylanAoilof troPMFCPASf oresuA.rezylanA

54 )PO.lcni(PL:MFCPAS esuotd ezirohtuasi)PO.lcni(PL:MFCPAS(rennalPytid iuqiLMFCPASf oresuA.rennalPytid iuqiL

84 MLPPAS f oeeyolpme(laud ivid ninasiresu)MLPPAS(tnemeganaMelcycef iLtcud orPPASnAremotsucehtybd ezirohtua)seitrapd rihtniahcylppuselbaif itned iro,setailif f a,eesnecil

.tcud orptnemeganaMelcycef iLtcud orPPASd esnecilehtsseccaot

User types in SAP New Dimension Products (2)



38

Special user and IS-user types (SAP Software Component Price List)




97-17 9ot1epytelud omlaicepS ehtnid eniatnoctonsnoitcnuf PASlaicepsesuohwslaud ivid nierasresuelud omlaicepS.sd lohelurlautcartnoclaud ivid ninamohwrof d nametsysd rad nats

.)sepytresU4.5(ylraelcmehtemand na,d esusresuelud omlaicepsehtetirwrevO

58-18 58ot18EPYTR ESUSI laud ivid ninamohwrof d nastnenopmoccif iceps-yrtsud niesuohwsresuerasresuSI.sd lohelurlautcartnoc

.)sepytresU4.5(ylraelcmehtemand na,d esusresuSIehtetirwrevO



39

Examples of user classification (SAP Software Component Price List)




SAP AGNeurottstraße 1669190 WalldorfGermany T +49/1805/3434 24F +49/1805/3434 20

www.sap.com

sap system measurement

Documents