This blog will analyze some of the tables behind the license measurement.
Warning: the list of tables below is not complete. Do not base any assumptions on the content of these tables in your system. In updates and newer versions all content can change. The tables and the text in blog is to give you insight into the process. In any contract SAP will claim the right for inspection of actual usage of your system versus the license rights in your contract.
Questions that will be answered are:
- How do I know which objects are measured?
- How are objects measured?
- How can I find actual measured objects?
The tables behind license measurement
The best table to start with is the TUAPP table: measurement of applications.
Example is given below:
Here you can see that Advanced ATP is measured via call function module. In SE37 you can lookup the function module and see inside the code what exactly is measured:
The other entry in TUAPP we will take as example is Procurement Orders. Its application ID is 5000 and does not measure via function module.
First we get the application to unit and unit name from table TUAPP_UNT (units themselves are defined in table TUUNT):
Now we see procurement is counting Inquiry, Purchase order, Contract, Scheduling Agreement and Others.
The actual values read by the measurement for the application counters are stored in table TUCNT:
The tables behind the AC checks
The AC (anti cheating) modules use bit different tables.
Table TUL_AC_UNIT is to denote the table to count on:
Here you see the main procurement table EKKO has ID number 5018.
In table TUL_ACTTC you can lookup this value:
This data will be used in dynamic SQL statement that will list the user name (ERNAM) who did the create or change and uses AEDAT (last change or creation date) for table EKKO to count for check 5018.
This blog will give you tips & tricks for the SAP license measurement.
Questions that will be answered are:
- How to deal with license classification for background users?
- How to deal with license classification for standard SAP users?
- How to deal with license classification for SAP support and firecall users?
- What does Confusopoly mean?
According to OSS note 32326 – System measurement : Technical users all background users are free of charge. Classify them as type 91 Test users. This rule is valid for:
- Batch users to run background jobs
- SAP to SAP system connection users
- Interface batch users
Be careful with the interface users. If an external system posts data into SAP system with a single background user, but it is clear that in the source system multiple real users doing the actions, SAP might want to charge you for 'indirect use'.
System dialog users
SAP standard dialog users are excluded from system license measurement. See OSS note 1402837 – Info USMM/LAW: Excluded SAP users in the measurement for a full list.
SAP support users and fire-call users
For live support of an SAP system you typically will have 2 types of support users:
- Users for SAP themselves to logon to your system and provide support to you
- Fire-call users with elevated authorizations to solve time critical incidents
Both type of users have no direct business goal, but have only support usage. You can mark them as type 91 Test user, as long as you have a clear naming convention for these users and a general rule that they are locked unless they are needed.
User deletion as regular activity
The user measurement program (both USMM and USMM2) checks for deletion of users in the last three months. To avoid discussions on user deletion it is best practice to delete monthly, or bi-monthly, all persons which have left your company.
End validity date
Users who don’t have a current validity date are not counted in the user measurement program. You might want to schedule program RSUSR_LOCK_USERS in a regular batch job to end the validity of users that did not log on for long time automatically. See this blog for more details.
If you think you know all about SAP licenses, SAP will change everything again. Dilbert has a nice word for it: confusopoly:
Sometime people on sales/buying SAP joke about the SAP abbreviation being Shut-up And Pay.
EHP switches can deliver great new functionality. But not all of them are for free. This blog will explain how you know which ones are included in the standard license and which ones not.
Questions that will be answered are:
- How to know which switch has license impact?
- What are best practices for EHP switches?
Relationship between EHP switches and licenses
The relationship between EHP switch activation and licenses is explained in OSS note 1524246 – Relationship of licenses and business functions.
Attached to this OSS note is the most recent version of the PDF listing which switches are part of the standard license, and which switches require an extra license.
How to read the document?
The document is sorted per business area. Best way is simply use the find button in the PDF and search for your switch.
Example of 2 switches that don’t have license impact:
The pricing comment and License (material number) column are empty. These switches are part of standard license.
Example of switch with license impact:
For this switch your company should be in possession, or acquire the license mentioned in the last column.
EHP switches best practices
Since EHP switch can have license impact the following best practices is suggested:
- Restrict SFW5 EHP switch activation access to basis team only (display for all is ok)
- Explain basis team the fundamentals of the licenses and EHP switches
- Determine in your company who must approve EHP switch on and make clear to basis team only to execute the activation after this approval
If you have switched on a switch with licenses and don’t want to use it, check if it is a reversible switch. Then simply undo this. If it is not reversible, don’t use the corresponding functionality. The latter is much harder since you need to restrict authorizations to that function very carefully.
In the previous blog the new SAP license model for indirect access. The biggest challenge after reading the blog will be: how can I know the impact for my situation and my SAP system?
For this purpose SAP has developed an estimation tool.
Questions that will be answered in this blog are:
- Which note do I need to apply to get the estimation tool?
- How do I run the estimation tool?
- Why is the tool estimation only?
Warning: this tool only gives estimation. The tool cannot take into account specific configurations you have done to standard SAP that influence the outcome. Also the tool cannot take into account potentially company specific agreements you have made with SAP.
Installation of the estimation tool
The OSS note to install is depending on your version (S/4HANA or ECC):
Running the estimation tool
After the note is installed you can start program DAC_S4_COUNT_DOCUMENTTYP_ITEM:
Fill out the date and user ID to check.
Result is the amount of documents in the period:
How does the counting work?
The counting estimation in the ABAP is simply executing a select count for the timeframe and user on the respective tables for specific document types.
Example below is the counting of purchase order line items:
Here you can see only lines from EKPO with type lc_bstyp_f (which has value ‘F’) are selected. If you have configured your system differently (for example copied F to Z and are using Z) the count program will not find and report this.
This is the reason why the program is only to give you an estimation.
The tool is heavy in development. Regularly check the tool OSS note for new updates of the note version.