SAP Licensing Glossary

SAP's proprietary programming language used to develop custom applications, reports, and enhancements within SAP systems. ABAP developers require Developer User licences in the SAP Named User model. Relevant in audits because systems with many custom ABAP objects are harder for SAP to measure and therefore harder to audit accurately.

Provisions within SAP's Master Agreement that determine whether subsidiaries, joint ventures, or group companies can use the parent organisation's SAP licences. SAP's default position is that affiliates require separate licences unless explicitly included. A well-negotiated agreement should define the exact list of included affiliates and the process for adding new entities — particularly important ahead of M&A activity.

A licence metric used for specific SAP products where the number of users is not the relevant measure. Engine licences are typically priced by capacity, transaction volume, or installation count. Common in SAP extended warehouse management (EWM), transportation management (TM), and manufacturing execution. Engine licences are often misunderstood and frequently misreported in audits.

SAP's cloud-based procurement and supply chain management platform, acquired in 2012. Licenced separately from core ERP under a subscription model based on spend under management or user metrics. Ariba's integration with S/4HANA can trigger Digital Access document charges when procurement documents flow between systems. See our SAP Ariba licensing guide.

Americas' SAP Users' Group — the largest SAP user organisation in North America. ASUG membership provides access to benchmarking data, SAP product roadmaps, and peer networking. Relevant to procurement because SAP monitors which customers are active in user groups and factors group participation into commercial relationship management. See also: DSAG, UKISUG.

The estimated financial value of an organisation's licence compliance shortfall — the difference between licences contracted and licences required based on actual usage. SAP's initial audit claims typically overstate exposure by 3–5× the true figure due to USMM overcounting, contestable user classifications, and aggressive interpretation of indirect access rules. Independent expert review consistently reduces claimed exposure. See our SAP audit defence service.

SAP's demand for payment to cover historical licence usage that exceeded contracted entitlements. Back-licence claims cover the period from when unauthorised usage began (as measured by SAP) to the audit measurement date. SAP calculates back-licence claims using current list price, not the price originally contracted, which inflates the claim significantly. Every element of a back-licence claim is negotiable and challengeable.

An SAP system account used for automated processes, scheduled jobs, and batch processing — not interactive human use. Batch users should not require Named User licences under SAP's licensing terms if they are purely technical accounts with no human interaction. However, SAP's USMM tool may include batch users in measurement counts, creating false exposure. Proper configuration and documentation of batch user accounts is essential audit preparation.

The schedule attached to an SAP Order Form that lists every licensed product, the quantity contracted, and the corresponding annual maintenance fees. The BoM is the definitive record of what you have purchased. Common problems include products added to BoMs that were never requested (SAP-initiated additions), outdated quantities, and products listed at incorrect licence types. Review every BoM line before countersigning any SAP contract document.

SAP's integration, extension, and data management platform. BTP licences are structured around credits (the consumption currency), service plans (Free, Metered, Subscription), and global accounts. BTP credits are included in RISE with SAP contracts, but the allocation is typically insufficient for enterprise integration architectures. 70% of customers with BTP credits in their RISE deals never fully consume them, which SAP uses as a benchmark — not as evidence you have enough. See our SAP BTP licensing guide.

A provision in SAP's Master Agreement that gives SAP the right to renegotiate, terminate, or modify licence terms when there is a change in the customer's ownership or corporate control. SAP uses change of control clauses aggressively in M&A situations to demand new licences, price uplift, or migration to cloud products. Negotiating precise definitions of "material change of control" and carve-outs for internal restructuring is essential in any SAP contract. See our guide on SAP change of control clauses.

SAP S/4HANA deployed on a hyperscaler infrastructure (AWS, Azure, GCP) and managed by SAP — the primary RISE with SAP delivery model. Sometimes called "Private Cloud Edition" or PCE. Licence terms differ from on-premise S/4HANA: subscription-based, bundled with infrastructure and support, and with specific contractual terms around customisation, data portability, and exit. See our S/4HANA Cloud vs On-Premise comparison.

The difference between an organisation's measured licence usage (as determined by USMM or LAW) and their contracted licence entitlement. A positive compliance gap means you have more usage than licences contracted. A negative gap means you have unused (shelfware) licences. SAP's initial audit report always presents the compliance gap in its most unfavourable form — using aggressive user classifications and maximum possible indirect access charges. Independent review typically reduces the stated gap significantly.

