Why Named User Licence Optimisation Matters
Named user licence costs are the single largest controllable variable in most SAP estates. A 1,000-user enterprise overpaying by one licence tier on 300 users incurs €500,000–€1,000,000 in annual waste. But the true cost is higher: SAP's annual support obligation sits at 22% of net licence value, compounding the overspend indefinitely.
When support costs are factored in, that €500k underperformance becomes a €610k annual problem. Over five years, it totals €3 million in excess spending.
Misclassification is systematic. Our analysis of 80+ licence audit defence engagements reveals that enterprises consistently over-assign licence types to manage perceived risk. Finance teams opt for Professional User to avoid audit exposure; they rarely downgrade. The result: entire departments assigned Professional User rights when Limited Professional User or Employee Self-Service would suffice.
The Five-Step Optimisation Process
1. Run ST03N Workload Analysis
ST03N is SAP's transaction analysis tool. It extracts 12 months of transaction history per user, showing exactly which transactions each user executed, how often, and in which modules.
- Scope the data: Pull ST03N data for the past 12 months to capture seasonal variation (fiscal year-end cycles, budget periods, month-end closes).
- Filter for active users: Exclude accounts with zero activity (dormant test users, contractors no longer active).
- Identify top-10 transactions: For each user, extract their top 10 most-executed transactions. This shows their primary functional area.
ST03N output is raw; it requires interpretation. A user executing SE16N 400 times per month is a power user querying analytics (likely requiring Professional User). A user executing PA30 (personnel master) 15 times per month is a payroll administrator (Limited Professional User is appropriate). A user executing PA20 (cost allocation) three times quarterly is a functional controller (Employee Self-Service may be sufficient).
2. Map Transactions to Licence Classification Matrix
SAP's licence classification matrix ties transaction codes to user types. Professional User has unrestricted access across all modules. Limited Professional User is restricted to one or two functional areas. Employee Self-Service is restricted to personal data (timesheet, expense report, leave request entry).
Cross-reference each user's top-10 transactions against SAP's authorisation matrix. If all 10 transactions are available to Limited Professional User, the user is over-classified.
This step is critical and often missed: transaction permission mapping is complex, and SAP regularly updates the matrix. Engaging SAP directly or consulting Redress Compliance's classification library ensures accuracy.
3. Flag Candidates for Downgrade
Three user cohorts consistently over-classified:
- Display-only users: Execute only SE11, SE12, SM51 (display tables, check logs). These should be Employee Self-Service or no licence.
- Single-module users: Work exclusively in one functional area (e.g., AP only, Payroll only). Limited Professional User is appropriate.
- Inactive users: Haven't logged in for 90+ days but still consume a licence. Should be deactivated entirely.
Typical downgrade candidates: 20–35% of your user base. A 1,000-user estate will contain 200–350 users available for downgrade or deactivation.
4. Get Business Owner Sign-Off
Before reassigning a licence type, secure written approval from the business owner responsible for that user or department. This step prevents disputes and ensures accountability.
Approach: Present the business owner with their user's top-10 transactions and SAP's licence type requirements. Ask: "Is this user performing these activities?" If the user is not executing the higher-tier transactions, approval is typically granted without friction.
Document approvals. If SAP audits and disputes a reassignment, your approval record is your defence.
5. Execute Licence Reassignment Before USMM Measurement Date
USMM (User and System Measurement) is SAP's audit tool. It captures a snapshot of your user estate on a specific date and ties that snapshot to your contract. Licence reassignments must occur before the next USMM measurement date.
SAP's standard measurement window is December 31 (SAP's fiscal year-end). Optimisation must be complete by November 30 to capture the new baseline in the December measurement.
After reassignment, run USMM internally to verify the new count matches your expected optimisation. This is your audit view — SAP will see the same data.
The Role of USMM: Your Audit Intelligence Tool
USMM is the tool SAP uses during licence audits. It measures named users by type and flags any user whose executed transactions exceed their assigned licence type. Running USMM quarterly gives you the audit view before SAP does.
The data is sobering. Most enterprises discover they have 15–25 users executing transactions above their assigned type. SAP upgrades these users to the correct tier and back-charges three years of maintenance on the difference.
USMM also reveals shelfware: users licensed but inactive. Every inactive Professional User costs €3,000+ per year plus 22% support. Deactivating 30 unused Professional Users saves €99,000 annually and eliminates three years of potential audit back-charges.
Advanced user analytics and USMM audits identify hidden cost recovery opportunities in every SAP estate.
Learn how Vendor Shield optimises your licence position.DDLC and Named Users: Two Independent Dimensions
A common misconception: reducing named user counts reduces DDLC exposure. This is incorrect. Named user licensing covers humans logging into SAP directly. DDLC (Digital Document Licence Compliance) covers non-SAP systems or automated interfaces accessing SAP data indirectly.
Optimising named user types does not change DDLC document exposure. If your e-commerce system processes 500,000 customer orders annually via SAP APIs, that 500,000 figure is DDLC liability — independent of your named user count.
Both dimensions must be audited separately. A 30% named user cost reduction is real value. But if DDLC exposure is unmanaged, audit risk and cost remain high.
S/4HANA Migration: The Critical Re-Baseline Moment
S/4HANA migration triggers a re-baseline of your entire user estate. SAP re-classifies all users into the new S/4HANA licence type hierarchy: Professional Use, Functional Use, and Productivity Use. This is not a 1:1 mapping from ECC types.
Here is the critical point: optimise your user assignments NOW, before migration. Users you downgrade pre-migration carry forward at the lower tier into S/4HANA. Users still assigned Professional User at migration are re-classified as Professional Use, locking in the higher cost for the next contract term.
SAP's incentive during migration: upgrade users and maximize the re-baseline. Your incentive: lock in the lowest accurate classification before re-baseline happens.
Action: If S/4HANA migration is planned for 2026 or 2027, run ST03N analysis and user optimisation by Q3 2026. That timing ensures your optimised baseline carries through migration and is contractually locked.
Shelfware: The Invisible Cost Drain
Inactive users are licensed but unused. They may be contractors who departed, test accounts never deleted, or employees on long-term leave. SAP audit tools flag these immediately.
A 1,000-user estate typically contains 20–40 inactive users (2–4%). If even half are Professional User, the cost is €30,000–€60,000 in annual waste, plus €6,600–€13,200 in support.
Process: Pull a user list with last-login dates (available via SAP's User Information System). Flag users inactive for 90+ days. Coordinate with HR to confirm departure or long-term absence status. Deactivate the account in the licence management system.
The Support Cost Multiplier
Annual support is calculated at 22% of net licence value. This compounds. Reducing named user licence spend by €1 million saves €220,000 per year in support fees permanently. Over five years, that's €1.1 million in support savings alone.
This is why optimisation ROI is immediate and long-lived. Spend reduction carries forward as long as the licence is in place.
Named user optimisation + DDLC audit + pre-migration baseline lock = a defensible, cost-accurate SAP estate.
Get expert guidance from buyers who have defended 80+ indirect access disputes.Vendor Negotiation: Clean Data Is Leverage
An optimised user count gives you clean negotiating data. SAP cannot inflate your baseline if you present accurate, ST03N-validated user assignments with business owner sign-off. The vendor's audit tool (USMM) will confirm your count, eliminating their negotiating room.
When contract renewals come due (SAP fiscal year ends December 31, so renewals typically close by Q4), accurate baseline data shifts price negotiation in your favour. You can negotiate volume discounts and support rates from a position of strength.
Timing: Optimise in Q3; lock the baseline by Q4 measurement; use clean data to negotiate renewals in Q4 or early Q1 of the next fiscal year.
Conclusion: Optimisation Is Continuous
Named user licence optimisation is not a one-time project. User populations change quarterly as new hires come aboard, contractors depart, and departmental roles shift. Annual reviews (aligned to SAP's fiscal year-end in December) ensure your licence estate stays right-sized.
The compounding cost of misclassification — licence fees plus 22% annual support — makes this a material financial control. Every 10% reduction in named user spend saves approximately 12% of your total SAP cost (after support multiplier).
For enterprises running SAP or planning S/4HANA migration, optimisation is the highest-ROI pre-migration activity. Lock in accurate user assignments before re-baseline; the savings carry forward for the entire contract term.