Contents
Key takeawaysThe named user typesCost and audit riskHow SAP measures usersGoverning classificationWhat we saw in 2024 and 2025What SAP will sayThe value at stakeWhat to do nextFAQSAP named user types form a price ladder from Professional down to self service. The type assigned to each user decides both the annual cost of the named user line and the audit exposure you carry.
- A ladder of prices. Professional is the most expensive business user type and Employee Self Service the cheapest, with Developer priced above both.
- Lowest fitting type. Each user belongs on the lowest type that covers the work they actually do in the system.
- Two ways to be wrong. Over classification wastes license and support budget, while under classification becomes an audit finding.
- SAP counts the user master. USMM reads the type recorded in SU01, counts unclassified dialog users at the most expensive type, and LAW counts each person once at their highest type.
- Drift is the norm. In our 2024 to 2025 reviews, Professional seats were over assigned by 20 to 40 percent and mappings were years out of date.
- Review on a schedule. Check the type mapping before every renewal and after every reorganization, and keep the usage evidence per user.
What are the SAP named user license types?
Classic SAP contracts use five main named user types. Developer usually sits at the top of the price list, followed by Professional, Limited Professional, Employee and, at the base, Employee Self Service. Each step down trades capability for a lower price per user.
This guide is for CIOs and license managers who govern classic SAP named user contracts in 2026. SAP describes the products on its SAP ERP pages, but the binding definitions sit in the Software Use Rights document attached to your contract. Read this page alongside our named user negotiation paper and the SAP Practice page.
| User type | What the contract allows | Typical people | Relative price |
|---|---|---|---|
| Developer | Access to the development tools to build modifications and add ons | ABAP developers, some project consultants | Usually above Professional |
| Professional | Operational roles plus system administration and management roles | Key users, finance and supply chain operators, Basis administrators | Highest of the business types |
| Limited Professional | A limited set of operational roles | Occasional or single area users | Middle |
| Employee | Defined tasks carried out solely for the user's own purposes, never on behalf of others | Staff who book their own travel, file expenses and raise purchase requests | Low |
| Employee Self Service | HR self services such as time entry, appraisals and skill profiles | The wider workforce | Lowest |
How does the ladder map to real roles?
Operational staff sit near the top, light transactional staff in the middle, and self service staff at the base. The goal is the lowest type that covers the work each person does.
- Professional. Full operational access across the licensed software, at the highest price.
- Limited Professional. A narrow transactional scope, such as one functional area or occasional postings.
- Employee and Employee Self Service. Tasks on the user's own record, at the lowest price.
Where do Developer and Worker users fit?
Developer is usually the most expensive type, and it often stays open on project consultants long after the project closes.
Many contracts also carry specialist types. Their wording changed across SAP price list versions, so check your own contract.
- Worker. Production and maintenance staff with a short list of defined tasks, such as displaying work instructions and confirming goods receipts.
- Manager Self Service. Approvals of travel, expenses and HR or procurement workflow items for a manager's own team.
Approvers are the most common misfit. The Employee type covers a person's own requests only, so a manager who approves for others needs Manager Self Service, where the contract offers it, or a higher type.
What changed with S/4HANA?
S/4HANA on premises introduced its own user types: Professional Use, Functional Use, Productivity Use and Developer Access. Under RISE with SAP, users convert instead into Full User Equivalents by tier. Our guides to S/4HANA user types and FUE licensing cover both, and the classification habits described here carry straight into them.
Optimize the Estate First: The SAP Work That Pays for the Negotiation
How does the user type drive SAP cost and audit risk?
The type sets the price of each user, so the mix of types sets the annual cost of the named user line. It also sets audit risk, because activity beyond the assigned type is a finding. SAP's standard agreement terms are published in the SAP agreements center.
The cost does not stop at the license fee. SAP Enterprise Support is priced as a percentage of the license value, listed at 22 percent for new on premises purchases, so every user placed one step too high costs you again every year the contract runs.
Why does classification cut both ways?
Over classification wastes budget. Under classification creates exposure. A mapping built from measured usage, with evidence kept per user, protects you on both sides at once.
| Type | Relative cost | Risk if the type is wrong |
|---|---|---|
| Professional | Highest | Wasted budget if over assigned |
| Limited Professional | Medium | Exposure if usage exceeds the licensed scope |
| Self service | Lowest | Exposure if operational use creeps in |
What does a reclassification look like in dollars?
Say a company holds 1,000 named users: 400 Professional, 250 Limited Professional and 350 Employee. Use illustrative net prices of $3,000, $1,200 and $400 per user, or the prices on your own order form. A usage review finds 120 Professional users who work in a single area and 30 who only handle their own travel, expenses and purchase requests.
| Type | Users before | Value before | Users after | Value after |
|---|---|---|---|---|
| Professional at $3,000 | 400 | $1,200,000 | 250 | $750,000 |
| Limited Professional at $1,200 | 250 | $300,000 | 370 | $444,000 |
| Employee at $400 | 350 | $140,000 | 380 | $152,000 |
| Total | 1,000 | $1,640,000 | 1,000 | $1,346,000 |
The corrected mix is worth $294,000 less, about 18 percent, and every user keeps the access they use. At the 22 percent support rate, the support attached to that difference is $64,680 a year.
On a perpetual contract the saving rarely comes back as a refund. It shows up as Professional licenses freed for new hires instead of bought, as a smaller shortfall at the next measurement, and as a lower user base carried into an S/4HANA or RISE conversion.
SAP RISE Negotiation Guide
Pricing benchmarks and contract terms for RISE, including how your named user mix converts into the subscription.
Get the white paper →How does SAP measure named users in an audit?
SAP counts the license type recorded in your user master. The measurement program USMM reads the type stored against each user ID in SU01, and the License Administration Workbench (LAW, opened through SLAW or SLAW2) consolidates the results from every system. Neither tool checks what each person did in the system.
Two rules matter most. Dialog users that were never classified are counted at the default, which is the most expensive type. And LAW merges a person's IDs across systems and counts that person once, at the highest type any of those IDs carries. Our guide to USMM, LAW, SLAW and STAR covers the mechanics.
How can you check your own position before SAP does?
- SU01 and SU10. The license data tab shows each user's contractual type, and SU10 changes it in bulk once the evidence supports a move down.
- USMM. Run it yourself on each productive system before the annual request arrives and read the unclassified count first.
- LAW. Choose the matching rule for combining users, such as user name or email address, and check that one person does not appear three times.
- ST03N. Workload statistics show which transactions each user ran, which is the evidence for every reclassification.
- SUIM and RSUSR200. SUIM lists the roles each user holds, and RSUSR200 lists users by last logon date so you can lock leavers and dormant accounts.
The audit sequence that follows the measurement is covered in our SAP license audit process guide.
How do you govern named user classification?
Governance keeps the mix correct as people change jobs. Set a review cadence, classify from usage and hold evidence for each assignment. SAP's direction toward cloud subscriptions, covered in SAP news, makes the discipline more valuable, because the user mix you hold today becomes the basis of any conversion.
What review cadence keeps the mix accurate?
An annual review before each renewal or contract amendment, plus a check after any reorganization, keeps drift under control.
- Annual review. Classify every user before each renewal and before SAP's measurement request.
- Event triggers. Recheck after reorganizations, divestments, shared service transfers and large role redesigns.
- Evidence trail. Keep the usage proof behind each user's type, so a query from SAP gets an answer in days.
- Provisioning rule. Make the license type a required field in the joiner process, so new users are never created at the default.
| Time before the date | What to do |
|---|---|
| 12 months | Export every user with the assigned type, run USMM and LAW yourself, and check that ST03N keeps enough history. |
| 6 months | Map each user to the lowest fitting type, correct the clear cases in SU10 and lock dormant accounts. |
| 3 months | Rerun the measurement, price the difference and settle any disputed populations internally. |
| 1 month | Confirm the corrected mix is what goes to SAP and into the renewal or conversion quote. |
What have we seen in SAP named user reviews in 2024 and 2025?
Most customers carried more Professional users than their work required. Fredrik Filipsson reviewed roughly 30 to 40 SAP named user environments in 2024 to 2025, and three patterns came up repeatedly.
- Professional over assignment. Professional users were over assigned by 20 to 40 percent of seats.
- Stale mappings. Classification had gone unreviewed for 2 to 4 years at most customers.
- Recovered cost. Correcting the mix cut named user cost by 15 to 30 percent.
The cause was usually the same. Types were set at go live, often by a user template that carried Professional, and never revisited while the organization changed underneath them.
Why treating classification as back office hygiene costs you money
The usual view is that named user classification is a housekeeping task for the Basis team with little strategic value. We disagree. The customers we reviewed had left it alone for years and paid for Professional seats that up to two in five of those users did not need.
A one time cleanup fixes the number for about a year. Run classification as a recurring control with an owner and a date in the calendar, so the saving from the first correction does not leak back.
Every named user type is a price. The question for a CIO is which type each person needs, and the headcount comes second.
What will SAP say about reclassification, and how should you answer?
Expect the account team and the audit team to defend the current mix. These are the lines we hear most, with replies that work.
- "Unclassified users count at the most expensive type. That is the system default." Classify them before you submit. The measurement you send is your data, and nothing stops you correcting the user master first.
- "Those users do not meet the Limited Professional definition in your contract." Ask which clause, in which version of the Software Use Rights you signed. Then map the users' transaction history against that wording, line by line.
- "Settle the shortfall now and reclassify afterward." Decline that order, because a shortfall priced on the uncorrected mix becomes licenses and support you pay for every year.
- "Move to RISE and the user types stop mattering." The FUE conversion weights users by tier too. An inflated Professional count becomes an inflated Advanced count.
Can you cut support on licenses you no longer need?
You can, but the cut is permanent. SAP introduced partial termination of licenses and their support in 2013, but a terminated license cannot be switched back on and must be bought again, possibly at a lower discount. Reassign surplus Professional licenses to growth before you terminate anything. Our SAP support and maintenance guide covers the current terms.
What is the CIO level value at stake?
The named user line is one of the largest SAP costs a CIO controls directly. Classify users from measured usage and you set that cost yourself, where today it is often set by the template applied at go live.
What should your contract say about user types?
- Definitions fixed at signing. Name the version of the Software Use Rights that defines each type, so a later revision cannot move activities up a tier during your term.
- License exchange rights. Ask for the right to convert surplus Professional licenses into lower types at their paid value, so a correction does not strand money.
- A correction window. If a measurement shows a shortfall, you get a set period to reclassify and remove leavers before anything is invoiced.
- Price holds by type. Additional users of each type are priced at your contracted rate for the full term.
- Unclassified user handling. Agree that users without a type are reviewed with you before they are counted at the default.
How does this change with company size?
A 500 user company with one production system can review every user by hand in a few weeks. A 20,000 user group with many systems needs the LAW matching rule, a provisioning rule and a named owner, because the gap between the default and the correct mix grows with every system added.
Large workforces sit mostly at the base of the ladder, which our self service user guide covers in detail.
What to do next
- Export the user master. List every named user with the assigned type from SU01 across all productive systems.
- Map usage to type. Pull ST03N history and place each user on the lowest type that covers the work.
- Price the gap. Quantify what current over classification costs in license value and yearly support.
- Correct the clear cases. Reclassify in SU10, lock leavers and keep the evidence behind each change.
- Set the cadence. Schedule an annual classification review before renewal, with event triggers after reorganizations.
- Carry the mix into the deal. Take the corrected count into the next renewal, measurement or conversion. Our white paper, SAP named user licenses: the user classification audit, walks through each step.
Frequently asked questions
Which named user license types does SAP offer?
In classic SAP contracts the main types are Developer, Professional, Limited Professional, Employee and Employee Self Service. Many contracts add specialist types such as Worker and Manager Self Service. The list and wording depend on the price list version you signed, so read the definitions in your own Software Use Rights document first.
Which SAP named user type is the most expensive?
Developer usually carries the highest price, followed by Professional, which covers operational work plus system administration and management roles. Employee Self Service is the cheapest because it only covers HR self services on the user's own record, such as time entry and appraisals.
How does classification drive SAP cost?
Each type has its own price, so the mix sets the total without changing the headcount. The effect compounds because support is charged as a percentage of license value, and because the classified user list becomes the starting point for any S/4HANA or RISE conversion quote.
How does classification affect SAP audit risk?
SAP compares the types measured by USMM and LAW with the types you own. Users doing work above their assigned type are a finding if SAP tests activity, and users left unclassified are counted at the most expensive type, which inflates any shortfall before the conversation starts.
How often should a CIO review named user classification?
Once a year before renewal or SAP's measurement request, and again after any reorganization, divestment or shared service transfer. In the reviews we ran, most mappings had been untouched for two to four years, long enough for a large share of the workforce to change roles.
How much can correct classification save?
In our reviews it cut named user cost by 15 to 30 percent. On a perpetual contract that saving usually arrives as licenses you avoid buying and a smaller shortfall, with support reductions only where you choose to terminate surplus licenses permanently.
What governance keeps the named user mix correct?
Give classification an owner, a yearly date and a rule in the joiner process that makes the license type a required field. Pair that with event triggers after reorganizations and a stored usage record for each user, so the evidence exists before SAP asks for it.
Is named user classification a strategic task for a CIO?
Yes. The named user line is one of the largest SAP costs under direct CIO control, and the classification decided today follows the company into S/4HANA and RISE, where users are converted by tier. Treating it as a yearly control keeps that cost managed.