Licensing
SAP licensing determines what you are entitled to use and what you pay, and it is notoriously complex. A working understanding helps you avoid compliance surprises and design cost-aware solutions.
Even non-commercial roles should understand licensing, because how you design integrations and user access can create unexpected (and expensive) licence consumption, especially indirect/digital access.
- Traditional on-premise licensing is a capital purchase plus annual maintenance.
- Named users: licences per person, by user type (professional, functional, employee, developer), each with different rights and cost.
- Engines / package licences: for specific functionality measured by a metric (e.g. documents, revenue, orders).
- Watch out: Ignoring indirect/digital access, a common source of compliance cost.
The main licensing dimensions
- Named users: licences per person, by user type (professional, functional, employee, developer), each with different rights and cost.
- Engines / package licences: for specific functionality measured by a metric (e.g. documents, revenue, orders).
- Indirect / digital access: usage of SAP data by third-party or automated systems, a major area of attention.
On-premise versus cloud/subscription
Traditional on-premise licensing is a capital purchase plus annual maintenance. Cloud and RISE move to subscription: you pay ongoing for capacity and users, with infrastructure and upgrades included. The metrics and audit dynamics differ significantly.
Why it matters to practitioners
Even non-commercial roles should understand licensing, because how you design integrations and user access can create unexpected (and expensive) licence consumption, especially indirect/digital access. License-aware design is a real skill.
Common pitfalls
- Ignoring indirect/digital access, a common source of compliance cost.
- Assuming all users need the top licence type, right-size by role.
- Treating licensing as someone else’s problem, design choices affect it.