SAP Shelfware & Unused Licence Assessment: 20-Point Expert Checklist

USMM (User and Service Measurement Management) is SAP's own licence measurement tool, and it is the single most important diagnostic you can run before any renewal conversation. Execute USMM across every production client and compare the output to your current contractual licence schedule. Pay close attention to the spread between Professional, Limited Professional, and Self-Service user types — the mix directly determines your renewal baseline. Expert note: Run USMM outside of an official SAP audit window so the results are yours to use without triggering formal compliance obligations. Organisations consistently find that their contract reflects original purchase quantities, not actual deployment, often revealing surpluses of 20 to 40 percent in specific licence types.

Dormant accounts are the most common and easily recoverable form of SAP shelfware. Report SU01 or use table USR02 to extract last login dates for all active accounts. Any account with no login in 90 days is a shelfware candidate; accounts with no login in 180 days are almost always safe to lock and eliminate. Expert note: Industry assessments consistently find that 15 to 25 percent of named SAP users are effectively inactive. At average Professional user values of £1,200 to £3,000 per licence, 200 inactive users in a 1,000-seat deployment represents £240,000 to £600,000 in maintenance recoverable at renewal. Lock and document before presenting to SAP's renewal team.

User account offboarding is one of the most common compliance failures in SAP environments. When employees leave without their SAP accounts being deactivated, those accounts continue to contribute to the USMM count and accrue maintenance costs. Request a full export of active SAP accounts and compare against your HR system's active headcount. Expert note: Organisations with rapid headcount changes — due to restructuring, M&A activity, or high contractor turnover — routinely find 5 to 15 percent of SAP accounts belong to individuals no longer with the company. This is simultaneously a licence cost issue and a security risk. Document every orphaned account with the corresponding licence type and cost to build a quantified business case for removal.

Professional User is the most expensive named-user type, covering unrestricted access across all S/4HANA functional areas. However, a large proportion of Professional users in most deployments use only a narrow set of transactions that would qualify for Limited Professional or Self-Service classification. Analyse actual transaction usage via SM20 or SAP's licence classification tools and compare against the formal role requirements. Expert note: The price differential between Professional and Limited users is substantial — often three to five times the per-user cost. An organisation with 200 users currently classified as Professional who genuinely only execute limited transactional functions could generate £120,000 to £400,000 in annual maintenance savings through reclassification. SAP will scrutinise downgrade requests but cannot reject a reclassification supported by transaction usage evidence.

In multi-system SAP landscapes — where separate instances exist for ECC, S/4HANA, BW, and Solution Manager — the same individual often has accounts in multiple systems. Under SAP's licensing model, duplicate accounts across systems may count multiple times unless properly managed under the LAW (Licence Administration Workbench) consolidation process. Expert note: LAW is designed to consolidate user counts across systems, but it must be configured and executed correctly. Organisations that have grown through acquisition or that run parallel SAP systems frequently find significant duplication in their consolidated licence counts. Verify that LAW is running on the most current data set and that all systems are included in the consolidation before the next measurement.

SAP S/4HANA uses Full User Equivalents (FUEs) as the primary licensing metric, with different user types contributing different FUE weightings. Errors in FUE calculation are common — particularly when migrating from ECC named-user counts — and can result in over-provisioning. Review the FUE conversion methodology used at original contract signature and validate against current user mix. Expert note: Organisations that migrated from ECC to S/4HANA and applied a straightforward named-user-to-FUE conversion frequently discover that the mix of Professional, Limited, and Self-Service users in the live system produces a lower FUE total than the contracted amount. This over-contracted position represents direct maintenance savings available at renewal if properly documented.

Compile a complete list of every SAP software component, engine, and add-on in your contractual entitlement — not just what is installed, but what is licensed. For each entitlement, determine: Is it deployed? Is it configured? Is it actively used in production? Any entitlement in the deployed-but-not-used or licensed-but-not-deployed categories is recoverable shelfware. Expert note: The most common engine shelfware in enterprise SAP accounts includes legacy CRM and SRM modules superseded by cloud successors, BPC Planning licences for projects that never completed full rollout, GRC components purchased but only partially implemented, and HCM modules where SuccessFactors was adopted instead. Each of these carries a 20 to 22 percent annual maintenance charge. Document each unused component with its licence value and annual maintenance cost to build the ROI case for removal.

