SAP S/4HANA Licensing Types Explained: Professional, Limited, and Self-Service Users
SAP S/4HANA’s licensing model can be complex, with different user categories carrying very different access rights and costs.
This advisory explains the three primary S/4HANA license types—Professional, Limited, and Self-Service—and how to map employees to the correct category.
IT executives will learn how to avoid overpaying by aligning each user’s role to the right license, ensuring broad access for power users while using cost-effective licenses for others.
In short, understanding the various SAP S/4HANA licensing types is crucial for controlling ERP costs and ensuring compliance.
Understanding S/4HANA User License Categories
In SAP S/4HANA, not all users are equal – license types are tiered based on the extent to which a person uses the system. This tiered approach allows enterprises to mix and match user licenses, rather than paying top dollar for every single user.
The main categories are:
- Professional Users: Full enterprise access across all modules and transactions. These are your power users – think senior analysts, finance managers, supply chain planners, or IT administrators who perform end-to-end processes without restrictions. A professional user license grants the broadest privileges (including configuration and cross-functional reporting) and, unsurprisingly, comes at the highest price point.
- Limited Users (Functional Users): Focused access restricted to specific business areas or modules. These users primarily work within a single functional domain – for example, a procurement clerk in purchasing, a warehouse supervisor in inventory management, or an HR specialist in personnel administration. Limited users can create and edit transactions only in their designated area. This license type costs significantly less than Professional and is ideal for roles that don’t need full system access.
- Self-Service Users: Very constrained access for simple self-service tasks. This typically applies to a broad base of employees who use SAP to enter timesheets, file expense reports, view pay stubs, or submit basic requests. They have no access to core business transactions beyond their data. Self-service licenses (often referred to as Employee Self-Service or ESS users) are the most cost-effective per user and can be offered in volume (sometimes even bundled in bulk packs), as these users individually add minimal load to the system.
Each category has clearly defined permissions. SAP’s standard license definitions outline exactly what modules or activities each user type can perform. Professional covers everything. Limited (sometimes called Functional or Limited Professional) covers a specific subset, sufficient for departmental roles. Self-service is minimal.
There are other niche categories (such as “Productivity” or Developer licenses), but Professional, Limited, and Self-Service are the core buckets that most employees will fall into. The goal is to provide every user with the access they need and no more, at a cost commensurate with their usage.
Professional Users: Full Access at a Premium
A Professional license is the “all-you-can-eat” option in S/4HANA. It enables full functionality across the ERP system.
A user with this license can run transactions in finance, procurement, sales, production – any module that’s part of your S/4HANA solution. Typically, only a minority of your SAP users require this level of access.
Examples include:
- A finance director who needs to generate company-wide financial reports, post journal entries, and also configure settings in Controlling.
- An SAP BASIS administrator or IT analyst with broad system access for support, customization, and cross-module troubleshooting.
- A supply chain manager oversees end-to-end processes from purchasing to manufacturing to distribution.
Due to their broad scope, Professional licenses are the most expensive.
This is where SAP generates a significant portion of its licensing revenue.
Cost impact: On a traditional price list, one professional user license might list in the thousands of dollars range (e.g., roughly $3,000–$6,000 per user as a one-time fee in on-premise scenarios, plus annual support).
In a subscription model, this could equate to around $ 200 or more per user per month. These figures can vary, but it’s clear that each Professional user significantly affects the IT budget. Therefore, you want to allocate these licenses only to users who truly need that full access.
Actionable insight:
Review who in your organization is tagged as a Professional user. Often, companies discover some staff have unnecessarily broad access (and a pricey license) even though their job could be done with a lower-level license.
By downgrading those users to a Limited license, you can save money – as long as their role doesn’t genuinely require the full enterprise scope.
However, be careful: if someone does need cross-functional capabilities, they must remain Professional, or you risk compliance issues (more on that later).
On-Premise vs. Cloud for SAP S/4HANA: Total Cost of Ownership Compared
Limited (Functional) Users: Focused Scope for Departmental Roles
A Limited user license (also known as Functional User or Limited Professional) offers a middle ground. It’s tailored for users who work within a single module or business function and do not require enterprise-wide access.
This is a common category for many business users. For example:
- A procurement specialist who creates purchase orders, goods receipts, and vendor records in the Materials Management (MM) module – but doesn’t touch Finance or Sales processes.
- A warehouse or production clerk who updates stock levels or records shop floor data in one plant’s context.
- An HR staff member managing employee records or payroll in the HCM module, without engaging in operations outside HR.
Limited users can still enter and edit transactional data, but only in their allowed area. Suppose they attempt to perform tasks outside their licensed scope (for example, a warehouse clerk attempting to post an accounting document).
In that case, it should be blocked by their authorizations – otherwise, that would violate the licensing terms.
Cost benefits:
Limited user licenses are considerably less expensive than Professional licenses.
Typically, they are priced around a few hundred to low thousands of dollars each (perhaps a $500–$1,500 list price on-premise), or on the order of tens of dollars per month in a cloud subscription.
In practical terms, you might afford 5–10 Limited users for the cost of one Professional. This can translate to significant savings when you have many users who only need limited access.
A key strategy in SAP license management is maximizing the number of people who can be categorized as Limited users (within reason).
By mapping employees to the lowest appropriate license type, you optimize your spend. Real-world example: A global manufacturer migrating to S/4HANA identified that out of 500 total users, only ~100 were true power users needing Professional licenses.
The other 400 were scoped to one department each, so they negotiated for 400 Limited user licenses. This mix saved them a significant sum up front and every year on support, compared to licensing all 500 as Professional by default.
However, note that “limited” truly means limited – you must design user roles in SAP such that these users cannot perform activities outside of their scope. SAP auditors will review the transactions executed by a Limited user.
Suppose those transactions are reserved for the Professional level. In that case, SAP can reclassify that user as Professional in an audit (meaning you’d owe the license difference and back maintenance for that user).
We’ll discuss avoiding this compliance trap in a later section.
Self-Service Users: Low-Cost Licenses for Light Touch Users
At the bottom of the hierarchy are Self-Service users, intended for employees who interact with S/4HANA in a very light way.
These users typically:
- Enter personal data or requests – for instance, recording their time sheet, updating their address, or submitting travel expenses.
- View information relevant to them, such as pay slips, benefits information, or team calendars.
- Possibly raise simple requests or approvals – e.g., a manager approving leave requests or a salesperson checking a customer order status (if those actions are read-only or very limited in scope).
Self-service users do not create core transactional data for the company beyond the forms they use for self-service.
They wouldn’t, for example, create a sales order, post an invoice, or modify a material master. In older SAP terminology, this is often referred to as Employee Self-Service (ESS) or Manager Self-Service (MSS) licensing.
Minimal cost: These licenses are priced very low to encourage licensing the entire workforce if needed. In some S/4HANA contracts, SAP might bundle a large number of ESS users for a nominal fee. For instance, you might see something like “ESS users at $100 per 100 users” or other bulk arrangements. In an enterprise agreement, the cost per Self-Service user could be as little as a few dollars per year.
The idea is that these users are so limited that charging full price would discourage companies from extending SAP to rank-and-file employees. SAP would rather have everyone in the system (for things like HR self-service) at a low entry cost.
From a cost management perspective, Self-Service users are rarely where you overpay – they’re cheap. The primary concern is ensuring that you correctly identify who qualifies as a self-service user versus those who require a higher level of support.
For example, a production line worker might primarily enter time on jobs (self-service), but if they occasionally also adjust inventory, they may need a Limited license.
Always double-check that none of your supposed “ESS users” are performing tasks that overlap with functional usage.
Mapping Roles to License Types (How to Avoid Overpaying)
One of the biggest challenges – and opportunities – in SAP S/4HANA licensing is mapping your job roles to the right license categories.
The goal is twofold: to minimize costs by avoiding “over-licensing” while also staying compliant by avoiding “under-licensing.” Achieving this balance requires a detailed understanding of what each user does in the system.
Here’s how to approach mapping roles to license types:
1. Analyze User Activities: Start by auditing what transactions and modules each user (or role) accesses. SAP provides tools like USMM and LAW (License Administration Workbench) to measure user activity. For example, if Joe is in Sales and only ever uses the Order Management transactions, that’s a strong indicator he can be a Limited user tied to the Sales module. If Mary occasionally runs company-wide financial reports or cross-module analytics, she might need a Professional license. Use actual usage data over job titles – sometimes a user’s system usage differs from their job description.
2. Classify by “Highest” Need: A user should be classified to the highest level of access they use. If someone does anything that requires a Professional license, you must count them as Professional even if 90% of their work is limited. For instance, an HR specialist might primarily handle HR tasks (Limited scope), but occasionally runs a global headcount report that touches multiple areas. That one task tips them into Professional territory. Rather than pay for a full license just for that, you might decide to restrict their access and have a true Professional user run that report for them. This kind of internal policy can avoid unnecessary professional licenses.
3. Role Design as a Control: Work closely with your SAP security and role design team. You can enforce license compliance by designing roles and authorizations effectively. If you have a “Limited Logistics User” role, configure it so that the role physically cannot execute transactions outside the logistics module. This way, even if someone tries, they are prevented – which both maintains compliance and ensures you’re getting what you paid for. In effect, your technical roles should map one-to-one with license types (e.g., a role for Professional users, roles for various Limited user groups, etc.). Clear definitions internally will prevent ambiguity.
4. Periodic True-Ups: Make license mapping an ongoing process, not a one-time set-and-forget. As people change positions or new functionality is added to your SAP system, review whether license assignments need to change. It’s common to perform an internal “true-up” or license audit annually (ahead of SAP’s official audit) to catch any users who have outgrown their license. Perhaps the clerk in Marketing was initially given a Professional license, but now only uses a CRM add-on tool – perhaps they no longer need to be considered Professional. Conversely, someone given a Limited license might have gradually accrued more responsibilities and now should be upgraded to Professional before an audit flags them.
5. Avoid Shelfware: Overpaying can also happen when you purchase far more licenses than you use. Enterprises sometimes overestimate their needs and buy, say, 300 Professional licenses, but end up using only 200. Those 100 are “shelfware” – an unnecessary expense (including 20% annual maintenance on each!). To avoid this, carefully map out current needs but also consider phased growth. It’s often better to slightly under-buy and add users later (or negotiate flexible terms) than to over-buy upfront and carry idle licenses. Keep an eye on unused accounts as well – if employees left the company or no longer use SAP, remove or retire those users so they aren’t counted in an audit.
By meticulously mapping roles to the appropriate SAP S/4HANA license type, you’ll ensure each user is licensed precisely – neither too high (wasting money) nor too low (risking compliance penalties). This is the cornerstone of cost-effective SAP license management.
Cost Implications and Optimizing the License Mix
To truly understand why user classification matters, IT leaders should consider the cost implications of each license type.
Below is a comparison that highlights how choosing the right mix of licenses can dramatically affect your SAP spend:
| User License Type | On-Premises License (One-Time List Price) | Cloud Subscription (Approx. per Year) |
|---|---|---|
| Professional User | $3,000 – $6,000 per user one-time (+20%/yr maintenance) | $2,400 – $3,000 per user/year (≈$200–$250 per month) |
| Limited (Functional) User | $500 – $1,500 per user one-time (+20%/yr maintenance) | $600 – $1,200 per user/year (≈$50–$100 per month) |
| Self-Service User | Typically a few hundred dollars or less (often sold in bulk packages) | Nominal – often bundled at low cost (e.g. large ESS blocks for minimal fees) |
Indicative pricing only – SAP’s official price list is confidential and street prices are usually much lower after negotiation.
As shown above, Professional users can cost 4-5 times more than Limited users, and Self-Service is cheaper still. This means that the license mix (i.e., the proportion of each type) is a major driver of total cost. Two companies with the same number of total users could have very different annual costs based on their mix of license types. For example, 100% Professional users versus 50/50 professional and limited could be a night-and-day difference in budget.
Optimizing the mix: Many organizations find that only 15-25% of their SAP user base truly needs professional-level, with the rest falling into limited or self-service. If your initial quote from SAP seems expensive, examine the assumed user distribution. It may be skewed toward more Professional licenses than necessary. Push back and model scenarios: “What if we only had 50 Professional and the rest Limited – what would that cost?” SAP’s sales team can provide quotes for different mixes, and this transparency often reveals cost trade-offs (e.g., one extra Professional might cost the same as five Limited users). Armed with this info, you can make a business case to adjust the license allocation.
Also, be aware that SAP’s rules historically discouraged classifying too many users as cheap licenses. In older contracts, there were sometimes ratio requirements (for instance, you couldn’t have 0 Professional and 500 Limited – a certain proportion had to be Professional). In modern S/4HANA licensing, SAP has relaxed strict ratios. However, common sense still applies: if you tell SAP that out of 500 users, only five are Professional, they might scrutinize whether that’s realistic for your operations. Ensure your license mix aligns with how a typical company uses SAP; if it deviates, be prepared to justify it (with usage data or by showing certain users only use a satellite system, etc.).
Negotiation and Discounts: The list prices in the table serve as starting points. In practice, large enterprises rarely pay list price. Discounts of 30–50% off (or more) are achievable, especially when you’re migrating from an older SAP ERP (ECC) to S/4HANA or making a significant new investment. Timing can be beneficial – the end of the quarter or fiscal year is when SAP is more flexible in closing deals. You might negotiate not just per-user pricing but also contract terms like price protections, the ability to swap license types (convert some Professional to multiple Limited licenses if needs change), and credits for unused legacy licenses. For example, if you already owned a bunch of SAP ECC licenses, SAP often provides conversion credits to S/4HANA licenses to reduce the cost of your new agreement.
Total Cost of Ownership (TCO): Remember that on-premise licenses incur an annual maintenance fee (~20% of the upfront cost) that accumulates over time, whereas subscriptions include support in the recurring fee. Over 5 years, the initial license plus maintenance for on-prem can be comparable to 5 years of subscription – it depends on negotiated discounts and how you value the flexibility of subscription vs. owning licenses. When optimizing costs, consider the horizon: If you plan to use S/4HANA for 10+ years without major changes, owning it with limited maintenance might be cheaper. If you anticipate needing to scale users up or down or possibly move to cloud infrastructure, a subscription (or RISE with SAP model) might offer more flexibility despite similar long-term spend.
In summary, to avoid overpaying: buy only what you need, and structure your license mix to match your organization’s actual usage patterns. The savings from rightsizing can be redirected to other IT initiatives, while still maintaining full coverage for SAP.
Compliance and Audit Considerations
No discussion of SAP licensing is complete without touching on compliance. SAP regularly audits its customers, and user licenses are a primary area of scrutiny. The worst-case scenario of trying to save money is getting hit with a surprise bill after an audit reveals that you have underlicensed some users.
Here’s how to stay safe:
- Misclassification Risks: As mentioned earlier, if a user is performing activities outside the bounds of their license type, SAP can flag this. For instance, if a “Limited” user runs a company-wide financial report or accesses configuration transactions, the audit will report them as needing a Professional license. The company would then be required to purchase that license (and possibly pay back maintenance fees for the period of unlicensed use). To prevent this, enforce strict role controls. Ideally, it should be technically impossible for a Limited user to do Professional-only tasks. Regularly review high-authorization roles to ensure they’re only assigned to Professional license holders.
- Inactive Users Count: It may be surprising, but even inactive or unused accounts can still count against your license totals if they remain in the system. SAP’s audit tools typically count every named user by license type. If you simply lock an old user ID but don’t delete it or classify it properly, an auditor may include it (assuming you should have had a license for it). Best practice is to regularly purge or formally retire accounts that are no longer needed. Develop an internal process for de-provisioning SAP access when employees leave or change roles; ensure licenses are not left attached to inactive users.
- Indirect Access: While our focus is on named user licenses, be aware of indirect use – scenarios where external systems or non-human processes interact with SAP data. This has its licensing model (SAP’s Digital Access documents approach), but it’s worth noting because sometimes companies try to avoid user licenses by funneling activity through external systems. SAP monitors this, and you could face compliance issues if, say, hundreds of customer portal users effectively use SAP in the background without proper licensing. The safer route is to address indirect access via SAP’s offered model (document-based licensing) or by acquiring the appropriate entitlements for those external users. The takeaway: Every SAP user requires a license – either a named user license or an appropriate indirect license.
- Audit Preparation: Don’t wait for SAP’s official audit notice to find out if you’re compliant. At least once a year, run your measurement using SAP’s license audit tools (USMM/SLAW) or a third-party software asset management tool. Reconcile the results with your purchases. If you discover a shortfall (e.g., you have 10 more Professional users in the system than you bought licenses for), you have an opportunity to address it proactively. It’s far better to voluntarily true-up or adjust usage than to be caught off guard. Similarly, you may find that you’re over-licensed (perhaps you bought 300 Limited, but only 250 are in use). You might be able to terminate maintenance on the unused portion or negotiate a swap for other needs – but only if you’re aware of it through an internal audit.
- Keep Documentation: Maintain clear records of your entitlements (what you purchased) and how you assigned them. During an audit, SAP will ask for user lists by license type. If you’ve been diligent, each user in the system is assigned the correct license type in SAP’s user master data. A common mistake is leaving some users as “generic” or uncategorized, which SAP’s tools then default to the Professional category (the most expensive) when counting. Avoid this by ensuring every user ID has a license type classification in the system. Also, document any special cases (like a single individual having two accounts for different purposes) to explain to auditors so they don’t count them twice.
Staying compliant with SAP S/4HANA licensing is a continuous effort.
By treating license management as an ongoing governance process – with regular reviews, clean-ups, and alignment among HR, IT, and procurement – you can significantly reduce the risk of a surprise audit.
And when you’re confident in your compliance, you’re in a stronger position to negotiate renewals and changes with SAP from a place of knowledge rather than fear.
Recommendations (Practical Tips for Optimization)
To wrap up, here are expert tips for managing SAP S/4HANA licenses effectively:
- Map License Needs Early: Before signing any SAP agreement or migrating users, map out your business roles to S/4HANA license types. Estimate how many Professional, Limited, and Self-Service users you truly need based on current job functions. This homework prevents overbuying licenses you won’t use.
- Right-Size License Assignments: Continuously align each user with the most cost-effective license that meets their requirements. Give Professional licenses only to true power users and decision-makers. Move everyone else to Limited or Self-Service as appropriate. This rightsizing should be revisited periodically (e.g., quarterly or semiannually) as roles and usage evolve.
- Use Data to Drive Decisions: Leverage SAP’s user audit reports or tools to identify usage patterns. If someone with a Professional license is only executing transactions in one module, consider downgrading them. Conversely, identify any Limited users generating errors or getting blocked – they may be candidates for an upgrade if their job requires more access.
- Clean Up Regularly: Implement a routine (at least annually) to remove or reassign licenses for departing employees, duplicate accounts, or inactive users. Reducing this “license bloat” ensures you’re not paying maintenance on users who aren’t using the system. It also makes audits smoother by minimizing irrelevant accounts.
- Negotiate for Flexibility: When dealing with SAP, don’t just haggle on price – negotiate terms that allow flexibility. For on-premise licenses, aim for the right to swap license types (e.g., trade 5 Limited for 1 Professional or vice versa) as needs change, and caps on maintenance fee increases. For cloud subscriptions, seek the ability to adjust user counts annually without huge penalties. A well-crafted contract can save money over the long term as your business changes.
- Monitor Indirect Usage: Although our focus is on named users, keep an eye on indirect access as well. Track interfaces and API usage. If you use SAP’s Digital Access (documents licensing) for external interactions, monitor consumption against your entitlements. This will prevent unforeseen costs associated with events like an influx of e-commerce orders or IoT data overwhelming your ERP.
- Engage Experts if Needed: SAP licensing is intricate. Consider bringing in third-party licensing consultants or utilizing software asset management tools, especially before significant contract negotiations or migrations. Experts can identify optimization angles and ensure you’re not missing any hidden compliance issues. The cost of an advisory service can be tiny compared to the potential savings on an SAP deal.
- Plan for Future Growth: When allocating licenses, think a few years ahead. If you expect your user count to grow or plan to implement new SAP modules, factor that into your licensing strategy. It might be more cost-effective to secure an extra buffer of licenses at a discount now (or lock in pricing for future additions) than to scramble later at possibly higher rates. Conversely, avoid overcommitting far beyond your near-term needs – try to align purchases with realistic adoption timelines.
By following these recommendations, CIOs and IT procurement leaders can ensure they maximize the value of their SAP S/4HANA investment without overspending or compromising compliance.
Checklist: 5 Actions to Take
For IT executives ready to act, here’s a simple step-by-step plan to get a handle on S/4HANA user licensing:
- Take Inventory of Users and Roles: Gather a current list of all SAP users in your organization and document their roles and the modules they access. Identify which users are currently classified as Professional, Limited, or Self-Service (or not classified at all).
- Match Usage to License Type: For each user or role, determine the license category to which they should be assigned based on their activities. Use SAP’s usage reports or interviews with department leads. Flag any discrepancies (e.g., someone in a minor role holding a Professional license, or a heavy cross-module user listed as Limited).
- Adjust Roles or License Assignments: Collaborate with your SAP security team to adjust authorizations so that each user’s access aligns with the intended license. This may mean restricting some users’ permissions to keep them within a Limited scope, or upgrading certain users to Professional if they truly need broader access. Update the license type classifications in SAP for each user accordingly.
- Optimize the License Count: Compare your updated license needs against what you’ve contracted. Do you have too many of one type and not enough of another? If you’re in an active contract negotiation or renewal, use this data to right-size your purchase. If mid-term, consider approaching SAP for an adjustment or use any contract flex provisions to redistribute licenses. Eliminate any unused licenses (retire user IDs if possible) to avoid counting them.
- Implement Ongoing Governance: Establish a governance process for SAP licensing to ensure ongoing compliance. This could include quarterly internal audits of user activity, a policy to review license types when employees change roles, and an annual reconciliation prior to the SAP audit. Assign clear ownership (e.g., a SAM manager or SAP basis team lead) to continuously monitor license compliance and optimize costs.
Following this checklist will put you on a proactive footing – ensuring your SAP S/4HANA licensing is always aligned with actual business usage and that any surprises do not catch you off guard.
FAQs
Q1: What’s the difference between Professional, Limited, and Self-Service SAP users?
A: These labels indicate how much of the SAP S/4HANA system a person can use. A Professional user can access all or most of the system’s functionality across modules – it’s meant for power users who need broad capabilities. Limited (or Functional) users are restricted to one domain or module (like only Finance, only Procurement, etc.), so they have a narrower scope at a lower cost. Self-service users have the smallest scope – usually just their data or very lightweight tasks (such as entering timesheets or viewing personal information). In essence, Professional = full access (high cost), Limited = partial access (mid cost), Self-Service = very minimal access (low cost).
Q2: How do we decide which license type a particular employee needs?
A: Determine the transactions and processes that the person will use in SAP. Suppose they require cross-departmental functionality or high-level functions (for example, a controller closing books or someone handling end-to-end order-to-cash processes). In that case, they likely need a Professional license. If they work in a specific area (like just warehouse management or just HR) and won’t venture beyond that, a Limited user license should suffice. Employees who use SAP solely for self-service or simple approvals can be designated as Self-Service users. It’s wise to start by mapping each job role in your company to an SAP usage profile, then assign the license type that covers that profile. When in doubt, err on the side of giving a user the lower license and restricting their access – you can always upgrade a license later if needed. Still, you don’t get money back for over-licensing someone who never uses the extra capabilities.
Q3: What if a user with a Limited license ends up doing something requiring a Professional license?
A: This is a compliance red flag. In day-to-day terms, the system might not automatically stop them if their roles allow it – which is why you should design roles carefully. Suppose it does happen (say you discover via audit logs that a Limited user ran an out-of-scope transaction). In that case, you should address it immediately: either remove that access or upgrade their license. If SAP auditors find it, they will likely demand you purchase a Professional license for that user retroactively, possibly with back-dated maintenance fees. Repeated or widespread misclassification can also hurt your credibility with SAP. It’s far better to prevent this scenario by ensuring each user’s authorization matches their license level. Some companies even implement license-based controls in SAP security: essentially, scripting or tools that ensure no Limited user ID can execute a Professional-level T-code.
Q4: How can we reduce our SAP S/4HANA licensing costs without violating compliance?
A: The key is optimization, not avoidance. First, make sure you’ve right-sized every user – no one should have a more expensive license type than necessary. This might involve downgrading some users from Professional to Limited if their usage is limited. Second, stay on top of license recycling – when someone leaves or a project ends, reassign or remove that license to avoid paying for unused licenses. Third, negotiate smartly with SAP: bundle users in bulk for discounts, request price protections, and align purchases with SAP’s sales incentives (such as year-end deals). Also, consider leveraging the mix of license types: for example, if certain occasional tasks are pushing many users into Professional licenses, see if you can centralize those tasks to fewer users and let others remain on Limited licenses. Finally, consider third-party tools or services that analyze SAP usage; they can often highlight hidden optimization opportunities (like a report showing 20 users with Pro licenses never used beyond the Limited scope). By taking these actions, many enterprises have trimmed 15-30% off their SAP license costs while staying fully compliant.
Q5: Do these user license types apply if we use SAP S/4HANA in the cloud (or under RISE with SAP)?
A: Yes, the concept of Professional vs. Limited vs. Self-Service users still exists in SAP’s cloud offerings – but the licensing measurement works a bit differently. In S/4HANA Cloud (including the RISE with SAP model), instead of buying individual named-user licenses outright, you typically purchase a subscription based on Full User Equivalents (FUEs). Under that system, each Professional, Limited (often referred to as “Core” in cloud terminology), or Self-Service user type is assigned a weight (for example, a Professional might be assigned 1.0 FUE, a Limited user 0.2 FUE, and a Self-Service user 0.033 FUE). You subscribe to a total FUE quota that covers your mix of users. So the idea of different user levels remains – a Professional user consumes more of your subscription quota than a Limited one. The good news is this provides flexibility: you can adjust the mix of user types as long as you stay within your total FUEs. The cost implications are similar (heavy users cost more, light users cost less); it’s just packaged in a cloud-friendly way. Whether on-premises or in the cloud, you should still classify users carefully. It’s even more crucial in the cloud model because if you overshoot your FUE allotment with too many heavy users, you’ll need to buy additional capacity. Bottom line: Professional, Limited, and Self-Service notions are alive and well in S/4HANA Cloud – they’re just accounted for via subscription metrics instead of traditional licenses.
Read about our SAP License Optimization Service.
