SAM4U: Software Asset Manager

SAP has released the SAM4U tool to manager your software licenses for SAP. This tool is especially useful in large SAP landscapes.

The SAM4U tool helps you to optimize the licenses. It does not replace the formal license submission tool SLAW2.

Benefits of SAM4U

  1. Improved SAP license cost control
    SAM4U continuously analyzes actual SAP usage and compares it with purchased license entitlements. It helps identify: over-licensed users, under-licensed users, users automatically classified into expensive license categories.
    Opportunities to reduce license costs through reclassification.
  2. Proactive audit readiness
    Instead of waiting for an SAP audit: License consumption is continuously monitored. Compliance gaps become visible early. Entitlements and usage are maintained in one place. This reduces surprises during SAP license audits.
  3. Consolidated View Across Multiple SAP Systems

Usage data from ECC, S/4HANA and other ABAP systems is consolidated. License consumption is tracked centrally. Landscape-wide reporting becomes possible.

  1. User classification optimization

SAM4U analyzes: actual usage, authorizations, assigned roles.

It highlights users who may be consuming more expensive license types than necessary and suggests optimization opportunities.

  1. Authorization analysis

The tool provides: current vs. target user classifications, detailed authorization object analysis, role and profile impact assessments.

This is useful for Basis, Security, and GRC teams performing role redesign or license optimization exercises.

  1. Transaction usage analysis

SAM4U tracks: active user behavior, transaction code usage, historical activity.

Transaction analysis can be leveraged for authorization role redesign.

  1. SAP HANA consumption insights

SAM4U includes: historical HANA memory consumption, database growth trends, HANA enterprise edition analytics. This gives visibility into HANA utilization over time.

  1. Simulation capability

According to the SAM4U user guide, the tool can simulate: changes to roles
changes to authorizations, impact on required license quantities.

This allows “what-if” analysis before implementing role changes.

  1. No data leaves the customer network

License data remains inside the customer’s environment. SAP does not receive operational usage data through SAM4U. This addresses common security and confidentiality concerns.

  1. No additional license cost. SAM4U tool is free of charge.

Time to implement the tool is not for free.

Set up of SAM4U

The setup of the SAM4U tool is clearly described on the SAP help file for SAM4U. SAP also offers help with a service to implement the tool on their SAM4U site.

Central installation

The first part is the installation of the central tool on the central system.

Choose a system with a high S4HANA version. Do not use SAP solution manager.

First make sure on the central system the bug fix notes listed in 3646933 – SAM4U Solution | Fiori Application | V2 are applied. And apply the notes for 3292019 – SAM4U Data Extractor.

Once done goto the installation and upgrade part of the SAP help file for SAM4U:

F0llow all the steps:

Hints: the first 2 steps are confusing. It tells you to start transaction /n/SAM4U/START, but that only works when step 2 is done, where you create the actual start variant.

After completing all the steps when starting transaction /n/SAM4U/START the FIORI page should launch:

Connecting the SAP systems

Per SAP system you want to connect, first apply the notes for 3292019 – SAM4U Data Extractor. The per connected system follow the steps in the SAP help file for SAM4U for the Data Extractor Guide:

Choose between RFC based or file based data extraction. Important in both cases to give the user ID’s the appropriate authorizations as described in both Required Authorizations section as in the Data Gathering section. Make sure the data extractor job runs regularly.

The data of the extractors is stored in table /SAM4U/BEXDUSE. Looking at the content of this table as basis person can also help you to get insights into how end users are using the system. You can find transaction start, but also Remote Function calls.

Administration of systems

Before usage you must administer all your systems in the solution. This part is explained in the SAP help file for SAM4U:

After setting up the proper authorizations go to the Administration section:

In the SAM4U tool add the system by clicking the + sign:

In the popup that comes select the RFC you created from the central system to the backend system. Make sure the user in your RFC has the rights to run and read the SAM4U tables, and has the rights to run the SAM4U RFC modules. If the rights are not ok, the tool will make the connection Red (without further detail). To get the details of what is missing in the target system role, run an ST01 or STAUTHTRACE in the target system for the user ID used in the RFC.

First do one system to test the entire function. When you are happy, repeat for all backend systems.

Next step is to download the ruleset xls which is attached to OSS note 3113382 – Authorization-based SAP S/4HANA User Simulation / FUE Projection. Upload the downloaded xls with the Upload button:

Next step is to download License Entitlement file from me.sap.com. Instructions are given on top. Use the upload button to upload the file:

Running the tool

On the landscape tab run the tool per landscape to gather the data, by pressing the Go button:

Wait until the results are done.

Go to the Consolidation tab and create a consolidation and execute it:

Now the data sections in the Analytics and License entitlement are visible with the data:

For all the functions here, the SAP help file for SAM4U links is excellent to explain the details:

OSS notes and SAP references

If you need bug fix notes search on me.sap.com with the term SAM4U.

Link to the official SAM4U marketing. Small and simple blog on SAM4U.

Link to the YouTube explanation of SAM4U.

SAP user measurement consolidation for multiple systems: SLAW

This blog will explain how to consolidate multiple SAP user measurements into 1 combined measurement using the SLAW tool.

