SAP S/4HANA user license types explained. Your user mix sets the FUE bill.

S/4HANA converts professional, functional and self service users into Full User Equivalents at 1.0, 0.2 and 0.0333 each. Your user mix drives the subscription cost far more than your headcount, and correcting the mix is where the recoverable money sits.

Which user license types does SAP S/4HANA use?

S/4HANA under RISE with SAP or S/4HANA Cloud has three user tiers, set by depth of access. Professional users sit in SAP's Advanced use category, functional users in Core use, and self service users in Self Service use. Each tier converts into Full User Equivalents (FUEs) at a fixed ratio, and SAP sizes your subscription on the FUE total.

The tier should reflect what a user does in the system, which SAP reads from the roles and authorizations assigned to that user. Job title and department do not enter into it. The table sets out what each tier covers and what it weighs.

Professional users (Advanced use)

These users hold broad operational access. They create and change master data and documents across modules, and some configure the system. SAP's definition of Advanced use extends to system administration and management roles, which is why it carries the full weight of 1.0 FUE per person.

Functional users (Core use)

Functional users transact within a defined scope. A receivables clerk posting cash, a planner running MRP for one plant or a warehouse operator confirming transfer orders all work hard in the system, but inside one area. Five of them make one FUE.

Self service users

Self service users act only on their own data: they submit requests and expenses, record time, approve items routed to them and report on their own records. Thirty of them make one FUE, so the ratio is written as 0.0333, sometimes rounded to 0.033.

Where do developers fit?

SAP counts developers separately. In SAP's RISE pricing, each Developer Access user converts at 2 FUEs, double a professional user. SAP Note 3333812 describes how metered developers are verified, so keep a named list and remove developer authorizations from anyone who no longer builds in the system.

Full Use Equivalent or Full User Equivalent?

They are the same unit. SAP's paperwork calls it a Full Use Equivalent, while account teams and the market say Full User Equivalent. Search your order form for both spellings, because the defined term is the one the contract uses.

The binding definitions sit in SAP's Service Description Guide, the service use descriptions behind your RISE or S/4HANA Cloud order. The slides the ratios were first presented on carry no contractual weight. Any tier review has to be argued from that guide.

How do you convert S/4HANA users into FUEs?

Multiply each population by its ratio and add the results. Because the weights fall so steeply, a large headcount collapses into a small FUE total when the mix reflects what people do.

A 1,250 person population lands at 124 FUEs. The self service tier holds 80 percent of the headcount and accounts for about a quarter of the cost.

Now take the same population with the kind of over assignment we find in practice. Move 60 of the functional users up to professional and the total rises by 48 FUEs, a 39 percent increase in the bill for no additional capability. Each of those 60 users now costs five times what the work requires.

What does a correction look like on a larger population?

Say a company converts 2,000 SAP users and SAP's initial mapping places 400 in Advanced, 600 in Core and 1,000 in Self Service. A review of transaction history then finds 120 professionals who work in a single area, 20 professionals who only approve, and 60 functional users who only submit and approve.

The review removes 126 FUEs, just under 23 percent of the subscription, and every user keeps the transactions they run. The 120 single area professionals account for 96 of them, because moving a user from professional to functional removes four fifths of that user's cost. Moving a user to self service removes almost all of it.

The FUE licensing guide covers the full calculation mechanics, and the FUE calculator runs your own numbers in minutes.

How do legacy ECC named users map to S/4HANA tiers?

By default, SAP lands anything that used to be a Professional named user in the Advanced tier. Migrations from ECC carry the old user list across at the top weighting unless someone argues each population down, so the over assignment is systematic.

ECC contracts usually hold several named user types, including Professional, Limited Professional and Employee Self Service users. The conversion is the one point where each of those populations gets priced again, and the table below shows where each group tends to land once you test it against what the users actually do.

On premises S/4HANA licensing kept named user types of its own, such as Professional Use, Functional Use and Productivity Use. That is where the market's professional and functional labels come from.

Our guides to mapping legacy SAP licenses to S/4HANA roles and SAP named user license types cover the older models, and the self service user guide covers the lightest tier in detail.

How do you decide which tier each user belongs in?

Start from behavior. For each user, ask which transactions they run, at what depth and in what scope. Three populations account for most of the recoverable money:

• The inherited professionals. Users carried across from ECC at the top tier because they held Professional named user licenses. Their current S/4HANA behavior should set the tier, and the license they were given in 2015 should not.
• The single scope operators. Users who transact intensively inside one functional area, such as warehouse, receivables or plant maintenance. Heavy use of one area does not make a user broad. These are the 25 to 40 percent of professionals whose correct tier is functional.
• The approvers and requesters. Managers who approve, staff who submit and occasional reporters. Their whole footprint is own data activity, and each one priced above self service pays thirty times the correct rate.

