LICENSEWARE
Contribute

Quick guide to SAP S/4HANA Licensing

From the LICENSEWARE WikiLast edited Archive

Archive. This is an archived LICENSEWARE Wiki page, kept as a source. It is not a cited encyclopedia article and may contain unsourced or outdated claims. Use the encyclopedia articles for current, cited terms.

Archive: this is an archived LICENSEWARE Wiki article from the SAP White Papers gallery, last edited 2026-02-21, kept as a source. It is not an encyclopedia article and may contain unsourced or outdated claims. For current, cited terms see SAP Named User and Digital Access licensing.

On This Page

SAP S/4HANA is the core of SAP’s modern ERP strategy, and its licensing is a different beast compared to the old ECC world. Whether you’re migrating from ECC or starting fresh, understanding how S/4HANA licensing works is non-negotiable. Get it wrong, and you’re either burning cash on shelfware or walking into an audit with a massive compliance gap.

S/4HANA On-Premise: The Named User Game

For on-premise deployments, S/4HANA licensing still revolves around the classic Named User model, but with a critical twist. Unlike ECC, where licensing was often a mix of usage and authorizations, S/4HANA is almost entirely authorization-based. This means a user’s license type is determined by the roles and permissions they are granted, not what they actually do. If you give a user Professional-level access, you pay for a Professional license, even if they only run a few reports a week.

Here are the key on-premise user types you need to know:

  • Professional User: The top-tier license. Grants full access to all S/4HANA modules and functions. This is for your power users, admins, and anyone who needs to perform complex, cross-functional tasks.
  • Functional User: The standard business user. Provides access to core business processes and essential modules within a specific functional area, like finance or logistics. Less powerful than a Professional user, but still covers the majority of day-to-day ERP activities.
  • Productivity User: For light, self-service tasks. Think time recording, travel expense submission, or viewing personal HR data. These are your casual users who don’t live in SAP but need to interact with it for specific, limited tasks.
  • Developer User: For the tech team. This license is required for anyone using SAP’s development tools to create, modify, or test applications within the S/4HANA environment.

One of the biggest changes with S/4HANA is that you only need to license users who access the Digital Core. Users who only access specific “Package” solutions (like SuccessFactors or Ariba) that are integrated with S/4HANA do not require a separate S/4HANA Named User license. This is a significant departure from the old model and can lead to major cost savings if managed correctly.

S/4HANA Cloud (RISE & GROW): The FUE Model

In the cloud, SAP throws out the traditional Named User model and replaces it with Full Use Equivalents (FUEs). This is a subscription-based model where you purchase a pool of FUE capacity, and different user types consume that capacity at different rates. It’s more flexible than the on-prem model but requires careful management.

Here’s how the FUE weightings break down:

  • Advanced Use (1.0 FUE): The equivalent of an on-prem Professional User. This is your baseline, full-power user.
  • Core Use (0.2 FUE): Similar to a Functional User. Five Core Use users consume the same capacity as one Advanced Use user.
  • Self-Service Use (0.033 FUE): The cloud version of a Productivity User. You can have approximately 30 Self-Service users for the price of one Advanced user.
  • Developer Use (2.0 FUE): Developers are expensive in the cloud. One Developer consumes the same capacity as two Advanced users, reflecting their deep system access.

The beauty of the FUE model is its flexibility. A pool of 100 FUEs could support 100 Advanced users, 500 Core users, or nearly 3,000 Self-Service users—or, more realistically, a mix of all three. This eliminates the problem of having unused licenses in one category while being short in another. The downside? Authorization creep is even more dangerous. Accidentally giving a user a single extra permission can instantly flip them from a 0.2 FUE Core user to a 1.0 FUE Advanced user, burning through your FUE pool five times faster.

Migrating from ECC to S/4HANA

When you move from ECC to S/4HANA, you have two main options for your licenses: a contract conversion or a product conversion.

  • Contract Conversion: You trade in all your old ECC licenses and receive a credit towards a new S/4HANA contract. This is a full reset. It’s an opportunity to right-size your license estate and negotiate fresh terms, but it also means you’re fully committed to the S/4HANA licensing model from day one.
  • Product Conversion: You keep your existing contract but convert your ECC licenses to their S/4HANA equivalents. This is a more straightforward path, but it can be less flexible. SAP provides “compatibility packs” that allow you to continue using some of your old ECC functionalities in S/4HANA for a limited time, but these have an expiration date.

During the transition, SAP typically grants dual-use rights, allowing you to run both your old ECC system and your new S/4HANA environment in parallel without having to pay for two sets of licenses. This is critical for a phased rollout, but make sure you understand the terms and duration of these rights.

The migration is the perfect time to optimize. Before you convert, analyze your actual usage in ECC. Who really needs Professional access? How many users are dormant? Cleaning up your user classifications and eliminating shelfware before you move to S/4HANA can save you millions in the long run. Don’t just lift-and-shift your old, bloated license set—use the migration as a catalyst for a full-scale optimization.

See also

Esc