Xpandion Blog

  • Home
    Blog Home This is where you can find all the blog posts throughout the site.
  • Tags
    Tags Displays a list of tags that have been used in the blog.

10 Ways to Make Your Upcoming SAP Licensing Audit Easier

Posted by in Licensing & SAM
  • Font size: Larger Smaller
  • Hits: 7719
  • Print

Tis’ The Season. SAP Licensing Audit Season, that is.

b2ap3 thumbnail iStock 000023629996XSmall


As things in the office are heating up in anticipation of the imminent 2013 year-end SAP Licensing Audit, many hard decisions lay ahead for Licensing Managers and CIOs, like reconciling all users and their corresponding licensing types, reassessing and evaluating the status-quo of licenses, and reallocating numerous licenses. 



Use this handy checklist to make this excruciating process easier:

1. Start preparing now. Create a schedule containing all of your specific, attainable milestones. Tell your manager that much of your time and attention will need to be allocated for the upcoming audit. Pace yourself so you are set for your final deadline.

2. Do your homework. Find out your any rules your organization might have implemented in previous SAP audits. What worked, and what didn’t? Use this information to give yourself a leg up for your current audit.

3. Apply the Pareto principle.For large organizations running several SAP systems, use the 80–20 rule to determine which applications should be thoroughly inspected, scanned briefly or ignored completely. Due to overlap, you might just find that you have fewer systems to inspect than you thought.

4. Gather all the data. Don’t ignore certain users and/or license types. For instance, even though various user types, like “Communication” and “System” might not sound critical, usually such license types are for remote connections and should not be disregarded or mistakenly overlooked in the final report. 

5. Select a method for combining usernames. Unless your contract specifies otherwise, the SAP licensing model permits employees to hold several usernames within the organizational SAP systems, so it’s important to combine varying usernames and link them to the specific employee. For example, combine “JOHNS” in the ERP system and “JOHNSM” in the CRM system – linking both usernames to the employee John Smith who works in Finance. This can be a complicated and tedious task, which inevitably leaves a huge margin of error. Best to manage this process via automated software. 

6. Classify users by the right licensing type. If you think that SAP’s detailed instructions on how to produce an audit report is sufficient, think again. SAP indeed describes how to create the report, but classifying users to the right licensing type – the essence of licensing costs – is not addressed in the instructions from SAP. 

7. Never classify users to license types according to their granted authorizations. If you do this, you are classifying them based on responsibilities rather than de-facto usage. Most employees do not use all functions granted to them. In fact, on average they utilize only 7% of their granted authorizations!

8. Analyze a sufficient amount of data. Examine three month’s worth of data at minimum. The more data you analyze, the more accurate your conclusions will be. In most cases the recommended period for analysis is one year.

9. Analyze user activity. Several users and activities, such as SAP*, DDIC and EARLYWATCH, are preconfigured by SAP and should not go into your tally. If you do not pay attention, you are taking into account avoidable users! Consider classifying these preconfigured users as license type “Test” to avoid counting them unnecessarily. 

10. Remember the engines. SAP licensing is based on license-per-user, as well as software engines. Payment for software engines is calculated according to usage; assess which engines are really being used to ensure that your company is paying for only the necessary ones.


For a complete list of useful tips for your SAP Licensing Audit,

Dror Aviv joined Xpandion in 2010 as a programmer in the R&D team. Combining technical knowledge with implementation skills, Mr. Aviv serves today as a Senior Implementation Advisor, bringing with him extensive hands-on experience from the field. He works closely with customers at their sites, and is an expert in defining customer needs, translating them into business process and implementing them via ProfileTailor Dynamics’ suite of products.


  • No comments made yet. Be the first to submit a comment

Leave your comment

Guest 21/07/2017


in XpandionPosted by Yoav Michaeli

Pay (Only) As You Use

Pay (only) as you use – innovative approach? Indeed (although we have already recommended a similar approach in SAP licensing by concurrent users, suggesting that companies pay only for the licenses they really need). I am a big believer in SAP® and also in methods that enable enterprises to be...
in XpandionPosted by Yoav Michaeli

Optimize Licensing Costs. Increase Security

These are amongst some of the most worrying words that enterprises and managers can hear.  And, yet, they are a part of day to day terminology- whether whispered behind  soundproof board room doors, discussed openly by upper management or colleagues addressing them casually over the wate...
in XpandionPosted by Moshe Panzer

Xpandion and the Cloud: Compliance in Loosely-Connected Environments

For the last couple of years, the cloud has proven to be both an obstacle and an opportunity for enterprises. Even the largest Fortune 500 Companies who like to have their data on their own servers can't ignore the cloud anymore and are forced to create a policy for using it. Even if they aren't m...
in XpandionPosted by Yoav Michaeli

Do You Understand the Meaning of Behavior-Based Profiling?

Xpandion creates “behavior-based profiling” for business applications. Sounds impressive, huh? However, do you know what it means, exactly?

in Security & AuthorizationsPosted by Dror Aviv

When SAP® users get sleepy

“Dormant” SAP usersSome licensing-optimization tools for SAP, including ProfileTailor LicenseAuditor claim that they can identify “dormant user accounts”. Some customers don’t understand what this means and say – we identify dormant user accounts by ourselves – just look at table ‘USR02’ and see the...



157 Yigal Alon Street,

Tel Aviv 67443, Israel


US Office


3310 W Braker Lane Suite 300-253

Austin, TX 78758, USA


India Office


C 103, Akruti Orchid Park, Andheri-Kurla Road,

Andheri East, Mumbai, India