SAP named user types. Classify to cost.

SAP named user types form a price ladder from professional down to self service, and the type each user is assigned to drives both the annual cost and the audit risk the estate carries.

This guide is for CIOs and license managers governing an SAP named user estate in 2026. Read it with the named user negotiation paper and the SAP Practice page.

What are the SAP named user types?

SAP named users form a ladder from professional at the top through limited professional to employee and self service at the base. Each step trades capability for cost. SAP frames its model on the SAP ERP pages.

How does the ladder map to real roles?

Operational staff sit near the top, light transactional staff in the middle, and self service staff at the base. The aim is the lowest fitting type for each person.

• Professional: full operational access, highest price.
• Limited professional: narrow transactional scope.
• Employee and self service: own record tasks, lowest price.

How does type drive cost and audit risk?

Type sets price directly, so the mix drives the annual cost. It also sets audit risk, because usage above the assigned type is a finding. SAP agreement terms sit in the SAP agreements center.

Why does classification cut both ways?

Over classification wastes money. Under classification creates exposure. A defensible mapping from measured usage protects both sides at once.

How do you govern named user classification?

Governance keeps the mix correct as roles change. Set a review cadence, classify from usage, and hold evidence for each assignment. SAP cloud direction is covered in SAP news.

What cadence keeps the mix honest?

An annual review before renewal, plus a check after any reorganization, keeps drift in check. Most estates we see had not reviewed in years.

• Annual review: classify before each renewal.
• Event triggers: recheck after reorganizations.
• Evidence trail: keep usage proof per user.

What is the CIO level value at stake?

Across a large estate the named user line is one of the biggest SAP costs a CIO controls directly. Correct classification turns it into a managed number rather than a default one.

Where the common advice on SAP named user types is wrong

The standard view is that named user classification is a back office hygiene task with little strategic value. We disagree. Across the named user estates Fredrik Filipsson reviewed in 2024 to 2025, classification had gone unreviewed for 2 to 4 years and the professional tier was over assigned by 20 to 40 percent. The buyer side move is to treat classification as a recurring governance control, not a one off cleanup. Correcting the mix cut named user cost by 15 to 30 percent on these estates, and a yearly cadence keeps the saving from leaking back. Hygiene done on schedule is a strategy.

Every named user type is a price. The CIO question is not how many users you have, but which type each one truly needs.

What to do next

1. Export every named user with the assigned type.
2. Pull usage and map each user to the lowest fitting type.
3. Quantify the cost of current over classification.
4. Correct the clear cases and hold the evidence.
5. Set an annual classification review before renewal.
6. Add event triggers after reorganizations.
7. Carry the corrected mix into the next renewal.

White Paper · SAP

SAP named user licenses. The user classification audit

Read it free.

Read the white paper

Frequently asked questions

What are the SAP named user types?

SAP named user types form a ladder from professional at the top through limited professional to employee and self service at the base. Each type carries its own price and access scope.

Which named user type is the most expensive?

The professional user is the most expensive type because it grants full operational access. Self service is the least expensive, covering only own record tasks.

How does classification drive SAP cost?

Type sets price directly, so the user mix drives the annual cost. Placing each user on the lowest fitting type lowers the total without removing anyone.

How does classification affect audit risk?

Under classification creates exposure when usage exceeds the assigned type, while over classification wastes budget. A measured mapping protects both the audit position and the cost.

How often should a CIO review classification?

Review classification annually before renewal and after any reorganization. On most estates we see, the mapping had not been reviewed for two to four years.

How much can correct classification save?

Across our reviews, correcting the classification cut named user cost by 15 to 30 percent. The saving comes from professional users wrongly assigned against their actual work.

What governance keeps the mix correct?

An annual review, event triggers after reorganizations, and a usage evidence trail per user keep the mix correct. Governance on a cadence stops drift from returning.

Is named user classification a strategic task?

Yes. The named user line is one of the largest SAP costs a CIO controls directly, so classification governance turns a default cost into a managed one.