SAP's cloud travel and expense management product. Licenced on a per-user subscription basis, typically as "Concur Travel", "Concur Expense", or combined bundles. Integration between Concur and SAP ERP (for financial posting) may trigger Digital Access charges for financial accounting documents. See our SAP Concur licensing guide.

An SAP Named User licence type authorising the holder to create, modify, and test ABAP programs, workflows, and configurations in SAP systems. Developer users carry a significant licence cost premium — typically 3–5× a standard Professional licence. A common audit finding is that users with Developer access in production or quality systems have not been separately licenced. Developer users in non-production systems are covered by the same Developer licence if the user is the same person.

SAP's licensing model for non-human access to SAP — specifically, transactions created in SAP by third-party systems via interfaces and integrations. Digital Access is charged per document type, not per user. The nine chargeable document types are: Sales Orders, Purchase Orders, Delivery Notes, Invoices (Customer), Purchase Invoices, Material Documents, Financial Accounting Documents, Plant Maintenance Orders, and Quality Management Notifications. This model replaced the older "indirect access" Named User approach in 2018, but legacy indirect access claims still occur. See our Digital Access licensing guide.

Deutschsprachige SAP-Anwendergruppe — the German-speaking SAP user group and one of the most influential customer advocacy organisations in the SAP ecosystem. DSAG has a history of challenging SAP on pricing, audit practices, and product decisions. Membership provides benchmarking data and negotiating intelligence. Active DSAG members consistently negotiate better commercial terms from SAP than non-members. See also: ASUG, UKISUG.

SAP's legacy ERP platform, also known as SAP ECC or SAP R/3. SAP announced end of mainstream maintenance for ECC on 31 December 2027, with extended maintenance available through 2030 at additional cost. Approximately 85% of SAP's installed base was still running ECC as of 2025. The ECC migration deadline is the single most powerful commercial lever available to enterprise buyers in SAP negotiations. See our SAP ECC end of maintenance guide.

A large, consolidated SAP licensing contract that bundles multiple products, user types, and maintenance into a single all-inclusive deal. ELAs typically offer lower per-unit pricing in exchange for a larger total commitment and multi-year term. The appeal of an ELA is simplicity; the risk is that ELA pricing is often built on inflated consumption assumptions, and the "unlimited use" provisions are more restricted than they appear. Before signing an ELA, independent modelling of your actual licence requirements is essential. See our SAP ELA advisory service.

The current state of an organisation's SAP licence entitlements as held in SAP's systems — the official record of what you have purchased, at what quantity, and for what products. Your ELP is maintained in SAP's Customer Portal (SAP for Me) and is the starting point for any audit measurement. A clean, accurate ELP is essential for audit defence, as discrepancies between ELP and Order Forms are common and can create false compliance gaps.

An SAP Named User licence type for employees accessing SAP exclusively for self-service HR functions: viewing payslips, submitting leave requests, recording working time, and accessing Employee Self-Service (ESS) or Manager Self-Service (MSS) scenarios. Employee users are significantly cheaper than Professional or Limited Professional licences. A common cost reduction opportunity is identifying users classified as Limited Professional or Professional who exclusively use Employee-scope functions.

SAP's premium support tier, charged at 22% of net licence value annually. Enterprise Support replaced Standard Support as SAP's default offering in 2009. It includes 24/7 technical support, access to SAP's support portal, and SAP ActiveGlobal Support services. Enterprise Support is typically the largest annual line item in an SAP budget after the initial licence cost. Organisations can negotiate maintenance fee caps or explore third-party alternatives. See our SAP Enterprise Support alternatives guide.

SAP's cloud-based Vendor Management System for contingent workforce and services procurement. Licenced on a per-user or transaction basis under separate cloud subscription agreements. Fieldglass integration with SAP ERP can trigger Digital Access charges. See our Fieldglass licensing guide.

SAP's modern user interface framework, replacing the legacy SAP GUI with browser-based, role-based applications. Fiori is included in S/4HANA licences and does not require separate licensing for standard use. However, certain Fiori apps require specific SAP BTP services that may consume credits. Organisations migrating from SAP GUI to Fiori should confirm which apps are included in their S/4HANA licence before deployment. See our Fiori licensing guide.

A normalisation metric used in some SAP licence models to convert different user types into equivalent "full use" units. FUE calculations apply weighting factors to different user types — for example, 1 Professional user = 1 FUE, while 1 Limited Professional = 0.4 FUE. FUE totals determine overall licence cost in models that use this metric. See our detailed guide on SAP Full-Use Equivalent licensing.

