SAP USMM – User Licensing Report

USMM is a SAP licensing Tool to determine the number of users and the chargeable objects of the modules for SAP system.

Submitting Licensing report to SAP

Step 1: Generate License report

Navigate to USMM tx in SAP system & click on ‘System Measurement’

The system measure would trigger some background jobs which can be monitor from SM37, looks for jobs RSUVM* & wait for these jobs to be completed.

Go to ‘System measurement in the Menu and click on ‘Export to Law file’.

Save the file to a local folder (i.e. – USMM_License)

Step 2: Generate License report on all SAP systems

Perform this step in all the SAP systems
Save the License file for each system in the local folder

Step 3: Submit Report to SAP

Log on to any SAP production system.

In this system run transaction SLAW

This is the License Administration Workbench

Import all the systems data using the first icon on step 1 (Import Data of a System)
Once all the systems LAW files are imported from all SAP systems(already generated report)
Click on Combine Users –> Click on Consolidate All Data
DO NOT click on ‘Send results’ button yet.

Go to results tab to make sure to verify & review the reports along with the stake. Once numbers are satisfactory, you are good to submit report to SAP.After the number are satisfactory.

Click on Send (This will send the report to SAP)

LMBI – License Measurement tool for Business Objects

As per my earlier post, i have shared how BO licensing works.

Once you have install the BO license (CS & named user), now it’s time to audit the license as per license Contract with SAP. LMBI tool requires to perform this action.

This tool will run 2 things – Measurement & Consolidation.

Measurement – This need to run first time based on your version (32bit/64bit) by giving BO administrator credentials, once it’s collected the data successfully. it’s create the measurement.xml file in the respective location. This file requires to import in Consolidation tool.

Consolidation – This tool import the previous run measurement.xml file & ask you several questions. i.e. BO is standalone or integrated server, CPU details, licensing contract with SAP & will show the output whether you are consistent with your license or not.

Below Notes helpful to perform the action –

2817296 – Need correct License Measurement Tool (LMBI) for BI Platform
2383265 – How to launch License Measurement Tool (LMBI) when CORBA SSL protocol is configured

How SAP Business Objects Licensing works

There are different type of licensing available for SAP Business Objects as per the version installed. SAP released multiple notes to understand the same. This is quite different from SAP ABAP & JAVA system.

This comes with “Named User License”, “Concurrent Sessions Based Licensing”, CPU based etc…

Most details covers in below notes –

1285639 – What license types are available for Business Objects Enterprise?

1794184 – What are the different license types (NUL, CAL, CS, CSBL, CPU) for SAP BusinessObjects products

2251998 – How to generate license keys for SAP BusinessObjects Business Intelligence Platform (all versions)

1251889 – License key request for SAP Analytics Solutions (previously SAP BusinessObjects)


Example –

NUL Licensing – Means how many named user login into the system simultaneously. These are guaranteed users which will get the access of BO system.

CSBL Licensing – Means suppose 1 user login into the BO system & then he login into crystal reports or create any other session without disconnecting the previous one, then he is creating multiple concurrent sessions & if these sessions are exhausted by some users then another user can’t login into the system & it will throw an error.

CPU based licensing – Means unlimited named users & concurrent sessions,based on your BO hardware, ideally how many CPU cores & metrics installed in Virtual/Physical server.


Monitor the Current Usage of SAP Business Objects –

Before changing/updating license in BO, please verify the Global System Metrics on your Business Objects Server.

Login into BO Application ——–> Settings ————> View Global System Metrics

The above will show the Purchased license details with Peak License Used.

How to run DB2 commands for SAP

useful DB2 commands which needs to run to administer the DB2 Database for SAP workloads.

#To start DB2

#To connect to particular database
db2 connect to dbname

#To check DB configuration/parameters
db2 get db cfg for dbname

#To update DB configuration/parameters
db2 update db cfg for dbname using LOGARCHMETH1 DISK:/db2/TST/archivelog

This is an example, you can update any parameter as per your requirement. LOGARCHMETH1 is parameter which need to update to keep the archive logs, This parameter is visible by check DB configuration command & after updating any parameter, DB restart requires & sometimes offline DB backup requires before starting up the DB.

#Backup DB2 Database
db2 backup database dbname to /location

#Restore DB2 Database
db2 restore db dbname from /location on /db2/TST/sapdata1

The above command will restore the DB on /db2/TST/sapdata1 folder. Make sure to check the DB parameters once restore completed as it always point to old configuration. After restore many times DB can’t start & throw roll forwarding error, in this case you need to complete the roll forwarding with below command –

#To end the roll forward status
db2 rollforward db TST to end of logs & complete

#To deactivate DB before shutting down
db2 deactivate db dbname

#To shut down DB normally

#To shut down db forcefully as application connections were still exists
db2stop force

#To check all schema in DB2 DB
db2 select schemaname from syscat.schemata

#To list all the tables for all DB’s
db2 list tables for all

#To list all the tables in respective DB
db2 list tables for schema dbname

#To manually generate the archive logs
db2 archive log for database dbname

#Unlock DDIC or any other user in DB2
db2 “update SAPSID.USR02 set UFLAG=0 where BNAME=’DDIC’ and MANDT=’000′

#Check HA/DR status in DB2
db2pd -d dbname -hadr | grep -i hadr

DB2 HA/DR Cluster Stop / Start

SAP application should be shut down before stopping the DB2 cluster.

Azure SUSE Linux host running on SBD cluster – Cluster should be set on maintenance mode
(This is a mandatory step otherwise Virtual Name will switch to other host if DB get down in Primary mode. By setting up maintenance mode, it stick on the same node until maintenance mode OFF)

Shut down sequence – Primary DB & then Secondary DB
Startup sequence – Secondary DB & then Primary DB

Login to Primary DB host & verify the crm_status

#Stop the HADR
db2 stop hadr on db dbname
db2 deactivate db dbname

Login to Secondary DB host and run below commands

#Stop the HADR
db2 stop hadr on db dbname
db2 deactivate db dbname

#Start the HADR on Standby/Secondary host first
db2start hadr on db dbname as standby

#Start the HADR on Primary host
db2start hadr on db dbname as primary

#Verify the HADR status on both hosts
db2pd -d dbname -hadr | grep -i hadr

I will update the list with more commands very soon….