SAP License Harvesting: Reclaiming Unused Licenses

Why harvesting matters

License harvesting is the systematic process of identifying SAP user accounts that are unused, under used, or over provisioned, and reclassifying or removing them to reduce the licensed entitlement count. Across our Fortune 500 engagements the average harvest opportunity is between 18 and 28 percent of the named user count. For estates with 10,000 named users that represents direct contract cost reduction in the seven figure range.

Harvesting matters for three reasons. The first is that SAP charges by named user count, and unused accounts charge the same as used accounts. The second is that unused accounts present a security exposure because dormant accounts are common targets for credential reuse. The third is that harvesting evidence is the cleanest way to enter a renewal or audit cycle with a defensible position. The full optimization framework is in our SAP cost optimization pillar.

Inactivity thresholds and the harvest list

The standard inactivity threshold for the harvest list is 90 days of no logon. Users who have not logged on for 90 days are candidates for either reclassification to a lower license type or removal. The 90 day window aligns with the SAP measurement cycle and with the practical reality that quarterly absence almost always indicates a job change, project end, or role change that has not been reflected in the SAP user master.

The harvest list should be generated from SUIM and STAD data, cross referenced against HR active employee data, and reviewed with the role owners before any removal action. Cross reference our user misclassification guide for the classification rules and our license optimization expertise for the engagement model.

The reclassification path

Before removing a user, evaluate whether the user can be reclassified to a lower license type. A user classified as Professional who only consumes display transactions can be reclassified to Functional or Productivity at a fraction of the cost. The reclassification path preserves the access while reducing the entitlement cost. The path requires evidence in the form of transaction usage data over a 90 to 180 day window.

Reclassification typically converts 30 to 40 percent of harvest candidates into lower cost entitlements rather than removals. The remainder are removed entirely. The blended saving on the harvest population averages 60 to 75 percent of the original cost.

The reclassification decision tree intersects with the indirect access posture. Users who consume only through integrations may not need a named user license at all, depending on the contract terms. See our indirect access detection guide and the indirect access expertise page.

The reclaim workflow

The reclaim workflow runs in four stages. Identify, validate, action, document. Identify produces the harvest list from SUIM data. Validate cross references against HR data and role owner confirmation to eliminate false positives. Action executes the reclassification or removal in the SAP user master. Document captures the evidence trail for the audit defense file.

The workflow should run quarterly as a standard hygiene activity, not annually as a project. A quarterly cadence captures the reclaim opportunity while it is small enough to action without organizational friction. Annual harvesting tends to surface large populations that require change management overhead and that often miss the window before the next measurement. See our self audit guide for the cadence framework.

Common harvesting mistakes

Three mistakes recur across the harvesting programs we have reviewed. The first is removing users without evidence retention. When SAP measurement runs after a removal, the measurement may include the removed users unless the removal is documented and the removal date is retained. The second is reclassifying without transaction evidence. Reclassification without evidence collapses under audit scrutiny and SAP reverses the reclassification. The third is removing users with composite roles that span multiple business processes. The removal may inadvertently break workflows that other users depend on.

The defense against all three mistakes is process discipline. Evidence, validation, documentation. The harvesting program should produce an audit defense file as a natural output of the workflow, not as a separate exercise. Cross reference our audit data collection guide and findings dispute guide.

Building a sustainable program

A sustainable harvesting program has three elements. A quarterly review cadence with a documented owner. A defined reclassification decision tree that the team can apply consistently. A reporting view that shows the reclaim trajectory over time and ties the savings to budget evidence. The combination converts harvesting from a one time project into a continuous control that produces compounding savings.

The first quarter of a new harvesting program typically captures the largest reclaim. Subsequent quarters capture smaller amounts that net out joiners, leavers, and role changes. The mature steady state is a quarterly reclaim of 2 to 4 percent of the user population, which sustains the cost base at the optimized level. See our license consulting service for the engagement model and our audit complete guide for the broader defense framework.