1. Build Your Current-State Package Inventory

Before you can optimise SAP package licensing, you need to know what you own. Most enterprises cannot answer this question with confidence: "What packages do we have, at what edition, in what quantity, for how long, and what are we paying?"

Start with your Order Forms and your License Analysis Workbook (LAW). These documents contain the ground truth of your SAP licensing estate:

  • Order Forms: Show package names, editions (Professional, Limited Professional, Engine), Named User quantities, and contract terms (e.g., annual, multi-year)
  • LAW: Your master record. Contains all active entitlements, maintenance start/end dates, and the BoM (Bill of Materials) for each system
  • Maintenance records: Show which packages are under support and for how long

Create a spreadsheet that consolidates all packages across your production, non-production, and development estates. Include columns for package type (e.g., SAP S/4HANA Enterprise Management Professional, SAP Analytics Cloud Named User), edition, quantity, monthly cost, and primary use case. This inventory becomes your baseline against which all optimisation discussions are measured.

Many enterprises find that their actual package holdings differ from what they think they have—duplicate entries, legacy packages nobody uses, or packages that were never decommissioned after projects. That gap is your first savings opportunity.

2. Map Package Usage to Actual Business Activity Using USMM Data

Licensed packages mean nothing if you don't know whether they are being used. This is where Universal Size Measure Management (USMM) becomes critical. USMM is SAP's reporting framework that translates system activity (transactions, batch jobs, document volumes) into licensing obligation.

Extract USMM data from your SAP systems for the past 12 months. This data tells you:

  • Which users logged in and how often
  • What transactions they ran (sales orders, purchase requisitions, GL posting)
  • Which modules were touched (SD, MM, FI, HCM, etc.)
  • Peak and average usage patterns by month

Cross-reference your USMM data against your package inventory. For each package, ask: Is usage rising, stable, or declining? Are there packages with zero recorded activity over the past 12 months? Which packages are driving the highest transaction volume?

If a package shows zero activity, you have found your first conversation with SAP: a package to rationalise or downgrade. If usage is declining year-on-year, there is a trend to document and leverage. If usage is concentrated in a small percentage of your Named Users, you may be overspending on quantity.

3. Identify Over-Assigned Packages and Under-Utilised Entitlements

Once you have inventory and usage data, the math becomes simple. An over-assigned package is one where licensed capacity exceeds actual need by a measurable margin.

Common scenarios we encounter:

  • Unused packages: A Financial Management package on a development system that nobody has touched in 18 months
  • Over-licensed user populations: Named User licenses for 200 people but USMM shows only 120 active users for the past year
  • Edition mismatches: Professional edition deployed where Limited Professional edition would deliver the same functionality for 40% less cost
  • Indirect Access creep: Named User packages assigned to backend processes that should be running under Engine licences

Build a rationalisation table. For each package, calculate:

Package Edition Licensed Qty Active Users (12mo avg) Utilisation % Monthly Cost Rationalisation Opportunity
Enterprise Management Professional 150 98 65% $45,000 Reduce to 110 NU (25% saving)
Financial Management Professional 40 0 0% $18,000 Decommission (100% saving)
Analytics Cloud Named User 80 45 56% $32,000 Right-size to 50 NU (37% saving)
Supply Chain Limited Prof 200 195 97% $28,000 No change (healthy utilisation)

This table is your foundation for commercial negotiation. It shows SAP exactly which packages you are rationalising and why, based on your own USMM data and activity logs.

Watch Out: False Utilisation Claims

SAP audit teams sometimes argue that a package must be "kept licensed" because of potential future use, regulatory requirements, or "ecosystem value." Challenge this directly. If USMM shows zero activity for 12 months, that package is not being used. Document this objectively and do not accept vague assertions about future intent.

4. Build a Defensible Effective Licence Position (ELP) for Your Package Estate

An Effective Licence Position (ELP) is SAP's term for the minimum licence footprint required to legally operate your systems without audit risk. Your ELP should reflect your actual usage, not your current spend.

Construct your proposed ELP by:

  1. Starting with active users: Use USMM data to count the number of Named Users who actually logged in during the measurement period (typically the past 12 months)
  2. Adding margin for growth: Most enterprises add 10–15% buffer to account for seasonal peaks or new hires coming online. This is defensible because you can justify it with historical variance data
  3. Documenting by system and module: Show your ELP broken down by system (ERP, Analytics, HCM, etc.) and by module (Sales, Procurement, Finance). This granularity makes your position stronger in negotiation
  4. Addressing indirect access separately: If you have batch processes, integrations, or scheduled jobs touching SAP, these require Engine licences or indirect access fees, not Named User licences. Clarify this distinction in your ELP

