...it already begins when the contract's content and its structure are planned. What must be defined is not only the contractual framework when the contract is concluded; one must also take into account what could happen in future years, with regard to software care and maintenance.
Set in stone: save resources in SAP license and authorization management. [Shutterstock: 229664911, Inked Pixels]
The fear of security gaps and data leaks is costing more and more IT personnel their sleep at night. Sensitive corporate data needs to be protected by using sophisticated authorisation concepts. Peter Rattey from Voquz sums up the 10 commandments for SAP License & Authorization Management to save you time and money.
Indirect access licenses: How to make something complicated even more complicated [shutterstock: 296778314, zimmytws]
In the last several months, much has been written about “indirect access”. What does this mean and which licenses should SAP customers be purchasing? Even SAP has not exactly provided clarity, but rather has increased the confusion by making amendments to the description of the “SAP NetWeaver Foundation for Third Party Applications” in the Pricing and Conditions List (PCL) 2016/2.
At Sapphire recently, SAP claimed that more than 3200 customers had moved to S/4 Hana, and painted a “simple” roadmap for customers making the move.
Indirect use is currently the spectre haunting all established SAP customers. Is a menacing follow-up licencing requirement in prospect? No – by the very nature of things it is not: many a threat is much less frightening than it first appears to be. There is just no proof to reinforce the fear – and this is also how DSAG, the application-usersꞌ association, views this subject.