SAP S/4HANA Licensing Guide 2026
Named-user types, engine metrics, indirect/digital access, and the economics of RISE with SAP — a buyer's guide to controlling cost and audit exposure as you move to S/4HANA before the 2027 ECC deadline.
Executive Summary
The migration from SAP ECC to S/4HANA is the largest licensing event most SAP customers will face this decade, and the deadline pressure of mainstream ECC maintenance ending in 2027 is itself a commercial lever SAP uses to shape deals. S/4HANA changes how SAP is licensed — new named-user categories, the FUE (Full Use Equivalent) model under RISE, and a formalized approach to indirect/digital access — and each change creates both a trap and an opportunity.
This guide explains the metrics, the Digital Access document model, and the RISE with SAP bundle, then sets out how to convert existing entitlements without overpaying. The core message: SAP conversions are negotiated, not calculated. The "contract conversion" SAP proposes is one of several paths, and it is rarely the cheapest for the customer.
1. The S/4HANA Licensing Model
S/4HANA on-premise is licensed through two intertwined dimensions: named users and engines (also called packages). Every human who accesses the system needs a named-user license of an appropriate type, and certain functional capabilities — payroll, specific industry solutions, high-volume processing — are licensed separately by a usage metric such as documents, revenue, or records. Getting the user classification right is the foundation of a defensible position, because SAP's default is to assume the most expensive category.
| User type | Intended for | Relative cost |
|---|---|---|
| Professional Use | Operational/configuration roles with broad access | Highest |
| Functional Use | Defined operational tasks, narrower scope | Medium |
| Productivity Use | Light/self-service and reporting access | Lower |
| Developer | Build/extend roles | Specialized |
Over-classification is the most common and most reversible source of overspend. A workforce dropped wholesale into Professional Use can cost multiples of the same workforce classified by actual role. Classification should be evidence-led, mapped from authorization roles and real transaction usage, not assigned by org chart convenience.
2. Indirect and Digital Access
Indirect access — third-party or custom applications reading or writing SAP data without a human SAP user — was for years SAP's most feared and least predictable audit area. SAP's Digital Access model attempts to standardize it by licensing nine document types (sales, invoice, purchase, service, financial, material, quality, time-management, and manufacturing documents) created in the system, rather than the indirect users behind them.
This is genuinely an improvement in predictability, but it introduces its own risk: a document-based estimate can be high if integrations create documents inefficiently, and SAP's Digital Access Adoption Program (DAAP) offers incentives that are time- and deal-bound. Customers should measure their actual document creation before accepting any estimate, and weigh Digital Access against retaining indirect-user licensing where that is cheaper for their integration pattern.
SAP's tooling can estimate Digital Access documents, but the estimate is a starting position. Document counts depend heavily on how integrations are designed — and reducing unnecessary document creation before measurement is a legitimate, often substantial, cost lever.
3. RISE with SAP and the FUE Model
RISE with SAP bundles S/4HANA Cloud, infrastructure, and managed services into a single subscription priced largely on the Full Use Equivalent (FUE) metric — a conversion that maps different user types into a common unit. RISE simplifies procurement and shifts capital to operating expense, but it also re-bases the relationship: existing perpetual entitlements and their paid-up maintenance are effectively traded for a subscription, and the FUE count plus the bundle scope become the new negotiation surface.