Published: 31 July 2014
Summary
SAP is approaching an increasing number of customers for significant, unbudgeted license fees related to indirect use. SAP software professionals should carefully validate those indirect use claims and the value received from them to mitigate costs.
Included in Full Research
- Common Triggers for Discussions About Indirect Use
- Maintain Older or Vague Indirect Use Clauses From Earlier SAP Contracts to Improve Your Negotiating Position
- SAP Indirect Use Interpretations Have Evolved Over the Years
- Do Not Accept SAP System Measurement Guide Definitions as Contractually Binding
- 2. Infrequent (Daily, Hourly) Batch Data Transfers Should Not Be Charged
- 3. Real-Time, Synchronous and Bidirectional Use of SAP Software Can Be Charged
- 4. Indirect Users Should Be Identifiable Users, Not Devices
- 5. Multiplexing Front-End Applications Built for the Express Purpose of License Fee Avoidance Should Not Be Acceptable to Either Party, and Does Constitute Indirect Use
- Use SAP Solution and Enterprise Architects to Categorize the Type of Integration to SAP, and the Relative Value Derived, to Reduce Indirect Fees
- Negotiate Lower-Priced User Categories or Alternative Pricing Metrics With SAP for Lower-Value Indirect User Scenarios