SAP UK v Diageo – an important ruling for customers with indirect access issues

Published on

Late last week, a UK court ruled in favor of SAP in the case of SAP UK v Diageo. This is a rare occasion where SAP has chosen to take its efforts to secure license fees for what is commonly termed ‘indirect access’ through the legal system. I spent the weekend digesting the text of the ruling, which I found remarkably lucid and devoid of mind numbing legalese.

In the analysis that follows, I will avoid much of the technical detail, sticking to a relatively simple way to explain the problem and what the judge in this case determined.

How does indirect access arise?

The ‘indirect access’ issue has been a running sore among SAP customers for some years. Essentially it boils down to this: SAP wants paying additional license fees where a third party system accesses data generated by SAP systems. This normally happens through a machine-to-machine interface but will likely mean that users who are not licensed by SAP on the originating system get access to data generated by the SAP system, albeit inside the third party system. To that extent, those additional users are not necessarily aware that they are accessing SAP data.

Diageo represents a fairly typical case where SAP systems generate data that is subsequently fed into Salesforce systems for the purpose of self service by customers rather than routing via SAP systems to Diageo call center agents.

In order to win, SAP had to show that the terms and conditions of the contract with Diageo contained language which allows SAP to make an additional charge. The judge ruled that is the case. Diageo for its part argued that the manner in which the data was transferred to Salesforce meant that the SAP enabling technology was acting as a ‘gatekeeper’ for the data rather than providing a means to access the data by additional users.

To read more, please click here

Source: diginomica

Our User Group Community

8 hours ago

If you missed it last week, the second part of @chairmanb's #licensing blog post is now live! The post focusses on……