Your proposed ELP becomes the target state in negotiation with SAP. It says: "We need exactly this many licences to operate our business, based on 12 months of measured activity. Anything above this is waste."

5. Run the Commercial Conversation with SAP

Once you have inventory, usage data, and a proposed ELP, you are ready to negotiate. This conversation typically happens with your SAP Account Executive or during a contract renewal discussion.

Here is the structure:

Step 1: Lead with Audit Risk Mitigation

Frame your package rationalisation as a shared goal: "We want to ensure our licence position is audit-proof and defensible." This positions you as collaborative, not adversarial. SAP's audit team looks unfavourably on customers with sloppy licensing, so offering to tighten your position is genuinely valuable to both sides.

Step 2: Present Your USMM Data and Utilisation Analysis

Show your rationalisation table. Walk SAP through the specific packages you intend to reduce or eliminate, and cite USMM activity logs as justification. If a package shows zero usage for 12 months, that is an unambiguous reason to decommission it. If usage is 65% of licensed capacity, make the case for downsizing.

Step 3: Request a Price Concession or Volume Adjustment in Exchange

SAP calculates pricing based on your package footprint. Smaller package footprint = lower pricing. In most cases, when you rationalise packages, SAP will agree to reduce your monthly recurring charge or provide credits against future maintenance.

The negotiation math is straightforward: If you eliminate $18k/month in unused packages and SAP offers you a 15% discount on your remaining $150k/month spend, you have saved $22.5k/month ($18k + $22.5k = $40.5k), or $486k annually. That is a concrete ROI from package optimisation.

Step 4: Document the New Package Entitlements in an Order Form Amendment

Do not rely on email or verbal agreement. Once SAP accepts your rationalisation proposal, demand a formal Order Form amendment that clearly states:

  • Packages being decommissioned and effective decommission date
  • Packages being reduced, with new Named User or Engine quantity
  • New total monthly recurring charge (MRC)
  • Effective date of the change

This document protects you in any future audit. It proves that your reduced package footprint was negotiated and agreed with SAP, not unilaterally imposed.

Get Expert Support on SAP Package Negotiation

Package optimisation involves real money and complex T&Cs. Our advisors help enterprises construct defensible ELPs and negotiate from strength with SAP. We work strictly on the buyer side.

Book a Free Consultation

6. Common Mistakes Enterprises Make (and How to Avoid Them)

Based on 25 years advising enterprise SAP customers, we have seen predictable patterns of error:

Mistake 1: Overestimating Future Use

CIOs often say: "We keep this package licensed 'just in case' we need it." This is how enterprises end up with 12-month-old packages on the ledger that nobody has touched. Use data, not hope. If a package has not been used in 12 months, decommission it. You can always re-license it if requirements change—but re-licensing is far cheaper than carrying unused capacity for years.

Mistake 2: Confusing Named User Capacity with Actual Users

"We have 150 named user licences" does not mean 150 users are active. USMM data will show you the true count. Many enterprises license for organisational potential (e.g., all possible Finance team members) rather than actual active users. This is a spending leak. Right-size to active + small growth buffer.

Mistake 3: Ignoring Indirect Access Exposure

Batch processes, integrations, and scheduled jobs that touch SAP systems require licensing. If these are running under Named User accounts, you are exposed. Either convert them to Engine licences (cheaper for batch processes) or acknowledge the indirect access exposure and negotiate an indirect access fee with SAP. Do not ignore it.

Mistake 4: Not Documenting USMM Data Before Negotiation

SAP will challenge any claim about low usage unless you can produce system logs. Extract and preserve 12 months of USMM data before you approach SAP with a rationalisation proposal. This is your evidence.

Mistake 5: Accepting SAP's List Price Without Negotiation

Package optimisation creates negotiating leverage. You are offering to simplify SAP's audit position by right-sizing your own entitlements. In exchange, ask for price concessions—volume discounts, annual prepay discounts, or maintenance rate reductions. Do not settle for a simple right-sizing without commercial benefit.

Mistake 6: Failing to Update the Order Form Amendment

Verbal agreement with your Account Executive is not enough. If your package optimisation is not recorded in a formal Order Form amendment, it will not hold up in an audit. Get it in writing.

Building a Continuous Package Optimisation Cycle

SAP package optimisation is not a one-time project. Your usage changes, business priorities shift, and new packages may be introduced. We recommend an annual review cycle:

  • Q1: Extract 12-month USMM data and build current utilisation report
  • Q2: Analyse rationalisation opportunities and prepare business case
  • Q3: Approach SAP with optimisation proposal and negotiate
  • Q4: Implement changes and document in Order Form amendment

This rhythm ensures you are always operating from current data and capturing optimisation opportunities as they emerge.