Skip to content
IT Canvass
Menu
ServiceNow
SailPoint
SAP
TutorialsContact
Getting started · Lesson

Licensing

Quick answer

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.

Key takeaways

  • 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.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

See the courseAsk a question

Check your understanding

  1. Which statement is true of Licensing?

    • A. SAP PI/PO (Process Integration / Process Orchestration) is SAP’s classic on-premise integration middleware…
    • B. Cloud and RISE move to subscription: you pay ongoing for capacity and users, with infrastructure and upgrades…
    • C. Vendor management in MM concerns the vendor master data, now the Business Partner in S/4HANA, that…
    Show answer

    B. Cloud and RISE move to subscription: you pay ongoing for capacity and users, with infrastructure and upgrades…

    Covered in the “On-premise versus cloud/subscription” section of this lesson.

  2. Which of these also applies to Licensing?

    • A. Confusing company code with company or plant.
    • B. The metrics and audit dynamics differ significantly.
    • C. Uncertified Linux distribution/version.
    Show answer

    B. The metrics and audit dynamics differ significantly.

    Covered in the “On-premise versus cloud/subscription” section of this lesson.

  3. Which part of the Learn SAP curriculum covers Licensing?

    • A. Getting started
    • B. SAP ABAP development
    • C. SAP downloads
    Show answer

    A. Getting started

    This lesson sits in the Getting started section of the Learn SAP course.

Frequently asked questions

What does the term Licensing refer to in SAP?

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.

What else is worth knowing about Licensing?

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.

What is the practical takeaway on Licensing?

Traditional on-premise licensing is a capital purchase plus annual maintenance.

What tends to go wrong with Licensing?

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.
CallWhatsAppEnquire