Contents
Key takeawaysWhat the license coversWho fits the tierS/4HANA and RISERight sizing, with an exampleChecking your positionWhat we have seenSAP's lines and repliesRenewal and contract termsWhat to do nextFAQSAP Employee Self Service is the lowest cost named user type, built for staff who only post their own time, leave or expenses. Because those staff are so numerous, putting them on higher types is one of the largest sources of SAP over licensing.
- The lowest cost named user. Employee Self Service covers staff who act only on their own records: time, leave and expenses.
- It is not for operational work. Transactions, master data and, in the classic model, approvals for others all require a higher type.
- Several types share the label. SAP's Software Use Rights split self service into Employee, Employee Self-Service, Employee Self-Service Core and Manager Self-Service users, each with its own task list.
- RISE widens the tier. Self Service use converts at 30 users per FUE and includes display and approval rights.
- Misplacement is common. Most SAP customers carry staff on higher types who only ever do self service tasks.
- Right sizing is low risk if you keep evidence. Classify from measured activity, trim unused authorizations and keep the proof for the next true up.
- Review before every renewal. People change roles, and a correct classification drifts within a year or two.
This guide is for SAP license managers sizing their user population in 2026, on classic ECC contracts, on S/4HANA on premises or on RISE with SAP. Read it alongside our named user types guide, and see the SAP Practice page for how we run these reviews.
What does the SAP Employee Self Service license cover?
The Employee Self Service user covers staff who act only on their own records: posting their own time, requesting their own leave and filing their own expenses. It is the lowest cost named user type SAP sells, and it gives no right to work on anyone else's data.
SAP positions its ERP user model on the SAP ERP pages, but the binding wording sits in the SAP Software Use Rights document that your contract references. In the classic on premises model that document defines several separate self service user types, and the label "self service" in a contract can mean any of them.
| Named user type | What SAP's definition allows | Limit |
|---|---|---|
| SAP Employee User | Travel planning and expense reporting, procurement self services, room reservations, and the standard reports tied to those tasks | For the individual's own purpose, not for or on behalf of others |
| SAP Employee Self-Service User | Time and attendance entry, employee appraisals, talent and skill profiles, profile match up | HR self services only |
| SAP Employee Self-Service Core User | Employee records maintenance, employee directory, benefits and payment, leave management, E-Recruiting | For the individual's own purpose |
| SAP Manager Self-Service User | Administrative change requests, requisitions, appraisals, compensation planning and approval, approval of travel requests and expenses, HR and procurement workflow tasks | Tasks related to the manager's direct reports or business unit |
The list shows why a single "self service" count on an order form is not enough. Time entry, leave and expenses fall under three different definitions, so check which types your contract actually holds before you move anyone into them.
Where does self service stop?
The tier stops at the user's own records. Approving on behalf of others, running operational transactions or maintaining master data all push a user into a higher type.
- In scope. Own time, own leave, own expenses.
- Borderline. Viewing payslips and simple personal updates. The Core definition covers benefits and payment and records maintenance, so these are in scope only if you hold that type.
- Out of scope. Approvals, operational transactions and master data.
What about managers who only approve?
In the classic model, approving leave or expenses for direct reports is outside the employee types. SAP defined the Manager Self-Service User for exactly that work, so an approving manager does not need a Professional license to do it.
Many companies still carry their approving managers as Professional users because that was the default type when the account was created.
How do shop floor staff fit?
Shop floor staff who only record time and leave belong in self service. The moment they confirm production orders or document maintenance activities, SAP's definition points to the Worker User, which covers production and maintenance workers and includes the Employee User rights.
S/4HANA Negotiations: The Discount Is Dead. The Tier Is the Deal.
Who actually fits the self service tier?
Large parts of any workforce fit. Shop floor staff, field employees and office workers who never touch operational SAP belong here, provided their activity stays on their own records. SAP's direction toward cloud subscriptions, reported on SAP News, does not change who fits. It changes how the tier is priced.
| Role | Typical task | Right tier |
|---|---|---|
| Shop floor staff | Time and leave only | Self service |
| Office employee | Expenses and leave | Self service |
| Team approver | Approves others | Higher type (Manager Self-Service in the classic model) |
| Operations user | Runs transactions | Higher type |
How big is the self service population?
In most SAP customers, staff who qualify for self service make up 40 to 60 percent of the headcount. That scale is why misplacing them on higher types costs so much, even though each individual seat is cheap.
SAP RISE negotiation guide
RISE pricing benchmarks, FUE sizing and the contract terms to settle before you sign.
Get the white paper →How is self service licensed in S/4HANA and RISE with SAP?
Under RISE with SAP S/4HANA Cloud, self service becomes Self Service use, one of three tiers converted into Full Use Equivalents (FUEs). SAP's service use descriptions set the ratio at 30 self service users to 1 FUE, against 5 Core use users or 1 Advanced use user per FUE.
The definition is also wider than the classic employee types. SAP's service use description gives Self Service use display and approval use rights across the solution, plus a named list of capabilities that includes Time Sheet and Self-Service Requisitioning. A manager who only approves can therefore sit in the cheapest tier under RISE.
What does that mean at a conversion?
The conversion from ECC to S/4HANA or RISE is the one point where every user is priced again. Classic Professional users tend to land in Advanced use by default, so argue approvers and pure self service staff down before signature. Our guide to S/4HANA user types covers the full tier mapping.
SAP's Self Service use list also names Goods Movement, Production Execution, Maintenance Execution and Physical Inventory. Many shop floor and maintenance workers who needed the Worker User in the classic model can therefore be mapped to Self Service use, so check their activity before accepting a Core use mapping.
How do you right size staff into self service?
Pull real activity, find users on higher types who only do self service tasks, then move them down. The saving is large because the population is large and the price step between tiers is steep. The contract terms that govern user types sit in the SAP agreements center, and the definitions there decide every case.
How much can right sizing save? A worked example
Say a hypothetical company runs RISE with 6,000 named users: 900 in Advanced use, 2,700 in Core use and 2,400 in Self Service use. A review of activity finds 100 Advanced users and 500 Core users who only post their own time, leave and expenses or approve requests.
| Tier | Users before | FUE before | Users after | FUE after |
|---|---|---|---|---|
| Advanced use (1 per FUE) | 900 | 900 | 800 | 800 |
| Core use (5 per FUE) | 2,700 | 540 | 2,200 | 440 |
| Self Service use (30 per FUE) | 2,400 | 80 | 3,000 | 100 |
| Total | 6,000 | 1,520 | 6,000 | 1,340 |
The subscription falls by 180 FUEs, just under 12 percent, and no user loses a task they perform. In this example the eligible self service group is 3,000 people, half the headcount, and 20 percent of them sat on higher types. Both figures sit inside the ranges we see in practice.
Most of the saving comes from the 100 Advanced users, who each drop from 1 FUE to one thirtieth. The 500 Core users contribute the rest. On a classic perpetual contract the arithmetic works the same way, but the benefit shows up as Professional licenses you no longer need to buy when headcount grows.
What is the risk of getting it wrong?
Place a user too low and any operational use creates audit exposure. The protection is evidence, so right size from measured activity.
- Measure first. Classify users from real activity logs and ignore job titles.
- Move the clear cases. Pure self service users go down. Users with occasional operational activity stay where they are until their roles change.
- Trim the roles. Remove posting and maintenance authorizations the user never exercised, so the system and the license agree.
- Keep the evidence. Hold the activity proof for each reclassified user for the next true up or audit.
How do you check your own self service position?
Start with what SAP will measure, then compare it with what people actually do. Five standard tools cover most of it.
- SU01, License Data tab. Shows the contractual user type set on each user master record. Dialog users left unclassified are counted at the measurement default, which in practice is usually the Professional type.
- USMM. SAP's system measurement transaction. Run its user classification check before any measurement to find unclassified and misclassified users.
- LAW or SLAW. Consolidates measurement results across systems so a person with accounts in several systems is counted once at their highest type.
- ST03N. Workload statistics with transaction usage per user, which is your evidence of what each person does.
- SUIM. The user information system, for listing the roles and authorizations each user holds.
RISE customers can check their contracted FUE quantities and entitlements in SAP for Me, then compare them with the tier each user actually needs. Our guide to USMM, LAW, SLAW and STAR explains how each tool reports users.
What have we seen in SAP self service licensing reviews?
Fredrik Filipsson reviewed roughly 30 to 40 SAP user populations in 2024 and 2025, and the self service tier was almost always underused as a way to cut cost. The same patterns came up again and again.
- Misplaced staff. Between 15 and 30 percent of staff eligible for self service sat on higher types.
- The saving. Right sizing them into self service cut user cost by 10 to 20 percent.
- The scale. Self service users made up 40 to 60 percent of total headcount.
The cause was rarely a bad decision. Users were created with a default type, roles were copied from colleagues with broader access, and the classification was never revisited as people changed jobs.
Why the cheapest tier deserves more attention than the expensive one
The usual advice is that self service users are too cheap to bother with, so effort should go to the expensive professional seats. We disagree, because the self service tier is the largest group in most user populations.
A small price step across thousands of misplaced users adds up to more than a large step across a handful. Work the cheap tier first, since volume is where this saving sits.
The cheapest seat SAP sells is the one most often withheld from the people it was built for.
What will SAP say about self service users, and how should you answer?
Expect SAP's account and audit teams to argue for the higher type whenever a user's roles allow it. These are the lines we hear most, with the replies that hold up.
- "These users hold approval roles, so they are Professional users." In the classic model, approvals for direct reports are defined under the Manager Self-Service User. Under RISE, approval use rights sit in Self Service use. Ask SAP to name the definition it is relying on.
- "The measurement shows them as unclassified, so they count at the default." Classify them in SU01 and rerun USMM before the results are final. The default is a gap in the user master data and says nothing about the work these users do.
- "Their roles include posting transactions." Ask for the user list and the transactions in question. If the activity history shows the transactions were never run, remove the authorization and have the user remeasured.
- "Move to RISE and the classification question goes away." It does not. The FUE count is still built from each user's tier, and a user mapped into Core use costs six times a Self Service user.
How does self service play into a renewal?
A right sized self service population lowers the total user cost you carry into the renewal. Settle the corrected mix first and make it the starting point, before any discount is discussed, because a discount applied to an inflated user count still pays for seats you do not need.
What contract wording should you ask for?
- Definitions by version. Name the version of the Software Use Rights or the RISE service use description that defines each user type, so a later revision cannot move tasks into a heavier type during your term.
- Reclassification right. Ask for the right to move users between types as their work changes, without buying new licenses for the lower type.
- A correction window. If a measurement finds users above their licensed type, you get a set period to fix classifications and roles before any purchase is due.
- Price hold on additional users. Self service users and FUEs added during the term are priced at the contracted rate.
- Measurement output. SAP shares the per user result of every measurement so you can check each classification.
Our white paper on the SAP user classification audit sets out how to argue each type from the contract wording.
When should the review start?
| Time before signature | What to do |
|---|---|
| 12 months | Export every user with the assigned type, run the USMM classification check and pull ST03N activity per user. |
| 6 months | Reclassify the clear self service cases and trim their roles. Push the role changes through testing into production. |
| 3 months | Remeasure, quantify the saving and put the corrected mix into your renewal position. |
| 1 month | Confirm the order form carries the type definitions, the correction window and the price hold. |
What to do next
- Export the user list. Pull every user with the assigned license type from SU01 or USMM.
- Find the pure self service users. Use activity data to identify users on higher types who only post time, leave or expenses.
- Move the clear cases down. Reclassify them into the lowest tier and remove authorizations they never use.
- Quantify the saving. Price the difference across the right sized population, in licenses or FUEs and in dollars.
- Keep the evidence. Store the activity proof for each reclassified user.
- Take the corrected mix into the renewal. Settle it before any discount conversation starts.
- Repeat before each renewal cycle. Rerun the review after every reorganization as well, because people change roles.
Frequently asked questions
What is the SAP Employee Self Service user license?
It is the lowest cost named user type in SAP's user model, for people who use SAP only to act on their own records, such as posting time, requesting leave or filing expenses. The exact rights depend on which self service type your contract holds, so read the definition in the Software Use Rights version your agreement references.
What tasks does the self service tier cover?
Time entry, leave requests, expense claims and viewing personal records such as payslips, all for the user's own data. It does not cover operational transactions or master data maintenance. Approvals for others need the Manager Self-Service User in the classic model, while RISE Self Service use includes approval rights.
Who fits the self service tier?
Shop floor staff, field employees and office workers who never run operational SAP. In the classic model, shop floor staff who confirm production orders or record maintenance work are the exception, because that activity falls under the Worker User definition. Under RISE, several of those production tasks sit inside Self Service use.
How much can right sizing into self service save?
In our reviews, moving eligible staff into the self service tier cut user cost by 10 to 20 percent. The result depends on how many eligible users sit on higher types and how steep the price step is in your contract, so measure your own population before you quote a number internally.
What happens if a self service user does more?
Any approval for others or operational transaction takes the user beyond the tier, and an audit will count them at the higher type. Classify from measured activity so no user is placed too low, and remove authorizations the user does not need, because a measurement reads what the roles allow.
Is self service the same as a limited user?
No. Self service is the lightest tier and covers only the user's own records. A Limited Professional user covers narrow transactional work inside a defined area, so the limited type costs more and allows more. Users who post documents for the business, even occasionally, belong there or higher.
How do you prove correct self service classification?
Keep per user activity logs, for example ST03N workload data, showing each reclassified user only performs self service tasks, together with the role assignments at the time. With that record you can answer an auditor with evidence instead of argument at the next measurement or true up.
When should you review self service assignments?
Before every renewal, at any conversion to S/4HANA or RISE, and after any reorganization. Staff change roles, and a self service user can drift into operational work that needs a higher type, just as a former clerk now doing only self service tasks can come down.