Snow Optimizer for SAP’s Integration with Snow License Manager
In the previous article series focused on the SAM tools for SAP we described what a SAM tool can or cannot do based on the different criteria influencing the technical capabilities (e.g. the importance of understanding the data sources behind every product group). As independent reviewers, we base our writing on our experience and thus we engage in updating our readers every time we learn something new.
We were recently notified about a number of changes put through by Snow for its Snow License Manager (SLM) with Snow Optimizer for SAP. An overview of the changes can be found below:
- SLM’s lists all the SAP Systems maintained in SOS
- SAP Agreements can be uploaded in the SLM
- SLM’s recommendations are being updated with information coming directly from SOS, related to users count, authorized users list per user license types. In this way, you can keep an eye on your SAP user license type consumption directly from SLM.
- You can see install evidences of the on premises solutions (except of course for the measurable engines for which records of use evidences are stored in the ABAP tables)
- You can see the cloud installations (e.g. SAP SuccessFactors). The integration nowadays goes both ways and the use information of cloud solutions flows back to Snow Optimizer for SAP.
Enhanced version of SOS
Starting with Snow Optimizer for SAP (SOS) version 2.2 (released at the end of April 2019) the SLM information is also brought back in the optimizer. This means that you can find all the details visible in the SLM back in the optimizer. This enables the cloud solutions to be visible in the optimizer as well. Besides the flow of data from SLM to SOS, other new features are also enabled starting with version 2.2.
The optimizer is now able to load data for outbound and inbound IDocs, batch input processes, and RFC destinations and users for which new reporting capabilities have been enabled.
On the user authorization side, Snow created new reports and conditions having the purpose of checking if different authorization objects are assigned to users or not. This is helping to determine the user license type that needs to be allocated to a user.
Engines were also a target for improvement and thus the new version brings new columns highlighting if a user is relevant or not for the measurement and if the measurement result represents an indicator of the software program being in use or not.
As you may have read in our previous whitepaper related to the most common compliance issues seen at SAP customers, one of the challenges they have is to keep up with the latest notes SAP releases in order to refresh their engines installation. Checking the relevancy of a measurement result is crucial when determining your compliance position. Therefore, the new functionality offered by SOS helps customers to keep an eye on the relevant results only.
Make sure you also take the proper steps in order to implement the applicable notes and clean up your environment from the unwanted measurement results. We’re happy to assist you in getting control over your SAP compliance position. Contact us and let us know how we can help you.
This article was published on 04-06-2019
Catalina has been working in the license management industry since 2015. Before joining B-lay, she worked as a Senior Technical Consultant for the License Management Services (LMS) Department within Oracle for two years, performing technical measurements during audits.
Currently, she is conducting the technical analyzes for SAP and Oracle Applications as well as working as a Solution Advisor for Oracle Siebel, Oracle Hyperion and SAP Applications. Over the past years, Catalina has supported Oracle and SAP customers globally and she leverages her technical and licensing knowledge to help organizations discover, understand and overcome their compliance challenges.
Catalina holds a bachelor’s degree in Economic Cybernetics and a master’s degree in Cybernetics and Quantitative Economy from Bucharest Academy of Economic Studies.