SAP licensing is one of the most complex and costly areas in enterprise software management. With over 400,000 customers in more than 180 countries, SAP dominates the ERP market, and its licensing model has evolved significantly since the company was founded in 1972 by five former IBM engineers in Walldorf, Germany. Understanding how SAP licenses work is essential for any organization running SAP, whether on-premise, in the cloud, or in a hybrid setup.
Named User Licensing
The foundation of SAP licensing is the Named User model. Every individual who accesses an SAP system must be assigned a Named User license. The type of license required depends on the level of access and authorizations granted to that user, not necessarily on what they actually do in the system. This is a critical distinction, especially in S/4HANA, where license measurement is authorization-based rather than usage-based.
SAP defines several user license types for on-premise S/4HANA deployments. Professional User licenses provide full access to all major modules and functions, enabling complex transactions and in-depth analytics. Functional User licenses cover core business processes and essential modules without the advanced capabilities of a Professional license. Productivity User licenses are designed for basic or self-service tasks such as updating personal data, recording time, or viewing pay slips. Developer User licenses are intended for individuals creating, modifying, or testing applications within SAP S/4HANA.
For customers on RISE with SAP (the cloud subscription model), the naming convention changes but the concept is similar. Professional Use becomes Advanced Use, Functional Use becomes Core Use, and Productivity Use becomes Self-Service Use. Understanding the mapping between on-premise and cloud user types is essential when planning a migration.
Named User licenses typically account for 40 to 70 percent of total SAP contract costs, making user type optimization one of the highest-impact areas for cost reduction.
Digital Access (Indirect Access)
One of the most significant shifts in SAP licensing came in 2018 when SAP introduced the Digital Access licensing model. This was largely a response to the landmark Diageo lawsuit, where SAP claimed that Salesforce users accessing SAP data constituted indirect access requiring additional licenses.
Digital Access covers scenarios where non-SAP systems, such as CRM platforms, e-commerce portals, IoT devices, or custom integrations, create, read, or update data in SAP. Rather than licensing each external user, SAP introduced a document-based pricing model built around nine document types.
The nine document types are Sales Documents, Invoice Documents, Purchase Documents, Manufacturing Documents, Material Documents, Quality Management Documents, Service and Maintenance Documents, Financial Documents, and HR Documents. Each document type has a multiplier that determines pricing. Organizations pay based on the volume of documents generated by external systems interacting with SAP.
This model replaced the previous approach of requiring Named User licenses for every individual who indirectly touched SAP data, which was widely seen as impractical and punitive. However, Digital Access still represents a significant compliance risk for organizations that have not properly assessed their third-party integrations.
Deployment Models and Pricing
SAP offers several deployment options, each with its own licensing and pricing structure.
On-premise licensing follows the traditional perpetual license model. Organizations pay an upfront license fee and then annual maintenance fees, which run between 19 and 22 percent of the license cost depending on the support tier. SAP Enterprise Support costs 22 percent annually, while SAP Standard Support costs 19 percent, though Standard Support is being gradually phased out.
RISE with SAP is SAP’s flagship cloud offering, a subscription-based model that bundles S/4HANA Cloud Private Edition with infrastructure, tools, and services. RISE uses a Full Use Equivalent (FUE) based pricing model, converting traditional Named User licenses into a subscription framework. This is SAP’s preferred path for customers migrating from ECC.
GROW with SAP targets the mid-market segment with S/4HANA Cloud Public Edition. It offers a more standardized, lower-cost entry point with less customization flexibility.
Hybrid models combine on-premise and cloud environments, allowing organizations to keep certain systems on-site while leveraging cloud scalability for others.
SAP Audits and Compliance
SAP enforces license compliance through its Global License Audit and Compliance (GLAC) team, which was recently rebranded to Global Adoption Insights and License Compliance. The GLAC team conducts two types of audits.
Basic audits involve self-measurement using SAP’s License Administration Workbench (LAW) tool. Customers run the LAW report, which captures system usage data, and submit the results to SAP. This is typically done annually as part of the standard maintenance agreement.
Enhanced audits are more thorough, SAP-led reviews where the GLAC team performs a deeper analysis of license consumption, user classifications, and indirect access patterns. These typically occur every three years or when SAP identifies potential compliance gaps.
Common compliance risks include user type misclassification (users with higher authorizations than their license type permits), unaccounted indirect or digital access from third-party integrations, over-licensing (paying for licenses that are not being used), and under-licensing (not having enough licenses to cover actual usage).
The 2027 ECC End-of-Life Deadline
One of the most pressing issues in the SAP ecosystem is the end of standard maintenance for SAP ECC, scheduled for December 31, 2027. After this date, SAP will no longer deliver patches, security fixes, or functional updates for ECC systems.
Organizations still running ECC face a critical decision: migrate to S/4HANA (on-premise or via RISE with SAP), pay a premium for extended maintenance, or explore third-party support options. Given that migrations typically take 18 to 36 months, the window for action is closing fast.
The migration to S/4HANA also triggers a licensing restructure. User types, metrics, and entitlements change during the conversion, creating both risks and opportunities. Organizations that approach the migration strategically can use it as an opportunity to right-size their license estate, eliminate unused entitlements, and negotiate better terms.
Key SAP Products to Track
Beyond the core ERP, SAP’s product portfolio includes several independently licensed solutions that organizations need to manage. SAP HANA (the in-memory database), SAP BW/4HANA (data warehousing), SAP SuccessFactors (HCM cloud), SAP Ariba (procurement), SAP Concur (travel and expense), SAP Analytics Cloud, SAP Business Technology Platform (BTP), SAP Business One (for SMBs), and SAP Business ByDesign (mid-market cloud) all carry their own licensing terms, metrics, and compliance requirements.
Effective SAP license management requires visibility across the entire product landscape, not just the core ERP system. Tools that can aggregate usage data, map authorizations to license types, and flag compliance gaps are essential for organizations looking to optimize their SAP spend.