Introduction – Why There’s So Much Confusion About SAP Licensing
SAP’s named user licensing can feel like a maze. If you’ve ever wondered, “What license does a read-only user need?” — you’re not alone. Even SAP customers with decades of experience still grapple with the same questions.
Why all the confusion? Because SAP’s definitions are complex, often inconsistent across products, and sometimes left open to interpretation. This ambiguity can lead to costly missteps – and SAP often benefits when customers are unsure. For more insights, read our overview article, SAP Named User Licensing Explained: Types, Costs, and Optimization.
Fortunately, clarity is possible. This FAQ cuts through the vendor jargon and myths with straight, no-nonsense answers to your most common SAP licensing questions.
Common Questions and Straight Answers
Q: Can two people share one SAP login?
A: No. SAP’s licensing model is strictly named user – one person per login, no sharing. Using one ID for multiple people violates your SAP contract and will trigger audit flags.
Quick Tip: If several employees need access, give each their own user ID and assign each the cheapest license that meets their needs. Never try to cut costs by sharing credentials – it’ll backfire.
Q: What license do I need for read-only users?
A: Usually, a low-tier license like an Employee Self-Service (ESS) user or a Limited Professional user, depending on what they need to view. For someone who only checks reports or HR info, an ESS license typically covers it.
Don’t: Pay for a full Professional license if the user isn’t executing transactions. Match the license to their activity – viewing data can usually be covered with an ESS or other limited license.
Q: What’s the difference between a Professional and Limited Professional user?
A: A Professional user license gives full access to all SAP modules and transactions. A Limited Professional user license restricts access to specific modules or business areas.
Here’s a quick comparison of the two license types:
| Aspect | Professional User | Limited Professional |
|---|---|---|
| Access Scope | Full access to all SAP modules and transactions. | Limited to specific modules or functions. |
| Typical Roles | Cross-functional power users. | Departmental users focused in one area (e.g. an HR clerk or warehouse supervisor). |
| License Cost | Highest cost tier (baseline 100%). | ~50% of Professional’s cost. |
Quick Tip: Don’t pay for a Professional license if a user’s job doesn’t require it. Usually only about 15–20% of users truly need a Professional license.
Q: Can I reassign an SAP license from one user to another?
A: Yes – SAP allows license reassignment. You can “recycle” a license from a departing or changing employee to a new user.
Note: You can reassign licenses freely, but only one user can use a given license at a time. Always deactivate the old user before assigning their license to someone new. Keep a simple log of reassignments (who had it, who now has it, when) as an audit trail.
Q: What happens if I delete inactive users?
A: Be careful – deleting a user outright removes the audit trail of that account. Never delete users without preserving evidence first.
Better: Don’t delete users at all – deactivate them instead. Lock the account so it no longer counts in license reports, but keep its history for audits. Make it a routine to do a quarterly cleanup: deactivate any users who left or are idle, and record it in a log for compliance.
Q: What license does a developer need?
A: A developer (someone who writes ABAP code or configures SAP) needs a Developer named user license. It’s one of the most expensive user types, because it grants access to development tools and transactions (like SE38, SE80 in the ABAP workbench) that regular users don’t get.
Why: SAP requires anyone accessing development and configuration functions to have this higher-tier license – even if they don’t use SAP for business tasks.
Cost Control Tip: Only assign Developer licenses to technical staff who truly need those programming or admin privileges. Don’t give an IT staffer a Developer license unless they really need to code.
Q: What’s the cheapest SAP license type?
A: The lowest-cost named user license is generally the Employee Self-Service (ESS) user. This is intended for basic self-service activities (like entering timesheets, viewing paystubs, or browsing internal data). An ESS license often costs only about 5–10% of what a Professional license costs, and it comes with very limited access (ESS users typically can’t perform any core transactions beyond viewing their own info).
Tip: Review your user list for folks who only do basic lookups or self-service. You can potentially downgrade many infrequent or view-only users to ESS licenses (or similar low-tier licenses) and save a lot of money.
Q: What happens if my licenses are misclassified (e.g., a user has the wrong license type)?
A: SAP auditors treat misclassified users as under-licensing. They’ll likely charge you for each such user at full Professional price, plus up to two years of back maintenance fees. In short, misclassification can become very expensive.
Fix: Don’t wait for SAP to find it. Regularly run your own internal license audit (using SAP’s LAW/USMM tools or a SAM tool) to catch and correct any misclassifications. Make sure each user’s license type matches what they actually do in the system. It’s much cheaper to adjust proactively than to pay SAP’s penalty prices.
How to clean up non-compliance, User License Audit & Cleanup: How to Keep SAP Accounts Compliant and Cost-Efficient.
Q: Can I have generic accounts for integrations or batch processing?
A: Yes – SAP allows technical or “system” accounts for things like integrations, background jobs, or testing. But you need to manage them carefully under the license rules. Each generic ID still counts as a named user, so give it an appropriate license type and keep it under control.
Rules for Generic IDs:
- Document each generic account and its purpose.
- Assign each a proper license type (e.g., technical or Limited user) that fits its purpose.
- Never allow multiple people to share one generic ID at the same time. Ideally, restrict these accounts to system use only (no direct human login whenever possible).
Audit Tip: Clearly label your technical accounts (for example, prefix them with “TECH_” or “INT_”) and keep a list of them. That way, it’s clear in an audit that these are system accounts (not unlicensed extra users).
Q: How often should I review user licenses?
A: Do a license review at least quarterly. Don’t wait for a yearly true-up or audit – things change fast. Users switch roles, leave the company, or start using new modules, which can cause your license assignments to get out of sync quickly.
Why: SAP’s audit tools (LAW/USMM) capture a snapshot of current usage. If you haven’t adjusted licenses in a long time, that snapshot could reveal lots of surprises (inactive accounts, mis-assigned licenses, etc.). Regular check-ups prevent that.
Tip: Set up a quarterly routine (with automated reminders) to remove or reassign licenses from people who have left, downgrade users who no longer need high-level access, and fix any role/license mismatches. Regular maintenance keeps you compliant.
Q: What’s the difference between Named User and Concurrent User models?
A: Named User licensing (SAP’s standard model) means each individual who accesses the system needs their own license. It’s one license per person, no matter how often or how little they use SAP. Concurrent User licensing means a pool of licenses is shared by multiple people, with only a limited number of users active at the same time. However, SAP does not allow this model for its main ERP systems.
Tip: Don’t mix up these concepts. If someone thinks 50 licenses can cover 100 users by sharing, they’re mistaken – SAP doesn’t work that way.
Q: What should I do before an SAP audit?
A: Before SAP’s audit, make sure you:
- Run your own LAW/USMM measurement internally to understand what SAP’s audit tools would find. This is your “first draft” – do it privately.
- Clean up obvious issues: deactivate or remove any users who shouldn’t be counted (e.g., duplicate or obsolete accounts). Ensure each remaining user is correctly licensed.
- Document special cases: Prepare a list of your generic accounts and any recent license reassignments, so you can readily explain them.
Pro Tip: Control the narrative. Never give SAP your raw, unclean user data. Run your own audit, fix issues, and only hand over a clean, defensible report.
Bonus: “Mini Myths” to Clear Up
Let’s bust a few quick myths that often trip up SAP customers:
❌ “Multiple people can share one license.” – No, one user per license, always.
❌ “Inactive accounts don’t need licenses.” – Wrong. If a user ID exists in the system, it can still be counted in an audit.
✅ “You can reassign licenses freely as long as you document it.” – Yes! SAP licenses aren’t tied to a person forever. Just make sure you retire the old user ID so you’re clearly within compliance.
✅ “It’s wise to run internal license measurements before SAP does.” – Absolutely. Finding and fixing issues yourself is much better than letting SAP find them.
Insight: “SAP doesn’t forgive confusion — it monetizes it. The more you clarify internally, the less you pay externally.”
5 Quick Reminders for Staying Compliant and Cost-Effective
- ✅ One user = one license. Never assume two people can share a login.
- ✅ Downgrade anyone not performing transactions. Don’t pay for Professional licenses if a user’s activity is basic or read-only.
- ✅ Recycle licenses from inactive accounts promptly. If someone leaves or a project ends, reclaim and reassign their license.
- ✅ Tag and track generic IDs. Make sure every account (even technical ones) is accounted for and given the right license type.
- ✅ Run internal license audits every quarter. Don’t wait for SAP’s official audit – find and fix issues on your own terms.
Read about our SAP Licensing Services.