A legacy SAP user classification used in older contracts for users who perform a defined, limited set of business transactions. The Functional User type has been largely superseded by the Limited Professional and Employee user types in current SAP licensing models, but may still appear in older Order Forms and legacy contract schedules.

The top-level organisational unit in SAP BTP, containing all subaccounts, credits, and service entitlements. Global accounts hold your BTP credit balance. Credit consumption is tracked at the subaccount level but deducted from the global account pool. Understanding your global account hierarchy is essential for BTP cost management and audit preparation.

SAP's suite of applications for access control, process control, audit management, and risk management. GRC is licenced separately from the core ERP system, with specific user types and engine metrics. Access Control (AC), Process Control (PC), and Risk Management (RM) modules are each licenced independently. See our SAP GRC licensing guide.

SAP's cloud ERP package targeting mid-market and growth companies, built on S/4HANA Cloud (Public Edition). GROW uses a subscription model with per-user pricing and fixed implementation methodology. Unlike RISE (which targets enterprise customers migrating from on-premise), GROW is designed for greenfield deployments. See our GROW with SAP guide.

SAP's in-memory database platform, mandatory for S/4HANA deployments. HANA licencing is measured in memory capacity (GB or TB) under either Runtime (bundled with S/4HANA, limited to SAP workloads) or Full-Use (broader use rights) editions. Runtime HANA licences cannot be used for non-SAP workloads — a common compliance trap for organisations running custom databases on HANA infrastructure. See our SAP HANA licensing guide.

SAP's cloud-based supply chain planning application, replacing APO (Advanced Planner and Optimizer). Licenced on a per-user or capacity basis under cloud subscription. IBP integration with S/4HANA for demand signals and supply responses may involve SAP BTP services. See our SAP IBP licensing guide.

The use of SAP software by a third-party system or application without a direct SAP Named User licence. Under the pre-2018 indirect access model, every non-human device or system accessing SAP required a Named User licence. SAP's indirect access claims generated over $1 billion in additional licence revenue between 2015 and 2018, including landmark cases. In 2018, SAP replaced indirect access with the Digital Access model for new document creation — but legacy indirect access claims still arise under older contract language. See our SAP indirect access guide.

SAP's BTP-based integration platform as a service, replacing SAP Process Integration (PI) and Process Orchestration (PO). Licenced via BTP credits under the Integration Suite service. Integration Suite is a key component of most S/4HANA migration architectures — and its credit consumption is frequently underestimated in RISE contract proposals. See our Integration Suite licensing guide.

SAP's generative AI assistant embedded across SAP products including S/4HANA, SuccessFactors, and Ariba. Joule is being positioned as an AI layer across the SAP portfolio. Licensing for Joule and SAP's wider AI capabilities is evolving — currently partially included with certain subscription tiers and partially metered via BTP credits. Enterprises should negotiate clear AI feature licensing terms before they become commercially material. See our SAP Joule and AI licensing guide.

SAP's consolidation tool for collecting user and system measurement data from multiple SAP systems into a central landscape measurement. LAW aggregates USMM outputs from individual systems and de-duplicates users who access multiple systems, presenting a consolidated licence position. LAW output is used in enhanced audits to build the Compliance Report. Unlike USMM (which runs on individual systems), LAW operates at the landscape level and requires landscape administrator access. See our SAP LAW technical guide.

Enterprise architecture management platform acquired by SAP in 2023. LeanIX helps organisations manage application portfolios, IT transformations, and technology roadmaps. Licenced as a SaaS subscription with per-user or per-application metrics. See our SAP LeanIX licensing guide.

An SAP Named User licence type for users who perform a specific, limited set of business transactions — typically single-function roles like purchase order approvers, goods receipt processors, or timesheet submitters. Limited Professional licences cost approximately 40% of a Professional user licence. A key cost optimisation lever is identifying users classified as Professional who only perform Limited Professional-scope activities. See our SAP Named User types guide.

A contractual mechanism allowing an organisation to return unused SAP licences and receive a corresponding reduction in annual maintenance fees. SAP's Licence Bank programme allows customers to deposit licences they no longer need and reduce their maintenance obligation. The terms — including which licences are eligible, the credit value, and the timeline — are highly negotiable. See our SAP Licence Bank guide.

