SAP licence management is the practice of knowing what SAP software an organisation is entitled to use, how that compares with how it is actually used, and what that costs now and at renewal. It sits between procurement, IT and finance, which is often why nobody owns it completely.
For most large South African enterprises, SAP is one of the largest software contracts on the books. It is also one of the hardest to read, because the position is spread across a master agreement, years of order forms and amendments, and measurement data that lives inside the SAP systems themselves.
What does an SAP licence position consist of?
- Users. In classic ECC contracts, named-user types such as Professional, Limited Professional and Employee. In RISE with SAP and S/4HANA Cloud, Full Use Equivalents (FUEs). See how FUE licensing works.
- Engines and packages. Functionality licensed on a business metric such as revenue, employees or orders, rather than per user.
- Indirect use. Documents created in SAP by other systems, licensed through Digital Access or older indirect-use terms.
- Maintenance and support. Usually a percentage of the licence value, paid every year and rising with every addition.
- Obligations. Renewal windows, ramps, price holds and conversion credits written into order forms.
Why does SAP licence management matter?
Three reasons come up in almost every estate we review:
- Overspend. Users classified at expensive types who only read reports, engines sized for growth that never came, and maintenance paid on licences nobody uses.
- Audit exposure. SAP asks most customers to run an annual system measurement. Classification errors and unlicensed indirect use found there become commercial conversations on SAP's terms.
- Transition decisions. The move to S/4HANA or RISE with SAP converts your existing position into a new contract. If the starting position is wrong, the new contract inherits the error.
Licence management, SAM tools and audits compared
| Focus | Typical owner | Limitation | |
|---|---|---|---|
| SAM tool | Installed software and usage data | IT asset management | Rarely holds contract terms |
| Licence audit | Compliance on the publisher's terms | SAP | Looks backward, sets the agenda for you |
| Licence governance | Entitlement, use, cost and obligations together | CIO and CFO, with an advisor | Needs disciplined evidence collection |
What does good SAP licence governance look like?
Every figure about SAP that reaches an executive can be traced to a signed document or a measurement from your own system. Exposure is stated as a range, because licence questions rarely have a single answer. Findings are kept separate from recommendations. And there is a register of every document requested from SAP or your implementation partner, so "they confirmed it on a call" never stands in for the agreement itself.
That is the standard our SAP licence management and governance service runs on.
The short version
SAP licence management is not a tool or a one-off audit. It is a standing, evidenced view of entitlement, use, cost and commitments, kept current enough to be useful before every renewal, measurement and negotiation.
Common questions
What is SAP licence management?
SAP licence management is the practice of knowing what SAP software an organisation is entitled to use, how that compares with actual use, and what it costs now and at renewal. It covers users, engines, indirect use, maintenance and contractual obligations.
Who should own SAP licence management?
It usually spans IT, procurement and finance. The most effective model has one accountable owner, often in the CIO or CFO office, supported by an independent advisor and the SAP centre of excellence.
How often should an SAP licence position be reviewed?
At least once a year before the annual system measurement, and again ahead of every renewal, major rollout or move to S/4HANA or RISE with SAP.