Questions that will be answered are:

  • How to use the SLAW tool?
  • Which options and help does it bring for consolidation of user measurement?
  • How to consolidate if users have different user ID’s across the systems?

SLAW2

The SLAW tool has a successor in the SLAW2 tool. See this blog to see how SLAW2 works.

Preparation of consolidation

In each of the systems where you have run USMM user measurement, you have to export the data in the LAW file format. To do this go to USMM and select menu option System Measurement and Export to LAW file:

Export of LAW file

Save as local file is the most common and easy option. Repeat this for all your systems.

LAW consolidation

You need to select one system for consolidation. This can be your main ECC productive server or for example your solution manager system.

In the consolidation system start transaction SLAW:

SLAW start screen

The consolidation process consists of 4 steps:

  1. Load all the LAW files
  2. Combine the users
  3. Consolidate
  4. Send consolidated results

First load all of your LAW files, before going to the user combination.

In the step Combine Users you have several options to combine the users:

Combine users

The best option for your consolidation is dependent on the differences per system. If you user name is the same per system, then this is good option. If the username is different per system, but your email is kept consistent per system, then this is a better option. Last resort is to do by name.

After the combination you can start the consolidation. Result of the consolidation for test users on name looks as follows:

Consolidation on name

If you see cleansing opportunities, do use them. After the cleansing start USMM again, export LAW file and rerun the consolidation.

Tips & tricks for license measurement

For tips and tricks for license measurement read this dedicated blog.

Bug fix notes

SAP user license measurement

This blog will explain about SAP user license measurement.

Important: this blog will explain in general terms. Your own company might have bit different agreements in their contract! Especially for larger companies no SAP contract is ever the same.

Questions that will be answered in this blog are:

  • How to measure users in the SAP system?
  • How can the USMM tool help in the clean up?
  • How does it work when I have same user in multiple productive system?

General tips and tricks on user measurements can be found in this blog.

USMM2

In newer systems USMM is replaced by USMM2. For more information on USMM2 see this blog.

USMM user measurement tool

The user measurement tool USMM is the starting point. Start transaction USMM and you will come to the tool launch page:

USMM start screen

Important first step is to go to the tab User Types and activate the types according to your contract:

USMM active user types

Reminder: these types can be different company depending on the contract.

These activated types will now be visible in the SU01 License tab:

License tab in SU01

User classification check

In the USMM tool the first thing to do before running the measurement is to validate the user classification. From the USMM start screen click the user classification button. This will now list all the users in your system and the assigned or determined user classification:

User classification overview

If you want to change a classification you can do that in SU01 license tab, or directly from this screen by selection of the record(s) and pressing the Classify Selected Records button.

General rules for classification:

  • Background users (type B and S) typically count as Technical users
  • Non-classified dialog users will be set to Default (meaning SAP will count them as the most expensive type of users)
  • Locked users will be counted as well
  • Users outside of validity period will not be counted in the measurement
Deleted users and users outside of validity date will not be counted in the measurement, but the statistics of these actions will be!
If you execute regular clean up (every month or quarter) this will be seen in the statistics. If you do clean up just before the measurement it will be seen as well, and might lead to discussion. If you do monthly clean up discussions will end fast.

Executing the user measurement

After you have classified and checked all the users,you can start the user measurement in USMM by hitting the System Measurement button.

The USMM tool will now run by firing a huge amount of SM37 jobs. Wait until the jobs are finished (typically max 10 min runtime). Then you can see in USMM the result of the run in the log:

USMM run log results

The USMM tool will both do the user and automated engine measurement.

The USMM tool can be run as frequently as you want. The Send to SAP button is a real send and cannot be reverted.

Improving the USMM results

You can improve the USMM results via the User Data Analysis button:

User data analysis

Here there are several lists to help you find why certain elements are reported.

You can use this lists to find errors in the classification and do extra cleanup. Then you can rerun USMM before you submit the data to SAP.

Multiple productive systems

If you have multiple productive systems a lot of users will be present in both systems. Example: user is present in the core ECC system and runs reports in the BI system.

For the SAP user measurement you want to count the user only once.

To help you in this administration activate in USMM the Multi-Client/System type:

Multi client system user type

In SU01 license tab you can now refer to this type, and set the main system for user measurement:

Multi system user in SU01 tab

If you have multiple systems you run USMM per system. For consolidation of the runs per system you can use the SLAW tool (license administration workbench), or it successor the SLAW2 tool.

LUI License utilization information

The LUI (license utilization information) tool is an online SAP tool that has all the information on your on premise and cloud licenses information combined. For cloud the usage is automatically visible. For on premise systems you can upload the usage via the SLAW files. This can give you insights into under-consumption and over-consumption of licenses. Read more in this blog.

SAP user measurement background information

The most current SAP user measurement background information can be found on the SAP support pages for user measurement.

For  tips and tricks on user management see this dedicated blog.

For the new license model for digital access, read this blog.

For more technical background on how the measurement is performed, read this blog.

For more background on licenses for SAP solution manager, read this blog.

For more background on FIORI ODATA usage, read this blog.

For more background on EHP switches and licenses, read this blog.

Bug fix notes: