A named user is an SAP license assigned to one identified, named individual, required for every person who accesses an SAP system directly regardless of how often, with the Professional user type carrying the highest list price at roughly 3,000 to 4,000 dollars per user before discount. The license follows the person, not the seat, so it cannot be shared, and the type assigned to each person, not the headcount alone, determines what the estate costs.
The named user types
SAP's classic licensing splits users into tiers by what each person is allowed to do. A Professional user can perform operational and administrative work across modules, a Limited Professional is restricted to a narrower role-based set of tasks, and an Employee or Self-Service user is confined to occasional self-service functions such as entering a timesheet or a leave request. Each tier down costs materially less, and the rule is that a user must hold the lowest type that still covers everything they actually do.
| User type | Typical use | Relative cost |
|---|---|---|
| Professional | Full operational and admin work | Highest |
| Limited Professional | Role-restricted operational tasks | Medium |
| Employee / Self-Service | Occasional self-service only | Lowest |
| Developer | Build and configuration work | Premium |
The classification is a contractual definition, not a technical one, which means it is negotiable and frequently mis-set. The detail of each tier and how SAP defines the boundaries sits in the named user licensing guide and the user type comparison.
Why over-assignment is the common overspend
SAP licensing tends to drift upward. New users are often created as Professional by default, roles change without the license type being revisited, and dormant accounts keep their expensive classification. Because the measurement counts each user at their assigned type, a population full of over-assigned Professionals inflates the bill even when most of those people only enter the occasional transaction.
Negotiation point: Profile actual usage against assigned type before any SAP measurement. Reclassify every user to the lowest type their real activity supports, and deactivate dormant accounts so they leave the count entirely. On most estates this removes a layer of Professional licenses that were assigned by habit, not by need, and the saving carries straight through the USMM and LAW measurement into the renewal baseline.
How named users are counted at measurement
Named users are counted once a year by the USMM system measurement, which reads the license type assigned to each active account and tallies the totals by type. The count is mechanical. It reports whatever classification sits in the system, so a user assigned Professional is counted as Professional whether or not their daily work justifies it. Inactive accounts are counted too unless they are locked or formally excluded before the measurement runs, which is why dormant users are a quiet source of overspend. The per-system totals then flow into the License Administration Workbench, where the same person holding accounts in several systems is deduplicated to a single license. Because the measurement is a snapshot, the cleanup work of reclassifying and deactivating has to be done before the run, not after, or the inflated numbers carry into the annual declaration and the renewal baseline.
How S/4HANA changes named users
S/4HANA replaces the named user catalog with Full User Equivalents, where each user type maps to a fraction or multiple of one FUE, and the contract is sized in FUEs rather than discrete user counts. The conversion math, including which old user types map to what FUE weight, is set out in the FUE counting guide. Getting the named user classification right before conversion matters, because an over-assigned population converts into an over-sized FUE commitment. Our SAP advisory practice rightsizes user types before measurement and conversion, and the full picture sits in the SAP licensing guide.