SAP License Reclassification: Downgrading User Types

What reclassification is

SAP license reclassification is the formal change of a user from one license type to another based on the actual transaction usage observed. A user originally classified as Professional, but who only consumes display transactions, can be reclassified to Functional or Productivity at a fraction of the cost. Reclassification is distinct from removal. The user remains active. Only the entitlement classification changes.

The largest reclassification opportunity sits in the Professional to Functional and Professional to Productivity transitions. These transitions typically reduce the per user cost by 40 to 70 percent. Across the typical Fortune 500 estate the reclassification opportunity is 12 to 22 percent of the total license cost base. The fuller framework is covered in our SAP licensing models explained guide.

The classification decision tree

The classification decision tree intersects three inputs. The transactions the user actually executes, the categorization of those transactions in the SAP price list, and the contract terms that govern the customer estate. The output is the lowest defensible classification given the observed transaction profile.

A user who executes only display transactions in the last 180 days is a Productivity candidate. A user who executes a narrow set of transactional codes in a single functional area is a Functional candidate. A user who executes a broad set of transactional codes across multiple functional areas is a Professional. The decision tree applies the lowest classification that the transaction evidence supports.

Evidence requirements

Reclassification without evidence collapses under audit scrutiny. The standard evidence package includes the STAD transaction usage data for the user over the relevant measurement window, the SAP price list categorization of those transactions, and the role assignment history that supports the classification position. The window should be at least 180 days to demonstrate that the usage pattern is stable rather than episodic.

The most common audit reversal of a reclassification is on the evidence quality dimension. Customers who reclassify based on assumed usage rather than measured usage routinely lose the position when SAP measurement produces a different result.

The evidence file should also include the change documentation. When the classification was changed, who approved the change, what evidence supported the decision. Cross reference our audit data collection guide and our license optimization expertise for the file structure.

Reclassification under audit

When an SAP audit measurement runs, the SAP toolset applies the SAP side classification logic rather than the customer side classification. The two often disagree. The defense is to enter the audit with a documented evidence package that supports each reclassification decision and to challenge the SAP measurement on the specific transactions and specific time windows where the SAP side and customer side disagree.

The dispute path runs through the audit findings response, the LAW measurement review, and the formal dispute mechanisms within the contract. The detail is in our audit findings dispute guide and our LAW measurement guide.

Edge cases and exceptions

Three edge cases recur. The first is the user with executive level authorizations who only logs in occasionally. The transaction history is sparse but the authorization scope is broad. The defensible position depends on whether the contract classification is usage based or authorization based. The second is the user with composite roles that include transactions across multiple functional areas, but who only executes a narrow subset. The defense is the same evidence package, but the role history may need to be cleaned up to support the position.

The third is the user who consumes through integration rather than direct logon. These users often fall outside the standard named user classification entirely and into the indirect access framework, which has different pricing and different defense requirements. See our digital access conversion guide and our indirect access detection coverage.

Implementation cadence

Reclassification should run on the same quarterly cadence as license harvesting, because the two activities share the same evidence inputs. The quarterly review identifies both harvest candidates and reclassification candidates from the same SUIM and STAD data set. The action workflow then routes the candidates to the appropriate remediation path. The combined cadence produces a sustained cost base reduction of 3 to 6 percent per quarter in the first year and 1 to 2 percent per quarter in steady state.

The reclassification program should report into the same governance forum that owns license optimization, audit defense, and renewal preparation, because the three programs share the same evidence base. See our license harvesting guide for the harvest workflow and our license consulting service for the engagement model.