Question 1

What is SAP indirect access and why is it such a big deal?

Accepted Answer

Indirect access is when non-SAP-licensed users, systems, or bots access SAP data through third-party applications, integrations, or APIs. Historically, SAP licensed every indirect user as a named user — leading to enterprise findings in the tens or hundreds of millions when third-party CRMs, e-commerce platforms, or bots touched SAP data. The Diginet / Indeed-style cases publicized the exposure and forced SAP to introduce the Digital Access model.

Question 2

What is SAP Digital Access and how is it priced?

Accepted Answer

Digital Access licenses indirect use by the volume of documents created in SAP via non-SAP systems — sales documents, purchase documents, invoices, material documents, time-management documents, service documents, financial documents, and quality documents. It replaces named-user counting for indirect access. The model can be lower or higher cost than legacy named-user counting depending on document volume — modeling is essential before adopting it.

Question 3

Should we move to RISE with SAP?

Accepted Answer

RISE with SAP bundles S/4HANA Cloud, infrastructure, and managed services into a subscription. It simplifies procurement but moves you to a subscription cost curve, changes contract terms (especially around exit and data portability), and removes many of the negotiation levers customers have under traditional licensing. Model RISE versus on-prem S/4HANA over a 7–10 year horizon, not the 3-year window SAP typically presents.

Question 4

How is S/4HANA licensed versus ECC?

Accepted Answer

S/4HANA introduces new named-user categories (Advanced Use, Core Use, Self-Service Use) and 'Use Authorizations' that differ from ECC's Professional/Limited Professional/Employee user types. The conversion from ECC to S/4HANA license categories is not 1:1 and is one of the most consequential negotiations of an S/4HANA migration. SAP's default conversion proposals are rarely the customer's best outcome.

Question 5

What are SAP named user types and which one do we actually need?

Accepted Answer

SAP's classic named user types include Professional, Limited Professional, Employee, Developer, and various role-specific categories. Most enterprises over-license Professional users because the role-mapping was never refined. A user-classification exercise frequently reduces named-user costs by 20%+ before any negotiation.

Question 6

Will SAP audit us?

Accepted Answer

Yes — SAP runs annual License Audits (LAW reports) on most enterprise customers, with deeper engagements on a rolling cycle. Common findings include indirect access exposure, mis-classified named users, unauthorized use of engines and packages, and S/4HANA conversion gaps. Audit responses determine whether findings convert to large back-license charges or are negotiated down.

Question 7

Can we drop SAP support to save money?

Accepted Answer

SAP Standard Support and Enterprise Support carry mandatory annual maintenance fees on perpetual licenses. Dropping support is operationally possible but ends patches, legal/regulatory updates, and SAP support. Third-party SAP support providers (Rimini Street, Spinnaker) offer alternatives at roughly half the cost, with the same trade-offs as third-party Oracle support.

Question 8

What counts as indirect access?

Accepted Answer

Any access to SAP data, processes, or functionality through a non-SAP system, third-party application, integration platform, bot, or API. Common indirect-access scenarios include third-party CRM systems reading customer data, e-commerce platforms creating orders, RPA bots executing transactions, and integration middleware (MuleSoft, Boomi, others) pushing data into SAP.

Question 9

What are the nine SAP Digital Access document types?

Accepted Answer

