SAP licenses - always a reason to argue?

Some license ambiguities are cleared up with S/4 Hana at the latest. Not until you opt for the "S/4 Hana Only" license model, but still. But what does this "Only" mean?

In the course of the disagreements between SAP and various database manufacturers, SAP has had to deal specifically with the issue of reimbursement for database usage outside the intended standard.

The issue of third-party licenses has arisen specifically in this context. Thanks in part to DSAG, SAP has backed down considerably on this issue in recent months.

However, should one decide to use only the Hana database and undergo a contract change in the process, then this topic becomes almost obsolete. A legal basis is still difficult to classify, but SAP is happy to suspend this topic for most customers.

Only almost, of course. Because the new digital access licenses remain a major topic. These finally tangible guidelines for indirect use are also primarily thanks to the efforts of the DSAG.

Now the definitions of indirect usage can be defined much more precisely. Currently, twelve transaction data (e.g. FI posting lines, order lines, purchase order lines, etc.) have been defined, the origin of which - unless created by licensed SAP users - is to be covered by digital access licensing.

But beware: Here, too, the devil is in the details. For example, current license models such as "Sales Order Process" cannot be mixed with the new Digital Access license type. It is advisable to arrange a consultation with the SAP partner in order to make the right decision.

The assignment of business processes to categories such as "Professional Use" or "Functional Use" represents a further simplification in the licenses. The previous classification of Professional User and Limited User often led to problems during measurements.

But now it is clearly defined which business process can be displayed with which user. But here, too, you only get to enjoy the benefits when you change contracts.

And it is precisely this change of contract that poses the danger. Because with this change, you give up your previous license claims and thus also partially give up usage agreements for functions that are no longer possible in the new license model.

However, many of the young key account managers at SAP no longer know these conditions - and this is where the disputes between the customer and SAP often begin. That is why it is always advisable to first take a look at the existing contract structure and compare the functionalities used.

Especially topics like SRM and CRM can stand in the way of a contract change. It is always advisable to work out the exact roadmap for the next few years - and to combine the license negotiations with the change of solutions.

As long as you're still moving on old contracts, it's ultimately always a dialog that you can have here in many respects. With SAP, with your partner, and also with DSAG. Then solutions can always be found without barricades.

The topic of the cloud remains a complex area. It is still difficult for SAP partners to estimate the costs of planned scenarios in advance. This is because the interaction between cloud solutions, the SAP Cloud Platform and SAP Cloud Integration is what rounds off the correct price spectrum.

Particular care should be taken when integrating third-party scenarios into the cloud concept. Here again, it is important to ask exactly in which scenarios the topic of "digital access" becomes important, even into the ERP. Unfortunately, the only option here is to go through SAP or an SAP partner.

That's why it's not necessarily advisable here to take a look at the price list and get discouraged. Define requirements and approach SAP and partners openly.