USMM / LAW measurement
We perform a system measurement in line with SAP methodology, analysing user classification, license types, system usage and the audit trail.
We analyse SAP license usage: USMM/LAW, indirect access, BTP commits and RISE consumption. The audit helps prepare for a vendor audit, a contract renewal or a conversion to S/4HANA.
In past projects, we have identified measurable savings in annual SAP fees.
We analyse actual SAP license usage and compare it with the current license portfolio. In past projects we have identified measurable savings in annual fees, and in larger organisations this has meant hundreds of thousands to millions of złoty per year.
We identify licensing risks ahead of a formal SAP audit, reducing the risk of back payments, user reclassification or contractual corrections. This applies particularly to indirect access, digital access, user classification and license usage across multiple systems.
We provide concrete data on license usage, actual demand and areas for optimisation. This allows discussions with SAP to be grounded in figures rather than estimates prepared at the last minute.
The license audit helps assess the consequences of moving to a new licensing model, including FUE, RISE or GROW. The result is a license migration map with costs calculated over a 5-year horizon.
We perform a system measurement in line with SAP methodology, analysing user classification, license types, system usage and the audit trail.
We identify sources of indirect access and digital access: integrations, customer portals, web services, RPA, RFC and other scenarios where SAP data is used by external systems. The result is a licensing risk assessment and recommended actions.
We check whether the current license portfolio matches actual usage of the SAP systems. We prepare recommendations on user reclassification, license consolidation or contract restructuring.
We analyse BTP commit usage and RISE consumption. The goal is to reduce over-provisioning, unused commitments or the risk of exceeding agreed limits.
We prepare data, arguments and negotiating scenarios for discussions with the SAP account manager. Optionally, we support the client's procurement team in preparing for and conducting these discussions.
We prepare a license migration plan from ECC to S/4HANA, covering FUE, RISE, GROW and cost over a 5-year horizon.
A license audit begins with an inventory: SAP systems, products, user types, current license classifications, contracts and purchasing documentation.
We then carry out the USMM/LAW measurement, analysing user classification, actual system usage and how well the license portfolio matches real usage.
In parallel, we analyse indirect access and digital access, including integrations, portals, web services, RPA, RFC and other scenarios where external systems access SAP data.
Next, we review BTP commit usage, RISE consumption, and the potential impact of moving to FUE, RISE or GROW in connection with an S/4HANA conversion.
The final report contains a map of licensing risks, the potential value of savings, an action plan ahead of renewal, recommendations on reclassification, and the target licensing model.
Technology stack
Partnerships backed by our team's certifications. Full authorisation for delivery and support.
Industrial manufacturer
An ECC license audit ahead of conversion to S/4HANA. The project identified savings of 22% of annual fees.
Company in the financial sector
An indirect access audit for integrations with transactional systems, reducing the risk of additional licensing fees.
Corporate group
License consolidation across four subsidiaries, a migration plan to FUE, and identification of savings of 28% per year.
No. SNOK's preventive audit is an internal mapping of license usage. It does not require notifying SAP. The vendor receives the results only if the client decides to use them in a renegotiation or during a formal vendor audit.
Ahead of a contract renewal, before a conversion to S/4HANA, or when signs of a vendor audit appear. We also recommend a cyclical audit every 2-3 years as a preventive measure.
Indirect access means the use of SAP data or functions by external systems, such as customer portals, RPA solutions, integrations, web services or transactional systems. Under SAP's licensing policy, such scenarios may require separate licensing and are often a source of additional fees during audits.
Optionally - as subject-matter support for the client's procurement team. We do not negotiate independently on the client's behalf, but we provide facts, data, arguments and negotiating scenarios.