- SAP has strict audit practices, which, in combination with 50+ types of user classifications and manual accounting for some licenses, make maintaining compliance difficult.
- Mapping and matching SAP products to the environment can be highly complex, leading to overspending and an inability to reduce spend later.
- Beware of indirect access to SAP applications from third-party applications (e.g. Salesforce).
- Products that have been acquired by SAP may have altered licensing terms that are innocuously referred to in support renewal documents.
- Focus on needs first. Conduct a thorough requirements assessment and document the results. Well-documented license needs will be your core asset in navigating SAP licensing and negotiating your agreement.
- Examine indirect access possibilities. Understanding how in-house or third-party applications may be accessing the SAP software is critical.
- Know what’s in the contract. Each customer agreement is different and there may be terms that are beneficial. Older agreements may provide both benefits and challenges when evaluating your SAP license position.
Impact and Result
- Conduct an analysis to remove inactive and duplicate users as multiple logins may exist and could end up costing the organization license fees when audited.
- Adopt a cyclical approach to reviewing your SAP licensing and create a reference document to track your software needs, planned licensing, and purchase negotiation points.
- Learn the “SAP way” of conducting business, which includes a best-in-class sales structure, unique contracts and license use policies, and a hyper-aggressive compliance function. Conducting business with SAP is not typical compared to other vendors, and you will need different tools to emerge successfully from a commercial transaction.
- Manage SAP support and maintenance spend and policies. Once an agreement has been signed, it can be very difficult to decrease spend, as SAP will reprice products if support is dropped.
This guided implementation is an eleven call advisory process.
Guided Implementation #1 - Establish licensing requirements
Call #1 - Engage in a scoping call
Call #2 - Assess the current state
Call #3 - Determine licensing position
Guided Implementation #2 - Evaluate licensing options
Call #1 - Review product options
Call #2 - Review licensing rules
Guided Implementation #3 - Evaluate agreement options
Call #1 - Review contract option types
Call #2 - Review vendors
Guided Implementation #4 - Purchase and manage licenses
Call #1 - Determine negotiation points
Call #2 - Finalize the contract
Call #3 - Discuss license management
Call #4 - Evaluate and develop a roadmap for future licensing
After each Info-Tech experience, we ask our members to quantify the real time savings, monetary impact, and project improvements our research helped them achieve. See our top member experiences for this Blueprint, and what our clients have to say.