License harvesting is the systematic identification, documentation, and reservation of SAP entitlements that the estate is no longer using and is unlikely to need within the contract term. Carried into a renewal negotiation, the harvested quantum is the strongest piece of evidence the buyer can present that the contract is over-sized. Carried into an audit, it is the buffer that absorbs surprise classifications. Carried into a divestment or restructuring, it is the working capital of the licence portfolio. This article sets out the harvesting method, the dispositions, and the renewal application. It is the operational complement to our license optimisation service.
What we mean by harvest
A harvest is the formal reclamation of an entitlement that is contractually owned, technically deactivated, and procedurally available for reuse. It is distinct from a write-off (which is a contractual surrender), from a reclassification (which is a re-banding of an existing assignment), and from a shelfware identification (which is a status without an action). The harvest produces a documented pool that the procurement team holds and applies against future requirements.
The scope of a harvest
Three categories of entitlement are routinely harvestable. Each has a separate detection method and a separate reuse pathway.
Named-user entitlements
Users who are dormant, departed, replaced by automation, or reclassifiable to a lower band release named-user entitlement back to the pool. The detection method is the dormant-user analysis described in our dormant-user cleanup article; the disposition is the override register and a contractual harvest log.
Package entitlements
Industry packages, add-on modules, and optional functionality often retain entitlement after the underlying business process has been retired or migrated. A package usage scan against the relevant configuration tables identifies packages that have produced no transactions in the trailing twelve months. The disposition is package-specific.
Engine entitlements
Engine licences (Payroll, BW, BPC, GTS, MDG, and equivalents) carry capacity metrics that frequently exceed the realised volume. The harvest in this category is a capacity rebase to actual consumption with a documented growth headroom. The engine metrics pillar covers the per-engine method.
The detection method
The harvesting workflow follows four steps. Each step has documented outputs that feed the next.
Step one — baseline entitlement extract
The procurement team extracts the current entitlement quantities from the contract schedule. Each entitlement line is identified by SAP material number, contractual quantity, and unit metric. The extract becomes the upper bound of the harvest.
Step two — consumption pull
The technical team pulls actual consumption for the trailing twelve months. For named users, the source is SU01 plus ST03N. For packages, the source is the package-specific transaction table. For engines, the source is the engine-specific measurement object. The pull is the lower bound of the harvest.
Step three — gap quantification
The gap between entitlement and consumption, less a documented growth reserve, is the harvestable quantum. The growth reserve is a contractually defended forecast that protects against under-allocation in the renewal cycle. The reserve is typically ten to fifteen per cent of consumption for stable processes and higher for processes under active expansion.
Step four — disposition
Each harvestable entitlement receives a disposition: hold for renewal leverage, reassign to an active project, surrender for credit, or trade against a new product line. The disposition is recorded in a harvest log that survives leadership changes. See the named-user reclassification playbook for the related procedural sequence and the licence-types topic page for the metric definitions.
The discipline of the harvest is the disposition. An undisposed entitlement is shelfware. A disposed entitlement is a contractual instrument.
The renewal application
The harvested quantum is the single most useful asset the buyer carries into a renewal. SAP’s renewal proposal is generally a maintenance-plus-growth model: maintain the current entitlement and add the projected growth at the prevailing list price. A documented harvest disrupts the model because it disproves the current entitlement as a baseline. The renegotiation moves from price negotiation to right-sizing negotiation, and the saved margin is, in our practice, between fifteen and thirty per cent of the original proposal.
The renewal application requires the harvest to be evidenced. The override register, the consumption pull, the disposition log, and the growth reserve forecast are the four documents the renewal team brings to the table. Estates that surface a harvested quantum without the supporting evidence find the proposal restated rather than reduced. The contract negotiation pillar covers the negotiation arithmetic in detail.
The audit application
A documented harvest is a defensive instrument at audit. When the audit team raises a surprise classification or a previously unobserved engine consumption, the harvested pool absorbs the claim without triggering a purchase. The estate is in technical surplus rather than in technical shortfall, and the audit conversation moves to a reconciliation rather than to a sale. See the audit defence pillar for the surrounding methodology.
The conversion application
S/4HANA conversion negotiations treat the legacy entitlement portfolio as the starting point for the FUE allocation. A harvested portfolio reduces the legacy footprint that translates into the conversion, which reduces the FUE quantum that the migration is sized against. The harvest therefore reduces both the legacy maintenance line and the future subscription line. See the S/4HANA migration compliance pillar for the conversion arithmetic.
— 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 cadence
Estates that harvest quarterly maintain the cleanest portfolio and carry the strongest renewal position. Estates that harvest only at renewal lose the discipline through the cycle and surface incomplete evidence at the table. The licence optimisation handbook sets out the quarterly cadence and the documentation templates. See also the financial-services reclamation case file for the cadence in practice on a 25,000-user estate.
Where to start
The first quarter of a harvesting programme is typically the highest yield. The accumulated entitlement gap of years of growth-only purchasing surfaces in a single pull, and the renewal team carries a substantial harvested quantum into the next negotiation. Subsequent quarters refine the baseline and protect against the accumulation recurring. The first-quarter yield in our practice averages between eight and fourteen per cent of the licence portfolio, depending on the depth of the entitlement schedule and the discipline of the prior cycle.