Release note: samQ v3.6.1

The focus of this release is on the user grouping, which now leaves nothing to be desired. Test us and prove us wrong!

Complex license distribution

In the past, we were repeatedly confronted with new versions of license distribution requests deviant from standard, which often arose from traditional corporate structures. Now we have enriched samQ in such a way that any kind of license distribution can be realized automatically. An example: If a user receives license A optimized in system X, then he must receive license B in system Y and license C in system Z. Sounds complicated? It is. But luckily samQ now takes care of this automatically for you.

User grouping becomes more transparent

In many companies, there are different requirements of how a user ID grouping should take place. Historical or organizational basics are often the reason why different users in different SAP systems are merged into one user and thus only receive a resulting license.

These different groupings are already possible in samQ. However, the problem was that a grouping working in the background, delivered correct results, but the ruleset of the grouping often fell into oblivion. Therefore, the optimization results could no longer be explained plausibly at some point, even though they were completely correct due to the grouping in the background.

With the optimizations in the new release, this can no longer happen to you. When opening samQ, the user is informed about the currently running grouping with date specification.

Fixed licenses become more transparent

In samQ, users can always be provided with a fixed license and thus fall out of the optimization. This happens when certain conditions from the contracts make this necessary. Such fixed conditions have long been possible in samQ. In Customizing you simply set the conditions, which then automatically lead to the fixing of the user.

Another possibility is mass fixing, which is usually forgotten later because the reasons for this action can no longer be retrieved. In the past, this has repeatedly led to confusion because it was not clear where this fixed setting came from. This is now made transparent in samQ by a corresponding indicator on the fixed user. It is now immediately apparent where the user received his fixed license from.

Extension of the user type in the samQ Report

It used to be easier: in the past one dialogue user was subject to licensing and all others were not. That has changed radically over time. Many system users are now subject to licensing. In the developer systems, SAP searches for licensed users who only make customizing and much more.

These conditions have long been taken into account in samQ and used automatically. Up to now, however, it was not possible to recognize transparently in the report which type the corresponding user corresponded to. A small thing, but still important. Now, in the cross-system license display, it can be seen for each user subject to license whether he is a dialog user or a technical user.

LAW User from the USMM can be used for grouping

We have already been offering the automatic consolidation in samQ before the LAW consolidation for some time now. But there is a special problem.

Most companies grow with time. They often grow through acquisitions. And with the acquisition, additional licenses and SAP systems are also taken over. Due to naming conventions and other adverse circumstances, the only option is to mark different user IDs in the USMM. For this you have to use the so-called characteristics in such a way that different user IDs are combined to form a single user in LAW consolidation when measuring these values. Sounds deeply technical and complicated – and it is!

This is exactly what samQ can now take into account. It automatically recognizes in the SAP systems that the users belong together and merge them.

Contact us

Send a message

Request a callback

Contact us