SAP BW and BPC licences are frequently purchased to support large analytics or planning transformation projects. When projects stall, are deprioritised, or are superseded by cloud analytics tools (such as SAP Analytics Cloud or third-party platforms), the BW and BPC engine licences continue generating maintenance costs. Check actual query volumes, active BW workspaces, and BPC input schedules against licence quantities. Expert note: Organisations that have migrated parts of their analytics estate to SAP Analytics Cloud, Microsoft Power BI, or Tableau often retain full BW engine entitlements that are now significantly over-provisioned relative to residual usage. This is one of the highest-value engine shelfware categories — BW licences can represent £500,000 to several million pounds in licence value in large SAP estates, with corresponding maintenance reductions available at renewal.

SAP GRC Access Control, Process Control, and Risk Management are commonly purchased as part of a compliance transformation programme. Partial implementations — where Access Control is live but Process Control was deferred — create shelfware. Review which GRC modules are genuinely live in production and cross-reference against the entitled components and their associated named-user counts. Expert note: GRC licence structures are complex and often poorly understood by both IT and procurement teams. Access Control licences are typically based on the number of SAP users whose access is governed by the GRC system, not on GRC system users themselves. Verify the measurement methodology being applied and confirm that the entitled user count reflects current governance scope rather than an original project forecast.

SAP Solution Manager (SolMan) is required for managed SAP landscapes but is often licensed beyond actual deployment scope. Check whether SolMan licences cover the number of managed systems actually in use, and whether premium SolMan capabilities (ITSM, Change Request Management, focused build) are licensed but not activated. Expert note: With SAP transitioning customers toward SAP Cloud ALM for lifecycle management, many accounts carry Solution Manager entitlements for capabilities that will be migrated to the cloud platform. Before renewal, assess what SolMan functionality remains genuinely in use versus what has migrated or is planned to migrate, as this affects negotiation leverage for SolMan maintenance removal or conversion credits.

SAP licences for development, quality assurance, and sandbox systems are frequently overlooked in shelfware assessments because they lack the visibility of production systems. However, test and development instances can carry significant maintenance obligations — particularly where legacy ECC development systems are maintained alongside S/4HANA production environments. Expert note: SAP contractual terms generally distinguish between production and non-production systems, but legacy contracts sometimes include maintenance obligations on named non-production instances. Review every non-production system in the licence schedule and confirm whether any can be decommissioned, consolidated, or moved to a lower-cost development licence category.

Digital Access licences cover business documents created in SAP by third-party systems — sales orders, purchase orders, delivery notes, financial postings, and so on. If your organisation purchased a Digital Access entitlement as part of a DAAP (Digital Access Adoption Programme) agreement or subsequent negotiation, run SAP's document measurement tools to compare actual document volumes against your contracted entitlement. Expert note: Organisations that conservatively estimated document volumes at Digital Access adoption often find they are significantly over-licensed relative to actual consumption. Document type-by-type measurement is essential — the total entitlement may be over-provisioned even if specific document types are close to limit. Over-provisioned Digital Access entitlements represent maintenance savings available at the next renewal if supported by measurement data.

Every third-party system that creates, reads, or modifies data in your SAP environment is a potential indirect access liability. Catalogue all integration points — EAI platforms, RPA tools, e-commerce systems, custom applications, and middleware — and confirm each has a documented licence basis under either the legacy SAP indirect access framework or the Digital Access model. Expert note: Organisations that have expanded automation through RPA platforms (UiPath, Automation Anywhere, Blue Prism) or integrated new SaaS applications without a licence review often have uncovered indirect access exposure. Conversely, organisations that purchased legacy indirect use licences for specific integrations that are now no longer active may be paying maintenance on those entitlements unnecessarily. Both directions require investigation.

When organisations transitioned from legacy indirect access licences to Digital Access through the DAAP programme, SAP offered conversion credits — typically calculated as a percentage of existing indirect access maintenance spend — toward Digital Access document entitlements. In many cases, organisations took more conversion credits than actual measured document volumes required. Expert note: If your DAAP conversion was completed and you purchased document entitlements significantly above measured consumption, you are paying annual maintenance on those excess entitlements. Quantify the gap between contracted document volumes and actual measured consumption. This documented over-entitlement position is the foundation for a maintenance reduction negotiation at your next SAP renewal.