Sales documents, purchase documents, invoice documents, material documents, time-management documents, service & maintenance documents, financial documents, and quality-management documents (typically grouped into a set referenced as nine document categories in SAP's published model). Each created document counts toward the Digital Access entitlement.

Question 10

Can we measure our Digital Access exposure before SAP does?

Accepted Answer

Yes. SAP provides the Digital Access Estimation Note and tools that count qualifying documents created via indirect interfaces. Running an independent measurement before SAP raises the topic is critical — it gives you a baseline, a negotiating position, and time to remediate before exposure is formally documented.

Question 11

How does the ECC-to-S/4HANA license conversion actually work?

Accepted Answer

SAP offers Contract Conversion and Product Conversion paths from ECC to S/4HANA. Conversion translates existing entitlements into new S/4HANA categories using SAP's ratios, with optional credit for existing investment. The translation is rarely neutral — most default conversions favor SAP's commercial outcome. Independent modeling of both paths is essential.

Question 12

What is SAP S/4HANA Cloud Private Edition versus Public Edition?

Accepted Answer

Private Edition is a single-tenant cloud deployment with greater customization, run by SAP under RISE. Public Edition is multi-tenant SaaS with standardized processes and faster release cadence. Licensing, customization rights, contract terms, and migration paths differ materially — the choice should be driven by business fit, not by SAP's preferred sales motion.

Question 13

Will switching to RISE affect our existing custom code and integrations?

Accepted Answer

Yes. Moving to RISE — especially Public Edition — constrains custom code, BAdI usage, and certain integration patterns. Existing customizations may need clean-core refactoring. Plan the technical assessment in parallel with the commercial assessment; the two often invalidate each other if done separately.

Question 14

How are SAP Professional Users counted?

Accepted Answer

Each named individual requiring Professional access requires one Professional User license, regardless of how often they log in. Generic IDs, service accounts, and shared logins create their own counting questions — and audit findings.

Question 15

What are SAP engines and packages and why do they matter?

Accepted Answer

Engines (e.g., Payroll, BW, PI/PO, certain industry solutions) are licensed separately from named users, often by metric (employees paid, GB processed, document volume). Audit findings frequently surface engines that were deployed during a project and never licensed, or where usage grew past the contracted metric.

Question 16

Do contractors and consultants count as SAP users?

Accepted Answer

Yes, if they have named access to SAP systems. The classification (Professional, Limited Professional, Employee) depends on their actual use. Many enterprises mis-classify external users at the highest tier 'to be safe', overpaying significantly.

Question 17

What is included in RISE with SAP?

Accepted Answer

S/4HANA Cloud (Private or Public Edition), infrastructure (hyperscaler-hosted), SAP Business Technology Platform credits, technical managed services, and tools for transformation. The exact composition varies by deal — what is bundled vs sold separately is a key negotiation point.

Question 18

What happens to our existing SAP licenses if we move to RISE?

Accepted Answer

Existing perpetual entitlements are typically credited into the RISE subscription via SAP's conversion ratios. The credit is rarely full and is one of the levers most worth negotiating. Walking into RISE without quantifying the credit you are giving up is a multi-million-dollar mistake.

Question 19

Can we exit RISE if it doesn't work out?

Accepted Answer

Exit options depend entirely on contract terms. Standard RISE contracts typically include term commitments, exit assistance, and data extraction provisions — but the defaults often favor SAP. Negotiate exit, data portability, and run-out support before signing, not after.

Question 20

What is the SAP LAW report?

Accepted Answer

License Administration Workbench (LAW) is the SAP tool used to consolidate USMM measurement results across systems into the annual report required by most SAP contracts. Submission frequency and contents are contractual — but how the report is prepared and what supporting analysis accompanies it is largely customer-controlled.

Question 21

Should we run USMM and submit LAW exactly as SAP requests?

Accepted Answer

Submission is contractual — but the underlying user classification, engine reporting, and digital access counting should be reviewed and validated before submission. Most over-licensing and most under-licensing both originate in unconsidered LAW submissions.

Question 22

What if SAP claims a large indirect access exposure?

Accepted Answer

Do not accept the initial number. SAP's first indirect access findings are routinely based on broad assumptions about non-SAP system interaction. Independent analysis of actual document creation, integration patterns, and user behavior frequently reduces the claim by 70%+ — and often replaces it with a smaller Digital Access subscription that is operationally cleaner.

Question 23

When is SAP's fiscal year end?

Accepted Answer

SAP's fiscal year ends December 31, with quarter ends March 31, June 30, and September 30. Like most enterprise vendors, SAP discount and concession behavior is materially stronger at quarter and year end — especially Q4.

Question 24

Can we negotiate down SAP maintenance fees?

Accepted Answer

Maintenance percentages are largely standardized, but the base on which they are calculated is negotiable through shelfware retirement, license restructuring, and credits at major events (S/4HANA conversion, RISE adoption). Reductions of 10–25% are achievable in the right deal structures.

Question 25

What SAP contract clauses should we always negotiate?

Accepted Answer

Watch for: indirect/digital access carve-outs, named-user reclassification rights, M&A coverage, exit and data portability terms (especially under RISE), price-protection across the term, audit scope and notice, and any 'as updated' references that allow SAP to change underlying terms.

SAP licensing questions, answered straight.

Jump to a topic

Questions people actually ask about SAP licensing

Indirect access and Digital Access

S/4HANA migration and conversions

Named users and engines/packages

RISE with SAP and cloud commitments

SAP audits and LAW reporting

Contracts, maintenance, and negotiation

Go deeper on SAP licensing

Have an SAP licensing question this FAQ doesn't answer?