The overarching contract between an organisation and SAP SE that governs all licence purchases, support obligations, and the parties' rights and responsibilities. Also referred to as the General Terms and Conditions (GTC) or Software Licence Agreement. The Master Agreement is supplemented by Order Forms (which specify what is purchased) and Support Maintenance Schedules (which govern maintenance terms). Every enterprise SAP customer has a Master Agreement — often signed many years ago, rarely reviewed, and frequently containing clauses that can be challenged.

The process of measuring SAP licence usage across an organisation's systems using SAP tools (USMM, LAW) to determine the Effective License Position. System measurements are required by SAP contracts annually. SAP uses measurement data in both self-service (STAR/SLAW) and audit-driven (enhanced audit) contexts. The data submitted in system measurements feeds SAP's commercial intelligence on your organisation. See our guide on what to share and withhold in SAP system measurements.

SAP's standard licensing model for human access to SAP systems. A Named User licence is assigned to a specific individual identified by their SAP user ID. The five main Named User types are: Professional (full access), Limited Professional (restricted function set), Employee (self-service only), Developer (development and configuration), and Test (non-production testing). Named User licences cannot be shared between individuals. Unused Named User licences are counted as contracted and charged maintenance fees regardless of use.

The transactional document issued under SAP's Master Agreement that records specific purchases — products, quantities, licence types, prices, and contract terms for a particular transaction. Order Forms incorporate the Master Agreement's terms by reference. Reviewing every Order Form before signature is essential: SAP frequently includes unagreed additions, incorrectly priced line items, and unfavourable terms inserted as standard. A red-lined Order Form is a normal part of any SAP negotiation.

An SAP licensing model for certain functional modules where access rights are granted to a defined package of transactions rather than to individual users. Package licences are measured by the number of users who access the package, or by a technical metric specific to that module. Common in industry-specific SAP solutions (IS-U for utilities, IS-Retail, IS-Oil & Gas). Package licence auditing is complex because USMM does not natively measure all package transactions accurately.

SAP's premium support tier above Enterprise Support. Preferred Success includes a dedicated Customer Success Manager, proactive health checks, and accelerated support response. Charged as an uplift on top of the standard 22% Enterprise Support fee. Before purchasing Preferred Success, organisations should benchmark whether the additional services justify the cost — many do not. See our Preferred Success guide.

The highest-tier SAP Named User licence type, granting unrestricted access to all SAP application functionality. Professional users are the most expensive user type and represent the largest component of most enterprise SAP licence bills. SAP's USMM tool defaults to classifying ambiguous user profiles as Professional — overstating Professional user counts is the primary driver of audit exposure for most organisations. See our detailed SAP Named User types guide.

The largest independent provider of third-party SAP support, offering an alternative to SAP's Enterprise Support at significantly reduced cost (typically 50% of SAP's maintenance fee). Rimini Street provides technical support, regulatory updates, and performance tuning for SAP ECC and other platforms. Moving to Rimini Street eliminates the ability to deploy future SAP patches and product updates — a decision that must be weighed against the cost savings. See our independent maintenance comparison.

SAP's bundled cloud ERP offering, launched in 2021, combining S/4HANA Cloud Private Edition, SAP BTP credits, business process intelligence (Signavio), and SAP Enterprise Support in a single subscription contract. RISE is SAP's primary vehicle for migrating customers from on-premise ECC to cloud. The RISE bundle obscures individual component pricing, making independent cost analysis essential. Average overpayment on RISE contracts without independent review is 20–40%. See our RISE with SAP guide and analysis of RISE hidden costs.

SAP's next-generation ERP platform, built natively on SAP HANA in-memory database. S/4HANA is available as on-premise (perpetual licence), cloud public edition (GROW), and cloud private edition (RISE). The licence model for S/4HANA differs materially from SAP ECC — user types are restructured, some licence categories are eliminated, and new mandatory components are added. Migration from ECC to S/4HANA almost always results in licence cost uplift unless carefully pre-negotiated. See our S/4HANA licensing guide.

SAP's cloud-based business intelligence and planning platform. SAC is licenced on a per-user basis with distinct user types: Business Intelligence Users, Planning Users, and Predictive (data scientist) Users. SAC's integration with S/4HANA for live data connectivity may require additional BTP service entitlements. See our SAP Analytics Cloud licensing guide.