SAP Fiori and self-service portal deployments extend SAP access to business users, customers, and suppliers who require only specific transactional functions — expense submission, purchase order approval, leave requests, and similar. If these individuals are classified as Professional users rather than Self-Service or External User types, the organisation is paying a significant classification premium. Expert note: This misclassification is particularly common in post-implementation environments where the provisioning team applied Professional user classification as a blanket default. Identify all users whose actual SAP transactions are limited to self-service portal functions and quantify the reclassification saving — Self-Service users are typically priced at 10 to 20 percent of Professional user cost in comparable licence metrics.

BTP capacity is allocated as part of RISE with SAP contracts and as standalone entitlements for integration, extension, and analytics use cases. BTP consumption is measured in capacity units, service-specific credits, and infrastructure metrics that are frequently over-provisioned at contract signature based on projected extension activity. Expert note: Many organisations receive BTP capacity as part of their RISE bundle but deploy only a fraction of it in the contracted term. BTP shelfware is invisible unless specifically measured — it does not appear in USMM. Pull BTP consumption reports from the BTP cockpit and compare against contracted capacity. Unused BTP capacity represents negotiation leverage for a capacity reset or credit against future BTP services at renewal, even if it cannot be directly converted to cash savings.

RISE with SAP bundles have expanded to include SAP Business Network (supplier connectivity), SAP Signavio (process intelligence), and SAP Joule (AI capabilities). Many customers included these components as part of bundle pricing without a clear deployment plan. Components included in the bundle but never activated represent both wasted investment and missed value realisation. Expert note: The significance here is twofold: first, at renewal, SAP will negotiate on the basis of the full bundle value — including components you are paying for but not using — which inflates the renewal baseline. Second, if you can demonstrate that specific bundle components have zero deployment, you have a documented basis to negotiate a bundle restructure or a credit. Identify every RISE bundle component, its activation status, and its approximate contribution to the overall contract value.

SAP's cloud HCM, procurement, and expense solutions — SuccessFactors, Ariba, and Concur — are licensed on a per-employee or per-seat basis. Where these were contracted against projected headcount or planned deployment scope, actual active user counts may be significantly lower than the licensed position. Expert note: Cloud application licences can be harder to reduce than on-premise entitlements because SAP's cloud contracts often include minimum commitment periods and consumption floors. However, documenting the gap between contracted and active users creates leverage for the next renewal cycle. For SuccessFactors specifically, where modules are contracted independently (Recruiting, Learning, Payroll, Compensation), identify which modules have low or zero adoption and whether the corresponding seat entitlements can be restructured or reduced at renewal.

SAP offers trade-in credit mechanisms — sometimes referred to as conversion credits or swap credits — that allow customers to exchange unused legacy entitlements for new product licences or RISE with SAP subscription credits. The value of trade-in credits varies significantly based on negotiation position, deal size, and SAP's strategic interest in the account. Expert note: Trade-in credits are most valuable when the customer has a documented, quantified shelfware position and is making a concurrent purchasing decision — such as a RISE migration, a new cloud application, or a BTP extension project. Organisations that bring a clear shelfware inventory to renewal negotiations typically receive trade-in credit at 30 to 70 percent of the remaining licence value, compared to near-zero recovery if shelfware is allowed to simply lapse. Present SAP with a precise, evidence-backed list of unused entitlements before opening renewal discussions.

Shelfware accumulates when licence procurement decisions are disconnected from actual deployment timelines and business adoption rates. The most durable protection against future shelfware is a governance process that requires a licence impact assessment before any SAP expansion, integration, or user provisioning decision. This should involve IT, procurement, finance, and the relevant business owner in a structured review. Expert note: Best-practice SAP governance committees meet quarterly to review USMM consumption trends, track upcoming renewals, and assess whether pending projects will require licence changes. Embedding this governance into change management means that no new SAP integration, no new user classification, and no new module activation proceeds without a documented licence approval — eliminating the structural conditions that create shelfware in the first place. This is a process investment that consistently delivers 10 to 20 percent reduction in licence spend over a three-year horizon in well-managed SAP estates.