The short version of the SAP Cloud ERP licensing transition - one topic per block. Plus a practical guide to why continuous license monitoring matters beyond the initial cleanup.
SAP Cloud ERP uses PUPM (Per User Per Month) licensing - each user's cost is determined by the Business Catalogs assigned to their role. What you assign locks in cost for the duration of your contract.
FUE multipliers are gone. In PUPM each user carries a named license: Finance Base/Premium, SCM Base/Premium, Operational, Self-Service, or Developer. The Business Catalogs assigned to their role determine which one. The math is no longer yours.
Highest type wins. One Concur catalog added to a Self-Service role promotes the user to Finance Premium. Across 50 people that is €33,000 more per year, for a feature most of them barely touch.
PUPM contracts run 3–5 years. Adding licenses mid-term is allowed. Reducing them is not. Cuts happen only at renewal. You have one window to right-size before the meter starts.
Everything you need to understand how PUPM pricing works in SAP Cloud ERP - and where it gets expensive without visibility.
PUPM replaces FUE multipliers with named license packages: Finance Base / Finance Premium (covers Ariba, Concur, Sustainability), SCM Base / SCM Premium (planning, logistics), Combo Base (Finance + SCM merged), Operational (purchasing, sales, customer service), Self-Service (cheapest, for leave requests and timesheets), and Developer (ABAP, SAP Build). Each Business Catalog maps to one of these levels. Premium tiers nest Base: buying Premium includes everything in Base for that domain.
A user inherits the highest license type among all catalogs assigned to their role. SAP IAM measures this automatically. One Concur catalog added "just in case" can promote an Accounts Payable accountant from Finance Base to Finance Premium, and if that role is widely assigned, the cost multiplies across an entire team. There is no proration: you pay full Premium even if 90% of usage stays within Base. Role mapping becomes the real cost driver.
Take 50 employees who use Concur only for travel expense reporting. Classified as Self-Service: 50 x €5/month = €250/month. Re-classified as Finance Premium because of one Concur catalog: 50 x €60/month = €3,000/month. That is a €2,750 monthly delta, or over €33,000 per year, caused by a single "x" in the role-mapping matrix. This is the highest-type-wins rule in numbers, and the reason catalog-level usage data matters before any role goes live.
SAP enforces commercial floors. Finance Base or Premium requires 25 users minimum as an entry point. Buying any other Base SKU (e.g., SCM Base) requires at least 1 Finance Base alongside it. Finance Premium removes the Base minimum, but Premium pricing still applies to every Premium user. A company starting with the purchasing module alone still has to buy 1 Finance Base + 25 Base/Premium users, even if fewer staff actually need them. Plan licensing against minimums, not headcount.
PUPM bundles in features that previously required separate licenses. Base includes Multi-Bank Connectivity, Market Rates, Digital Access, Build Base. Premium adds Ariba, Concur, Sales Cloud, Project Management, Sustainability. This simplifies procurement, but creates a trap: bundled features look "free", so companies hand them out via roles without thinking about cost. Every Premium-only feature you assign elevates user types under highest-type-wins. Bundled does not mean cost-neutral.
Once you sign PUPM, the contract runs 3–5 years, and reducing license volume is only possible at renewal. Additions mid-contract are allowed, cuts are not. Use the transition window to map actual usage per user and per Business Catalog. A continuous monitoring tool (SAP GRC, SAP IAG, SmartGRC, or GRC Aura) is what separates paying for what you use from paying for what you once assigned.
License usage changes every month. People change roles, projects end, processes get automated. A one-time cleanup is a snapshot. GRC Aura is the ongoing signal.
Even if you've already signed a 3-year FUE or PUPM contract, new employees still require additional licenses - and you still choose what tier to assign. Without data, the default is "give them everything, just in case." With GRC Aura, you see what users in the same role actually open. You assign the right tier on day one instead of discovering 18 months later they never needed Premium.
Someone used an Advanced feature heavily during a project that finished 6 months ago. The role is still assigned. The license is still charged. SAP has no mechanism to alert you when access becomes unused - that's not their business model. GRC Aura tracks usage on a timeline, so you see exactly when the last activity happened per user, per role, and per Business Catalog.
One-time cleanup at migration or renewal - identifies immediate savings before you sign.
Ongoing signal - catches new hires over-licensed, detects usage that stopped, flags role drift before the next renewal window.
Not just at renewal. Every month.
Connect GRC Aura to your SAP Cloud ERP tenant - 3-4 days setup, read-only access, first savings visible on day one.
English
Deutsch
Svenska
Français
Polski
Magyar
Italiano
Español