Massachusetts Public University System.

This case study describes the engagement, redacted to remove identifying client information, in which a multi campus Massachusetts public university system reduced its annual SAP licensing cost by thirty one percent through a centralized named user review and Full User Equivalent classification cleanup. The engagement ran for sixteen weeks. The evidence trail was built to be audit ready before any classification change was committed back to SAP. The savings were not extracted from negotiation. They were extracted from accuracy.

The client

A Massachusetts public university system with five campuses, an integrated medical center, and a research enterprise spanning multiple federally funded laboratories.

The system had run SAP for over fifteen years. Named user assignments had accumulated organically across multiple chancellor administrations, several finance reorganizations, two business school reaccreditations, and a campus consolidation. Nobody had sat down with the named user list as a coherent population in more than a decade.

The default classification for the majority of administrative users had been Professional User. The default classification for academic researchers and graduate teaching assistants had also been Professional User, partly because the procurement team did not have a defensible rationale to use anything else.

The problem

The trigger event was a routine SAP support renewal proposal in which the published list price increase compounded against a named user count that had grown organically rather than deliberately. Procurement asked a straightforward question. How many of these users actually need a Professional license? The answer the system did not have, was that nobody knew.

The Professional User in SAP is the most expensive named user category, designed for users who configure or operate transactional core SAP. The Functional, Limited Functional, Employee Self Service, and Developer categories all carry materially lower list prices. Misclassification of Professional Users in any sufficiently large estate is a material commercial cost. SAP licensing is one of the most user category driven licensing models in the enterprise software market.

The biggest SAP discount most institutions have available to them is reclassification accuracy. The discount is already in the contract. They just have to claim it.

FUE and named user drift

SAP's transition framework towards S/4HANA introduces the Full User Equivalent measurement, in which named users are converted into FUEs at a defined ratio per category. A Professional User is one FUE. A Functional User is approximately one fifth of an FUE. The arithmetic is unforgiving. Misclassification of one thousand Professional Users into Functional categories saves approximately eight hundred FUEs per thousand. For a multi campus university system that arithmetic is millions in annual support and subscription cost.

Named user drift in higher education is structural. Students graduate but accounts persist. Faculty retire but accounts persist. Administrative reorganizations create new accounts and rarely retire the old ones. Research grants conclude and the principal investigator's account remains active for a year or more in case archived data is needed. Each of these drivers has a defensible rationale. Cumulatively they produce a named user population that is dramatically larger than the active user base, and weighted heavily towards the most expensive Professional category by default. See our S/4HANA advisory service for the broader FUE framework.

The centralized review approach

Our partner ran the engagement from the system's central administration office, with a sixteen week plan structured in four phases.

• Phase one. Population reconciliation. Pull every named user across all campuses, all SAP clients, and all integrated systems into a single inventory. Reconcile against active employee, student, faculty, and contractor records in the enterprise identity systems. Identify the population that should not have been active.
• Phase two. Activity instrumentation. Capture transaction code usage by user across a six month rolling window. Pair each user with the transactions they actually executed, the modules they actually opened, and the reports they actually pulled. The activity data became the empirical basis for classification decisions.
• Phase three. Reclassification with evidence. Reclassify users from Professional to lower categories where the activity data supported the change. For every reclassification, document the evidence in a format that would survive an SAP audit pass back. Apply the same logic to the FUE conversion.
• Phase four. Commercial close. Submit the reclassified named user inventory to SAP as part of the support renewal. Negotiate the support renewal against the corrected baseline. Close the renewal on the new number with the audit trail attached.

Read more about the broader pattern in our SAP audit defense framework and the SAP Knowledge Hub.

Findings

The reconciliation phase identified roughly three thousand named user accounts that no longer mapped to any active record in the enterprise identity systems. A further two thousand accounts mapped to records but had no activity in the prior twelve months. Twenty one percent of the named user population was either inactive or could not be reconciled.

The activity instrumentation phase identified that approximately forty percent of the population classified as Professional was executing only transactions that fell within the Functional or Employee Self Service category definitions. Most of these users were faculty or research staff who had received Professional classification by default at account creation, despite never executing a Professional transaction. The activity data was the breakthrough. SAP's classification logic is not subjective. It maps to transaction code definitions in published guidance.

A smaller number of users were retired entirely. The remainder were reclassified into Functional, Limited Functional, or Employee Self Service categories with documented evidence on file.

Commercial outcome

The thirty one percent saving was structured as a renewed support agreement on the corrected named user baseline, with a written acknowledgment from SAP that the reclassification methodology was acceptable for the purpose of the renewal. The S/4HANA migration trajectory was preserved, with the FUE conversion running on the corrected named user inventory. The same approach can be re run on a rolling annual cadence. The university system has incorporated the named user review into its annual budget cycle.

The total saving across the renewal term, before any further reclassification work, ran into the eight figures. The audit ready documentation of every classification change means that the reduced position is defensible if SAP elects to challenge it in a future review. Read also our SAP Services overview and the SAP RISE negotiation guide for the broader commercial framework.

Lessons for any institution running SAP

Three observations from this engagement that apply to most institutions running SAP at scale.

• Named user classification is the single largest controllable variable in SAP licensing cost. The discount is in the contract. The work to claim it is administrative, not negotiating.
• Activity data beats job title every time. Classification decisions made from organizational charts produce systematic Professional User overcount. Classification decisions made from transaction code activity produce defensible accuracy.
• Run the review on a rolling cadence, not as a one off. Named user populations drift. The reclassification work has to be incorporated into the annual support renewal cycle to stop the drift accumulating again.

If your institution is preparing a SAP support renewal, an S/4HANA migration, or a RISE conversion, our SAP Services team can scope the named user review and run the FUE arithmetic. Read also our case study library, Vendor Shield for always on cover, and the benchmarking service for a peer comparison of your position.