Defining FUE scope for SAP license agreement
A Scandinavian stock-listed company was preparing a new SAP license agreement and needed to define the scope of Full Use Equivalent (FUE) licensing.
The challenge
The customer understood that the number of FUE users would have a direct impact on license cost. At the same time, it was not fully clear how different user types, roles, and ways of working should be interpreted within SAP’s licensing model, or how the FUE concept would work in practice.
Our approach
s4access supported the customer in defining the FUE scope as part of the license negotiation process.
The work focused on reviewing the customer's SAP user base, roles, and usage logic, and mapping these to SAP's FUE model. A key part of the work was analysing and interpreting the underlying data, supported by the use of dedicated tools to ensure that the analysis was consistent and based on actual system usage.
In addition to defining the scope, a significant part of the work was helping the customer understand how the FUE-based model actually works in practice — what is being measured, how users are interpreted over time, and what this means from a business perspective.
Together with the customer, a clear and well-justified FUE definition was established that reflects the real situation. In parallel, a practical approach was defined for how the FUE model would be managed after the agreement — including how the situation is monitored and how changes in the user landscape are handled.
Achievements & Benefits
The customer gained a clear understanding of their FUE scope and the logic behind the new licensing model.
This enabled them to define a realistic scope, avoid unnecessary license costs, and establish a practical way to manage FUE after contract signature — reducing the risk of unexpected impacts over time.
Customer Comments About
s4access Service
"Without the specialist support from s4access, we would not have been able to complete this work with the required level of confidence. Their expertise helped us not only to define the right scope, but also to understand how the model works and how to manage it going forward."