Across the SAP estates we have advised on since 2018, approximately 80% carry a named user pool that is structurally over-licensed by between fifteen and twenty-five per cent. The over-licensing is rarely the result of negligence; it is the cumulative effect of years of role drift, project-team carryover, dormant accounts, and conservative classification decisions made under audit pressure. Each individual decision was rational at the time. The aggregate result is a license pool that no longer matches the actual workforce profile.
Rebalancing the pool is a mechanical exercise that rarely takes more than six weeks of elapsed time and produces a savings ratio of fifteen to thirty per cent on the annual user-licence line. This article walks through the seven-step workflow that consistently produces those results.
The seven steps
The workflow is sequential. Skipping any step weakens the final result, but each step is mechanically straightforward and can be executed by the customer’s internal team with limited external support.
Step 1: Baseline the current pool
The first task is a complete inventory of the current named user population, broken down by license type, organisational unit, primary system, and activity status. The baseline is extracted from SUIM, USR02, and the USMM history. The output is a single table with one row per user and approximately fifteen columns capturing the relevant attributes.
The baseline should reconcile to the most recent USMM submission. Any discrepancy between the current baseline and the USMM extract — additions, deletions, classification changes — should be explained before the rebalancing analysis proceeds. Unexplained discrepancies are often the source of subsequent audit findings.
Step 2: Identify and remove dormant users
Users who have not logged in within the prior six months are candidates for deactivation. The threshold is conservative; SAP’s own guidance and most audit decisions tolerate up to three months of dormancy without penalty. The six-month threshold provides a margin of safety while removing the highest-confidence category of over-licensing.
Dormant Professional users are the most expensive category and the first to remove. Dormant Functional users follow. Dormant Limited Professional users have the lowest per-user cost but contribute to overall pool size and audit complexity. See our companion piece on dormant named user cleanup for the operational mechanics.
Step 3: Reconcile contractor and project-team accounts
The second-most-common over-licensing category is contractor and project-team accounts that remained active after engagement end. The reconciliation is mechanical: cross-reference the active SAP user list against the current vendor master, the active engagement schedule, and the active employee roster. Any account without a current match in at least one of those three should be reviewed for deactivation.
This step routinely identifies five to fifteen per cent of the named user population. The financial impact depends on the classification of the accounts; project-team accounts are disproportionately likely to be Professional users, so the per-user saving is high.
Step 4: Run the role-content analysis
For the surviving population of active, current users, the next step is a role-content analysis that maps each user’s actual authorisation footprint against the contractual definitions of the named user types in use. The analysis is run from SUIM and the role authorisation tables; output is a single table identifying any users whose authorisation footprint does not match their current classification.
The output usually splits into two populations: users currently classified at a higher tier than their authorisation footprint requires (over-classification, a savings opportunity), and users classified at a lower tier than their authorisation footprint requires (under-classification, an audit risk). The rebalancing exercise addresses both, although the savings opportunity is the primary focus.
Step 5: Run the transaction-usage analysis
Even where the authorisation footprint suggests a higher classification, the actual transaction usage may not. A user with the authorisation to run Professional-level transactions but no usage history of those transactions can often be reclassified to Functional or Limited Professional without operational impact. The transaction-usage analysis identifies this population by extracting the prior twelve months of transaction history from ST03N or the equivalent statistics tables.
This is the most commercially valuable single step. The over-classification finding from role-content analysis alone is conservative; combining it with transaction-usage produces a larger and equally defensible reclassification population.
Step 6: Apply the contract-aware reclassification
The reclassification itself is the simplest step technically and the most complex contractually. Each candidate user is reviewed against the specific contract definitions in force — not the SAP price-list descriptions, but the actual contract clauses, which often vary subtly from the price-list defaults — and reclassified where the contract definition supports the change.
The reclassification is documented in a written rationale per user. The documentation is the audit defence in subsequent measurement cycles; without it, SAP’s auditor will reverse the reclassification on first challenge.
Step 7: Run the impact analysis and the next-cycle plan
The final step quantifies the financial impact of the rebalancing, identifies the new license pool size and mix, and produces the plan for the next twelve months of ongoing optimization. The plan typically includes a monthly dormant-user review, a quarterly contractor reconciliation, a semi-annual role-content drift check, and an annual full rebalancing exercise aligned to the USMM submission.
The financial framing
On a typical mid-large enterprise SAP estate with 5,000 named users and an annual user-licence run-rate of $4.8M, the rebalancing exercise routinely identifies $720K-$1.2M of annual savings. The dormant-user removal accounts for approximately a third; the reclassification accounts for the remainder. The savings persist year-over-year, compounding through the remaining contract term.
The investment is approximately six weeks of focused effort from a small cross-functional team — typically the SAP administrator, a procurement analyst, and an external advisor where the scope warrants it. The payback is in months, not years, and the discipline established by the workflow continues to pay back in every subsequent measurement cycle.
The pre-USMM timing
Rebalancing is most valuable when completed sixty to ninety days before the annual USMM submission. The timing allows the reclassification decisions to settle in the production system before the measurement extract is generated, eliminating any timing artifacts in the submission. Customers who attempt rebalancing inside the thirty-day window before USMM frequently introduce more risk than they remove.
When to bring in external advisory
The rebalancing exercise can be entirely internal for organisations with mature SAP administration teams and contract-savvy procurement. The cases where external advisory adds disproportionate value are first-time rebalancing exercises (where the customer has no internal baseline of what good looks like), post-acquisition rebalancing across recently merged estates, and rebalancing that is part of a broader S/4HANA migration preparation.
The governance loop that holds the gains
The single most common pattern after a successful rebalancing is gradual drift back to the original over-licensed position within 18-24 months. Without a governance loop in place, role changes, new hires, project teams, and acquisitions reintroduce the same patterns the rebalancing removed. The governance loop has four elements: a monthly dormant-user lock review, a quarterly contractor reconciliation against the active vendor master, a semi-annual role-content audit against the documented classification policy, and an annual full rebalancing aligned to the USMM submission. Each element is mechanical and the cumulative time investment is approximately one day per month of analyst effort.
The conversation with internal stakeholders
Rebalancing decisions sometimes meet resistance from individual business units who experience reclassification as a downgrade. The conversation is easier when framed as a contractual compliance and license-hygiene matter rather than a cost-saving exercise. A user reclassified from Professional to Functional retains the same operational access where the role authorisation footprint warrants Functional; nothing about the user’s ability to do their job changes. Where genuine functional restriction is required to support the reclassification, the conversation needs to be honest about that scope reduction. Pretending otherwise produces user pushback that undermines the rebalancing effort.
For the related disciplines, see our named user true-up strategy, role-based reclassification, and named user audit risk areas articles. For the broader context, see the USMM topic page, the SAP License Optimization service, and the license optimization handbook white paper. The global manufacturer license rebalancing case file documents an $1.8M annual saving on a 7,200-user estate.