
SAP indirect access can occur when people or automated systems interact with SAP ERP through another application. The 2017 SAP v. Diageo judgment shows why that interaction can affect licensing. For a new integration, the starting point is your agreement and what the integration actually does.
What the Diageo Judgment Decided
In SAP UK Ltd v Diageo Great Britain Ltd [2017] EWHC 189 (TCC), the court found that usage through two Salesforce-based applications, Connect and Gen2, was unauthorized under the parties’ mySAP ERP agreement. The court held that SAP was entitled to additional license and maintenance fees. The judgment left the amount for later assessment if the parties could not agree. Read the judgment.
How SAP Digital Access Fits In
The Diageo judgment interpreted a particular named-user agreement. SAP now also describes a document-based Digital Access model. Under that model, qualifying document items created in SAP through non-SAP intermediaries are counted across nine document types. The terms that apply to your organization depend on your SAP products and signed agreements. Read SAP’s Digital Access overview.
What to Review Before Connecting a Third-Party System
- Map the integration. Identify the application, users or automated processes, and the SAP system they interact with.
- Trace the activity. Record whether the integration reads, creates, updates, or deletes records. Identify the SAP documents it creates and the expected volumes.
- Check the contract. Have your licensing team review the signed agreement, order forms, and amendments for the systems and activities in scope.
- Include licensing in the business case. Compare expected licensing, implementation, and operating costs alongside the benefits of the integration.
Try It in Our Live SAP S/4HANA System
Use SAP GUI or Fiori to practice with sample data. Here are three ways to get started.
- Post a sample journal entry.
- Trace the accounting entries behind a goods movement.
- Explore a Controlling app in SAP Fiori.
