A buyer side guide to SAP named user license types for CIOs in 2026. What each type covers, how classification drives cost, and how SAP audits the result.
SAP named user licenses classify every person by the work they do, from professional through limited to employee self service, and each type carries its own price. The classification, not the headcount, decides the cost, and it is auditable.
This guide is for CIOs and SAP license managers in 2026. Read it with the SAP licensing guide and the SAP Practice page so the classification and the contract stay aligned.
SAP classifies users by the breadth of their access. The heavier the rights, the higher the price. The categories below cover most agreements, though the exact names follow your contract generation.
Professional users carry broad operational and administrative rights. They run core business processes daily and represent the highest priced type. Reserve them for staff who genuinely need that reach.
Limited users are restricted to defined tasks, such as a specific role in logistics or finance. They cost less than professional users. SAP sets out its user based model on the software use rights pages.
Because each type has its own price, the mix of users sets the bill. A pyramid with a few professionals and many self service users costs far less than one where everyone holds a professional license.
SAP named user types, relative cost view
| User type | Typical rights | Relative cost |
|---|---|---|
| Professional | Broad operational and admin | Highest |
| Limited or functional | Defined task scope | Medium |
| Employee self service | Occasional, self service tasks | Lowest |
| Developer or specialist | Build and configure | Varies by contract |
SAP measurement tools compare assigned users against owned licenses. If staff are classified below their real use, the audit reports an underlicensing gap. If above, you are simply overpaying.
Named user licensing is a classification problem, not a counting problem. Get the pyramid right, and the cost looks after itself. Get it wrong, and you either overpay every year or face a true up at audit.
Pull usage data, then reclassify each user to the lowest type that fits. Keep evidence of the basis, since SAP can audit the result. Done well, the exercise lowers cost without removing access.
SAP named user licenses classify each person by the work they do, from heavy professional use down to light employee self service. Each type carries its own price, and every user who touches the system needs one. The classification sets the cost.
The exact set depends on your contract generation, but most agreements center on professional, limited or functional, and employee self service users. Older contracts may carry developer and other specialist types. Your price list defines the ones you hold.
Professional users have broad operational rights and carry the highest price. Limited or functional users are restricted to defined tasks and cost less. Assigning professional licenses to staff who only need limited rights is a classic overspend.
SAP measurement tools such as USMM and LAW report the named users you have assigned against the licenses you own. If staff are classified below their actual use, the audit flags an underlicensing gap and a true up bill.
Yes, within the rules of your contract. Moving users to the lowest type that genuinely matches their work lowers the license cost. The key is that the classification must reflect real usage, since SAP can audit it.
Classic on premise contracts use named user types, while cloud and RISE deals use Full User Equivalents. Many enterprises run both, so the classification discipline carries across as they migrate to cloud.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Named user licensing is a classification problem, not a counting problem. Get the pyramid right, and the cost looks after itself.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on SAP renewal moves, named user classification, indirect access posture, and the buyer side moves we are running in client engagements.