An SAP system account used for technical system-to-system communication, interface processing, and RFC connections — not human users. Service users should be excluded from Named User licence counts. However, USMM may capture service users in measurement outputs if they are improperly configured or if their usage patterns are indistinguishable from interactive users. Proper documentation of all service users and their purpose is essential audit preparation.

SAP licences that have been contracted and are generating annual maintenance fees but are not deployed or actively used. Shelfware is endemic in enterprise SAP estates — typically 15–30% of contracted licences are unused at any given time. Shelfware represents a direct negotiation asset: evidence of unused licences can be used to challenge renewal pricing, seek Licence Bank deposits, or offset new product requirements. See our SAP shelfware guide.

SAP's process intelligence and mining platform, acquired in 2021. Signavio is included in RISE with SAP bundles (as "Business Process Intelligence") and available standalone. Licenced by user count and the volume of process data analysed. See our SAP Signavio licensing guide.

SAP's self-declaration portals for annual licence measurement submission. STAR (SAP Technical Access Registry) and SLAW (SAP Licence Audit Workbench) are the tools through which customers submit their annual system measurement data to SAP without a full audit. The data submitted via STAR/SLAW is used commercially — SAP's account team receives this data and uses it to assess upsell opportunities. See our guide on what to share and withhold in SAP self-declarations.

A contractual mechanism in SAP deals where credits are accumulated from one deal and can be applied to future product purchases. Software credits are often offered as part of renewal negotiations to offset the cost of new cloud products. The terms governing credit accumulation, expiry, and eligible products are highly negotiable and frequently unfavourable in SAP's standard proposals. See our SAP software credits guide.

SAP's cloud HCM (Human Capital Management) suite, covering core HR (Employee Central), recruiting, onboarding, learning, performance management, and compensation. SuccessFactors is licenced on a per-user-per-module basis under annual subscription. Integration between SuccessFactors and S/4HANA for organisational data may trigger Digital Access charges. See our SuccessFactors licensing guide.

The contractual schedule within SAP's Master Agreement that governs support terms, maintenance fees, escalation clauses, and the parties' rights to modify or terminate support services. The Support Maintenance Schedule is where annual fee escalation clauses (typically 3–5% built-in increases) appear. Negotiating a maintenance cap or price protection clause in the Support Maintenance Schedule is a high-value procurement activity.

Support services for SAP software provided by a vendor other than SAP SE — primarily Rimini Street and Spinnaker Support. TPM providers typically offer support at 40–50% of SAP's Enterprise Support fee. Moving to TPM forfeits access to SAP patches, updates, and new functionality — making it most suitable for organisations on stable, mature SAP landscapes not planning S/4HANA migration in the near term. See our SAP third-party maintenance guide.

The annual process of reconciling contracted SAP licence quantities against actual usage, and paying for any excess usage identified. True-ups are typically triggered by system measurement (USMM/LAW) outputs submitted to SAP. SAP's true-up process is structured to maximise the amount owed — using current list pricing for excess licences, applying the most expensive applicable licence type, and including indirect access charges where applicable. See our SAP licence true-up guide.

UK & Ireland SAP Users' Group — the regional SAP user organisation for the UK and Ireland. UKISUG membership provides access to benchmarking data, SAP negotiation guidance, and peer community. Particularly relevant for UK public sector organisations navigating Crown Commercial Service framework agreements. See also: ASUG, DSAG.

SAP's built-in transaction (transaction code USMM) for measuring Named User licence usage within a single SAP system. USMM examines user master data, role assignments, and transaction usage history to classify each user into a licence type and produce a measurement report. USMM is the primary tool used in SAP audits. Critical limitation: USMM defaults to the most expensive applicable licence type when user activity is ambiguous — systematically overcounting Professional users. Every USMM output should be reviewed and challenged before submission to SAP. See our USMM measurement guide.

A reduction in SAP's list price based on the total value of an enterprise deal. SAP's standard volume discount tiers are rarely published, and SAP account teams are instructed not to volunteer the maximum discount available. Independent benchmarking consistently reveals that initial SAP proposals offer 20–40% less discount than achievable with informed negotiation. See our SAP volume discount negotiation guide.

SAP's digital workplace and central entry point product, providing a unified launchpad for SAP and non-SAP applications. Work Zone is licenced per user and available in Standard and Advanced editions. Advanced edition includes additional collaboration features. Work Zone is often included in RISE proposals as a bundled component — understanding what is included versus separately licensed is important in RISE contract review. See our SAP Work Zone licensing guide.