Key Takeaways
- SAP licence baseline benchmarking follows 8 distinct phases from data extraction through compliance monitoring
- Phase 1-4 cover data collection, classification, analysis, and gap identification (typically 6-10 weeks)
- Phase 5-6 focus on benchmarking comparison and opportunity sizing (typically 2-4 weeks)
- Phase 7-8 address contract renegotiation and ongoing compliance (typically 4-8 weeks to contract amendment)
- Each phase has specific deliverables, success criteria, and go/no-go decision points
- Full cycle from kickoff to contract amendment typically spans 12-16 weeks for enterprise organizations
SAP Licence Baseline Benchmarking Checklist: The 8-Phase Framework
SAP licence baseline benchmarking is a structured process, not an ad-hoc analysis. When enterprises skip phases or cut corners, they create blind spots that auditors exploit later. This section breaks down the complete baseline benchmarking process into 8 phases, with specific deliverables, timelines, and decision criteria for each.
Use this checklist as your implementation roadmap. Each phase has dependencies on the previous phase, so sequence matters. The timeline provided is realistic for a medium-sized enterprise (3,000-7,000 users). Smaller organizations will move faster; larger organizations may take longer.
Phase 1: Data Extraction (Weeks 1-3)
Objective: Extract the raw data foundation for your baseline assessment from Solution Manager and SAP LAW.
- Extract full USMM (User Master Data) from Solution Manager, including user ID, type, creation date, last login date, role assignments
- Export LAW (Licence Agreement Workbench) position statement showing current licence entitlements per user type and module
- If RISE with SAP contract: Export SLAW (Simplified LAW) FUE allocations and cloud subscription details
- Request 12-18 month activity logs from SAP Security Audit Log (SAL) covering user logins and key transaction activity
- Document your data sources, extraction dates, and data quality issues (duplicate records, incomplete user data)
- Verify data consistency: USMM user count should reconcile with LAW entitlements (with documented exceptions)
- Store extracted data securely with access controls and version control
Deliverable: Consolidated user data spreadsheet, LAW position statement summary, activity log extract
Success Criteria: All four data sources extracted; user count reconciliation completed; data quality issues documented
Phase 2: User Type Classification Review (Weeks 4-5)
Objective: Systematically review each user's current assigned type and identify misclassification candidates.
- Categorize all users by current assigned type: Professional, Limited Professional, Developer, Employee, other
- For each user, document: transaction access count (distinct transaction codes run in past 12 months), module scope (which modules they access), role assignments, last login date
- Apply classification rules from your SAP agreement: Professional license requires full module access; Limited Professional requires restricted transaction set; Employee requires ESS-only; Developer requires development system only
- Flag reclassification candidates: users whose documented usage does not align with assigned type
- Segment candidates into confidence levels: high-confidence (clear reclassification, zero ambiguity), medium-confidence (likely reclassification, minor exceptions), low-confidence (grey zone, requires further review)
- Identify dormant accounts: users with zero logins in past 18 months, verified against HR records for separation or permanent assignment
- Identify locked accounts: accounts with security locks set, to be evaluated for deactivation
Deliverable: Classified user inventory with reclassification flags, confidence levels, dormant account list, locked account list
Success Criteria: 95%+ of users classified with documented rationale; reclassification candidates segregated by confidence level
Phase 3: Dormant Account and Technical Debt Identification (Weeks 5-6)
Objective: Surface accounts that consume licences without active use or clear purpose.
- Verify dormant accounts with business stakeholders: For each user with zero 18-month logins, confirm with their manager that the account is no longer needed or schedule deactivation
- Classify dormant accounts by type: separated employee (can be deleted immediately), long-term leave (document expected return date), permanent assignment elsewhere (document transfer), unknown (escalate for clarification)
- Coordinate with SAP BASIS team to identify batch users, service accounts, and system integration accounts: These may not require traditional naming licensing depending on your contract terms
- Document technical debt: accounts created for legacy integrations, test accounts, generic shared accounts. Determine which can be consolidated or deleted
- Schedule deactivation for verified dormant accounts with clear effective dates
- Document deactivation plan with business sign-off and contingency if accounts are reactivated later
Deliverable: Verified dormant account deactivation plan, batch/service account inventory, technical debt remediation roadmap
Success Criteria: All dormant accounts verified with business; deactivation schedule confirmed with stakeholders
Phase 4: Indirect Access and Digital Access Assessment (Weeks 6-8)
Objective: Inventory all non-traditional access paths to SAP and assess licensing exposure.
- Document Fiori applications: launchpad users accessing SAP via Fiori apps (identify count of unique ESS users, transactional app users, analytics app users)
- Catalog mobile applications: Any mobile apps (Fiori mobile, custom apps, third-party apps) connecting to SAP
- Inventory web services and APIs: Any API consumers, data integration tools, or external systems connecting to SAP (provide details on whether human-initiated or automated)
- Map business intelligence access: SAP Analytics Cloud users, BW/Analytics Designer users, embedded BI consumers
- Document EDI and partner portals: Any electronic document exchange or partner self-service accessing SAP
- Quantify indirect access exposure: X unique human users access SAP indirectly; Y automated systems connect via APIs
- Classify by licensing implication: ESS-only (likely no additional licensing), transactional access (may require licensing), read-only access (contract-dependent), API/automated (contract-dependent)
- Make explicit position statement: "We do / do not believe indirect access to [specific function] requires additional named user licensing per our SAP agreement, because [reason]"
Deliverable: Indirect access inventory, licensing exposure assessment, position statement on indirect access claims
Success Criteria: All indirect access paths identified; licensing exposure quantified; contractual position documented
Phase 5: Industry Benchmark Comparison (Weeks 8-10)
Objective: Compare your user distribution and licensing footprint against industry benchmarks to identify outliers.
- Document your current state: Total users by type, modules licensed, annual licensing spend, licensing cost per user
- Obtain industry benchmark data: STAR reports, peer data from comparable enterprises in your industry/region, SAP benchmarking tools output
- Compare your Professional/Limited Professional ratio against benchmark: If you are 90% Professional and benchmark shows 65%, you are over-indexed on Professional licensing
- Compare module licensing against benchmark: If you license 10 modules but primarily use 4-5, you are over-provisioned on module scope
- Identify outliers: Areas where your footprint significantly diverges from benchmark (usually indicates over-licensing or misclassification opportunity)
- Validate outliers with business: Areas with significant benchmark variance should be reviewed with business stakeholders to confirm they are genuine outliers vs. benchmark misalignment
- Document industry context: Different industries have different licensing patterns (manufacturing vs. services vs. financial services). Adjust benchmark expectations accordingly
Deliverable: Benchmark comparison report showing your position vs. industry norms, identified outliers with business justification
Success Criteria: Benchmark data obtained and validated; outliers identified and confirmed
Phase 6: Gap Analysis and Opportunity Sizing (Weeks 10-12)
Objective: Quantify the cost reduction opportunity and financial impact of proposed adjustments.
- Calculate over-licensing gap: (Licences paid for under LAW) minus (active users in USMM) = number of over-licensed spots
- Model reclassification scenarios: Conservative (high-confidence reclassifications only), Moderate (high + medium confidence), Aggressive (including low-confidence)
- For each scenario, calculate: Users reclassified from Professional to Limited Professional; resulting licence quantity change; resulting annual cost reduction
- Quantify dormant account savings: Dormant users × average licence cost per user × months until contract adjustment = annual savings
- For RISE contracts: Model FUE reallocation and potential FUE reduction; quantify BTP credit optimization opportunities
- Calculate total opportunity: Sum of reclassification savings + dormant account savings + FUE optimization + BTP optimization = total annual cost reduction potential
- Calculate maintenance impact: 22% of licence cost reduction = maintenance savings (to be included in contract adjustment)
- Model financial impact over contract term: If contract extends 3 years, multiply annual savings × 3 to show total 3-year opportunity
Deliverable: Opportunity sizing report with financial models for each scenario, 3-year projection
Success Criteria: Cost reduction quantified for conservative and moderate scenarios; financial impact clear to stakeholders
Phase 7: Contract Review and Renegotiation Strategy (Weeks 12-14)
Objective: Understand your contract terms, establish your negotiating position, and prepare the renegotiation case.
- Deep-dive contract review: Analyse your SAP licence agreement for user type definitions, module scope, maintenance calculation, indirect access clauses, adjustment procedures
- Confirm reclassification defensibility: Ensure your proposed reclassifications align with your agreement's definitions of each user type. If definitions are ambiguous, document your interpretation
- Identify contract adjustment procedures: Does your agreement allow mid-term adjustments? What notice period? What effective date options?
- Understand indirect access position: Does your agreement explicitly address Fiori, mobile, API, or indirect access? What is SAP's likely position vs. your defensible position?
- Build your adjustment case: Document baseline findings, reclassification logic, dormant account deactivation plan, and financial impact. Prepare 10-15 page executive brief
- Determine negotiating tactics: Will you approach SAP with contract amendment request (aggressive), cost reduction proposal (moderate), or audit reconciliation (collaborative)?
- Establish fallback positions: If SAP resists full cost reduction, what is your acceptable compromise? What minimum savings justify the effort?
- Coordinate with SAP account team: Schedule discussion with SAP sales/account team to introduce baseline findings and discuss adjustment options
Deliverable: Contract analysis summary, adjustment case document, negotiation strategy memo
Success Criteria: Contract position clear; baseline adjustment case documented; negotiation strategy agreed with internal stakeholders
Phase 8: Implementation and Compliance Monitoring (Weeks 14+)
Objective: Execute contract adjustment, implement system changes, and establish ongoing monitoring to prevent post-baseline licence drift.
- Implement user reclassifications: Update user assignments in USMM per your classification review. Phase implementation (Phase 1: high-confidence, Phase 2: medium-confidence) to reduce risk
- Deactivate dormant accounts: Execute deactivation schedule on agreed dates. Document before/after user counts
- File formal contract adjustment with SAP: Submit official amendment request with baseline data, reclassification documentation, dormant account list, and financial impact. Request specific effective date and pro-rata credit calculation
- Negotiate contract relief: Work with SAP to reach agreement on adjusted LAW entitlements, maintenance cost reduction, and potential contract extension terms
- Execute contract amendment: Obtain signed amendment reflecting adjusted entitlements and pricing
- Implement indirect access resolution: If indirect access exposure was identified, document either (a) licensing commitment, (b) technical controls, or (c) contractual exemption to resolve the exposure
- Establish quarterly compliance monitoring: Quarterly reviews of active user count by type, new user additions, account deactivations, to ensure licence footprint remains aligned with baseline
- Document lessons learned: Capture what worked, what didn't, and process improvements for future baseline updates
Deliverable: Contract amendment, implemented reclassifications, deactivation records, quarterly compliance dashboard
Success Criteria: Contract amendment executed; reclassifications implemented; cost savings realized; monitoring process established
Timeline Overview: Full Cycle Execution
Here's how an 8-phase baseline benchmarking effort typically flows:
Key Decision Points: Go / No-Go Checkpoints
After Phase 2 (Classification Review)
Decision: Is the reclassification opportunity material enough to pursue?
- Go: If high-confidence reclassification candidates represent 15%+ cost reduction, proceed to Phase 3.
- No-Go: If opportunity is less than 10% cost reduction, consider stopping and re-evaluating in 12-18 months after your user estate changes.
After Phase 4 (Indirect Access Assessment)
Decision: Does indirect access exposure require formal resolution before filing contract adjustment?
- Go: If indirect access is minimal or already justified contractually, proceed to Phase 5.
- Pause: If significant indirect access exposure exists, resolve it before filing adjustment (to prevent SAP raising it in negotiation).
After Phase 6 (Opportunity Sizing)
Decision: Is the financial impact sufficient to justify the effort and risk?
- Go: If cost reduction opportunity exceeds $250,000 annually (or equivalent % for your organization size), proceed to Phase 7.
- No-Go: If opportunity is below organizational threshold, consider deprioritizing or combining with other initiatives.
After Phase 7 (Negotiation Strategy)
Decision: Do we have defensible, contractually-justified reclassifications to propose?
- Go: If your reclassifications align with contract language and can withstand audit challenge, proceed to Phase 8 implementation.
- Reconsider: If your position is ambiguous or weak contractually, narrow scope to only highest-confidence changes or seek contract clarification from SAP first.
Execute Your Baseline Benchmarking Plan
Our advisors help enterprises navigate all 8 phases, from data extraction through contract amendment. We provide methodology, documentation, and SAP negotiation expertise to turn baseline findings into measurable cost reduction.
Start Your Baseline AssessmentFrequently Asked Questions
Can we skip phases or accelerate the timeline?
+You can compress the timeline slightly (10-12 weeks total) if you have strong internal SAP expertise and dedicated resources. However, skipping phases creates blind spots. Phase 4 (indirect access) is often skipped but frequently becomes an audit issue later. Phase 7 (contract review) is critical—skipping it means you file contract adjustments without understanding your contractual position. Execute all 8 phases. The time investment now prevents audit risk later.
What if we don't have the internal expertise to execute baseline?
+Engage an independent SAP licensing advisor to lead Phases 1-7. You provide internal resources to support data extraction (Phase 1), business stakeholder validation (Phases 2-3, 5), and contract negotiation (Phase 7). The external advisor brings methodology, objectivity, and negotiation experience. You maintain control over the process while leveraging expert guidance. Typical advisory engagement costs $40,000-$75,000 for a 5,000-user enterprise and delivers $400,000-$750,000 in first-year savings, for an 8-15x ROI.
What's the biggest risk in executing baseline benchmarking?
+The biggest risk is incomplete Phase 4 (indirect access assessment). Enterprises identify cost reduction opportunities, implement reclassifications, and file contract adjustments without formally addressing indirect access. SAP then leverages the unresolved indirect access exposure in negotiation: "You reclassified users, but you haven't addressed your 3,000 indirect Fiori users. We'll adjust your contract for reclassifications, but you need to license the indirect access separately." This negates reclassification savings. Always complete Phase 4 before filing Phase 7 adjustments.
How do we track progress across the 8 phases?
+Establish a baseline steering committee with IT leadership, finance, SAP management, and project sponsor. Hold weekly check-ins during Phases 1-4 (active work), bi-weekly during Phases 5-6 (analysis), and weekly during Phases 7-8 (negotiation). Use the phase checklist as your progress tracker. Create a simple Gantt chart showing phases, dependencies, and key milestones. This keeps all stakeholders aligned and prevents the baseline effort from drifting.
What if SAP refuses our contract adjustment request?
+If SAP refuses adjustment, you have two options: (1) Implement the reclassifications in your system anyway, creating a discrepancy between your system configuration and your LAW entitlements. This creates audit risk but gives you evidence of your actual footprint if SAP audits later. (2) Request audit reconciliation, triggering a formal audit where auditors review your classification logic. If your documentation is sound, reconciliation often produces adjustment more favorable than SAP's initial rejection. See our SAP audit defense service if you encounter resistance.
Related Resources
Explore more on baseline benchmarking execution and enterprise SAP optimization:
- The Complete SAP Licence Baseline Benchmarking Guide for 2026 — Comprehensive overview covering strategy, methodology, and outcomes.
- SAP Licence Baseline Benchmarking: Practical Enterprise Guide — Deep-dive into data extraction, classification methodology, and interpretation.
- SAP Licence Baseline Benchmarking: Key Risks and How to Mitigate — Understanding risks and audit protection throughout baseline execution.
- SAP Licence Baseline Benchmarking: Cost Reduction Strategies — Cost reduction levers and financial modeling from baseline findings.
- SAP License Optimization Service — End-to-end baseline benchmarking from kickoff through contract renegotiation.
- Case Studies — Real-world examples showing baseline execution timelines and outcomes.