SAP Business Suite – managing engines
Engines are split in two categories, depending if the engine can be measured:
- measurable engines
- self-declarable engines
The measurable engines’ data sources are ABAP tables. Their usage evidences are determined by the USMM transaction or a SAM tool. If the detected usage indicator (metric ID) is the same as the licensed metric ID, then the compliance position is automatically calculated when running the specific usage report (in Snow Optimizer for SAP’s case) or on the Dashboard (in FlexNet for SAP’s case). If the metric ID of the detected engine is not matching the licensed metric ID, then you as an end user need to investigate the reason of the mismatch and to perform manual updates in the tool to display accurate information.
One aspect that is not currently covered by all the SAM tool providers is the relevancy of a usage result. A system on which the SAP Notes have not been properly implemented before running a compliance check may generate false positive results (e.g.: by other SAP software applications that are actually in use) or historical records that are incorrectly showing the use of some engines (e.g.: for SAP software applications that are no longer in use). FlexNet for SAP is able to highlight some of these cases by showing some brief details about the usage validation.
However, when calculating the compliance of the detected engines, it is recommended to manually check the latest information on the SAP Support Portal. This will help you decide whether the usage should be counted as relevant or not. Unfortunately, at this point in time, these notes are not fully showed by any of the SAM tools. As a result of this the end user should not rely on these results without double checking the information on the SAP Support Portal.
For the self-declarable engines, the SAM tools provide the possibility to create new entries for your specific license entitlements with their specific metrics. In addition, the SAM tools allow you to register the usage value of these self-declarable engines (e.g.: revenue). Once the license entitlement has been created and the usage values has been registered, the license compliance check can be performed. The usage values are entered manually and as such highly depending on the correct interpretation or understanding of how the usage values should be determined (e.g.: should the revenue be declared for the whole company or for a limited amount of legal entities). This manual approach is error sensitive and highly depending on the knowledge and expertise of the person that enters the usage values for the self-declarable engines.
For example, if you have recently merged with another company and you started to monitor your own SAP licenses in an SAP tool, whose number of employees will you consider when you will set up the usage quantity in your SAM tool against that particular license? Your former number of employees? The number of employees of the company resulted after the merger? The number of employees in the Business Unit that is making use of the software program licensed on this metric?