What You'll Learn
This article provides a production-ready SAP package licence optimisation checklist spanning three 30-day phases. You'll discover how to extract USMM data, calculate FUE requirements, identify package licence opportunities, and execute commercial amendments with SAP—all with evidence-based positioning that stands up to audit scrutiny.
SAP package licence optimisation is not a one-time event—it's a structured, data-driven process that uncovers millions in hidden cost reduction opportunities. Yet without a clear roadmap, most enterprises defer optimisation indefinitely, leaving unnecessary spend on the table.
This checklist and 90-day action plan gives you the step-by-step framework to take control. Whether you are managing a multi-system SAP landscape, migrating to S/4HANA, or simply want to reclaim wasted spend, this guide breaks down the entire journey into three manageable phases: discovery, analysis, and commercial execution.
The Case for SAP Package Licence Optimisation
Most enterprises over-license SAP packages. The reasons vary: conservative initial scoping during implementation, fear of underestimating growth, legacy systems still on licence records after decommissioning, or simply no one has taken the time to measure actual use patterns. The result is the same: enterprises pay SAP for licences they do not consume.
Package licence optimisation addresses this head-on. By running USMM across your estate, exporting your Bill of Materials (BoM) from your contract, and calculating real FUE (Full Use Equivalent) requirements, you create an evidence-based case for amending your Order Form and reducing your SAP spend. In our experience, enterprises typically identify 15–35% in unnecessary package licence spend.
This article assumes you have a working knowledge of SAP licensing fundamentals. If not, start with SAP Licensing Basics. You will also benefit from understanding the broader SAP package licence landscape; read the complete pillar guide on SAP Package Licence Optimisation.
Phase 1: Discovery and Inventory (Days 1–30)
The first 30 days are about establishing baseline understanding. You will extract actual data from your systems, document your licensing position, and identify the gaps between contracted and active licences. This phase is heavy on data collection and light on analysis; precision here saves weeks later.
Phase 1 Checklist: Data Extraction and Cataloguing
| Task | Priority | Effort | Owner |
|---|---|---|---|
| Run USMM across all systems (ERP, BW, CRM, SRM, HCM) to capture user consumption metrics | Critical | 3–5 days | SAP Basis / ITAM |
| Export current Order Form and BoM from SAP contract repository | Critical | 1 day | Procurement |
| Map all Order Forms against current system landscape | Critical | 2 days | ITAM / Finance |
| Identify and catalogue all engine licences (Replication Server, Data Services, Analytics Cloud) | High | 2 days | SAP Basis |
| Run LAW (Licence Analysis Worksheet) against USMM output and Order Form | Critical | 2 days | SAP Licensing Advisor |
| Audit licence records for decommissioned systems still on contract | High | 3 days | ITAM |
| Catalogue all industry solution packages (IS-Retail, IS-Utilities, IS-Banking, IS-Healthcare) | High | 2 days | ITAM / Business Units |
| Document any BTP (Business Technology Platform) service credits allocated but not consumed | Medium | 1 day | Cloud Architecture |
| Prepare data export package for Phase 2 analysis | High | 2 days | ITAM |
Key Phase 1 Actions: Step-by-Step
- Run USMM on your SAP systems: USMM captures user logon data, transaction frequency, module usage, and concurrent user counts. Work with your SAP Basis team to execute USMM reports across all production and non-production systems. Export the output to CSV with user IDs, transaction codes, logon counts, and timestamps. Do not filter the data at this stage; you will need the full picture for FUE calculations in Phase 2.
- Extract your BoM from SAP documentation: Your Order Form contains a Bill of Materials listing all packages, user types, and engine licences you are entitled to hold. Request this from your SAP contract owner or download from the SAP Licence Information System (LIS) if available. Format the BoM into a spreadsheet with columns for package name, user type (Named User, Concurrent User, Service Provider), quantity, and effective date.
- Map Order Forms to systems: You likely have multiple Order Forms covering different systems, acquisitions, or contract periods. Create a master mapping showing which Order Form covers which system(s), the effective date, the total licences contracted, and any amendments to date. This prevents confusion in later phases when negotiating amendments.
- Identify all engine licences: Engine licences (Replication Server, SAP Data Services, Analytics Cloud, Integration Suite) are often overlooked in optimisation projects. Pull a complete list from your procurement records and licensing spreadsheets. Note the quantity of each engine licence, the system it serves, and any unused instances.
- Run LAW against your data: LAW is SAP's licensing worksheet tool. Input your USMM data and Order Form BoM into LAW to generate a preliminary licence position. This output shows you, in SAP's own terms, where you have surplus capacity and where you might be under-licensed. Save the LAW output in full; you will use it to build your ELP (Effective Licence Position) in Phase 2.
- Audit for decommissioned systems: Many enterprises retire SAP systems (old R/3 instances, redundant implementations, or regions divested) but forget to remove them from licence records. Check your master system inventory against your contract BoM. Any systems no longer running should be candidates for licence removal.
- Catalogue industry solutions: IS-Retail, IS-Utilities, IS-Banking, and other industry solution packages are sometimes bundled into contracts but never activated. Work with business units to confirm which industry packages are actually in use. If an entire IS package is dormant, it becomes a negotiation point for removal.
- Document unused BTP service credits: If your contract includes BTP credits (for cloud services, integration, or data management), check your BTP utilization dashboard. Many enterprises provision credits conservatively and never consume them; unused credits are low-hanging fruit for optimisation.
- Consolidate Phase 1 deliverables: By day 30, you should have a data package containing USMM extracts, Order Form BoM, LAW output, system decommissioning audit, and a preliminary inventory of all packageable items. This becomes your input to Phase 2.
Phase 1 Success Indicator
You have successfully completed Phase 1 when you can answer: What is the total number of each user type licence I am contracted to hold, and how many am I actually consuming per USMM data?
Phase 2: Analysis and Opportunity Identification (Days 31–60)
Phase 2 transforms raw data into actionable opportunities. You will run FUE calculations, identify over-provisioned user classes, cross-reference packages against business processes, and build your Effective Licence Position (ELP) spreadsheet. This phase is analytical and produces the evidence needed for Phase 3 negotiations.
Phase 2 Checklist: Quantifying Opportunities
| Task | Priority | Effort | Owner |
|---|---|---|---|
| Calculate FUE (Full Use Equivalent) requirements for all user types | Critical | 5 days | SAP Licensing Advisor |
| Identify Professional users performing only Limited Professional transactions | Critical | 3 days | ITAM / Business Analyst |
| Map BTP service credit consumption against allocated credits | High | 2 days | Cloud Architect |
| Audit engine licence consumption vs. contracted quantities | High | 2 days | SAP Basis |
| Cross-reference package licences against active business processes and LoB usage | High | 4 days | ITAM / Business Units |
| Build ELP (Effective Licence Position) spreadsheet with BoM reconciliation | Critical | 5 days | SAP Licensing Advisor |
| Calculate financial value of each optimisation opportunity | High | 2 days | Finance / Procurement |
| Identify any T&Cs (Terms & Conditions) constraints that limit optimisation flexibility | High | 2 days | Legal / Procurement |
| Document all findings and build Phase 3 negotiation case | Critical | 3 days | SAP Licensing Advisor |
Key Phase 2 Actions: Step-by-Step
- Run FUE calculations: FUE is the SAP methodology for converting measured user behaviour into required licence quantities. FUE accounts for part-time users, users on multiple systems, and weighted transaction usage. Using your USMM data, calculate how many Named Users and Concurrent Users your actual usage demands. Typically, FUE requirements are 20–35% lower than contracted quantities, revealing significant optimisation potential.
- Identify over-licensed user classes: Pull a report of all users assigned Professional (full ERP access) licences and analyse their USMM transaction patterns. Many professionals only use a small set of transactions, which often fall into the Limited Professional category (e.g., order-to-cash, procure-to-pay subsets). Reclassifying these users from Professional to Limited Professional delivers material savings, often £200–£500 per user annually.
- Map BTP credit consumption: If you hold BTP service credits, log into your BTP consumption reporting dashboard and export 12 months of actual usage. Compare that against your contracted credit allocation. Excess unspent credits are negotiable; you can request a credit reduction or credit reallocation to higher-value services.
- Audit engine licence usage: For each engine licence you hold (Replication Server, Data Services, Analytics Cloud, Integration Suite), check system logs and consumption metrics. Are you running the licensed number of instances, or fewer? Unused instances are candidates for removal. Document the delta between contracted and active instances.
- Cross-reference package licences: For each industry solution package (IS-Retail, IS-Utilities, etc.) or functional package (SAP Analytics Cloud, SAP SuccessFactors connectors, etc.), verify with business unit owners whether the package is actively used. Many enterprises contract for packages "just in case" and never activate them. Packages not in active use for 90+ days are negotiation targets.
- Build your ELP spreadsheet: The ELP is your evidence foundation. Create a comprehensive spreadsheet with rows for each package, user type, and engine licence. Columns should show: contracted quantity (from BoM), actual consumption (from USMM/LAW), FUE-adjusted requirement, proposed quantity, and annual savings. The ELP becomes your single source of truth for negotiations.
- Quantify savings: For each proposed change (e.g., removing 20 Professional licences, reducing Concurrent Users by 50, delisting an unused IS-Banking package), calculate the annual cost impact using your SAP pricing schedule or recent Order Form amendments. Aggregate to total estimated annual savings. This number drives executive sponsorship and urgency.
- Review T&Cs for constraints: Your Order Form T&Cs may contain minimum commit periods, locked package bundles, or penalty clauses for early reductions. Have legal or procurement review the contract and flag any constraints that might limit your negotiation flexibility. Workarounds include: requesting amendments to T&Cs themselves, proposing staggered reductions over time, or trading reductions in one area for growth in another.
- Document findings: Prepare a clean, executive-summary document showing your current licence position, identified optimisation opportunities, proposed amendments, and projected annual and multi-year savings. This document becomes your Phase 3 negotiation brief.
Critical Timing Warning: Avoid Running Optimisation During Active Audits
If SAP has initiated a compliance audit or you are in the final stages of a recent audit closure, do not launch a package licence optimisation project simultaneously. Approaching SAP with optimisation proposals during or immediately after an audit signals that you are opening your estate to scrutiny, which can extend audit timelines, trigger additional data requests, and create adversarial negotiation dynamics. Wait until the audit is formally closed, documented, and closed-out by SAP before initiating optimisation discussions.
Phase 3: Commercial Execution (Days 61–90)
Phase 3 is where optimisation translates into contractual and financial reality. You will prepare your negotiation position, engage SAP's commercial team, execute amendments, and close the loop by updating your internal licence records.
Phase 3 Checklist: Negotiation and Closure
| Task | Priority | Effort | Owner |
|---|---|---|---|
| Assemble the negotiation position document with all ELP evidence | Critical | 2 days | SAP Licensing Advisor |
| Align internally on optimisation targets and fallback positions | Critical | 1 day | Procurement / Finance |
| Schedule commercial conversation with SAP account/licensing team | High | 1 day | Procurement |
| Present evidence-based position in formal commercial meeting | Critical | 1–2 days | Procurement / Licensing Advisor |
| Negotiate proposed amendments to Order Form and BoM | Critical | 5–10 days | Procurement / Licensing Advisor |
| Obtain signed amending Order Form(s) from SAP | Critical | 3–5 days | Legal / Procurement |
| Update internal ITAM systems with new licence entitlements | High | 2 days | ITAM |
| Update SAP user master records to reflect licence reclassifications | High | 3 days | SAP Basis / HR |
| Schedule quarterly optimisation reviews to maintain position | Medium | 1 day | ITAM / Finance |
Key Phase 3 Actions: Step-by-Step
- Prepare the negotiation position document: Assemble a formal brief showing your current contracted position, USMM data backing your optimisation case, FUE calculations, and proposed amendments. Use the ELP spreadsheet as the exhibit. The document should clearly state each proposed change, the rationale, and the financial impact. This is your evidence; do not present assumptions or soft data.
- Align internally: Before approaching SAP, secure executive agreement on your optimisation targets. Agree on your "best case" scenario (maximum reductions), your "target" (realistic middle ground), and your fallback position (minimum acceptable outcome). Brief finance on the expected savings timeline; most Order Form amendments are effective on the next billing cycle, not retroactively.
- Schedule the commercial meeting: Contact your SAP account executive or licensing manager and request a formal commercial review meeting. Position it as a "licence optimisation and compliance review" rather than a "cost reduction request" (SAP's commercial teams are more receptive to compliance-focused framing). Request that SAP bring their licensing subject matter expert to the meeting.
- Present your case: In the meeting, present your USMM data, FUE calculations, and ELP findings clearly and professionally. Acknowledge that SAP's initial scoping was reasonable given the constraints at the time, but actual usage patterns now show a different picture. Propose specific, documented amendments. Avoid confrontational language; frame this as a true-up that benefits both parties.
- Negotiate amendments: SAP may challenge your USMM data, question your FUE methodology, or propose counter-offers. Be prepared to defend your position with documented evidence. Consider trading: if SAP resists reducing core user licences, offer to grow spending in higher-margin areas (e.g., cloud services, advanced analytics). Negotiations typically take 1–2 weeks; allow time for SAP's approvals process.
- Obtain signed amendments: Once you and SAP agree on the amendments, request a formal amending Order Form(s) documenting the changes. Ensure the amendments clearly state: the old BoM, the new BoM, the effective date, the new annual fee, and any transition provisions. Have legal review before signature to ensure T&Cs are not inadvertently modified.
- Update your ITAM systems: Once the amended Order Form is signed, update your internal systems of record (licence management tools, entitlement registers, financial systems) to reflect the new licence position. This ensures your team operates from correct entitlements going forward and prevents over-licensing claims in future audits.
- Execute user master record updates: If your optimisation included reclassifying users from Professional to Limited Professional, update SAP user records in the system itself. Work with your SAP Basis team to apply user type changes in the customer master. Document the changes for compliance records.
- Schedule quarterly reviews: Optimisation is not a once-and-forget exercise. Schedule quarterly reviews to monitor your licence consumption against the new baseline, ensure no unplanned growth triggers over-licensing, and identify new optimisation opportunities. Many enterprises find recurring small savings add up to another 5–10% reduction annually.
Real-World Optimisation Checklist Summary
The following table consolidates all three phases into a single action checklist with priorities. Use this as your daily tracker throughout the 90-day initiative:
| Milestone | Checklist Item | Priority | Status |
|---|---|---|---|
| PHASE 1: DISCOVERY (Days 1–30) | |||
| Week 1 | Run USMM on all systems and export to CSV | Critical | □ |
| Week 1 | Extract Order Form BoM from contract repository | Critical | □ |
| Week 1 | Create Order Form to system mapping | Critical | □ |
| Week 2 | Identify and catalogue all engine licences | High | □ |
| Week 2 | Run LAW against USMM data and Order Form | Critical | □ |
| Week 3 | Audit for decommissioned systems on licence records | High | □ |
| Week 3 | Catalogue active vs. inactive industry solution packages | High | □ |
| Week 4 | Document unused BTP service credits | Medium | □ |
| Week 4 | Consolidate Phase 1 data package | Critical | □ |
| PHASE 2: ANALYSIS (Days 31–60) | |||
| Week 5 | Calculate FUE requirements for all user types | Critical | □ |
| Week 5 | Identify over-licensed Professional users | Critical | □ |
| Week 6 | Map BTP credit consumption | High | □ |
| Week 6 | Audit engine licence consumption vs. contract | High | □ |
| Week 7 | Cross-reference packages against business processes | High | □ |
| Week 7 | Build ELP (Effective Licence Position) spreadsheet | Critical | □ |
| Week 8 | Calculate financial value of all opportunities | High | □ |
| Week 8 | Review T&Cs for constraints | High | □ |
| Week 8 | Prepare Phase 3 negotiation case document | Critical | □ |
| PHASE 3: EXECUTION (Days 61–90) | |||
| Week 9 | Align internally on optimisation targets | Critical | □ |
| Week 9 | Schedule commercial meeting with SAP | High | □ |
| Week 10 | Present evidence-based position to SAP | Critical | □ |
| Week 10–11 | Negotiate and agree amendments | Critical | □ |
| Week 12 | Obtain signed amending Order Form(s) | Critical | □ |
| Week 12 | Update ITAM systems and entitlement records | High | □ |
| Week 12 | Update SAP user master records | High | □ |
| Week 12 | Schedule quarterly optimisation reviews | Medium | □ |
Common SAP Package Optimisation Opportunities
While every enterprise's SAP landscape is unique, certain optimisation patterns recur:
- Professional to Limited Professional reclassification: 20–40% of Professional-licensed users perform only Limited Professional transactions. Reclassifying these users saves £200–£500 per user annually.
- Named User to Concurrent User conversion: If your actual usage shows sporadic, part-time access patterns, Named Users may be over-provisioned. Converting to Concurrent Users (same-system-only) can reduce costs 30–50%.
- Decommissioned system cleanup: Systems retired 2+ years ago often remain on licence records due to administrative oversight. Removing them saves the full annual cost of the licences.
- Unused industry solution packages: IS-Banking, IS-Retail, IS-Healthcare packages contracted "just in case" but never activated represent pure savings opportunity with zero operational impact.
- BTP service credit reductions: Enterprises frequently over-allocate BTP credits as insurance; most consume only 40–60% of allocated credits. Reducing allocations captures cash without affecting functionality.
- Engine licence right-sizing: Replication Server, Data Services, and Analytics Cloud licences are often licensed for peak capacity rather than average utilization. Reducing instance counts aligns spend with actual usage.
Building Your Internal Business Case
Executive sponsorship is critical to completing the 90-day initiative. Prepare a business case showing:
- Current annual SAP package licence spend: Your baseline.
- Identified savings opportunity: Conservative estimate (target 15–25% reduction).
- Three-year cash impact: Annual savings multiplied by three years = your NPV for ROI calculations.
- Implementation effort: 90 days of cross-functional time; resource plan it clearly.
- Risk mitigation: All optimisation is backed by SAP's own LAW methodology and USMM data, not assumptions.
- Upside potential: After the initial optimisation, quarterly reviews often identify additional 5–10% savings annually.
Present this business case to your CFO and Procurement leadership. The ROI (savings / implementation cost) is typically 10:1 or better.
Quarterly Reviews: Sustaining the Optimisation Gain
Once you have executed your Phase 3 amendments, do not consider the project closed. Schedule quarterly optimisation reviews (30–45 minutes per quarter) to:
- Monitor actual USMM consumption against the new baseline; flag any creep toward over-licensing.
- Identify new optimisation opportunities from system changes, acquisitions, or retirements.
- Review T&C amendments or new contract language that might enable additional savings.
- Prepare for SAP's next proposed expansion and counter with evidence-based cost control.
Many enterprises discover that quarterly reviews unlock 3–5% additional savings each year, compounding the ROI over time.
Linking to Related Optimisation Resources
SAP package licence optimisation is one element of a comprehensive cost control strategy. For deeper context, review:
- SAP Package Licence Optimisation: The Complete Enterprise Guide for 2026 – The pillar guide covering strategy, business cases, and landscape scenarios.
- SAP Package Licence Optimisation: Practical Enterprise Guide – Tactical implementation guidance for large, complex SAP environments.
- SAP Package Licence Optimisation: Key Risks and How to Mitigate – Risk framework and mitigation strategies for common optimisation pitfalls.
- SAP Package Licence Optimisation: Cost Reduction Strategies – Advanced tactics for maximising financial impact beyond basic package right-sizing.
Working with SAP Licensing Advisors
Many enterprises benefit from external expertise to guide the 90-day initiative. An independent SAP licensing advisor can:
- Validate USMM data extraction and FUE calculation methodology.
- Review your ELP spreadsheet for completeness and defensibility.
- Prepare the negotiation strategy and position document.
- Accompany you to the SAP commercial meeting and negotiate amendments.
- Review proposed amending Order Forms for hidden clauses or unfavourable terms.
Our experience shows that advisor-supported optimisation initiatives close 2–3 weeks faster and secure 5–15% more aggressive amendments than self-directed efforts. For a free consultation on your optimisation roadmap, get in touch.
Key Takeaways
- SAP package licence optimisation follows a predictable 90-day structure: Phase 1 (discovery), Phase 2 (analysis), Phase 3 (commercial execution).
- USMM data and FUE calculations are your evidence foundation. Use SAP's own methodology to make your case; SAP cannot credibly challenge your position if it is grounded in their tools.
- Build your ELP spreadsheet meticulously. It becomes your single source of truth for negotiations and your protection against future audit disputes.
- Avoid timing optimisation projects during active SAP audits. Wait until the audit is formally closed before initiating commercial optimisation conversations.
- Secure executive sponsorship early. Frame optimisation as a compliance and cost control initiative; quantify the 3-year savings impact to earn CFO and Procurement alignment.
- Plan for quarterly reviews post-implementation. Optimisation is not a one-time event; quarterly monitoring sustains the gain and identifies recurring savings opportunities.