The Professional user category is the most expensive named-user licence in the standard SAP price list and, in most estates, the single largest line in the entitlement bill. Reducing the Professional count is consequently the highest-value optimisation lever available to the SAP estate owner, and is the lever most frequently mishandled. The tactics that produce defensible reductions are not the tactics that produce the largest paper savings; they are the tactics that survive audit scrutiny, hold up in a renegotiation conversation, and remain valid across the measurement cycle. Across our SAP license optimization engagements we work through a consistent set of five reduction tactics.
Tactic one — evidence-based reclassification
The most common Professional reduction tactic is reclassification: moving users from Professional to Limited Professional, Employee, or Developer based on their actual usage profile. The tactic produces real reductions when supported by evidence; it produces audit exposure when not.
What “evidence” means here
The evidence is the documented transaction history of the user, captured from ST03 or equivalent usage statistics, mapped against the licence type definitions in the buyer’s contract. The user’s actual transaction set determines the lowest defensible licence type. The mapping is mechanical but must be documented: which transactions were observed, which user groups were active during the measurement period, and which contract clause supports the reclassification target. Reclassifications without this documentation are exposed to reversal during audit. The named user reclassification piece covers the evidence framework in detail.
Tactic two — role-based right-sizing
Some Professional users are misclassified not because their individual transaction history is light but because their assigned roles permit Professional-tier transactions that they never actually execute. Role mining identifies the gap between authorisation and usage and produces a redesigned role catalogue in which the most expensive authorisations are concentrated in a smaller set of roles assigned only to users who require them.
The redesign is a project, not a tactic per se, but the reduction it produces is durable: once the role catalogue is right-sized, the licence-type assignment naturally falls out. The role mining for licensing piece walks through the role-redesign discipline.
Tactic three — dormant user removal
Every estate carries a population of Professional users who are no longer active: leavers whose accounts were not deactivated, contractors whose access continued past the engagement, project users whose project completed without account cleanup. Each dormant user is a Professional-licence line item that produces no business value.
The clean-up sequence
The clean-up sequence is: identify the dormant population (last logon date as the principal criterion, supplemented by HR data on terminations and contract end-dates); apply the locking-then-deletion sequence required by the buyer’s audit trail policy; re-measure to confirm the user is removed from the licence count. The mechanics are straightforward; the policy framework around when users can be locked and when they can be deleted is the harder part and usually requires IT and HR alignment. The dormant user cleanup piece covers the full sequence.
Tactic four — shared accounts and reference users
The SAP licence model accommodates technical users, communication users, and reference users in defined ways. Each of these special user types occupies a Professional licence line in default configurations but can often be reclassified or removed from the licence count entirely, subject to the contract definitions and the buyer’s configuration.
The exposure here is misuse. Reference users, in particular, are designed to inherit authorisations from a template user and are intended for specific use cases (consistent authorisation profiles across user populations). Using reference user configurations to disguise active humans behind a single reference-user shadow is a common audit finding and produces material settlements. The reduction tactic is to identify the legitimate special-user population, remove illegitimate uses, and reclassify the remainder consistent with the contract definitions. The named user licenses topic page covers the special-user types in detail.
The single largest source of unnecessary Professional licences in most estates is not over-classification but inertia: accounts that should have been locked years ago, role catalogues that have not been revised since the original go-live, special user types that have accumulated outside the original design. Reducing the Professional count is mostly a cleanup discipline, not a clever-tactics discipline.
Tactic five — license harvesting and pool reassignment
Once dormant users are cleaned and reclassifications are complete, the resulting licence position typically shows surplus Professional entitlement against actual consumption. The surplus can be harvested into a reassignment pool: licences are formally retired from individual user assignments and held in a reserve from which new joiners and reclassification candidates can draw without expanding the contracted entitlement.
The discipline here is governance. A licence pool that lacks documented assignment-and-retrieval procedures degrades into informal grants and ad hoc reassignments that produce the same problems the cleanup intended to solve. The pool should sit inside a documented governance process with assignment criteria, retrieval criteria, and quarterly review. The license harvesting piece sets out the governance framework.
The renegotiation follow-through
The five reduction tactics together produce a lower measured Professional user count. The economic benefit of the lower count depends on how the buyer uses the position. The default option is reduced renewal cost: the next contract is sized to the lower count and the saving accrues. The more sophisticated option is contractual renegotiation: the surplus entitlement is converted to other licence types, to engine credit, or to BTP credit at favourable terms.
The conversion conversation requires the buyer to enter with a documented optimisation position. Without the documentation the conversion is at SAP’s discretion; with the documentation the conversion is a defensible negotiation. The SAP contract negotiation service handles the conversion discipline. The license optimization playbook white paper sets out the full negotiation framework.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
The practitioner’s position
Across engagements the recurring observation is that the Professional reduction available to most estates is in the range of fifteen to thirty per cent of the starting count, achievable within a single measurement cycle, with the savings sustainable across multiple cycles provided the cleanup discipline becomes operational. Buyers who treat reduction as a one-off project find the count rising again within eighteen months. Buyers who treat the discipline as ongoing maintain the lower count indefinitely. The manufacturer USMM cleanup case file documents an estate that sustained a twenty-three per cent reduction across three measurement cycles.
The follow-through
Professional user reduction is high-value work but only when the reductions are defensible. The discipline is documentation, audit-readable evidence, and a governance framework that keeps the position from regressing. Reductions taken without that discipline produce savings that are reversed at the next audit, with interest. The license metric selection piece covers the broader optimisation framework.