The evidence is transaction history: actual usage pulled from the system per user, then classified against the tier definitions in the Service Description Guide. SAP's account team will map by role catalog and history. The difference between the two mappings is what you negotiate.

Which reports show your current position?

• SLIM_USER_CLF_HELP. SAP's classification report in Private Cloud systems. It shows how each user is classified today. Apply the latest version of the SAP Note before you run it.
• Private Cloud Consumption card in SAP for Me. The metered FUE figure SAP holds for your subscription, with detail behind the metered value.
• ST03N workload statistics. Transaction usage per user over the retained period, which is the behavioral evidence for each reclassification.
• SUIM. The user information system, for listing which roles and authorizations each user holds.

Why usage logs alone will not lower your FUE count

The usual advice is to take usage logs to SAP and ask for users to be reclassified. We disagree with stopping there. SAP's FUE measurement reads the authorizations assigned through each user's roles, using a rule set SAP revises through versions of SAP Note 3113382.

A user who only approved requests last year but still holds posting authorizations measures as Core or Advanced. Use the usage evidence to redesign the roles, remove the authorizations the user never exercised, rerun the classification report, and negotiate from the measured result.

What have we seen in S/4HANA user mappings from 2024 to 2026?

Fredrik Filipsson benchmarked roughly 30 to 40 S/4HANA user mappings between 2024 and 2026. The professional tier was consistently over assigned against actual usage, in migrations and in steady state subscriptions alike.

• Professional over assignment. 20 to 35 percent of professional seats showed single scope or self service behavior in their transaction history and were priced at the full weight anyway.
• The functional fit. Functional access described the real work of 25 to 40 percent of the professional population.
• FUE recovered by correction. Reclassifying against evidence cut the FUE total by 10 to 25 percent, and no user lost access they actually used.

Timing explained most of it. The mix was set once, at migration or initial subscription, and never revisited, while the organization underneath changed every year.

The same 1,250 people can cost 124 FUEs or 172, depending only on how their tiers are mapped.

The customers that held their costs treated the tier mapping as a renewal document. They refreshed it against transaction history before every anniversary and argued from the contract definitions instead of the account team's role catalog. The wider subscription mechanics are in our S/4HANA licensing guide.

What will SAP's account team say about the user mix, and how should you answer?

Expect the conversation to push the mapping toward SAP's defaults. These are the lines we hear most often, with the replies that work.

Common lines and replies

1. "Your Professional users map to Advanced. That is the standard conversion." Ask for the per user classification output and the rule set version behind it. Then show which users in that list hold authorizations they have not used, and table your own mapping.
2. "Measurement is based on authorizations, so usage data does not matter." Agree on the measurement, then explain that the usage data is what drives your role redesign. Ask for the FUE quantity to be sized after the redesign, on the remeasured count.
3. "Size for the current count now and we will improve the discount." A larger discount on an inflated FUE quantity still pays for seats you do not need. Compare the two offers in dollars over the full term before you answer.
4. "You can clean up the mapping after go live." RISE subscriptions rarely allow the FUE quantity to be reduced during the term. A cleanup after signature only frees headroom you have already paid for.

What should your S/4HANA order form say about user tiers?

Write the tier rules into the order form while it is still open. These are the terms we ask for, and why each matters.

• Tier definitions by reference. Name the version of the Service Description Guide that defines Advanced, Core and Self Service use, so a later revision cannot move activities into a heavier tier during your term.
• Measurement method. State that FUE consumption is measured with the classification report and rule set in force at signing, and that you receive the per user output of every measurement.
• A correction window. If a measurement shows consumption above the contracted FUEs, you get a set period to adjust role assignments before any additional purchase is due.
• Price hold on additional FUEs. Any FUEs added during the term are priced at your contracted per FUE rate.
• Developer Access list. Developers are counted against a named list, because each one weighs twice a professional user and stale developer roles add up fast.

When should you review the S/4HANA user mix?

Review it at the conversion to S/4HANA or RISE and before every renewal, the two moments the order form is open. Role redesign takes time, so start well ahead of either date.

What to do next

1. Pull per user transaction history. Classify actual behavior against the tier definitions in your Service Description Guide, never against job titles.
2. Reclassify the single scope operators. The professionals who work one functional area belong in Core at one fifth of the weight. Redesign their roles so the measurement agrees.
3. Move the approvers and requesters to self service. Own data activity at thirty to one is the cheapest seat in the subscription.
4. Run the corrected mix through the FUE calculator. Put the difference, in FUEs and dollars, at the top of your renewal position.
5. Fix the mapping at the conversion or renewal. Do it while the order form is open, and write the tier definitions into it. The SAP practice runs the mapping and the negotiation with you, on your side of the table.

Frequently asked questions