STAR role analysis for S/4HANA licenses: what SAP addresses in note 3113382 and why companies should act now

Anyone who is switching to S/4HANA or has already migrated will be familiar with the issue: licensing models are becoming more complex, and the distinction between usage types is becoming blurred. This becomes particularly problematic when authorizations do not match the licensed usage rights. This is precisely where SAP comes in with the so-called STAR Service and the associated SAP Note 3113382 .

But what sounds like technical analysis on paper has enormous implications in practice.

The real problem

SAP uses the STAR tool to analyze how users actually use the system and compares this with the license model they have booked. For example, if a user is classified as an "employee" according to the license definition but uses functions assigned to a "professional user," they may be subject to additional charges.

What many don't realize is that the system not only looks at transactions, but also at permissions. The mere presence of critical permissions can trigger a higher license class—even if the transaction has never been actively used.

For companies this means:

• Opaque licensing situation

• Risk of expensive relicensing

• Lack of control in user and role assignment

The most common cause

In many cases, the cause lies in historically evolved role structures. Roles are maintained, adapted, and expanded over years. In the process, many companies lose track of which activities and transactions are actually needed and which generate unnecessary costs.

A clean, role-based licensing approach is often lacking. This is precisely where SAP Note 3113382 raises the alarm and shows that the existing authorization structure is not automatically license-compliant.

STAR Role Analysis: What to do now?

Companies should proactively check their S/4HANA roles for license relevance using the STAR Role Analysis. It's not enough to simply look at user activities. A thorough analysis of the assigned authorization objects is essential, ideally combined with a clear licensing model.

In case of doubt, a structured reconciliation saves six-figure sums and reduces the effort required for audits and true-ups in the long term.

How Yellow Sailor supports

Yellow Sailor supports companies in reviewing their S/4HANA role landscape for license compliance and sustainably optimizing it. We analyze existing roles, identify cost-relevant deviations, and develop a licensing model that fits your processes, not the other way around.

We work closely with the system, independently, and with a clear goal: transparency, security, and control over your licensing landscape.

Talk to us before SAP does.